UI/UX Design Proposal Template
A proposal for product design work, from research through handover, that you can copy and adapt. Below it: how to sell research to a client who just wants screens, and how to scope handover so you're not on call forever.
Updated September 30, 2026
The template
UI/UX DESIGN PROPOSAL: [Product or feature name] Prepared for: [Client name], [Company] Prepared by: [Your name] Date: [Date] Valid until: [Date + 30 days] 1. THE PROBLEM [What users are struggling with, and how the team knows. E.g. "Many new sign-ups never finish setting up their first project, and support tickets suggest the setup screen is the sticking point."] 2. GOAL [The change you're designing for, e.g. "More new users complete setup without contacting support."] We'll agree on how to measure it at kickoff. 3. SCOPE Research - Review of existing analytics, support tickets and any past research - [5] user interviews (you help recruit; I run and summarise them) Design - User flows for [the onboarding journey / the checkout / etc.] - Low-fidelity wireframes for [number] screens - High-fidelity designs for [number] screens, desktop and [mobile] - Clickable prototype of the main flow Validation - [5] usability tests on the prototype, with a findings summary Handover - Annotated designs and components in [Figma], a walkthrough with your developers, and [2] weeks of questions answered during build 4. NOT INCLUDED - Front-end development - A full design system beyond the components these screens need - Recruiting incentives for research participants (paid by you) - Screens outside the flows above (quoted separately) 5. TIMELINE Weeks 1-2: Research and findings Week 3: Flows and wireframes Weeks 4-5: High-fidelity design and prototype Week 6: Usability testing and final revisions Week 7: Handover 6. INVESTMENT [Fixed price for the scope above]: [price] Payment: [40]% to start, [30]% after wireframes are approved, [30]% at handover. 7. TERMS - [2] rounds of revisions at wireframe and high-fidelity stages. - Design changes during development are covered for [2] weeks after handover; larger changes are quoted. - You own the final designs on full payment. 8. NEXT STEPS Accept this proposal and I'll send the first invoice and a kickoff time.
Frame the problem with their evidence
UX proposals are strongest when the opening uses the client's own data: support tickets, drop-off in a funnel, sales call notes. It shows you're solving their problem rather than applying a process. If they don't have data, say that the research phase will get it.
When the client only wants screens
Some clients see research as a cost they can cut. Instead of arguing, show the trade-off: offer a version with research and one without, and state plainly what the second one assumes ("we'll design from your team's current understanding of users, which saves two weeks but means we won't find out if that understanding is wrong until after launch"). Let them choose.
Scope the handover
- Say what's in the files: annotated screens, components, states (empty, loading, error) and responsive rules.
- Include a walkthrough call with the developers.
- Put a time limit on questions during build, then quote further changes.
- Name the tool and who owns the file afterwards.
Tie payments to milestones
Product design projects run longer than most freelance work, so a single deposit and final payment leaves you carrying weeks of unpaid work. Split payments by approved milestone (research, wireframes, handover) so cash keeps pace with the work and both sides have natural checkpoints.
Related
- Web Design Proposal Template for FreelancersA free web design proposal template, plus what to include in a web design proposal: discovery, wireframes, design scope, revisions, pricing options and terms.
- Mobile App Development Proposal TemplateA mobile app development proposal template: MVP features, platforms, exclusions, milestone payments, post-launch support, maintenance and code ownership.
- How to Write a Scope of Work (With Example)How to write a freelance scope of work: the eight parts to include, vague vs specific wording, a full worked example, and a change-request clause you can copy.
- How to Price a Freelance ProjectHow to price a freelance project: work out your minimum rate, estimate hours honestly, and choose between hourly, fixed, package and value-based pricing, with worksheets.