A UX design proposal is where you stop being one of several designers a client is talking to and become the one who understood the problem. The proposals that win are not the ones with the lowest price or the longest feature list; they are the ones that frame the client's real problem, then lay out a clear process to solve it. Here is what to put in a UX design proposal, the section order that works, and how to turn a yes into a signed, paid project.
What a UX design proposal is
A UX design proposal is the document you send a prospective client after an initial conversation, setting out the problem you will solve, the work you will do, and what it costs. It is not a contract, and it is not a price list. It is a persuasive summary that shows you understand the client's product and users, and gives them a clear, low-risk path to hiring you.
The best UX proposals sell the process, not just the deliverables. A client rarely knows whether they need wireframes or a research study; they know their product is not working the way they want. A proposal that names that problem and maps a route through it is far more convincing than a list of screens and a number.
What to include in a UX design proposal
A strong UX proposal has a handful of sections, each doing a job.
The problem and goals:: the client's actual problem in their words, and what success looks like. This is the most important section and the one weak proposals skip.
Scope and deliverables:: exactly what you will produce, research, wireframes, prototype, design system, handoff, and what is not included.
Your process:: the phases you will run, discovery, design, testing, so the client sees how the work unfolds.
Timeline:: the phases mapped to weeks, with any dependencies on the client noted.
Pricing:: the investment, ideally split by phase, so the number is tied to visible work.
Why you:: brief, relevant proof, similar products, outcomes, testimonials, not your life story.
Next steps:: the single action the client takes to move forward.
Naming the problem in the client's own words is what separates a proposal that wins from one that reads like a template, since it proves you were listening rather than pitching.
The section order that works
Lead with the client, not with yourself.
Open with the problem and goals, so the first thing the client reads is their own situation, understood. Move to your process and scope, which show how you will solve it. Then present the timeline and pricing, which now land as the cost of a clear plan rather than a number in a vacuum. Close with brief proof and a single next step. Putting price after process, not before, is the small ordering choice that most changes how a proposal is received, since by then the client is reading it as an investment in an outcome they already want.
Turn the proposal into a signed project
A proposal that gets a yes still has to become a signed contract and a paid project, and the gap between them is where deals stall.
Keep pricing in the proposal and move the legal terms, ownership, revisions, and payment schedule, into the contract you send next, which the UX designer contract template covers. Send the contract the moment you get verbal agreement, while momentum is high. FileCurrent turns an accepted proposal into a contract the client signs online and an invoice for the deposit, so the yes becomes a booked, paid project instead of an email thread that goes cold. To price the work behind the proposal, the freelance UX designer rates guide covers the ranges.
Frequently asked questions
What should a UX design proposal include?
The client's problem and goals in their own words, the scope and deliverables, your process and phases, a timeline, pricing split by phase, brief relevant proof, and a single clear next step. The problem section matters most, since framing the client's real problem is what separates a winning proposal from a generic list of screens and a price.
How long should a UX design proposal be?
Long enough to frame the problem and map your process, and no longer, usually two to five pages. A client decides on the strength of the problem framing and the clarity of the plan, not the word count. Cut anything that is about you rather than about solving their problem, and keep the next step to a single action.
What is the difference between a UX proposal and a contract?
A proposal is persuasive: it frames the problem, the process, and the price to win the work. A contract is protective: it sets the legal terms, ownership, revision limits, payment schedule, and liability, once the client says yes. Keep pricing in the proposal and the binding terms in the contract, and send the contract as soon as you have agreement.
How do I price a UX design proposal?
Price by phase rather than a single number, so the cost is tied to visible work, discovery, design, testing. Start from your minimum rate, your target income and costs over realistic billable hours, then price up for research depth and product complexity. Presenting a phased investment reads as a professional process and is easier for a client to approve.
How do I present the price in a UX proposal?
Put it after your process and scope, not before, so the client reads it as the cost of a clear plan rather than a number in isolation. Break it into phases with a fee each, note what is included, and state the deposit required to start. Ending on pricing plus a single next step makes it easy for the client to say yes.
A winning UX proposal frames the problem, sells the process, and makes the next step easy. FileCurrent turns the yes into a signed contract and a deposit invoice in a couple of clicks, so your best proposals become booked projects instead of stalled threads. $15/month or $129/year. 7-day free trial, no card required.