Most freelancers and small agencies lose projects before the first pixel is drawn. Not because their design skills are weak, but because their web design proposal reads like a shopping list of tasks instead of a business case. The client sees “5 pages, responsive, SEO basics, 2 revisions” and does the only thing they can do with a list: compare your price against the cheaper list next to it.
This guide breaks down the exact structure of a proposal that wins, section by section, with sample wording you can adapt today. We will also cover a three-tier pricing table that raises your average project value, payment terms that protect your cash flow, and the most common reasons proposals get rejected.
What a Web Design Proposal Actually Is (and Is Not)
A web design proposal is a short, structured document (PDF, slide deck or web page) that restates your client’s problem, defines the outcome you will deliver, sets the boundaries of the work, and states the price and terms. It is a sales document with contractual edges, not a technical specification.
Here is the distinction that matters most:
| A proposal is not… | A proposal is… |
|---|---|
| A quote (a number in an email) | A framed argument for why that number is a good investment |
| A contract (legal terms, liability, IP) | The commercial summary the contract will be built on |
| A portfolio dump | Two or three proof points that match this client’s situation |
| A 40-page document | 6 to 12 pages that a busy owner can read in 9 minutes |
The Golden Rule: Frame Value, Do Not List Tasks
Every line in your proposal should answer the silent client question: “And what does that do for me?” Tasks are inputs. Clients buy outputs.
| Task language (weak) | Value language (strong) |
|---|---|
| Responsive design across devices | Your 68% of mobile visitors get the same clear path to the quote form as desktop users |
| Speed optimisation | Target load under 2 seconds on 4G, the threshold where your current bounce rate spikes |
| CMS setup and training | Your team publishes a new service page in 15 minutes without calling us |
| Contact form integration | Every enquiry lands in your CRM with source tracking, so you know which page produced the lead |
Practical tip: write your deliverables list first as tasks, then rewrite each line with the words “so that” in the middle. Delete the “so that” afterwards and keep the second half in the sentence.
The 10 Sections of a Winning Web Design Proposal
1. Cover Page and Title
Put the client’s name before yours. It signals the document was written for them, not pulled from a folder.
Sample wording: “Website Redesign Proposal for Nordvik Dental Clinic. Prepared by [Your Studio], 24 August 2026. Valid for 21 days.”
The validity date is not aggressive, it is professional. It also prevents a client from resurfacing in eight months expecting the same rate.
2. Problem Restatement (the Mirror Section)
This is the single highest-leverage page in the entire document and the one most proposals skip. Before you talk about yourself, prove you listened. Restate the client’s situation in their own words, gathered from the discovery call.
Sample wording:
“During our call on 12 August, you described three issues. First, your current site was built in 2019 and your team cannot update prices without contacting the original developer. Second, roughly 70% of your traffic is mobile, but the booking form is unusable on a phone, and you estimate you lose 10 to 15 appointment requests per month. Third, you are opening a second location in January 2027 and the current structure has no way to present two clinics without confusing visitors. If we solved only one of these, you said the booking form would be the priority.”
When a client reads their own problem described more clearly than they could describe it themselves, price sensitivity drops. This is where trust is built, not in your portfolio.
3. Objectives and Success Metrics
Convert the problems into measurable goals. Three to five maximum. Attach numbers wherever the client gave you numbers.
- Increase mobile booking form completions from an estimated 22 per month to 40 per month within 90 days of launch
- Reduce time to publish a content update from 3 days to under 30 minutes, handled in-house
- Deliver a structure that supports two locations at launch and a third without a rebuild
- Achieve Core Web Vitals in the green on mobile for all key templates
Be careful: commit to metrics you influence, not metrics you do not control. “Increase revenue by 30%” depends on their sales team. “Form completion rate” depends on your design.
4. Proposed Approach (Your Process)
Clients fear the unknown middle of a project. A named, phased process removes that fear and quietly justifies your price. Keep it to four or five phases with a one-line description each.
- Discovery and content audit – stakeholder interviews, analytics review, inventory of existing pages worth keeping
- Structure and wireframes – sitemap, user flows, low-fidelity layouts for key templates
- Visual design – full design of key templates plus a component library for consistency
- Build and integration – development, CMS setup, forms, tracking, accessibility checks
- Launch and handover – testing, redirect map, training session, 30-day support window
5. Scope Boundaries: In Scope and Out of Scope
This section prevents 90% of future arguments. Use two explicit columns. The “out of scope” list is not negative, it is protective for both sides, and it creates natural upsell paths.
| Included in this project | Not included (available separately) |
|---|---|
| Design and build of 8 unique page templates | Additional templates beyond 8, quoted per template |
| Migration of up to 25 existing pages | Copywriting for new pages |
| Two rounds of revisions per phase | Photography, video production, illustration |
| Technical SEO foundations and redirect map | Ongoing SEO campaigns and link building |
| One 90-minute CMS training session (recorded) | Hosting, domain and third-party licence fees |
| 30 days of post-launch bug fixes | Monthly maintenance and updates retainer |
Sample wording for change requests: “Requests outside the scope above are welcome. They will be documented in a short change order with cost and timeline impact, and work continues once you approve it in writing. Nothing is invoiced without your approval.”
6. Deliverables
Be concrete. A deliverable is something the client can open, click or download. Vague deliverables invite disputes at the end.
- Sitemap and user flow document (PDF)
- Wireframes for 8 templates (Figma link, view access permanent)
- Full visual design files with a reusable component library
- Live website on your hosting, tested on the latest two versions of Chrome, Safari, Firefox and Edge, plus iOS and Android
- 301 redirect map from all old URLs
- Analytics and conversion tracking configured with 4 goals
- Recorded training video and a 6-page written CMS guide
7. Timeline and Milestones
Use business weeks, not fixed calendar dates, and tie the start date to two events: signature and deposit. Always include the client’s own obligations in the timeline, because client delay is the number one cause of overrun.
| Phase | Duration | What we need from you |
|---|---|---|
| Discovery | Week 1 | Analytics access, 2 stakeholder interviews |
| Structure and wireframes | Weeks 2 to 3 | Feedback within 3 business days |
| Visual design | Weeks 4 to 6 | Brand assets, final copy for key pages |
| Build and integration | Weeks 7 to 10 | Hosting and DNS access |
| Testing, launch, training | Week 11 | Sign-off within 5 business days |
Sample wording: “Timeline assumes feedback is consolidated into a single response per round and returned within 3 business days. Delays beyond 10 business days may require rescheduling into the next available production slot.”
8. Three-Tier Pricing Table
A single price forces a yes or no decision. Three options change the question from “should I hire them?” to “which one do I choose?” That shift alone lifts close rates and average deal size.
Structure the tiers so the middle one is the obvious fit, anchor high on the third, and never make the cheapest option embarrassing to buy. Name the tiers by outcome, not by size.
| Essential Launch Fast |
Growth (recommended) Built to Convert |
Performance Scale and Optimise |
|
|---|---|---|---|
| Templates designed | 5 | 8 | 12 + component library |
| Discovery workshop | 60 min call | Half-day workshop | Full-day + user interviews |
| Copywriting | Client provides | 3 key pages included | All pages included |
| Conversion tracking | Basic analytics | 4 goals + dashboard | Full funnel + heatmaps |
| Post-launch support | 30 days bug fixes | 60 days + 1 review call | 90 days + A/B test round |
| Investment | 4,200 EUR | 7,900 EUR | 13,500 EUR |
Three rules for this table:
- Change what is included, not just the quantity. Tiers that differ only by page count invite negotiation on page count.
- Label one tier “recommended” and say why in one sentence: “Based on your goal of 40 bookings per month, Growth is the tier we recommend.”
- Use the word investment, not cost. Small wording change, consistent psychological effect.
9. Payment Terms
Ambiguity here is what turns a won project into a cash-flow problem. State the schedule as a short list, not a paragraph.
- 40% deposit on signature. This reserves your production slot and is non-refundable once discovery begins.
- 30% on approval of visual design.
- 30% on launch, or 30 days after design approval if launch is delayed by factors outside our control.
- Invoices payable within 14 days. Late payments accrue interest at the statutory rate.
- Projects paused by the client for more than 30 days may be re-quoted at current rates.
Sample wording: “All amounts exclude VAT and third-party costs such as hosting, premium plugins, stock photography and domain fees. These are billed at cost with your prior approval.”
10. Proof, Next Step and Acceptance
Close with two or three relevant proof points, ideally from the same industry, each with a one-line result. Then make the next action unmistakable and single.
Sample wording: “To proceed, click Accept below or reply to this email with “approved”. We will send the deposit invoice and the contract the same day, and your project starts the following Monday. Our next available production slot is the week of 14 September 2026. If you would prefer to discuss the tiers first, here is my calendar link for a 20-minute call.”
Why Web Design Proposals Get Rejected
After reviewing hundreds of lost deals, the reasons cluster into a short list. Almost none of them are about design talent.
| Reason for rejection | Fix |
|---|---|
| It talks about you before it talks about them | Put the problem restatement on page 2, your bio on page 9 |
| A single price with nothing to compare it to | Three tiers with different inclusions |
| No scope boundaries, so the client fears endless invoices | Explicit in / out table and a change order clause |
| Sent 8 days after the call, when momentum died | Send within 48 hours, always |
| Jargon the decision maker does not understand | Write for the owner, put technical detail in an appendix |
| Too long, no summary, no visual hierarchy | One-page executive summary at the front |
| No deadline, so the decision is postponed forever | 21-day validity and a named production slot |
| Vague deliverables that leave the client guessing | List files, counts and formats |
| Sent and never followed up | Three-touch follow-up over 12 days |
Presenting the Proposal Beats Emailing It
Whenever the deal size justifies it, walk the client through the proposal live for 20 minutes, then send the file. Emailed proposals get skimmed to the price page. Presented proposals get discussed, and objections surface while you are still in the room to answer them. It is argued more carefully on feedbucket.app.
A simple script that works:
- “Before I go through this, let me repeat what I understood from our call. Correct me if I got anything wrong.”
- Walk through problems, objectives and approach. Pause for agreement after each.
- Show scope boundaries. Explain that this protects their budget.
- Show the three tiers, state your recommendation and the reason.
- Stop talking. Let them react to the price first.
Follow-Up Cadence That Does Not Feel Pushy
- Day 2: “Just confirming the proposal arrived. Happy to walk through any section.”
- Day 6: Add value, not pressure. Share a relevant case study or a quick observation about their current site.
- Day 12: “I am scheduling September production slots this week. Should I hold one for you, or would you prefer I release it?”
- Day 21: Polite close-out. “I will assume the timing is not right and close the file. The door stays open.”
Format, Length and Tools
Length: 6 to 12 pages for projects under 15,000 EUR. Beyond that, add appendices rather than bloating the main document.
Format options, in order of effectiveness:
- Web-based proposal with an accept button and view tracking. You see when it was opened and which sections were read.
- PDF with clickable table of contents. Universal, easy to forward internally, which matters when a committee decides.
- Slide deck for presented proposals, followed by a PDF version for the record.
Whichever you pick, build a master template once, then customise only the problem restatement, objectives and pricing per client. A good web design proposal should take you 45 to 90 minutes to produce, not a full day. If it takes longer, your template is doing too little work.
Quick Pre-Send Checklist
- Client name spelled correctly everywhere, including the file name
- Problem restatement uses at least three phrases the client actually said
- Every deliverable is countable or openable
- Out-of-scope table is present and specific
- Three pricing tiers with different inclusions, one marked recommended
- Payment schedule, currency, VAT status and payment window stated
- Validity date and next available start date included
- One single call to action, repeated at the end
- Read aloud once to catch jargon
FAQ
What are 5 things all proposals should include?
At minimum: a restatement of the client’s problem, clear objectives, a defined scope with what is excluded, deliverables and timeline, and pricing with payment terms. Everything else, including your portfolio and team bios, supports these five.
How long should a web design proposal be?
Six to twelve pages for most small business projects. The decision maker should be able to understand the offer in under 10 minutes. Put technical specifications, detailed browser support lists and legal terms in appendices.
Should I include the price in the proposal or send it separately?
Always include it. Sending a proposal without pricing creates a second round of emails and kills momentum. Present the price inside a three-tier table so it is read in context rather than in isolation.
What is an RFP for a website?
An RFP (Request for Proposal) is a document the client publishes describing their requirements, budget range and evaluation criteria, inviting agencies to respond. When you answer an RFP, mirror their exact section order and terminology, because responses are often scored against a checklist. There’s a fuller breakdown if you want the detail.
How many revisions should I offer?
Two consolidated rounds per phase is the standard that protects both sides. Define a round as one set of feedback gathered from all stakeholders, delivered in a single document. Additional rounds are billed hourly at your stated rate.
Should I use a free web design proposal template?
A template is a useful starting skeleton, but templates are generic by definition and clients recognise them. Use one for structure, then rewrite the problem restatement, objectives and pricing tiers from scratch for every prospect. Those three sections are where deals are won.
How fast should I send the proposal after the discovery call?
Within 48 hours. Interest decays quickly, and being first often matters more than being cheapest. If you cannot deliver a full document in that window, send a one-page summary of what you understood and confirm the full proposal date.
What if the client says the price is too high?
Never discount the same scope. Reduce the scope instead: move to the lower tier, remove copywriting, cut template count, or phase the project across two budgets. Discounting without changing scope tells the client your first price was invented.
Final Word
A winning web design proposal is not a longer document, it is a better-framed one. Restate the problem so precisely the client feels understood, draw hard boundaries around the work so nobody is anxious, give three ways to say yes, and make the next step obvious. Do that consistently and you stop competing on price and start competing on clarity, which is a much easier fight to win.