Web design proposals have a specific problem that most other proposals don't: the client has no idea what they actually want. They know they need a website. They might have a Pinterest board of sites they like. But ask them about functionality, content structure, or integrations, and you'll get a shrug and "that's why we're hiring you."
That's not a complaint โ it's just the reality. And it's exactly why your proposal can't be a generic template. You're not just selling a website. You're defining what the website is, what it does, and what "done" looks like. The client is relying on you to scope the project they can't scope themselves.
Here's how to write a web design proposal that does that โ and wins the job without you eating the cost of scope creep three weeks in.
Start With the Client's Business Problem, Not the Website
The biggest mistake web designers make in proposals is leading with the website. "We'll build you a 6-page responsive WordPress site with..." โ stop. The client doesn't care about WordPress. They care about their business problem.
Before you write a single word of the proposal, you need to understand:
- What's not working right now? Is their current site slow? Outdated? Non-existent? Not converting?
- What does success look like? More leads? More sales? Just "look professional" is valid too โ but name it
- Who's the audience? A site for B2B software buyers is fundamentally different from a site for a local bakery
- What happens after launch? Who maintains it? Who updates content? This matters for scope
Your proposal's opening paragraph should reflect this understanding. Not "We propose a modern, responsive website..." but "Your current site takes 6 seconds to load, doesn't display properly on mobile, and has no clear call-to-action. That's costing you leads โ every person who bounces is a potential customer who went to a competitor instead."
The 6 Sections Your Web Design Proposal Needs
1. Project Overview (Half a Page)
Summarize what you understand the project to be. This is your chance to prove you listened during the discovery call. If the client reads this section and thinks "yes, that's exactly what we need," you're halfway to winning. If they read it and think "that's not quite what we meant," you've just avoided a project that would have been a nightmare.
2. Scope of Work (1-2 Pages)
This is the most important section in the entire proposal. It defines exactly what you're building and โ just as importantly โ what you're not building. Be specific about:
- Number of pages: "Up to 8 pages: Home, About, Services (3 sub-pages), Contact, Blog listing"
- Design rounds: "Two design revision rounds included. Additional rounds billed at $X/hour"
- Content: "Client provides all written content. I provide layout, typography, and image selection"
- Functionality: "Contact form, newsletter signup, blog with CMS, Google Analytics integration"
- What's NOT included: "E-commerce functionality, membership system, custom API integrations, copywriting, stock photography licensing"
That last bullet is the one that saves your life. Most scope creep comes from assumptions. The client assumed e-commerce was included. You assumed they knew it wasn't. Spell it out.
3. Timeline (Half a Page)
Break the project into phases with dates (or "Week 1, Week 2" if you don't have a start date yet). Web design projects typically follow this flow:
- Week 1: Discovery & sitemap approval
- Week 2-3: Design concepts (2 directions) + revision round 1
- Week 4: Design revision round 2 + final design approval
- Week 5-6: Development + content integration
- Week 7: Testing, client review, revisions
- Week 8: Launch + 14-day post-launch support window
Include a note about what happens if the client delays: "Timeline assumes content is provided by [date] and feedback is returned within 3 business days of each review milestone. Delays on the client side will shift the launch date accordingly."
4. Investment (1 Page)
Break the pricing down by phase, not by page. Clients understand phases better, and it shows them what drives the cost.
- Discovery & Strategy: $800
- Design (2 concepts + 2 revision rounds): $2,400
- Development & Build: $3,200
- Testing, Launch & Training: $600
- Total: $7,000
Offer payment terms: 50% deposit to start, 25% at design approval, 25% at launch. This protects you if the project stalls.
Consider offering two tiers: a standard option and a premium option with additional features (extra design round, SEO setup, content migration, training session). Giving the client a choice between "yes" and "which yes" is always better than "yes or no."
5. Maintenance & Support (Half a Page)
What happens after launch? This is where you set expectations and potentially sell ongoing work. Options:
- 14-day post-launch support: Bug fixes, minor adjustments, questions. Included in the project price
- Monthly maintenance plan: Plugin updates, security monitoring, content updates, hosting management. $X/month
- Hourly support after the 14-day window: $X/hour, billed in 15-minute increments
Being clear about this upfront prevents the "can you just quickly change this text" emails that eat your time three months later.
6. Why You (Quarter Page)
Keep this short. 2-3 relevant projects with links. If you don't have relevant examples, show work that demonstrates transferable skills. A well-built restaurant site shows you understand responsive design and UX even if you're pitching a law firm.
Web Design Proposal Pricing: What to Charge
Pricing is the hardest part for most designers. Here's the honest breakdown:
Don't Price by the Page
"$500 per page" is a terrible pricing model. A contact form page takes 30 minutes. A custom services page with animations and interactive elements takes 2 days. Price by the project, not the page count.
Don't Compete on Price
If you're the cheapest option, you'll get clients who want the cheapest option. Those are the worst clients. They'll negotiate every line item, delay every milestone, and question every invoice. Price for the value you deliver, not the floor of the market.
Do Factor In Scope Risk
If the client is vague about what they want, that's scope risk. Build a 20% buffer into your price for vague projects. You can always come in under budget. You can't go back and ask for more money when the scope doubles.
Scope Creep: The Web Designer's Nemesis
Scope creep in web design is practically inevitable. The client sees the design, gets excited, and suddenly wants "just one more page" and "can we add a blog?" and "what about a login area?" Here's how to handle it in the proposal:
- Include a change request process: "Any additions or changes outside the scope outlined above will be quoted separately and must be approved in writing before work begins"
- Define what a revision is: "A revision is a change to the existing design direction. A new design direction is a new concept and will be quoted as additional scope"
- Set content deadlines: "Content must be provided by [date]. If content is not received by [date], the project timeline will be adjusted and a rush fee may apply for expedited completion"
- Limit revision rounds explicitly: "Two revision rounds are included. Additional rounds are $X per round"
The client won't fight you on these terms if you explain them upfront. They'll appreciate that you're organized and professional. The clients who do fight you on these terms are the ones who would have been a nightmare anyway. You just dodged a bullet.
How Clozr Helps With Web Design Proposals
Clozr takes your discovery notes, project scope, timeline, and pricing and structures them into a professional proposal document. The framework prompts you for the sections that matter โ including the "what's NOT included" section that most designers forget until scope creep hits.
What it does:
- Structures your scope into clear phases with deliverables and dates
- Formats pricing tables and payment terms automatically
- Prompts you for the change request process and revision limits
- Generates a branded PDF you can send to the client directly
What it doesn't do:
- Scope the project for you โ that comes from your discovery conversation
- Set your prices โ you define the value, Clozr handles the presentation
- Replace your design thinking โ the creative direction is yours
The value: instead of spending 3 hours formatting a proposal in Google Docs, you spend 45 minutes in Clozr and have a document that looks like it came from an agency five times your size.
๐ Try Clozr free for 14 days โ write your next web design proposal in under an hour
(P.S. The best web design proposal advice I ever got: if you can't describe what "done" looks like in one sentence, you're not ready to write the proposal. Go back and do more discovery.)