How to Write a Web Design Proposal That Wins Clients (With Template)

A good proposal does more than list a price. It shows the client you understand their problem, explains how you will solve it, and makes saying "yes" easy. Here is the structure I recommend.
1. Start with their goals, not your skills
Open by summarising what you heard: the business, the problem and the goal. "You want more appointment bookings from local families, and the current site is hard to use on mobile." This proves you listened.
2. Describe the solution
Explain what you will build and why, in plain language. Link each feature to a goal: "A booking button in the header on every page, so patients can book in two taps."
3. Define the scope clearly
- Pages and templates included.
- Features and integrations.
- Content responsibilities.
- Number of revision rounds.
- What is not included.
4. Show the timeline
Break the project into phases — discovery, design, development, testing, launch — with approximate dates or durations and what you need from the client at each stage.
5. Present the investment
Call it an investment and present clear options if appropriate. Include the payment schedule. See how to price website projects.
6. Add proof
Include one or two relevant case studies or portfolio links and a genuine testimonial.
7. Terms and next steps
Summarise key terms (deposit, ownership after payment, revisions, support) and end with a simple next step: "Reply to approve, and I will send the invoice for the deposit."
A simple template
1. Your goals
- Summary of the business, the problem and the goal
2. The solution
- What we will build and why
3. Scope
- Included / Not included / Revisions
4. Timeline
- Phase, duration, what we need from you
5. Investment
- Price, options, payment schedule
6. Relevant work
- Case study links, testimonial
7. Next steps
- How to approve and startTip: Keep it short. A focused four-page proposal usually beats a thirty-page document nobody reads.
Mistakes that lose proposals
- Talking about yourself before the client's problem.
- Vague scope ("a modern website") that invites misunderstanding.
- No timeline or payment terms.
- Too many options — two or three is plenty.
- Slow follow-up. Send the proposal within a day or two of the call while interest is high.
Following up
If you do not hear back in a few days, send a short, friendly follow-up asking if they have any questions. Many proposals are won on the follow-up simply because the client was busy.
Turning a proposal into a contract
Once the client agrees, send a simple agreement based on the proposal, plus the deposit invoice. Start work after the deposit is paid. This protects both you and the client and sets a professional tone for the whole project.
Frequently asked questions
How long should a web design proposal be?
Usually a few pages — long enough to show understanding, scope, timeline and price clearly.
Should I include the price in a proposal?
Yes. Clear pricing with scope and payment terms helps clients decide quickly.
What if the client wants changes to the proposal?
Adjust scope and price together, and send an updated version so both sides agree in writing.


