Most designers lose work in the proposal, not in the pitch. The call goes well, the client says “send me something over”, and then the document lands in their inbox looking like a price list with a logo on top. Silence follows.
A proposal is not a quote. It is a sales document that proves you understood the problem, mapped the path to solving it, and removed every reason to hesitate. This guide breaks down exactly how to write a design proposal that converts, section by section, with the wording that makes clients sign instead of ghost.
Before You Write a Single Word: The 20-Minute Rule
Never write a proposal from a brief alone. Every proposal that wins starts with a conversation, even a short one. Before you open a blank document, you need:
- The business problem behind the design request (not “we need a new website” but “our enquiries dropped 40% and the site looks dated next to competitors”)
- The decision maker and who else needs to approve
- The deadline and what is driving it (a launch, a trade show, an investor round, a season)
- The budget range, even an approximate one
- What they have tried before and why it did not work
A useful line to use on the discovery call: “Before I put a proposal together, can I ask what would have to be true in six months for you to say this project was a success?” The answer becomes the backbone of your document.
Rule of thumb: if you cannot quote the client back to themselves in the proposal, you are not ready to write it.
The 9 Sections Every Winning Design Proposal Needs
Here is the structure we use and recommend to freelancers and small studios. It works for web design, branding, interior design, graphic design and UI/UX projects.
| # | Section | Job it does | Length |
|---|---|---|---|
| 1 | Cover and personalised intro | Signals this was written for them | 1 page |
| 2 | Problem statement | Proves you listened | 150 to 250 words |
| 3 | Goals and success metrics | Defines what “done well” means | Short list |
| 4 | Proposed approach | Shows method, reduces risk | 1 page |
| 5 | Scope and deliverables | Prevents scope creep | 1 to 2 pages |
| 6 | Timeline and milestones | Makes the project feel real | 1 page |
| 7 | Investment and pricing tiers | Moves the question from “if” to “which” | 1 page |
| 8 | Proof: you, your team, past results | Builds trust | 1 to 2 pages |
| 9 | Terms and next steps | Removes friction to signing | 1 page |
1. Cover Page and Personalised Introduction
The cover sets expectations about the quality of your work before anyone reads a word. Keep it clean: project name, client name, your studio name, date, and a validity period.
Then open with a short paragraph that could only have been written for this client. Reference the call, the date, and one specific thing they said. See creativemarket.com for their take.
Weak: “Thank you for considering our agency for your web design needs.”
Strong: “Hi Maya, thanks for the call on Tuesday. You mentioned that 70% of your bookings now come from mobile, but your current site was built for desktop first and loses people at the enquiry form. This proposal is built around fixing exactly that.”
Add a validity line underneath: “This proposal is valid for 21 days from the date above.” It creates a gentle deadline without pressure tactics.
2. The Problem Statement (Written in Their Words)
This is the single highest-leverage section and the one most freelancers skip. Before you talk about yourself, restate the client’s situation so accurately that they nod while reading.
Structure it in three beats:
- Current situation: what exists today, factually and without judgement
- The friction: what it is costing them in revenue, time, credibility or staff hours
- The stake: what happens if nothing changes in the next 6 to 12 months
Example wording: “Your current site was built in 2019 and has grown to 46 pages, many of which no longer reflect what you sell. Your team spends roughly 4 hours a week answering questions that the site should answer. Meanwhile, two newer competitors rank above you for your main service terms. Left unchanged, you continue paying for traffic that converts below its potential.” Much the same conclusion turns up on rohirrim.ai.
Notice there is no design jargon. The problem is always a business problem. Design is the answer, not the subject.
3. Goals and Success Metrics
Turn the problem into measurable outcomes. This protects you later: when the client’s cousin says “I don’t like the blue”, you can point back to agreed objectives. The piece Design Proposal Templates makes a good next read.
- Primary goal: increase enquiry form completions from mobile
- Secondary goals: reduce page load to under 2 seconds, allow the team to update content without a developer
- Success looks like: a 25% lift in enquiries within 90 days of launch, measured in analytics
Be careful with promises. Use “designed to” and “targeting” rather than guarantees on numbers you do not fully control.
4. Your Proposed Approach
Clients are not buying files. They are buying certainty that the process will not be chaotic. Lay out your phases in plain language, each with a purpose and an output.
| Phase | What happens | What you receive |
|---|---|---|
| 1. Discovery | Stakeholder interview, competitor review, content audit | Creative brief and sitemap |
| 2. Concept | Moodboards, direction options, key page wireframes | 1 approved creative direction |
| 3. Design | Full page designs, mobile and desktop | Figma file with components |
| 4. Build | Development, content migration, testing | Staging site for review |
| 5. Launch and handover | Go live, redirects, analytics, training | Live site and recorded training |
Add one line per phase about what you need from them. Clients respect a process that names their responsibilities, and it quietly protects your timeline.
5. Scope and Deliverables (Plus What Is Not Included)
Vague scope is the number one cause of unprofitable projects. Be specific with quantities and formats.
Included in this engagement:
- 8 unique page designs (home, services, 3 service detail, about, case studies, contact)
- Responsive layouts at 3 breakpoints
- Design system: typography scale, colour tokens, 12 reusable components
- 2 rounds of revisions per phase
- Source files handed over on final payment
Not included (available as an add-on):
- Copywriting and content creation
- Photography and video production
- Ongoing SEO, ads or maintenance after the 30-day support window
- Third-party licences, plugins, hosting and stock assets
The exclusions list feels uncomfortable to write and is the most valuable paragraph in the whole document. Pair it with a change policy: “Requests beyond the scope above are welcomed and quoted separately at $XX per hour, or as a fixed-price addendum, before any work begins.”
Define a “round of revisions”
Spell it out: “A revision round means one consolidated set of feedback from your side, collected from all stakeholders and delivered in a single document or comment thread within 5 working days.” This one sentence prevents weeks of drip-fed edits.
6. Timeline and Milestones
Show a realistic schedule in weeks, not exact calendar dates, unless the start date is confirmed. Always tie dates to client feedback windows.
| Week | Milestone | Client action needed |
|---|---|---|
| 1 | Kickoff and discovery | Provide brand assets and access |
| 2 to 3 | Concept direction presented | Feedback within 5 working days |
| 4 to 6 | Full design delivery | Consolidated feedback, final copy |
| 7 to 9 | Build and QA | Staging review and sign-off |
| 10 | Launch and training | Final approval and payment |
Add the safety clause: “Timelines assume feedback is returned within the stated windows. Delays in feedback shift subsequent milestones by an equivalent number of working days.”
7. Investment: Use Three Pricing Tiers, Not One Number
A single price invites a yes or no decision. Three options change the question to “which one?” and reliably increases average project value.
Use the word investment rather than “cost” or “price”, and always list the outcome next to the number.
| Option | Best for | What is included | Investment |
|---|---|---|---|
| Essential | Getting live fast | 5 pages, 1 concept direction, 1 revision round | $X,XXX |
| Recommended | Most clients in your position | 8 pages, design system, 2 revision rounds, CMS training, 30-day support | $XX,XXX |
| Growth | Teams who want results tracked | Everything above plus copywriting, SEO setup, 3 months of optimisation | $XX,XXX |
Three rules that make tiers work:
- Label the middle option “Recommended” and explain in one sentence why it fits their specific problem
- Never remove quality from the cheaper tier, only remove quantity and scope, so you are not selling a worse version of yourself
- Show the payment schedule directly underneath, for example 40% to book the start date, 30% at design approval, 30% before launch
If you work hourly or on retainer, state the rate, the minimum block, and how you report time. Ambiguity here is what clients remember when the first invoice arrives.
8. Proof: Who You Are and What You Have Delivered
Now, and only now, talk about yourself. Keep it relevant rather than exhaustive.
- One short bio or studio paragraph tied to the client’s industry
- Two or three mini case studies with a before, an action and a result in numbers
- One testimonial from a similar client, with a full name and company
- Named team members for the project, if you are a studio, so the client knows who they will actually speak to
Case study formula that works: “A boutique villa operator in Canggu was losing direct bookings to OTAs. We rebuilt the booking flow and reduced steps from 7 to 3. Direct bookings rose 38% in the first quarter after launch.”
9. Terms, Assumptions and the Next Step
Finish with the practical details, written in human language rather than heavy legalese:
- Payment terms: deposit, schedule, invoice due in 7 or 14 days, late fee
- Ownership and IP: transfers on final payment; you retain the right to display work in your portfolio
- Cancellation: work completed to date is billable, deposit non-refundable
- Support window: what is covered after launch and for how long
- Assumptions: client provides content by a set date, one point of contact, access to accounts
Then close with a single, obvious next action. Do not end on terms.
Closing wording that converts: “To move forward, select your preferred option and sign below. I will send the kickoff questionnaire and invoice for the deposit the same day, and we can begin on Monday the 26th. I currently hold one project slot for November.”
One call to action. One button or signature field. No “let me know your thoughts”, which invites a thought instead of a decision.
Wording That Wins vs Wording That Gets Ghosted
| Instead of this | Write this |
|---|---|
| “We will design a modern, beautiful website.” | “We will rebuild the booking flow so mobile visitors can enquire in three taps.” |
| “Cost: $8,000” | “Investment: $8,000, payable 40/30/30 across three milestones.” |
| “Unlimited revisions” | “Two consolidated revision rounds per phase, with additional rounds at $X each.” |
| “Let me know if you have any questions.” | “Sign below to confirm, or book 15 minutes here if you want to walk through the options.” |
| “Delivery in 4 to 8 weeks” | “Launch in week 10, assuming feedback within 5 working days at each milestone.” |
Format and Delivery: Small Details, Big Difference
- Keep it to 6 to 12 pages. Long proposals signal that you are padding. Put heavy detail in an appendix.
- Send a link, not just a PDF. Web-based proposals let you see when it was opened and which sections were read. Attach a PDF as a backup for clients who forward documents internally.
- Design the document. You are a designer. The proposal is a free sample of your work. Typography, spacing and hierarchy matter more than stock imagery.
- Send it within 48 hours of the call, while the conversation is still warm.
- Never send it without a note. A two-line email or voice message explaining your recommendation lifts response rates considerably.
The follow-up sequence
- Day 0: send the proposal with a short summary of your recommended option
- Day 3: “Checking you received this. Happy to walk through the scope if it helps.”
- Day 7: add value, not pressure. Share a relevant example or a quick observation about their site.
- Day 14: mention the validity date and your next available start slot
- Day 21: a polite close-out: “I will assume the timing is not right for now. Shall I check back in Q1?”
Most signed projects we see come from follow-up two or three, not from the original send.
Seven Mistakes That Kill Design Proposals
- Leading with your bio. The client cares about their problem first.
- Listing deliverables with no outcome attached. “12 social templates” means nothing without “so your team can post consistently without a designer”.
- One price, take it or leave it. Tiers keep the conversation alive.
- No exclusions. Everything you do not write down will be assumed as included.
- Design jargon. Atomic design, grids and tokens impress other designers, not buyers.
- Template smell. If the client can tell you reused it, you lose the trust advantage immediately.
- A weak ending. “Looking forward to hearing from you” is where momentum dies.
Quick Pre-Send Checklist
- Does the first page mention the client’s situation in their own words?
- Is every deliverable attached to a benefit?
- Are quantities specified (pages, concepts, rounds, formats)?
- Is there an exclusions list and a change-request policy?
- Are three pricing options shown, with one recommended?
- Is the payment schedule and deposit stated clearly?
- Are timelines conditional on client feedback windows?
- Is there exactly one call to action at the end?
- Have you proofread names, company spelling and currency?
- Is the file named professionally, for example Proposal_ClientName_WebsiteRedesign.pdf?
Frequently Asked Questions
What are 5 things all proposals should include?
At minimum: a clear problem statement, your proposed solution and approach, a defined scope with deliverables, a timeline with milestones, and pricing with terms. Everything else, from case studies to appendices, supports these five.
What are the 7 main parts of a project proposal?
Introduction, problem statement, objectives, proposed solution and methodology, scope and deliverables, schedule and budget, and conclusion with next steps. A design proposal follows the same skeleton with added visual proof and pricing options.
What is a proposed design?
A proposed design is your recommended solution to the client’s problem, described before any production work begins. In a proposal it usually appears as a written approach plus supporting references such as moodboards, wireframe sketches or a sitemap. It is a direction, not a finished design.
How long should a design proposal be?
Six to twelve pages for most freelance and small studio projects. Enterprise or tender responses may require more, but add length only where the client has requested specific documentation.
Should I include free design concepts in my proposal?
No. Speculative work lowers your perceived value and encourages clients to compare visuals instead of strategy. Show relevant past work and your process instead. If a client insists on concepts, quote a paid discovery or concept phase.
How much should I charge for a design proposal?
The proposal itself should be free. The research behind it does not have to be. For complex projects, sell a paid discovery sprint that produces a brief, sitemap or audit, then roll that fee into the main project if they proceed.
What tools are best for writing design proposals?
Proposal platforms with e-signature and tracking work best for conversion. Many designers build a branded master template in Figma, Canva or Google Docs and export to PDF. Whatever you choose, make sure it supports electronic signing and a clear payment link, since every extra step between “yes” and “signed” costs you deals.
How do I follow up without sounding desperate?
Follow up on a fixed schedule, add something useful each time, and give the client an easy way to say no. A line such as “If the timing is not right, just reply NO and I will close the file” frequently unlocks a reply and sometimes a yes.
Turn Your Proposal Into a Sales Asset
Learning how to write a design proposal is really about learning how to think like a buyer. Clients are not comparing your visuals to other designers. They are weighing risk: will this person understand my business, deliver on time, and stay inside the number we agreed?
Answer those three questions on every page and the signature becomes a formality. Build the 9 sections above into a master template once, then spend your time customising the first three sections for each client. That is where projects are won.
Need a second pair of eyes on your proposal, or a design partner for a project you have just quoted? Get in touch with our team and we will take a look.