What to include in a web design proposal

A web design proposal has one job: help the client say yes to the right project. It should show that you understood the problem, explain how you'll solve it, and make the price and the process easy to agree to.

Most proposals that stall aren't stalled by price alone. They stall because the client can't tell exactly what they'd get, when, or what happens next. This guide goes through the sections that remove that uncertainty.

Before you write: start from the brief

A proposal is much easier to write when the project is already described in a confirmed brief. The brief gives you the goals, audience, scope and timeline. The proposal turns them into an offer. If you don't have a brief yet, our guide on how to write a design project brief covers it.

The sections of a strong proposal

Want the outline without the explanations? Use the web design proposal template.

1. A short, personal introduction

Two or three sentences. Thank the client, name the project, and say what the document covers. Skip your company history. The client is reading to find out whether you understood them.

2. Your understanding of the problem

Restate the situation in your own words: what's happening now, why it matters, and what success looks like. This is where clients decide whether you were listening. Use their language and refer to the goals from the brief.

Example: "Your current site explains features but not the outcome, and it doesn't reflect the quality of the product. Before the January launch, you need a page that makes the value obvious and turns trial visitors into sign-ups."

3. Your approach, as phases

Break the work into a few named phases with a sentence each. Phases show the client how the project unfolds and where they'll be involved.

4. Deliverables

List exactly what the client will receive, as concrete items: "Homepage design for desktop, tablet and mobile", "Interactive prototype", "Component library". If it isn't on this list, it isn't in the project.

5. What's included and what isn't

A two-column list prevents most scope arguments before they start. Put the things a client might reasonably assume are included in the "not included" column.

• Included: the deliverables above, a set number of revision rounds, a progress update each week
• Not included: copywriting unless agreed separately, development and hosting, stock photography or font licences, extra pages beyond the agreed scope

6. Timeline

Give dates or week numbers for each milestone, and say what the timeline depends on, such as feedback arriving within a few days. A simple milestone list is enough. The point is that the client can plan around it.

7. Investment

Present the price clearly, in one place.

• Fixed price works well when the scope is well defined. The client knows the total, and you carry the risk of underestimating.
• Line items show how the total is made up and make it easier to adjust scope by adding or removing items.

Whichever you use, state the payment terms in plain language, for example a deposit to reserve the start date and the balance on delivery. If you charge for extra revision rounds or changes outside the scope, say how much here, not after the fact. To work out the fee itself, the freelance rate calculator turns your income, costs and estimated hours into a project price.

8. Next steps and how long the offer is valid

End with what the client should do to go ahead: reply to accept, sign the agreement, pay the deposit, book the kickoff. Numbered steps work best. Add how long the proposal is valid, so the price and dates don't stay open forever.

A note on legal terms

A proposal describes the offer, and many freelancers follow an accepted proposal with a separate design agreement that sets out ownership, revisions, cancellation and payment terms. Agreement templates, like our outline of the clauses a design contract needs, are a useful starting point, but they're general. Contract law differs between countries, so have your terms reviewed by a qualified professional where you work before you rely on them.

Mistakes that make proposals stall

• Leading with your process instead of their problem. Show that you understood them first.
• Vague deliverables. "Website design" leaves room for very different expectations.
• Hiding the price. If the client has to hunt for the total, they'll assume the worst.
• No "not included" list. This is where most scope disagreements come from.
• No clear next step. End with exactly what to do to start.

After the proposal is accepted

Once the client says yes, keep the same details flowing through the rest of the project: the agreement, the revision requests, the handoff and the invoice. When feedback starts arriving, a structured format helps. See how to structure client feedback on design work.