How to write a web design proposal

What a proposal is actually for

A web design proposal does three jobs at once. It reassures the client you've understood what they need. It defines the work precisely enough to be a real commitment. And it makes the decision easy, clear price, clear next step, no homework required.

Most proposals fail at one of these. Some are all reassurance and no scope, so they read well and commit to nothing. Some are all scope and no empathy, so they read like a legal document and win on price alone. The good ones do all three, and they carry forward: the scope you write to win the work is the same scope your team builds from. That's the test, a proposal that dies at signature was only ever a sales document.

The sections that win the work

A strong web design proposal has a predictable spine. Predictable is good, the client can find what they need, and you can reuse the structure every time.

1. 1Summary, a short restatement of the client's situation and goal, in their words.
2. 2Approach, how you'll tackle it, and why. This is where you show judgement.
3. 3Scope and deliverables, what's included, what isn't, and what they'll receive.
4. 4Timeline, phases, key dates and what depends on them.
5. 5Pricing, the number, what it covers, and the payment schedule.
6. 6Terms, revisions, change control, assumptions, sign-off.
7. 7Next step, exactly what happens when they say yes.

For the detail on each, including what to put in and what to cut, read sections every web design proposal needs.

Lead with their problem, not your logo

The quickest way to lose a client is to open with three pages about your agency's history and awards. They don't care yet. Open with their problem, stated so accurately they think "yes, that's exactly it". Trust is built in that first paragraph, not on your team page.

• Weak opening: "Founded in 2014, we are a full-service digital studio…"
• Strong opening: "Your current site takes eight seconds to load on mobile and can't take

bookings, so you're losing enquiries you've already paid to attract. Here's how we'd fix that."

Everything after that lands better once the client believes you understand the job.

Present scope and price with confidence

The scope section is where a proposal becomes a commitment rather than a wish. Name what's included and, just as important, what isn't. A clear out-of-scope list protects both sides and signals that you've done this before. See in-scope vs out-of-scope.

On price, confidence matters as much as the number. Present a single clear figure (or an honest range, firming to a fixed price) for the defined scope. Don't bury it, don't apologise for it, and don't itemise it into forty lines the client can pick apart, see why not to itemise every line. If you want to grow the deal, do it with optional extras the client chooses, not padding they didn't ask for. For reaching the number itself, read how to price a website.

Make signing the easy next step

A proposal should end by removing friction, not adding it. The client should know exactly what happens when they say yes: sign here, pay the deposit, we book you in for this date. If saying yes means a phone call, a printout, a scan and a return email, you've added three chances for the project to stall.

This is where the document and the tool meet. A proposal the client can open, read and sign in the browser, with the scope, price and terms all in one place, converts better than a PDF attachment that sits unopened. ScopeDeck's branded PDF export, client portal and native e-signature exist to make that last step a single click. For the full playbook, read getting a proposal signed.

Why proposals get ghosted

The silence after sending a proposal usually isn't rejection, it's friction, doubt or bad timing. The most common causes are a price with no context, a scope the client can't picture, a document that's hard to open, and no clear next step. Each one gives a busy client a reason to put it in the "later" pile it never comes out of. We cover the fixes in why proposals get ghosted.