Quote template for UX designers
UX quotes go wrong when the scope is a list of screens before anyone knows what the product needs. A better structure is phases: discovery, research, information architecture and wireframes, high-fidelity design, prototype and testing, handoff. Quote the first phases firmly and the later ones as an estimate that gets confirmed after discovery.
Be specific about research. How many participants, moderated or unmoderated, who recruits them and who pays the incentives. And about handoff: whether the client gets a design system with components and tokens, or a set of screens with annotations. Those are very different amounts of work.
From
Prepared for
Details
Items
Notes and terms
Free, no account. Everything stays in this browser: we don't receive or store what you type.
The example lines and prices are illustrations. Replace them with your own.
What a UX designer's quote should spell out
- Phases, with deliverables and an approval at the end of each.
- Research method, number of participants, recruitment and incentives.
- Wireframes versus high-fidelity, and how many screens or flows each covers.
- Number of prototype and testing rounds.
- Handoff: annotated screens, component library, design tokens, dev support hours.
- Tools and file ownership: whose Figma workspace the files live in.
Questions UX designers ask
How do UX designers price a project?
Usually by phase, with discovery and research as day-rate or fixed blocks and design either per screen or per day. Fixed pricing for the whole project only works once the scope is clear, which is usually after discovery.
How many usability test participants should a quote include?
Enough to find the main problems for your budget, often a small group per round. State the number, the format and whether the client recruits them, so the client can see what changes if they want more.
Should a UX quote include a design system?
Only if you list what it contains. A few shared components and colour styles is a small job. A documented system with tokens, variants and usage rules is a project of its own and should be quoted that way.
Quote it, then invoice it, without retyping
In OIO a proposal belongs to its client and project. When it's accepted it becomes an invoice draft with the same lines, and the money view shows what is outstanding and what is paid. Free plan, no card.
Start freeAlso for UX designers: invoice template and contract template. Quote templates for related trades: web developers, software developers, graphic designers, data analysts. Or browse all quote templates.