How to Write a Web Design Proposal That Wins the Project

Most web designers lose projects at the proposal stage — not because their quote was too high, but because their proposal did not make a case for why the price was worth it. A proposal is not a price list. It is an argument. It tells the client: here is what I understood about your situation, here is what I am going to do about it, and here is what that is worth.

When a proposal reads like a brochure ("we offer premium web design solutions with a customer-first approach"), the client has no way to evaluate it except by price — and on price alone, you will often lose to someone cheaper. Here is a structure that changes that dynamic.

Why proposals matter even for small projects

New freelancers often skip proposals for smaller jobs. "It's just a €600 site — I'll just send them a price." The problem is that without a written proposal, there is no shared understanding of what €600 includes. The client imagines something; you imagine something different. By week three, one of you is disappointed.

A proposal also signals professionalism. It shows you have thought about their specific situation rather than pasting in a template. For a client choosing between two freelancers of similar price, the one who sends a clear, considered proposal wins almost every time.

The wrong approach: sending a price list

A common new-freelancer mistake is sending a rates card or a bulleted list of services with prices. "Homepage: €400. About page: €150. Contact page: €100." The client reads this as a menu — and starts wondering whether they really need all of those pages, whether they could get away with just a homepage, and whether your per-page rate is competitive with the other designer they are talking to.

A rates card answers the question "what does it cost?" before the client is convinced of the answer to "why should I work with you?" Get the second question answered first.

The proposal structure that works

1. Understanding / problem restatement

Open by demonstrating that you listened. Summarise the client's situation in your own words: their business, the specific problem they have described, what success looks like for them. This is not a restatement of their email back to them — it is proof that you processed it, thought about it, and understood what matters.

This section should be specific. Not "you need a new website to improve your online presence." Something like: "Your current site doesn't load properly on mobile and hasn't been updated since 2019. You're getting enquiries through word of mouth but suspect you're losing leads who look you up online and can't find clear information about what you offer or how to get in touch. The goal of this project is to fix that."

Clients who feel understood are far more likely to trust you with their project. This section is your highest-leverage investment in the proposal.

2. Your proposed solution

Describe what you are going to build and why. Not just "a five-page website" — explain the thinking. "The homepage will be structured to answer the three questions visitors always have: what you do, who it's for, and how to get started. The services page will break down your three main service types clearly, with FAQs to handle the objections that typically come up in sales calls." This shows you have thought about their business, not just their website.

3. Scope of work

List every deliverable specifically. Pages, features, integrations, and — importantly — what is not included. "Copywriting is not included; client to provide all text content by [date]. Stock photography licence is included for up to ten images. Custom photography is not included." Clear scope prevents the scope creep conversations later. See the client management guide for why this matters.

4. Timeline

Give a realistic end date, broken into phases with milestones: design review, development, testing, launch. Be explicit about client dependencies: "Timeline assumes delivery of all copy and images by [date]. Client delays will push the launch date accordingly." This is not aggressive — it is professional. It also subtly communicates that you run a structured process, not an ad-hoc service.

5. Investment / pricing

Use the word "investment," not "cost" or "price" — it frames the spend as producing a return rather than an expense. Present a clear total with a line-item breakdown so the client understands what they are paying for. Then state payment terms: "50% deposit to begin, 50% on launch day before handover of files."

If you are offering packages, present all three options here — but make the middle tier the obvious choice by making it the most detailed and by positioning the premium tier slightly out of reach. Most clients pick the middle. See the pricing guide for how to structure tiers that work.

6. About you / trust signals

Keep this short. Two paragraphs, not a biography. One or two relevant past projects (with results if you have them), a brief statement of what you specialise in, and a sentence on your process or approach. The goal is not to impress — it is to reassure. The client wants to know you have done this before and you are not going to disappear mid-project.

7. Next steps

End with a single clear action. "To get started: reply with any questions, or sign the attached contract and send the 50% deposit — I'll block your start date in my schedule and we'll kick off on [date]." One action. Not "let me know what you think" or "feel free to reach out if you want to discuss further." Give them a clear path to yes.

Writing the "understanding" section to show you actually listened

The understanding section is where most proposals fail or succeed. To write it well, take proper notes on the discovery call. Before the call, prepare questions: What has made the current site a problem? What do your customers ask about when they contact you? What does success look like six months after launch? What have you tried before?

Then write that section immediately after the call, while the details are fresh. Use the client's own language where you can — if they described their business as "the go-to accountant for freelancers in Dublin," quote that back. It signals you were paying attention to more than the technical brief.

Presenting pricing with confidence

Anchoring matters. If your proposal describes a well-considered, thorough project and then presents a number, the number feels earned. If the proposal is thin and the first substantive thing the client reads is the price, the number feels arbitrary.

For itemised vs. lump sum: show a light breakdown (design, development, SEO setup) to justify the total, but present one total number rather than twenty line items. Too many line items invite the client to start deleting items to bring the price down. One total with a brief breakdown keeps the conversation at the level of "does the whole thing make sense" rather than "do I really need that?"

Common proposal mistakes to avoid

• Too long. If your proposal exceeds six pages for a standard small business site, it will not be fully read. Cut anything that is not directly relevant to the client's specific project.
• Too technical. The client does not need to understand CSS specificity or how you handle DNS transfers. Describe outcomes, not technical process.
• Too vague. "A professional website tailored to your needs" tells the client nothing. Be specific about pages, features, and deliverables.
• No clear CTA. Ending a proposal with "let me know your thoughts" leaves the client with no clear next step. Tell them exactly what to do if they want to proceed.
• Leading with your credentials. Clients do not open a proposal to read your bio. They open it to find out if you understood their problem. Put your credentials last, briefly.

Tools: what actually works

For most new freelancers, a well-formatted Google Doc or PDF is more than enough. It is free, looks professional, and is easy to update between proposals. For a more polished experience, Notion pages sent as links give clients a clean reading experience and let you see when they have opened it.

HoneyBook, Dubsado, and Bonsai offer proposal-plus-contract-plus-invoice workflows in one place — useful once you are sending enough proposals to justify the subscription. They are not necessary at the start. Canva templates can help if visual presentation matters for the client, but a well-written plain-text proposal from an experienced freelancer will almost always beat a beautifully designed one that says nothing specific.

For pricing, the website ROI calculator is a useful tool to include with proposals for clients who are uncertain about value — it helps them frame the investment against what the site could realistically generate in leads.