How to write a web design proposal that gets signed

A web design proposal has one job: help the person reading it say yes, and help them explain that yes to whoever else has to agree. It is not a brochure about your studio and it is not a contract written by a lawyer. It is the summary of a conversation you have already had, turned into a plan and a price the client can believe.

This guide walks through the proposal section by section, with examples in euros, and ends with a checklist you can use before you press send. The general method behind it, with a sample for a different kind of client, is in writing a business proposal step by step.

Before you write: earn the right to propose

The best proposals are written after a proper conversation, not instead of one. Before you open a template, make sure you can answer these questions in a sentence each:

• Why now? What changed that made them look for a new website this quarter: a rebrand, a new product, a site that breaks on phones, a sales team that stopped sending people to it.
• What does success look like? More enquiries, fewer support calls, a shop that the team can update without a developer.
• Who decides? The person you spoke to, a director, a board, a partner who never joined the call.
• What is the budget range? Ask directly. "Projects like this usually land between €12,000 and €25,000 depending on scope. Where do you see yourselves?" is a normal question, not a rude one.
• When do they want to decide, and when do they want to launch?

If you cannot answer these, a second call will do more for your win rate than a better-looking document. For the exact wording to use on that call, and a notes page laid out in proposal order, see the questions to ask on a discovery call.

The structure that works

Most signed web design proposals follow the same order, because it is the order in which a buyer thinks: do they understand us, can they do it, what will it cost, what happens next.

1. Cover: the client's name, the project in a few words, your logo, the date.
2. The challenge: their situation and goal, in their words.
3. Your approach: how you will solve it, in three or four steps.
4. Scope: what is included and what is not.
5. Timeline: phases, milestones and what you need from them.
6. Team: who will actually do the work.
7. Cases: two or three projects like theirs, with results.
8. Pricing: the investment, with options where they make sense.
9. Payment schedule: when they pay what.
10. Agreement: the terms in plain language, and how to accept.
11. Next step: one clear action and a date.

Keep each section short. A decision-maker who skims the cover, the challenge and the pricing should still understand the whole proposal.

Write the challenge in their words

The challenge section is where you prove you listened. Use the phrases the client used on the call. If they said "our site looks like it's from 2014 and nobody in sales wants to send it to customers", write that, not "the current digital presence does not reflect brand positioning".

A good challenge section has three parts:

• Where they are now: the current site, what it costs them in time or missed sales.
• Where they want to be: the outcome, ideally something they can measure.
• What is in the way: the reason they cannot get there alone.

Two short paragraphs are usually enough. If the client reads it and thinks "yes, exactly", the rest of the proposal is read in a different mood.

Describe the approach, not your whole process

Clients do not need your twelve-stage methodology diagram. They need to know what will happen to them, in order. Three or four steps work well:

1. Discover: a workshop with your team to agree goals, pages and content.
2. Design: homepage and key templates, two rounds of feedback.
3. Build: development on a staging site you can see as it grows.
4. Launch and care: go live, training, and a care plan to keep it fast and safe.

For each step, say what the client gets and what you need from them. That second part matters more than most studios think: late content is one of the usual reasons a web project runs over, and naming it now protects both sides.

Make the scope impossible to misread

Scope is where most disputes start, months later. Write it so that a person who was not on any call could tell whether a request is in or out. Count things: "up to 12 page templates", "two rounds of design feedback", "migration of up to 40 existing blog posts". Then list what is not included, such as copywriting, photography or third-party licences.

We have a separate guide on writing a scope of work clients understand, with a template and examples. If you also sell work outside websites, such as photography or a marketing retainer, the table in what changes in a proposal per industry lists what to count and what to exclude for each.

A timeline with dependencies

Show the timeline in weeks, not dates, unless the start date is fixed. Mark the moments where you wait for the client:

Then add one sentence: "If content arrives later than week 6, launch moves by the same number of weeks." It is not a threat. It is the deal.

Show the team and the proof

Buyers hire people, so show the two or three people who will actually work on the project, with a photo and one line about what they will do. Leave out the people they will never meet.

For cases, pick projects close to theirs in size or sector. For each one, give the starting point, what you did and what changed. If you have a number the client gave you permission to share, use it. If you do not, a short quote from the client works better than a vague claim.

Price it so the client can choose

A single take-it-or-leave-it number invites one question: is this too much? Options change the question to: which one fits us? You can do this in two ways:

• One project with optional extras: the rebuild at €18,500, plus a brand refresh and an SEO audit they can add.
• Tiers: three versions of the project at different levels, the approach covered in good, better, best pricing options.

Separate one-off work from recurring work. A website is a project; hosting, updates and support are a monthly care plan. Showing both on one page lets the client see the total cost of owning the site, and it gives you recurring revenue.

Show prices excluding VAT, then the VAT and the total, so nobody is surprised by the invoice. If you are unsure how to get to the number in the first place, start with our guide to pricing a website project.

Payment schedule and terms

Spell out when money moves. A common split for a project of €18,500 excluding VAT:

You can also offer a reason to pay differently: a small discount for paying the whole project upfront, or the option to spread it over a few months. Keep the agreement section in plain language: what you deliver, how changes are handled, who owns what after the final payment, how either side can end the work, and how long the proposal is valid.

End with one clear next step

The last page should say exactly what happens when they agree: "Sign by 31 October and we start on 11 November." Give a validity date, usually 14 or 30 days, so the proposal does not drift. Make accepting easy: a signature, a reply, a button. Do not end with "let us know what you think".

Then plan your follow-up before you send it. Our guide on when and how to follow up on a proposal has a schedule and email examples.

Checklist before you send

• The challenge uses the client's own words.
• Every deliverable in the scope is counted, and there is an "out of scope" list.
• The timeline shows what you need from the client and when.
• The team section shows the people who will do the work.
• Two or three relevant cases, each with a result or a quote.
• Prices excluding VAT, the VAT, and the total are shown.
• One-off and recurring costs are separated.
• The payment schedule adds up to the total.
• There is a validity date and one clear next step.
• You have read it on a phone, because a client may open it there first.
• Your follow-up is in your calendar.

How Propozit helps

Propozit turns your proposal into a branded 16:9 slide deck. You can try the structure above in the live demo: 11 slide types, from cover and challenge to cases, pricing, payment schedule and agreement, each fitting its content and scrolling easily on a phone. Its pricing slide shows a fixed-price rebuild with optional extras and monthly care plans in euros, VAT added on top, with live totals as the client ticks options. It also shows deals such as paying upfront to save 5% (see interactive pricing).

In an account today you can set your brand colours, fonts and logo with a live preview, invite your team, keep a price list and build your own decks in the editor. Switch on the payment plans the client can pick from, such as 50/50 or monthly instalments, and the payment slide, the terms and the signed PDF follow their pick. You can send the deck to your client, who signs in it, and see when they open it. Propozit is in early access and free to start, and the page on Propozit for web design agencies shows what it does for studios like yours.