How to write a design proposal clients can say yes to
A good proposal does not need a long deck. Here is what to include, how to present your price, and how to make it easy for a client to approve.
Many design proposals lose before the client reaches the price. They open with three pages about the studio, follow with a generic process diagram, and bury the part the client cares about somewhere near the end. The client skims, can't compare it to the other quote in their inbox, and replies "we'll get back to you."
A proposal has one job: to help a specific person make a decision with confidence, and often to help them explain that decision to someone else. Here's how we'd structure one, from the call before you write it through to the moment they sign. It works for a single Framer site as well as a larger brand project.
Don't write it until you've had the call
Most weak proposals are really weak discovery. If you don't know why the project matters now, you can only sell hours and deliverables. Before you open a document, make sure you can answer these questions:
- What's prompting this project now, and what happens if nothing changes?
- How will they judge whether it worked?
- Who else has a say, and who signs off?
- What's their deadline, and is it a real one?
- Have they set aside a budget, even a rough range?
Asking about budget feels awkward, but it saves everyone time. If they won't name a figure, offer ranges: "Projects like this usually fall into one of three levels. Which is closest to what you had in mind?"
Open with their problem, in their words
The first section should show that you listened. Skip the company history and write two or three sentences that restate the situation and the goal, using the terms they used on the call:
You're launching your paid plan in March, and your current site explains the product but doesn't lead visitors to sign up. You want a site your team can update without a developer, live two weeks before launch.
When a client reads that, they know this document was written for them. It also gives you a chance to catch misunderstandings early. If you've got the goal wrong, it's far better to find out here than in the second round of revisions.
Describe the result, then the work
Clients buy an outcome, but they sign off on a scope, so your proposal needs both. Start each phase with what they'll have at the end, then list what it includes:
- Weak: "Homepage design, 3 rounds of revisions."
- Stronger: "A homepage that explains the paid plan and leads to sign-up, designed in Figma and built in Framer, with two rounds of revisions."
Be just as clear about what's excluded. A short "not included" list covering items like copywriting, photography, custom integrations or ongoing maintenance prevents arguments later. It also opens a natural conversation if the client assumed one of those was part of the deal.
Offer options instead of one price
A single price invites a yes or no. Two or three options change the question to "which one fits us best?" and give the client a way to manage their budget without asking you for a discount. A simple structure might look like this:
- Essential: the smallest version that meets the main goal.
- Recommended: what you'd actually advise, with a sentence on why.
- Extended: the recommended scope plus extras such as more pages, CMS setup or training.
Each option should differ in scope, not only in price. If a client wants to pay less, something should come out, and that keeps your pricing honest. Don't pad the list with a third option you'd hate to deliver, since someone may well choose it.
Use a timeline that depends on them too
Show the phases with rough dates and mark what you need from the client at each point: content by this date, feedback within this many working days, one person to consolidate comments. Then state plainly that dates move if inputs arrive late.
This protects your schedule, and it also shows the client what the project will require of them. Clients usually appreciate knowing this up front, especially when their own team is busy. Express start dates in terms of signature and deposit: "We can begin the week after the agreement and first payment are in."
Keep proof short and relevant
Include one or two past projects that resemble this one, with a line on the situation and the result. Only use results you can actually support, and only share client work you have permission to show. If you don't have a similar case, describe your approach to the riskiest part of this project. That's more convincing than a gallery of unrelated work, and it takes up far less room.
Set the terms and make the next step obvious
End with the commercial details: price, payment schedule, how long the proposal stays valid, what counts as a revision and how extra work gets charged. Keep them readable, and have a proper contract ready for larger projects. If the terms carry real risk, it's worth having a lawyer in your country check your template once.
Then tell them exactly what to do: "Choose an option and reply to this email, and I'll send the agreement and first invoice the same day." Vague endings like "let me know your thoughts" invite more delay.
Walk them through it, then follow up
Whenever you can, present the proposal on a short call instead of just emailing it. You'll see where they hesitate and can answer questions right away. If you do send it first, keep the email to a few lines with the recommended option and the deadline stated clearly.
Agree when you'll talk next before you end the conversation, and follow up on that day with something brief. Silence usually means they got busy, not that they've said no.
Shorter is usually better
A proposal that fits on three or four pages and answers "what do I get, what does it cost, when is it ready and what do I do next?" will beat a beautiful thirty-page deck that hides those answers. Save your best sections as a template, rewrite the opening for every client, and keep track of which proposals turn into projects. After a few rounds, you'll know what actually persuades your clients.
