How to choose a web design agency

Almost every website project that goes wrong was showing warning signs in the first conversation. The agency talked about themselves rather than your customers. Nobody asked what the site was supposed to achieve. The quote was one number with no breakdown.

Here's how to run the selection properly, whether you're hiring locally or anywhere else.

Start with the goal, not the shortlist

Before you contact anyone, write down one sentence: what should this website do that the current one doesn't? Generate more enquiries. Stop the phone ringing with questions the site should answer. Book appointments without a human involved.

That sentence is the single most useful thing you can bring to a first meeting. It also tells you a lot about the agency. A good one will push back on it and ask why. A bad one will just nod and ask how many pages you want.

The questions that separate agencies

1. 01"How will we know if this worked?" A good agency has an answer involving numbers: enquiries, calls, form fills, conversion rate. A weak one talks about how it will look.
2. 02"Who writes the copy?" This is the most commonly skipped part of a project and the most common reason a nice-looking site doesn't convert. Get it settled in the quote.
3. 03"What happens after launch?" Find out what maintenance covers, what it costs, and what happens if something breaks at 9pm on a Friday.
4. 04"Can I see a site you built two years ago?" Anyone can show a launch-day screenshot. A site that still loads fast and ranks well two years later tells you far more.
5. 05"What do you need from me, and when?" Projects stall on client-side content far more often than on development. A realistic agency will tell you that upfront.
6. 06"Who owns the domain, hosting, code, and analytics?" The answer should be you, in writing.

Red flags

• Guaranteed #1 rankings. Nobody can guarantee this. Anyone offering it is either misinformed or lying.
• A quote with no breakdown. One number for 'website' makes comparison impossible and disputes inevitable.
• They hold your domain or hosting in their own account. This is leverage, and it gets used when you try to leave.
• No questions about your customers. If the whole first meeting was about design preferences, the site will be decoration.
• A portfolio of sites that all look identical. That's a template business, which is fine, but you should be paying template prices for it.
• Pressure to sign immediately, or a discount that expires this week.

What should be in the contract

• Exactly what's being delivered: page count, templates, and which functionality is included.
• Who supplies copy and images, and by when.
• Number of revision rounds, and what happens beyond them.
• Ownership of domain, hosting, source code, and all analytics accounts.
• What maintenance covers after launch, what it costs, and response times.
• A defined process for scope changes, so a mid-project addition doesn't become an argument.

Local vs remote, honestly

Hiring locally genuinely helps in a few situations: you want photography of your actual premises and team, you'd benefit from a face-to-face workshop, or your business depends on local market knowledge that would take an outsider months to build.

Outside those cases, proximity matters much less than people expect. What actually predicts a good outcome is how quickly they respond, whether they've solved your specific problem before, and whether they ask uncomfortable questions early. Optimise for those.

We work with businesses nationwide and worldwide. If you want a second opinion on a quote you've received, or a free audit of the site you already have, send it over and we'll tell you straight.