What Does a Web Design Agency Actually Do?

A web design agency does far more than design. On a typical Philippine project the visual design is perhaps a fifth of the work, and the parts clients rarely see, discovery, content structure, build, testing, launch, and handover, are where projects succeed or fail.

Understanding what an agency actually does is useful for two reasons. It tells you what you are paying for, and it tells you which parts you can reasonably do yourself.

What are the stages of a website project?

Skipping stages does not save money. It moves the cost, usually into rework, and occasionally into a rebuild eighteen months later when the shortcuts have compounded.

What happens during discovery?

Discovery establishes what the site is for. Not the design, the job.

A competent agency will ask who the site is for, what you want a visitor to do, how enquiries reach you today, what happens after someone gets in touch, which pages carry the business, and what has failed before. They should ask about the awkward parts too: which services you actually want more of, and which you would rather stop selling.

What you should receive is a written scope stating what is included and what is not. If it is verbal, it is not a scope, and it will be remembered differently by both sides in month three.

A frequent client mistake here is arriving with a design in mind rather than a problem. Saying "we want a site like this one" gives the agency a reference but not a brief, and a project built on a reference will look right and perform unpredictably.

Who writes the content?

This is the single largest cause of delay on Philippine website projects, and it is worth deciding explicitly at the start.

Three common arrangements:

You write it. Cheapest, and frequently the reason a project sits idle for two months. Businesses consistently underestimate how long writing thirty pages takes when nobody's job it is.

The agency writes it. Faster and more consistent, but it costs more and needs your input to be accurate. An agency cannot invent your service details or pricing.

Shared. You supply raw material and the agency shapes it. This is usually the best balance, and it should be stated in the scope rather than assumed.

Photography follows the same pattern and causes the same delays. Most businesses believe they have usable images and discover they have phone snapshots taken for social media.

What does the design stage actually produce?

Screens you can click through, agreed before anyone writes production code.

The point is to make decisions cheap. Moving a section in design takes minutes; moving it after the build takes days. This is where you should be most opinionated, and where "that is not how our customers think about it" is the most valuable sentence you can say.

What you should expect: key pages designed rather than every page, mobile considered alongside desktop rather than as an afterthought, and a consistent system of components rather than fifty bespoke layouts. What you should not expect is a finished site. Design is a plan, not a product.

What does the build stage involve?

Turning the design into a working site: templates, content management, forms, integrations, performance, and the things nobody notices unless they are missing, such as correct headings, sensible URLs, and pages that do not break at awkward screen sizes.

You should see progress in increments, typically every one to two weeks, on something you can open and click. Months of invisible progress is a warning sign regardless of the explanation offered.

This is also where integrations surface as real work. Connecting a booking system, a payment gateway, a CRM, or an email platform each involves someone else's rules and timelines. Payment gateway approval in particular runs on the provider's schedule, not the agency's.

What testing should happen before launch?

More than most clients realise, and it is worth asking specifically.

Real devices rather than only a desktop browser, since most Philippine traffic is mobile on mid-range phones. Forms tested end to end, including where submissions land and whether confirmation emails reach free email providers rather than a spam folder. Speed on mobile data, not office wifi. Broken link checks. Basic accessibility. And a check that analytics is recording before launch rather than a week after.

Ask the agency what their testing covers. A vague answer usually means the client is the testing.

What happens at launch, and what can go wrong?

Launch is a technical event with a few well-known failure modes.

Redirects. If URLs change, old links must point to new ones or you lose whatever search visibility you had. This is the most common and most damaging launch mistake.

DNS and email. Moving a domain can disrupt email if records are not carried across correctly.

Tracking. Analytics and any conversion tracking configured and verified.

Search Console. The new site submitted, with a sitemap.

A rollback plan. What happens if something is badly wrong an hour after go-live.

Launching immediately before a peak trading period is a decision to debug under pressure. Aim for a quieter week.

How long does a website project take?

