The Page That Answers the Question They're Too Polite to Ask

Most creative websites answer a question the client hasn't asked yet: what will I actually get? Fewer answer the one they're too polite to ask: what will it be like to work with you? That's the gap a short 'how I work' page fills.

UK clients, in my experience, would rather quietly hope for the best than open with 'how often will we speak?' It feels presumptuous. So they book, then spend the first fortnight decoding your email cadence. By the time they've worked it out, you're both slightly irritated and nobody's said why.

A single screen of plain English fixes this. Not a contract, not a services page, not a manifesto. Just the operating manual.

Deliverables don't tell the whole story

Look at most portfolio sites and you'll see the same shape: a list of services, a few project tiles, a contact form. That covers the what. It says nothing about the how.

How often will we meet? Who signs off the work? What happens when I send feedback on a Friday afternoon? How many rounds of changes are included before the mood shifts? These are the questions that decide whether a project feels calm or chaotic, and almost nobody addresses them before the contract is signed.

The result is a strange little dance. The client assumes daily updates because their last agency did. You assume weekly because that's how you've always worked. Neither of you says anything until week three, when someone sends a 'just checking in' email with a slightly wounded tone.

What actually goes on the page

Four or five short paragraphs, no more. Write them in the second person, as if you're talking to one client across a table.

Meeting rhythm. 'We'll have a 45-minute call every other Tuesday, plus a short written update each Friday.' That's it. No need to explain your philosophy of meetings.

Feedback and revisions. 'Two rounds of revisions are included. A third is a new conversation, priced separately.' Say the number. Clients respect a number far more than 'unlimited tweaks' — which everyone reads as 'this will never end'.

Response times. 'I reply to emails within two working days. I don't monitor messages at weekends or on bank holidays.' This one line prevents about a dozen low-level anxieties.

Decision-making. 'You sign off on strategy and budget. I make the final call on craft.' It sounds blunt written down; in practice it's a relief, because it tells the client exactly where their responsibility ends.

What you need from them. 'One named decision-maker, please.' Two is a committee. Three is a delay.

That's the whole page. One screen, maybe two on a phone. No stock photos of people pointing at whiteboards.

Why it filters as much as it sells

Here's the bit people miss. A 'how I work' page isn't just reassurance for the right client — it's a signpost for the wrong one.

The client who wants a call every morning reads 'weekly check-in' and quietly moves on. Good. The one who wants unlimited revisions reads 'two rounds' and books with someone else. Also good. You've just saved yourself a six-week project that would have ended in a stiff email and a refund request.

Most freelancers try to widen the funnel. This page narrows it, on purpose. British clients in particular tend to be quite good at reading between lines — if you say 'I work best with one decision-maker', they'll know whether that's them.

The politeness problem, and how the page solves it

We have a national habit of not asking direct questions about process. It feels like implying distrust. So the client says 'sounds great, let's go' and mentally fills in the blanks with whatever their last supplier did.

Your page fills in those blanks first. It gives them permission to ask follow-ups, because you've already raised the subject. 'You mentioned two revision rounds — what counts as a round?' is a much easier sentence than 'so... how many changes do I get?'

It also gives you a document to point at later. Not as a weapon — just as a shared reference. 'As the how I work page says, I'm off this week, back Monday.' No defensiveness required.

Keep it specific, keep it short

Avoid 'I'm passionate about collaboration'. Avoid 'every project is unique'. That's wallpaper. Use numbers, days of the week and plain nouns.

'Two working days' beats 'promptly'. 'Every other Tuesday' beats 'regular check-ins'. 'Two rounds' beats 'a flexible revision process'. Vague language reads as evasion, even when it isn't.

And keep the tone human. You're not drafting terms and conditions; you're describing a working relationship. A little dry humour goes a long way. 'I don't answer emails at weekends — not out of principle, just out of a need to be a person' is the sort of line that lands well with UK clients.

Where to put it, and when to update it

Link it from your contact page, your homepage footer and the bottom of every proposal. Three clicks maximum. If a client has to hunt for it, they'll assume it's not important.

Update it in January, and again whenever your process genuinely changes. A page that says 'weekly calls' when you've moved to fortnightly is worse than no page at all — it's a broken promise in writing.

And read it back before you send it live. If it sounds like a policy document, rewrite it. If it sounds like you explaining your week to a friend, you've got it about right.

What it changes

A short 'how I work' page won't win you work on its own. But it does something subtler: it moves the awkward conversations to before the money changes hands, where they're cheap. Clients arrive already knowing the rhythm. You spend less time managing expectations and more time doing the work.

In 2026, with everyone's inbox permanently near capacity, that's not a small thing. It's the difference between a project that runs on trust and one that runs on guesswork.