How to choose a web design agency: a builder's vetting checklist

To choose a web design agency, judge three things in order: whether their live work performs under real-world conditions, whether the people who will actually build your site can explain their decisions, and whether the contract leaves you owning what you paid for. Most guides give you forty questions to ask; this one comes from the builder's side of the table and tells you which few signals actually separate strong agencies from weak ones, what a proposal red flag looks like, and when you should not hire an agency at all.

The agency's own website is the strongest single tell

Before you read a single case study, open the agency's own site on your phone. This is the one project where they had no difficult client, no budget ceiling imposed by someone else, and no deadline they did not set themselves. It is their work under ideal conditions. If it is slow, generic, or broken on mobile, that is their ceiling, not their floor.

Check three things: does it load fast on a mid-range phone over mobile data, does anything about it feel considered rather than templated, and does the writing sound like people who understand business outcomes or like people reciting design vocabulary. An agency that ships a mediocre site for itself will not ship a better one for you.

How to evaluate a web design agency's portfolio like an engineer

Portfolios are curated. Screenshots hide load times, broken interactions, and the fact that the site may have been redesigned by someone else since. So do not evaluate the portfolio page; evaluate the live sites it links to.

• Run two or three portfolio sites through Google's free PageSpeed Insights and look at the Core Web Vitals results. Beautiful sites that fail these checks are common, and the failure is the agency's, not the client's.
• Use each site on a phone. Scroll, tap the menu, submit a form. Polish that survives a real device is rarer than polish in a screenshot.
• Look for range within a consistent standard of quality, not one style repeated. Five near-identical sites usually means one template.
• Check recency. If the newest live work is several years old, ask why. Teams change, and you are hiring the current team, not the one that built the showpiece.

Then ask the question almost nobody asks: who specifically built this, and do they still work here? White-label subcontracting is widespread. There is nothing inherently wrong with it, but you deserve to know whether the portfolio you are vetting was produced by the people you will be paying.

Questions to ask a web design agency, with the answers that matter

You do not need twenty questions. You need a handful where the shape of the answer is diagnostic. Here are the highest-signal ones, with what a good answer sounds like versus a warning sign.

• "Who will actually do the work on my project?" Good: named people, their roles, and whether any part is subcontracted. Warning: vague talk about 'our team' or a salesperson who cannot answer.
• "Walk me through a project that went wrong." Good: a specific story, what they changed afterwards. Warning: claiming nothing has ever gone wrong. Everyone has a failure; only weak agencies hide them.
• "What will you push back on?" Good: examples of telling clients no, with reasons. Warning: 'we build whatever you want.' You are paying for judgment, not just hands.
• "How do you handle performance and accessibility?" Good: they mention Core Web Vitals, WCAG, and testing on real devices without prompting. Warning: 'the site will be fast' with no specifics.
• "What happens after launch?" Good: a clear maintenance offering, defined response times, and a clean exit path if you leave. Warning: silence, or lock-in dressed up as support.
• "Do you use AI in your process, and where?" Good: a candid answer about where AI assists and where humans decide. Warning: either pretending they do not use it or being unable to explain their quality control over it.

The pattern across all of these: strong agencies are specific and comfortable with hard questions. Weak agencies are fluent and vague.

Red flags in proposals and contracts

The proposal stage is where most bad engagements are visible in advance. Watch for these.

• A single line item for the whole project with no breakdown of discovery, design, build, and testing. If they cannot itemize the work, they have not scoped it.
• A quote produced without a real conversation. Serious work is scoped after a call, not before one.
• No mention of who owns the finished work. You should own the design, the content, and the source code outright once you have paid. 'License to use' language is a leash.
• Hosting, domain, or analytics accounts registered in the agency's name. Every account should be in yours, with the agency added as a collaborator. This is the difference between firing a vendor and negotiating a hostage release.
• Unlimited revisions. It sounds generous; it actually signals no process, and it is how projects run six months late.
• Pressure tactics: expiring discounts, 'we only have one slot left this quarter.' Good agencies have pipelines, not countdown timers.

Also insist the contract covers a kill clause: what you pay and what you receive if either side walks away mid-project. Agencies that resist defining this are telling you something.

How to think about cost without a number in hand