Timelines are decided less by build complexity than by how fast the client side moves.

Two client-side factors move these more than anything the agency controls.

Who decides. If every question routes to a busy owner, the project runs at that person's calendar speed. Naming one decision-maker who can respond within about two working days does more for a timeline than adding people to the team.

When content arrives. Copy and photography are the most common reason a project sits idle. Starting that work during discovery rather than treating it as a pre-launch task is the single most effective protection for the date.

Be sceptical of unusually short quoted timelines. Usually something has been left out, and it is typically testing, content, or training, each of which reappears later as a problem rather than a saving.

What does an agency relationship look like after launch?

Most projects do not end at go-live, and it is worth agreeing what happens next before you need it.

Common arrangements are a fixed retainer covering hosting, updates, monitoring, and a set amount of change work; an hourly or ad hoc arrangement where you pay for what you use; or a clean handover where you take over entirely and the agency's involvement stops.

None is wrong, but the mismatch causes friction. A client assuming small changes are free and an agency assuming they are billable will fall out within two months. Ask specifically what counts as maintenance, what counts as new work, and what response time you can expect when something breaks.

What should handover include?

This is where clients are most often shortchanged, and it is entirely avoidable by asking in advance.

You should receive administrative access to the site, the domain, and the hosting, in your own accounts rather than the agency's. The code repository if the build is custom. Documentation of how to make routine changes. A short training session. And clarity on what happens next: what maintenance covers, response times, and cost.

The test of a good handover is simple: if the agency disappeared tomorrow, could another developer pick this up? The website handover checklist covers what should change hands, and how to read contract clauses that protect you covers the wording that makes ownership real.

What does an agency not do?

Worth stating plainly, because mismatched expectations here cause most disappointment.

An agency does not generate demand by launching a site. A new site does not rank immediately, and on a young domain it may not rank for months. An agency cannot write your service details or prices without you. It cannot make decisions you have not made about your own business. And it does not usually keep your content current after launch unless that is a service you bought.

If a proposal implies otherwise, particularly around traffic or rankings on a defined timeline, treat that as a claim to interrogate rather than a benefit.

Which parts could you do yourself?

Being honest about this saves money.

Realistically client-side: gathering content and photography, writing first-draft copy about your own services, providing access and credentials promptly, and making decisions quickly.

Realistically not: information architecture, responsive build quality, performance, accessibility, integrations, and launch mechanics. These are where DIY sites usually fail, and the failure is often invisible to the owner until traffic does not convert.

The middle ground, worth discussing openly, is content management after launch. Many Philippine businesses can maintain their own pages perfectly well if the site is built for it and someone is trained. Say so at the start, because a site built on the assumption that only the agency will ever edit it is built differently from one designed for a client to run.

The cost of doing the wrong parts yourself is rarely visible immediately. A site that looks acceptable but loads slowly, breaks on a mid-range phone, or has no working redirects will quietly underperform for years, and the owner usually attributes that to marketing rather than to the build.

How do you tell a good agency from a plausible one?

Ask what they would refuse to build. An agency that has never talked a client out of something is selling rather than advising, and the willingness to say "you do not need that" is one of the few signals that is hard to fake in a sales conversation.

Ask to see a live site they built and what was difficult about it. Ask who will actually do the work, since the person in the meeting is not always the person building. Ask what is excluded from the quote, because testing, content, training, and post-launch support are the usual omissions. And ask what happens if the project runs late.

Seven red flags when choosing a web design agency covers the warning signs, and how to choose between a freelance web designer and a design agency covers the wider comparison.

What should you do next?

Before approaching anyone, write one page: what the site must achieve, who it is for, what you want visitors to do, and what exists today that works or does not. That page shortens discovery, improves the quotes you receive, and tells you quickly whether an agency is listening.

For pricing context see what a website costs in the Philippines, and for what we do see web design agency Philippines. If you would rather talk it through, book a call.