Memorisely
Design Business

Writing design proposals that win

A simple structure that makes saying yes easy.

Zander Whitehurst

7 min read

A proposal is where a good conversation turns into paid work. It is also where many projects quietly die. Long documents, vague scopes and confusing pricing give clients reasons to hesitate. A good proposal does the opposite. It makes saying yes feel easy and obvious.

My early proposals were enormous. Twenty pages, a history of my career, a page about my design philosophy and a mood board nobody asked for. I was very proud of them. Clients, it turned out, mostly skipped to the last page to find the price. Lesson learned.

Have the conversation first

The best proposals are written after a proper conversation. Never send a proposal based on a single email if you can avoid it. Get on a call and understand:

  • What problem the client is trying to solve
  • Why it matters right now
  • What success looks like
  • Who makes the final decision
  • Roughly what budget they have in mind

The proposal should feel like a summary of what you agreed, not a surprise.

Lead with their problem, not your process

Start the proposal by reflecting the client's situation back to them in their own words. Show that you listened and understood.

A short paragraph explaining their challenge and the goal of the project is far more persuasive than a page about your methodology. Clients care about their problem first. Your process matters only because it solves it.

Describe the outcome

After the problem, explain what will be different once the project is finished. A clearer onboarding flow that helps more people get started. A brand that feels credible to investors. A design system that helps the team ship faster.

Outcomes help clients justify the investment to themselves and to anyone else they need to convince.

Be clear about scope

Scope is where misunderstandings start. Be specific about what is included:

  • The deliverables you will produce
  • The number of revision rounds
  • What the client needs to provide
  • What is not included

That last point matters more than people think. A short "not included" list prevents a lot of awkward conversations later.

Show a simple timeline

Break the project into a few clear phases with rough timings. Discovery, design, refinement and handover is a common pattern. Clients want to know when they will see work and when the project will be finished.

Keep it realistic. I always add a little buffer, because feedback rarely arrives as quickly as everyone hopes. Usually because somebody important is on holiday.

Four clear phases with a little buffer tell the client when they will see work and when it ends.

Offer options

Presenting three options rather than one price changes the conversation. Instead of deciding whether to hire you, the client decides which version suits them best.

A typical structure might be:

  • Essential. The core work needed to solve the problem.
  • Recommended. The core work plus the things that make it really successful.
  • Complete. Everything, including extra support or deliverables.

Make the recommended option the one you genuinely think is best. Most clients choose it.

Three clear options shift the question from whether to hire you to which version fits.

Keep pricing simple

Show the price for each option clearly. Include payment terms, such as a deposit to start and the remainder at agreed milestones. Avoid long lists of line items with individual prices, as they invite clients to start picking things off.

If you mention prices, write them in a way that is easy to read, for example £4,500 rather than a long breakdown of hours.

Make the next step obvious

End the proposal with exactly what happens next. Something like "To get started, reply to confirm your option and I will send the contract and deposit invoice." Remove every bit of friction between yes and starting.

I also like to include a date the proposal is valid until. It gently encourages a decision and protects you if your availability changes.

Keep it short

Most winning proposals I have written fit on three or four pages. Clear headings, short paragraphs and plenty of white space. If a client can understand the whole thing in five minutes, you are in a good place.

Follow up kindly

Send the proposal, then follow up a few days later if you have not heard anything. Offer to talk it through on a quick call. Often the client has a small question that is holding them back, and a two minute chat clears it up.

Start with a template

Create a simple proposal template with sections for the problem, outcome, scope, timeline, options and next steps. Use it for your next proposal and pay attention to what questions clients ask. Each question is a sign that something could be clearer next time. Proposals, pricing and client process are all part of our Build Your Design Business Bootcamp.

Keep reading

View all
View all

Optimize your AI for better experiences, not AI slop.

View all

AI Prototyping Skills

Prototype with AI using clean UI patterns and guardrails so flows feel product-grade, not generic template slop.

$99

AI UI Motion Skills

Motion and micro-interaction patterns that make AI-built UI feel designed, polished, and trustworthy in real products.

$99

Fix AI Slop Skills

Spot AI slop early and fix type, spacing, and components so your product looks intentional, not like a template.

$99

AI Responsive Design Skills

Responsive layout patterns for rails, sidebars, and breakpoints so AI-generated UI adapts cleanly from narrow to wide.

$99

AI Dark Mode Skills

Dark theme tokens, contrast, and surfaces that keep AI-generated UI readable and product-grade, not flat gray on black.

$99

AI Color Token Skills

Neutral and primary ramps with clear steps so AI palettes stay systematic, not a random set of accent hex codes.

$99
View all