A decision-maker has two design proposals open on her desk. Both teams are capable, and the budgets are similar.
One reads like a template with the company name pasted in. The other opens with a screenshot of the company’s own checkout flow and a short note: a quick test of that flow showed shoppers struggling to find the returns policy before they gave up.
She has not read a deliverable yet, and she already knows who understands her problem. That is what a design proposal is for. Here is how to write one that wins the work.
TL;DR
- A design proposal shows a client you understand their problem and can solve it.
- Open with the client’s problem before your proposal.
- Tie every design choice to a business outcome.
- Include nine elements: cover page, overview, objectives, scope, solution, timeline, deliverables, proof, price.
- The real differentiator: back the pitch with real user research.
- Userlytics helps you gather that evidence fast, from a free AI UX report to a full study.
What a Design Proposal Is and What It Does
The Interaction Design Foundation describes a design proposal as a document that sets out a potential design project for a prospective client, covering the approach, process, deliverables, timeline, and commercial terms. That is the mechanical definition. A sound design proposal does three jobs at once in practice.
A good proposal answers the client’s real question, which is rarely about your process and almost always about whether they can trust you with the project. The proposal sets expectations, so you agree on scope, cost, and responsibilities before work starts rather than arguing about them later. A design proposal is also where you make the case for the work, so the people who approve it can see why this is the approach to back.
It’s important to note that a design proposal is not a contract, though it often becomes the reference a contract points back to. It connects the first conversation to a signed statement of work, and when the proposal is clear, the contract becomes a formality.
Why a Strong Design Proposal Wins the Work
A strong design proposal helps you win projects in three ways.
- Design reads as an investment. According to McKinsey’s Business Value of Design study (2018), companies in the top quartile of its Design Index grew revenue and total returns to shareholders at nearly twice the rate of their industry peers over five years. Connecting your proposed design work to revenue, retention, or conversion helps decision-makers understand its business value.
- Bad design is costly. When an interface confuses people, they leave, and the cost shows up in the funnel rather than in a design review. Highlighting a specific usability issue in the client’s product demonstrates your expertise more effectively than simply claiming it.
- Research strengthens your approach. Including research and testing in your proposal shows clients how you will use evidence to guide design decisions and validate solutions.
9 Essential Elements of a Design Proposal
Most design proposals share the same backbone. You can add or drop sections to fit the project, and these nine cover the ground a client expects to see. Aim to keep each one short and concise, aiming to keep the proposal easily scannable rather than exhaustive.
| Element | What it does | Keep it to |
| 1. Cover page | Sets a professional first impression with the project name, client, and date | One clean page |
| 2. Project overview | Restates the client’s problem in your own words to prove you listened | Two to three sentences |
| 3. Objectives | Names the measurable outcomes the project is meant to move | Three to five goals |
| 4. Scope of work | Draws the line around what is and is not included | A short list, plus exclusions |
| 5. Proposed solution | Explains your approach and why it fits this client | A few paragraphs, with a visual if it helps |
| 6. Timeline | Breaks the work into phases with realistic dates | A simple phase table |
| 7. Deliverables | Lists the specific artifacts the client receives | Itemized, no vague “assets” |
| 8. Proof | Shows relevant experience: case studies, results, or research | Two or three focused examples |
| 9. Investment | States the price, payment terms and what each phase costs | Clear numbers, no surprises |
A quick word on how this differs from a design brief. A design brief captures the requirements and constraints of the work, usually written with or by the client. A proposal is your pitch to win that work, informed by the brief but separate from it.
How to Write a Design Proposal
With these elements in place, follow the steps below to write a clear and focused design proposal.
Start With the Client’s Problem First
Begin your proposal by describing the client’s problem in language they recognize. Highlight the challenge they shared, whether it’s a confusing checkout process, declining conversions, or a tight launch deadline. This shows you understand their priorities and sets the context for your proposed solution
Lay Out the Solution and Scope
Explain how you will solve the problem and why your approach fits this client. Tie each part of the solution to an objective you listed earlier, so the client can trace every activity back to a goal. Clearly define what the project includes and excludes to prevent changes in scope of work or requests for additional work beyond the agreed fee.
Set the Timeline, Deliverables and Price
Break the project into phases a client or stakeholder can picture, with dates you can actually hit. List deliverables as specific artifacts, a clickable prototype, a design system, or annotated screens, rather than a vague promise of designs. Present the price by phase or deliverable so the number reads as a set of decisions rather than one intimidating figure.
Show Relevant Proof
Include two or three examples that match the client’s situation rather than your whole portfolio. A short case study that names the problem, what you did, and the result the client reported carries far more weight than a gallery of unrelated work. Add a line of evidence from the client’s own product too, which the next section explains.
Make the Next Step Obvious
End the proposal with a single clear action: a link to book a call, a signature block, or a note on how to approve. A proposal that trails off into a request for thoughts makes the client do the work of moving forward. In other words, tell them exactly what happens when they say yes to the work
How to Back a Design Proposal With User Research
Here is the step almost every proposal skips. Strong proposals demonstrate an understanding of the client’s users and their needs before the project begins. Including user testing data gives the design process a foundation and reassures the client that decisions are evidence-based.
You do not need a full UX research program. Here is how to fold evidence into a proposal:
- Run a small study first. A prototype testing session, a first-click test, or a handful of unmoderated sessions surfaces where real people get stuck. One honest finding does more than a page of persuasion.
- State the finding with measured confidence. A line like “in a short unmoderated study, five of eight participants missed the primary call to action” is true and useful, and it names its own limit as a small, directional sample.
- Match the method to the question. Usability, as defined in ISO 9241-11, is how well specified users achieve goals with effectiveness, efficiency, and satisfaction in a context, a behavioral question rather than an opinion poll. A quick grounding in UX research methods and in quantitative or qualitative research keeps your evidence credible.
- Recruit the client’s real audience. With a panel of 2M+ participants across 150+ countries and 60+ languages, you can test with the client’s own users. The free AI UX report gives you an expert-reviewed read of a website, app, or Figma prototype.
See your user experience through your client’s eyes. Book a free demo and bring real user insights into your next proposal.
A Short Design Proposal Example You Can Adapt
Structure is easier to copy than tone, so here is the shape of a strong opening you can adapt. Notice how it leads with the client’s problem and a piece of evidence before it says a word about the designer.
- Overview. Your checkout converts well on desktop but drops sharply on mobile. In a quick five-session usability read, three of five mobile shoppers abandoned at the shipping step, where the form ran longer than one screen.
- Objective. Lift mobile checkout completion by redesigning the shipping and payment steps around what those sessions revealed.
- Scope. Discovery, wireframes, and a clickable prototype for the mobile checkout flow. Copywriting and back-end development sit outside this phase.
- Proof. A recent retail client resolved a similar drop after a two-week prototype test cycle, reported by their team.
- Investment. Phase one, discovery and wireframes, is a fixed fee. Phase two, prototype and handoff, is a fixed fee billed on approval of phase one.
The numbers above are illustrative, and yours should come from a real study of the client’s product. The pattern is what carries the proposal: problem, evidence, objective, scope, proof, and price, in that order.
Common Mistakes That Sink a Design Proposal
Even strong UX designers lose work to a handful of avoidable errors. Watch for these five.
| Mistake | Why it costs you | The fix |
| Sending a generic template | A proposal that could go to any client goes in the bin | Personalize the overview and the solution to this client’s problem every time |
| Burying the client in jargon | A stakeholder who cannot follow the proposal will not approve it | Keep terms like information architecture and heuristic evaluation in the body, explained, rather than in the headline |
| Skipping the business case | The budget holder is left to guess at the value | Say why the work matters commercially and link the ROI of UX work |
| Ignoring how weak UX shows in the numbers | A redesign you cannot connect to a business metric is one the client cannot justify | Tie it to how bad UX drags on conversion, which the client already tracks |
| Leaving revisions undefined | Silence invites scope creep and awkward conversations later | Say how many rounds the price includes and what a further round costs |
Turn Your Next UX Design Proposal Into a Signed Project
Before you send your next UX design proposal, include a relevant research finding to show how user needs inform your approach. Run a short usability study on the client’s current site or prototype, and open with what you learned. The person who arrives already understanding the users is hard to say no to.
If you want that evidence fast and reliable, that is what Userlytics does. Our platform pairs user testing with real people and AI-powered tools and analysis that support end-to-end UX research.
Ready to make evidence part of every proposal? Book a free demo and see how fast you can put real user findings in front of your next client.