Published price ranges for web design conflict wildly, because 'a website' spans everything from a template assembled in an afternoon to a custom-engineered product built over months. Comparing quotes without comparing scope is meaningless. What you can compare is what a quote buys: template versus custom design, whether motion and interaction are engineered or bolted on, whether performance and accessibility are tested or assumed, and what happens after launch.

The honest framing is cost per outcome, not cost per page. A cheap site that fails to convert visitors is the most expensive kind, the same way a cheap backend becomes expensive the day it matters, a pattern we have written about in the real cost of building a system that breaks at scale. Ask every agency to connect their scope to a business outcome. The ones who can are the ones worth shortlisting. For what it is worth, Kaev does not publish pricing for exactly this reason: every project is scoped and quoted individually after a short call.

Vet for the AI-search era, not just Google rankings

A growing share of buying research now happens inside AI assistants like ChatGPT, Perplexity, and Claude, which cite and summarize websites rather than listing ten blue links. An agency choosing your site's architecture in 2026 should be able to talk about this without being prompted.

• Ask how they make content citable by AI systems: clear answers near the top of pages, structured data, clean semantic markup.
• Ask whether they ship server-rendered pages that crawlers can actually read, or JavaScript-heavy builds that some AI crawlers cannot.
• Ask how they balance visual ambition with performance. It is possible to have both, but only when motion is engineered rather than layered on, the approach behind cinematic website design done properly.

If the answer to all of this is 'we do SEO,' the agency is optimizing for the last decade.

When you should not hire an agency

An honest guide has to include this. Agencies are the wrong choice in at least three situations.

• Your budget is at the low end of the market and your needs are simple. A well-configured site builder or a capable freelancer will serve you better than the cheapest agency you can find, which is usually the worst version of an agency.
• You need continuous design and development work indefinitely. Past a certain sustained volume, an in-house hire is cheaper and more responsive than a retainer.
• You cannot articulate what the site is for. If you do not know whether the goal is leads, credibility, or direct sales, discovery with any vendor will be expensive guessing. Do that thinking first, even roughly.

The freelancer versus agency question mostly comes down to risk and scope. A strong freelancer is excellent for well-defined, single-discipline work. An agency earns its premium when the project needs design, engineering, motion, and content to be coordinated, and when a single person disappearing cannot be allowed to stall the project.

A vetting checklist you can run in under two hours

Everything above compresses into a pass you can complete before any second call.

• Agency's own site: fast on your phone, distinctive, clearly written.
• Two live portfolio sites: pass Core Web Vitals, work on a real device, look current.
• Named team: you know who is building your site and whether work is subcontracted.
• Answers: specific stories, real pushback, a named failure, unprompted performance and accessibility talk.
• Proposal: itemized scope, scoped after a real conversation, no pressure tactics.
• Contract: you own code and content, all accounts in your name, defined revisions, kill clause, post-launch terms.
• AI-era readiness: they can explain how the site will be visible to AI search, not just Google.

An agency that clears all seven is rare. Two or more misses, walk away; the shortage of good agencies is real, but the cost of a bad one is worse.

Common questions

How do I evaluate a web design agency's portfolio?

Ignore the screenshots and open the live sites. Test them on your phone, run two through PageSpeed Insights to check Core Web Vitals, and confirm the work is recent. Then ask who specifically built each project and whether those people still work at the agency.

What questions should I ask a web design agency before hiring?

Ask who will personally do the work, for a story about a project that went wrong, what they would push back on, how they handle performance and accessibility, and what happens after launch. Specific answers are the signal; fluent vagueness is the warning.

What are the biggest red flags when choosing a web design agency?

A quote with no itemized scope, contracts where the agency keeps ownership of code or hosting accounts, unlimited revisions, pressure tactics like expiring offers, and an agency website that is itself slow or generic. Any one of these is worth a hard question; two or more is a reason to walk.

Should I hire a freelancer or a web design agency?

A strong freelancer suits well-defined, single-discipline projects and simpler sites. An agency makes sense when design, engineering, motion, and content need coordination and you cannot afford the project stalling because one person is unavailable. For continuous long-term work, an in-house hire often beats both.

Who should own the website when an agency builds it?

You should. Once paid for, the design, content, and source code belong to you, and the hosting, domain, and analytics accounts should be registered in your name with the agency as a collaborator. Anything less makes leaving the agency expensive by design.