How to Write a Web Design Proposal That Closes

If your proposal has to do the convincing, the proposal has already failed. By the time a document lands in a client's inbox, they should know roughly what you'll do and roughly what it costs. The document's job is to make saying yes easy — not to win an argument that should have been won on the phone.

The conversation that has to happen first

Designers who send proposals cold, straight after a first enquiry, lose most of them. You're guessing at scope, guessing at budget, and the client is comparing documents rather than people.

Before you write anything, you need three things from a conversation: what they're actually trying to achieve, what they'd consider a reasonable spend, and who else has to approve it. Ask directly. "Do you have a figure in mind?" is not rude, and the answer saves you writing a proposal for ten thousand when they were thinking two.

Lead with their problem, in their words

Open with a short section that restates what they told you, using their own language. If the owner said "we look amateur next to the big firms", write that — not "brand positioning is misaligned with market expectations".

This section does more than any portfolio page. It proves you listened, and it means that when they forward the document to a partner who wasn't on the call, the context travels with it.

Three options, and why the middle one wins

A single price invites a yes-or-no decision, and no is always the easier answer. Three options change the question from "should we do this?" to "which of these?" — a far better question to be asking.

• Essential — the smallest thing that solves the stated problem. Priced so it's clearly viable, not a token.
• Recommended — what you'd actually build. Say plainly that this is the one you suggest and why.
• Complete — the fuller version with the extras they mentioned wanting "eventually".

Most clients take the middle. The top option isn't there as a trick; it's there because some clients genuinely want it, and because it makes the middle look sensible rather than expensive.

Scope, written as a fence

Most of the pain in web projects comes from scope that was never written down. Say exactly how many pages, how many rounds of revisions, who supplies text and images, and what happens when something falls outside.

Write the exclusions too, plainly and without apology: content writing, photography, logo design, ongoing SEO, hosting beyond the first year. Clients don't resent clear boundaries — they resent discovering a boundary after they assumed otherwise. A clear exclusions list is also how an extra request becomes a paid change rather than an argument.

Price it against what it earns, not what it costs you

Hours are the weakest basis for a price, because the client is buying an outcome and hourly framing invites a negotiation about your speed.

Put the number next to something real instead. If the business's average job is worth £1,400 and the site currently loses enquiries because the form breaks on mobile, then a £3,000 build pays for itself in two recovered jobs. That sentence belongs in the proposal, because it moves the price from a cost to a comparison — and it only works if you learned those figures in the conversation.

Make the yes mechanical

End with exactly what happens when they agree: deposit amount, how to pay, what you need from them, and the first date in the calendar. Ambiguity at this point is where proposals go to die.

A line that costs nothing and works: "If you're happy, reply to this email with 'approved' and I'll send the invoice and the content checklist today." You've reduced the action to one word.

Length, format, and the follow-up

Two to four pages. Anything longer gets skimmed, and anything that needs a page of preamble is compensating for a conversation that didn't happen. Send it as a PDF or a simple web page — not an editable document, which invites redlining, and not a slide deck, which can't be read on a phone.

Then follow up. Say in the email when you'll check in, and do it on that day. "I'll give you a ring Thursday if I haven't heard" is not pressure; it's the thing that stops a proposal sitting unread for three weeks.

What a lost proposal should teach you

When one doesn't land, ask why — most clients will tell you. Usually it's one of three things: the price was outside a budget you never asked about, you proposed a rebuild when they wanted a repair, or someone you never spoke to made the decision. All three are fixable, and all three are failures in the conversation rather than the document.