Most web design projects don’t fall apart because of the work itself — they fall apart before the work even starts. A vague brief, a misunderstood scope, or a client who had a completely different budget in mind. A solid proposal doesn’t just outline what you’re going to build. It sets the terms of the relationship before a single line of code or design is produced.
In my experience, a well-structured proposal does more to win clients than a portfolio does. Clients expect you to have good work to show. What they don’t expect is someone who can explain exactly what they’re going to do, why, and for how much — in a document that reads clearly and professionally.
This guide covers what to include in a web design proposal, how to structure it, and the mistakes that cost freelancers work.
Quick Answer
A strong web design proposal includes: a summary of the client’s problem, your proposed solution, the scope of work, timeline, pricing, and your terms. Keep it focused and specific to the client — generic proposals get ignored. The goal is to show you understood the brief and can deliver a clear outcome.
Why Proposals Matter More Than Most Freelancers Think
A proposal is often the first piece of professional writing a potential client sees from you. Before they’ve seen you work, before they’ve spoken to a reference, they’re reading your proposal and forming a view of whether you’re someone they can trust with their project.
A proposal that’s too short looks like you didn’t think about the project. One that’s too long loses the client halfway through. The sweet spot is a document that answers every question the client is likely to ask — scope, cost, timeline, what happens if things change — without padding or filler.
The Freelancers Union offers useful resources on contracts and client relationships that complement what a proposal needs to do. A proposal isn’t a contract, but it’s the document that leads to one.
What to Include in a Web Design Proposal
1. Introduction and Problem Summary
Start by summarising what the client needs and why they came to you. This shows you listened during the brief and understand their situation. Keep it short — two to three sentences. The goal is to make the client think “yes, this person gets it.”
For example: “You’re launching a new landscaping business and need a website that generates local enquiries. Your current online presence is limited to a Facebook page, and you want a professional site that ranks for local searches and converts visitors into calls.”
2. Proposed Solution
Describe what you’re going to build and why it solves the client’s problem. Be specific. Don’t write “a modern website with great design” — write “a five-page WordPress website with a homepage, services page, about page, gallery, and contact page, designed for mobile users and optimised for local SEO.”
This section should reference the pages the site will include. If you’re building a WordPress site, knowing which pages every website needs helps you make sure nothing is missed from the scope.
3. Scope of Work
The scope section is the most important part of the proposal for protecting yourself. It defines exactly what is and isn’t included. Be explicit:
- How many pages are included
- Whether copywriting is included or the client provides it
- Whether photography or stock images are included
- How many rounds of revisions are included
- Whether ongoing maintenance is included after launch
Anything not listed in the scope can be treated as out of scope — and charged for separately if the client requests it later. Scope creep is the most common source of conflict on web design projects. A clear scope section prevents most of it.
4. Timeline
Break the project into phases and give a realistic timeframe for each. A typical small WordPress project might look like this:
- Discovery and planning — 1 week (brief, sitemap, content collection)
- Design — 1–2 weeks (wireframes, homepage design, feedback round)
- Development — 1–2 weeks (build in WordPress, mobile testing)
- Review and revisions — 1 week (client feedback, amendments)
- Launch — 1–2 days (DNS, final checks, go live)
Always note that the timeline assumes timely feedback and content delivery from the client. Delays on their side push the timeline back — and that needs to be stated clearly upfront.
5. Pricing
Present the total cost clearly. If you’re itemising, keep it simple — don’t break everything down into hourly estimates that give the client room to negotiate individual line items. A fixed project price is easier for clients to evaluate and easier for you to manage.
If your proposal includes optional extras — SEO setup, logo design, ongoing maintenance — list these separately as add-ons with their own prices. This lets the client upgrade without reopening the core negotiation. For guidance on setting your rates, pricing your web design services covers the main approaches and what to consider.
6. Terms and Next Steps
End with your key terms and a clear call to action. Include:
- Deposit required to begin (typically 30–50% upfront)
- Payment schedule (e.g. 50% on start, 50% on launch)
- What happens if the project is cancelled mid-way
- Who owns the final files and code after payment
- How the client accepts the proposal (reply, sign, or use a tool like DocuSign)
A signed proposal — or an email confirming acceptance — is the trigger for starting work and issuing the first invoice.
Practical Tips for Better Proposals
Personalise every proposal. A generic template sent to every client reads like a generic template. Spend five minutes adapting the introduction and proposed solution to the specific client. It makes a significant difference to how the proposal lands.
Keep it to one or two pages. Most clients don’t read long proposals. A focused, well-structured two-page proposal wins more work than a ten-page document full of padding. Say what you need to say and stop.
Send it as a PDF. A PDF looks professional, can’t be accidentally edited, and opens cleanly on any device. Don’t send a Word document.
Follow up. If you haven’t heard back within three to five business days, send a short email checking whether the client has any questions. Most proposals are lost to inaction, not rejection.
Set an expiry date. Include a line stating the proposal is valid for 14 or 30 days. This creates a soft deadline and prevents clients from coming back six months later expecting the same price.
Common Mistakes to Avoid
Being too vague about scope. “A website” is not a scope. Every ambiguity in the proposal will come back as a dispute during the project. The more specific the scope, the better protected you are.
Leading with your portfolio. Your portfolio belongs on your website, not at the top of a proposal. The proposal should lead with the client’s problem, not your credentials.
Underpricing to win work. A proposal priced below market rate attracts clients who value cost over quality. Price your work based on the value you deliver, not what you think the client wants to pay. For more on this, how to price web design services covers the key methods.
Skipping terms. Proposals without payment terms and revision limits leave you exposed. Even a short terms section removes most of the ambiguity that leads to difficult client situations.
When to Use Proposal Software
For simple projects, a PDF proposal built in Google Docs or Canva works fine. As your projects grow in size and complexity, dedicated proposal tools like Bonsai, HoneyBook, or Proposify add features like digital signatures, viewing tracking (you can see when the client opened it), and integrated invoicing.
These tools are worth considering once you’re sending proposals regularly — they reduce admin and give the client a smoother experience. For most freelancers starting out, a clean, well-written PDF is enough.
Conclusion
Write a specific introduction that shows you understood the brief, define your scope clearly, state your price without apology, and include your terms. Those four things are enough to produce a proposal that performs. If you’re still setting up the freelance side of your business, setting up your freelance web design website covers how to position yourself and attract the right clients from the start. Building a professional web presence is one of the first steps covered in the step-by-step guide to building a WordPress website.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.