UX/UI design proposal template

Prepared for [Client Company] by [Your Name], [Date].

Thank you for considering me to design [product name]. This proposal covers how I will turn what your users need into flows, screens, and a tested prototype your developers can build from, with scope defined by flows rather than vague page counts.

[Client Company] is building [describe the product] and needs the [onboarding / checkout / dashboard / core] experience designed so that users can [key task] without friction.

Today [describe: the product exists but users drop off at [point], there are only rough ideas, the current UI has grown inconsistent]. Success means [a tested design for the agreed flows and a measurable improvement in [metric] after launch].

1. Phase 1, Research and definition. I review analytics and support tickets, interview [3 to 5] users or stakeholders, and map the current journey. We agree exactly which flows are in scope before any screens are drawn.
2. Phase 2, Flows and wireframes. I design each flow in low fidelity first: every screen, state, and edge case (empty, loading, error), so we debate structure while changes are cheap.
3. Phase 3, Visual design and prototype. I bring the approved wireframes to high fidelity in [Figma], applying or extending your design system, and wire them into a clickable prototype.
4. Phase 4, Testing and handoff. I run [5] usability sessions on the prototype, fix what the sessions surface, and hand off annotated designs with a developer walkthrough.

• A research summary with the top usability findings and the agreed flow map
• Wireframes covering every screen and state in the agreed flows, including empty, loading, and error states
• High-fidelity UI in [Figma] with reusable components (buttons, forms, navigation) organized as a mini design system
• A clickable prototype of the core journey
• [5] recorded usability sessions with a findings-and-fixes summary
• Annotated developer handoff plus [2] weeks of async design support during the build

• Front-end development (I support the developers; I do not write production code)
• Marketing website design (a separate proposal)
• Flows not listed in the agreed flow map (added by change order)

Prices are placeholders. Set your own before sending.

• Scope is defined by flows and states, not screen counts, so 'we forgot the error state' never becomes a change order
• Designs are tested with real users before developers build them, which is the cheapest moment to be wrong
• Handoff includes the build: your developers get me for questions, not just a Figma link

This proposal is valid for [30] days. A deposit of [amount or %] is due to begin, with the balance due [on delivery / per the schedule]. Work outside the scope above is quoted separately before it starts.

Design ownership transfers on final payment, including Figma working files. Research recordings are for internal use only and participants' personal details are kept confidential; participant incentives, if any, are billed at cost.

To move forward, approve this proposal in writing and I will send the agreement and the deposit invoice. We can begin as soon as the deposit is received.

Accepted by: ______________________________ Date: ____________