Published
11 MIN READ
How to choose a web design agency
Choosing a web design agency means choosing who makes the decisions you won't be there to follow. A good-looking portfolio and testimonials don't separate a good vendor from a bad one, because everyone has both. What separates them is how they answer specific questions about scope, ownership, timeline and what happens after delivery.
This article lists the 15 questions that make that separation, with the answer you should hear for each one. They come from the inside, from people who write proposals and receive briefs every month. There's no list of agencies here, and that's on purpose: the goal is for you to be able to evaluate any vendor, including us.
What does a web design agency do?
A web design agency takes the project from understanding the business all the way to the published website. That includes discovery, page architecture, design, development, launch and handing the account over to the client. What varies enormously from vendor to vendor is how much of that chain they actually do themselves.
Many companies sold as agencies deliver a filled-in template. Others do the design but outsource development. Others do everything, but with four different people and an account management layer in the middle, which raises the cost and dilutes accountability. None of these models is wrong by nature. The mistake is hiring one while thinking it was another.
Freelancer, agency or website builder: which should you choose?
It depends on how closely your team can follow the project. A builder with a template works when the company is still figuring out its own positioning and wants something live fast. A freelancer works well for small, well-defined scope, with direct contact and lower cost. An agency or studio makes sense when the website is part of the sales pitch and someone has to answer for the result.
There's a fourth case almost nobody mentions: the company that already has a design team and only needs extra hands during a peak period. In that case you don't hire a fixed project, but rather for when a company only needs short-term support. Hiring an agency for that is expensive and creates friction with the in-house team.
The 15 questions to ask before signing
Ask all of them in writing, before any meeting. A serious vendor answers in one email. Whoever stalls on a simple question will stall on a hard problem. Next to each question is how we answer at Wama, so you have a concrete reference for what a complete answer looks like.
About who does the work
Who exactly will design my website? A name, not a job title. At Wama it's one person, from brief to deploy.
How many people touch the project and who is accountable for it? Every account management layer between you and the person doing the work is noise and cost. Here there is no such layer.
Do you use artificial intelligence? In which stages, and who reviews it? The honest answer today is yes. What matters is the second part. We use it for code and automation, and every result is read by a human before it reaches the client.
Who writes the website copy? It depends on the budget you sign up for, and that's exactly why it changes the price. Get it in writing.
The third question has gained weight recently. According to Veracode's 2025 GenAI Code Security Report, which tested more than 100 language models, AI-generated code introduced security flaws in 45% of the cases evaluated. The number doesn't condemn the tool. It condemns using it without review, and that's what the question needs to find out.
About technology and ownership
What platform do you deliver on, and why? If the answer is just the name of the tool, the why is missing. The choice has to come from what your team will need to do on its own later.
Who owns the domain when the contract ends? The right answer is you. At Wama the project is transferred to the client's account and the subscription goes on the client's card.
Can I edit the website myself later? How? Ask for a demo, not a claim. Editing content without touching the design is the bare minimum.
About scope, timeline and money
How many rounds of revisions are included? Here they're unlimited within scope, meaning the limit is the contracted scope, not the number of rounds. If the vendor gives you a number, check the price of an extra round.
What's out of scope and becomes an extra cost? A useful answer is a list, not a sentence. Whatever isn't written in the proposal will be billed separately.
What's the timeline, and what makes it slip? A company website takes 4 to 6 weeks. What makes deadlines slip is content that doesn't arrive, slow approvals and scope changes after the design is signed off.
How does payment work, and in how many installments? At Wama, half up front and half on delivery.
How much does it cost, and why that amount? A price without justification is a guess. The market benchmark is in what an honest proposal usually costs.
About what comes after
What happens to the website after delivery? Is there a monthly fee? What does it cover? In our case the client only takes on the platform subscription, with no maintenance contract.
Have you built something my size? Can I see it live? A link, not a screenshot. A website that's no longer live doesn't count as proof.
What do you refuse to do? Maybe the most revealing question on the list. Whoever accepts everything has no criteria. We refuse to copy a competitor's website and we refuse projects with a budget below our minimum range, because they can't fit without hurting the delivery.
How to compare three proposals without comparing only price
Request all three with the same brief. Without that, each vendor quotes a different project and the comparison means nothing. Then build a table with the rows below, which are the ones that usually hide the real difference in value between similar proposals.
What to compare | Why it changes everything |
|---|---|
Pages with their own layout | Twenty CMS-generated pages count as one. Five service pages count as five |
Who writes the copy | It changes the timeline by weeks and the price by a whole range |
Revision rounds and the price of an extra one | This is where the cheap proposal turns expensive |
Monthly cost after delivery | Plan, hosting, plugins, maintenance |
Ownership of the domain and the account | It defines whether you can switch vendors |
Timeline per stage | A final date alone doesn't let you hold anyone to progress |
Filling in this table usually reorders the proposals. The cheapest one at first glance often moves to the middle once copy and revisions are factored in. What you're buying isn't the assembly of screens. According to McKinsey's The Business Value of Design study (2018), which followed 300 companies for five years, companies in the top quartile of design maturity grew revenue 32 percentage points above their industry benchmark. Keep in mind that design isn't priced per page delivered, but by pricing for business results, not pages delivered, which explains why two quotes for the same scope can be so far apart.
What are the signs that an agency actually delivers?
There are four, and all of them can be checked before any meeting. The first is the agency's own website: a company that sells websites and keeps an outdated one is telling you something. The second is the smallest job it accepts, because that reveals where it really operates. The third is how long it takes to answer a simple question by email. The fourth is whether the projects in its portfolio are still live.
That last one is the easiest to check and the most ignored. Open five case studies from the portfolio and see how many still load. If half are down, either the clients didn't stay or the work didn't last. An example of applying open criteria to real names is in a list of agencies with the evaluation criteria in plain sight.
It's worth adding a fifth, newer sign: whether the agency publicly states how it uses artificial intelligence. Whoever hides it is betting you won't ask. We gathered agencies that publicly own their use of AI and what changes in each one's process.
Red flags in quotes and process
None of the situations below is proof of bad faith on its own. Two or more together, and it's time to ask for the next proposal.
The first one can be checked in minutes: compare the promised date with the timeline a serious agency can commit to for each type of project.
A fixed quote with no brief. Whoever quotes without knowing what the website needs to do is guessing, and the cheapest guess wins.
A timeline far below the market. A professional website in 48 hours is a filled-in template under another name.
A one-page proposal with a single number at the end. You can't compare it, and that's probably the point.
Silence about who writes the copy. It's the item that generates the most extra charges later.
A big discount at the first objection. If the price drops easily, it wasn't calculated.
Nothing in writing about domain ownership. That's what locks the client to the vendor.
Who owns the domain, the CMS and the website when the contract ends?
It should be you, and it needs to be in writing. There are three separate things here: the domain, the platform account where the website runs and the project itself. A contract can hand over all three, two or none, and the difference only shows up the day you want to switch vendors.
The twin question is what happens to the website after delivery: how much it costs per month and who answers when something breaks.
When the account is in the agency's name, any change depends on them and leaving means rebuilding. It isn't necessarily dishonest, but it changes your negotiating power for good. Ask before signing, and get the answer in the contract. A studio that works this way explains it without hesitation: see an agency that handles design, development and launch as a reference for clearly stated scope.
Common mistakes when choosing
Deciding by the prettiest portfolio. Beautiful design is the market's baseline, not the differentiator. What sets vendors apart is the process behind it.
Not sending the same brief to everyone. Without that, the price comparison means nothing.
Ignoring the cost of the following years. The savings at hiring disappear in the second year of poorly handled maintenance.
Hiring an agency when what you needed was extra team capacity. It's expensive and creates friction with the people already inside.
Expecting immediate results. A company website is reputation built over time. A vendor who promises to double sales with a new website is selling something else.
Frequently asked questions
How do I know if a website price is fair?
Compare scope, not the final number. Ask for the number of pages with their own layout, who writes the copy and the monthly cost after delivery. Two proposals with the same price can differ by weeks of work, and that's what determines whether the price is fair.
Is it better to hire a specialized or a generalist agency?
Specialized, when your case has a real industry or technology particularity. A generalist works well for a standard company website. The practical test is to ask how many projects similar to yours they've delivered and request the links to check whether they're still live.
How long until my website is ready?
A company website of medium complexity takes 4 to 6 weeks from brief to launch. What stretches that timeline most isn't the technical work, it's the client's content and the approval time for each stage. A vendor who promises days is selling a template.
What does the agency need from me to get started?
The website's goal, the audience, what sets the company apart, visual references and whatever brand material already exists. The more complete that package, the firmer the quote and the lower the chance of rework. Showing up to the meeting with the scope already written changes the whole conversation.
Can I switch agencies in the middle of a project?
You can, but it costs. If the domain and the platform account are in your name, you take what's already been done and only lose time. If they're in the agency's name, switching usually means starting over. That's why the ownership question comes before signing.
If you're evaluating vendors right now and want to see these answers applied to a real project, it's worth seeing how Wama runs a project, from brief to published website, with one person responsible from start to finish.
