Ask a client what they want from their new website and you’ll get a familiar list: modern, clean, mobile-friendly, easy to update. Ask them six months after launch whether they got what they wanted, and the answer is far less predictable.
The gap between those two moments is where most agency web projects go wrong. Not because the design was bad or the developer was incompetent, but because the brief captured what the client said they wanted rather than what they were actually trying to achieve.
We build websites white-label for marketing agencies across the UK, which means we see the brief, the client feedback, and the post-launch questions on dozens of projects a year. The patterns are remarkably consistent. Here’s what clients actually want — and how to give it to them without blowing your margin.
1. They want to stop worrying about it
Most business owners don’t want a website. They want the problem of not having a decent website to go away.
That distinction matters because it changes what “done” looks like. A client who wants a website is satisfied by a launch. A client who wants to stop worrying is only satisfied when they trust that the thing will keep working — that it won’t break, won’t go down, won’t get hacked, and won’t need their attention every fortnight.
This is why care plans sell so easily when they’re framed properly. You’re not selling hosting and updates. You’re selling the absence of worry. Agencies that present a maintenance retainer as an optional extra at the end of the project get a low take-up. Agencies that build it into the proposal from the start — as part of what “a working website” means — get most clients saying yes without a fight.
2. They want to know what’s happening, not what’s technical
Clients rarely complain about timelines. They complain about silence.
A four-week build with a weekly two-line update feels fast. A three-week build with no contact until the staging link arrives feels chaotic, even though the client got their site sooner. The perceived quality of a project is driven far more by communication rhythm than by delivery speed.
What works:
A short update every week, even when the update is “still building the templates, on track for Thursday.”
Plain English. “We’ve built the pages that show your services” beats “we’ve completed the custom post type templates.”
Naming the next thing you need from them, with a date. Most delays are caused by waiting on client content, and clients don’t realise they’re the bottleneck unless you tell them clearly.
If you’re outsourcing the build, this is the part you should never delegate. Your development partner handles the work; you own the relationship and the narrative.
3. They want to be able to change things themselves — a bit
Almost every client asks for a site they can update. Very few actually want to build pages.
What they really mean is: I want to change the phone number, swap a photo, add a team member, and publish a blog post without paying someone £90 to do it. That’s a much smaller requirement than a full page builder, and it’s a much better outcome.
Over-flexible sites are one of the most common causes of post-launch regret. Hand a client an unrestricted builder and within a year the design system has been picked apart — mismatched fonts, five shades of the brand colour, broken mobile layouts. Then they blame the agency for a site that “looks tired.”
The better approach is deliberate constraint: locked-down templates, a small set of pre-built content blocks that always look right, and clear editing for the fields that genuinely change. Clients get the control they wanted and the site still looks like the one they signed off.
4. They want the site to bring in business — and to see the proof
Every client says they want more leads. Fewer than half have any way of knowing whether they’re getting them.
Enquiry forms that email a single inbox, phone numbers that aren’t tracked, no analytics beyond a default install — this is the norm on sites we’re asked to rebuild. The client’s sense of whether the website “works” ends up based on vibes, and vibes are a terrible basis for a renewal conversation.
Building measurement in from day one is cheap and it protects the relationship:
Conversion tracking on every form and call-to-action.
A simple monthly summary: visits, enquiries, top pages, top sources.
Agreed benchmarks before launch, so “is this good?” has an answer.
When a client can see fourteen enquiries in a month that used to produce four, the price of the project stops being a topic of conversation. When they can’t see anything, every invoice gets scrutinised.
5. They want to feel like they had good taste
This is the one nobody puts in a brief.
Clients want to send the link to a peer, a competitor, or their spouse and hear that it looks great. A site that performs well but embarrasses them socially is a failed project in their eyes, no matter what the numbers say.
Practically, that means the visible craft matters: typography that isn’t default, imagery that doesn’t look like stock, spacing that gives the design room to breathe, and a homepage that says something specific about the business rather than “welcome to our website.” It also means resisting the urge to fill every section with content because the template has a slot for it.
It’s worth remembering that the client is the person who has to live with this site every day. Design decisions that are defensible but joyless tend to produce quiet, lingering dissatisfaction — the sort that shows up as a hesitation at renewal rather than a complaint.
6. They want one person to be accountable
Multi-supplier projects fail in the gaps. The designer says it’s a development issue, the developer says it’s a hosting issue, the hosting company says it’s a plugin issue, and the client is left refereeing a dispute between three companies they didn’t want to hire in the first place.
What clients want is a single number to call where the person who answers takes responsibility. That’s the core value an agency offers on a web project — more than design, more than code. Whoever is actually doing the building matters far less to the client than knowing that someone has it in hand.
This is precisely why white-label delivery works so well when it’s structured properly. The client gets one accountable relationship. You keep the relationship, the margin, and the strategic layer. The build happens behind the scenes at a fixed, predictable cost.
Turning this into a better brief
Most of the disappointments above trace back to the same root cause: the discovery conversation stayed at the level of features. Try replacing feature questions with outcome questions.
| Instead of asking | Ask |
| How many pages do you need? | Which of your services actually makes you money? |
| What do you want it to look like? | Who do you want to be taken seriously by? |
| Do you want a blog? | Who currently answers your customers’ questions before they buy? |
| Do you want to edit it yourself? | What did you have to ask someone to change on your last site? |
| What’s your budget? | What would a good year look like off the back of this? |
The answers give you a brief your development partner can build against, and — just as importantly — a set of shared expectations you can point back to when the feedback round starts.
The short version
Clients want to stop worrying, to be kept informed, to have a little control, to see proof it’s working, to feel proud of it, and to have one person accountable. Almost none of that is about code. All of it is about how the project is run.
Get those six right and the website itself becomes the easy part — especially if you’re not building it yourself.