How to choose a web design agency: the questions that actually matter
Every website conversation eventually gets to price, and price is the easiest thing to compare and the least useful thing to decide on. Two quotes for "a business website" can be wildly different projects wearing the same label.
These are the questions that tell you more than the number at the bottom of a quote — the ones we'd want a client to ask us, too.
Ask what the site is built on, not just what it looks like
A mockup can be pretty regardless of what's underneath it. Ask directly: is this a page builder or template platform, or is it hand-coded? Both can produce a working website, but they age differently — a heavily customised template tends to slow down and get harder to change as more gets bolted onto it, while a site built from a clean codebase stays easy to extend.
Neither answer is automatically wrong for every business. What matters is that the agency can explain the trade-off honestly instead of dodging the question.
Ask who owns the domain and the code when it's done
Some agencies register your domain in their own account, or build on a platform only they can log into and edit. That's fine as a managed service if you know that going in — it's a problem if you find out only when you want to leave.
Ask plainly: at the end of this project, do I have the login to my own domain registrar, my own hosting, and a copy of the actual source code? A confident "yes" with no hedging is what you're listening for.
Ask how they handle content, not just design
The single biggest delay in most website projects isn't design or code — it's waiting on final text and photos from the client. Ask upfront whether the agency writes copy, sources or shoots photography, or expects you to supply everything finished. There's no wrong answer, but there's a wrong surprise: finding out mid-project that a service you assumed was included isn't.
A good answer names a real process — a content questionnaire, a writing pass, a review round — rather than a vague "we'll figure it out together."
Ask what happens after launch
A website is never really finished — content changes, a bug turns up, a form stops sending emails six months in. Ask what support looks like after the site goes live: is there a retainer, a per-incident rate, or nothing at all once the invoice is paid.
An agency that's thought about this has a straight answer. One that hasn't will talk around the question — which is itself useful information.
Ask to see a real, live site — not a mockup
A portfolio full of static images tells you almost nothing about how a site performs. Ask for links to real, currently live sites the agency built, then actually open one on your phone: does it load quickly, does it look right on a small screen, does the contact form work if you test it.
That two-minute check tells you more about the quality you'll actually get than any amount of talking through a pitch deck.
Questions we hear a lot
How much should a website cost?
It genuinely depends on scope — a focused business site, an e-commerce build, and a web app are different projects. Be wary of a fixed price list quoted before anyone understands what you need; a real quote follows a real conversation.
Should I hire a freelancer or an agency?
Both can do good work. A freelancer is often cheaper and more flexible for a small, well-defined project; an agency usually offers more continuity if the person who built your site becomes unreachable. Ask the ownership and support questions above regardless of which you choose.
What's a red flag when talking to a web design agency?
A quote given before any real conversation about your goals, no live examples of past work, and being asked for full payment upfront before any work is shown are the three worth watching for.
Do I need to know anything technical to brief a website project?
No. What helps far more than technical knowledge is clarity on what the site needs to do for your business — bring enquiries, let customers book something, explain your services — and let the agency handle the technical decisions.
How long should a website project take?
A focused business website typically runs two to six weeks from a clear brief to launch. Projects run longer when content isn't ready, scope grows mid-project, or feedback rounds stretch out — which is itself a reason to ask about process upfront.
Have something worth building?
Tell us what you're trying to make happen. We'll reply with a plan, not a brochure.
Start a project