What should be included in a UI/UX design agency proposal at this price point?

Any proposal above $10,000 needs to specify the exact screen or flow count, research activities included, prototype fidelity and tool, revision rounds per deliverable, handoff format, and a payment schedule tied to milestones. A four-page document with a number and no deliverable list is not a proposal. It just transfers all the ambiguity risk onto the client.

A founder sent me a proposal last month asking if it was fair. The agency quoted $38,000. Four pages. No deliverable list, no screen count, no revision policy, no handoff format. That's a number with a logo on it. Not a scoped engagement.

The deliverable section is where most proposals fall apart. Vague language like "UI design for the core product" could mean eight screens or eighty. At Daasign, we list screens explicitly in every proposal, broken down by flow. A typical mid-range engagement for a B2B SaaS onboarding redesign looks like this: 6 onboarding screens, 3 dashboard states, 2 settings flows, 1 component library with 40–60 base components, and a Figma handoff file with auto-layout and named layers. That's a scope. The other version is a guess you're paying for.

The variables most founders miss

Research inclusion is the single biggest pricing variable I see founders overlook. A $25,000 proposal that includes three user interviews, a competitor audit across five tools, and a synthesis workshop is a completely different engagement from a $25,000 proposal that opens Figma on day one. Neither is wrong. But they're not the same thing. Ask the agency to separate research cost from production cost so you can decide what you actually need, rather than paying for something bundled in ways you don't understand.

Payment structure is also a signal worth paying attention to. Agencies I trust ask for 30–50% upfront, with the balance tied to delivery milestones rather than calendar dates. An agency asking for 100% upfront on a $40,000 project, or pushing all payment to completion with no milestone structure, is showing you how they handle risk. Specifically, they're putting yours on the table and keeping theirs off it.

For Montblanc's e-commerce design work, the initial proposal split payment across three phases: research and wireframe sign-off, high-fidelity screens, and dev handoff. Each phase had a specific output list and a defined acceptance criterion. That structure kept things clean across a nine-week timeline, with no disputes about what was done and what wasn't.

One thing I almost never see in UI/UX agency proposals is a stated assumptions list. Good proposals include a short section that says something like: "This scope assumes you have an existing brand identity, that engineering is using React, and that user testing will be conducted by your internal team." If any of those assumptions are wrong, the scope changes. If that section doesn't exist in the proposal you received, you're carrying that risk quietly, and you probably don't know it yet.

If you want to compare a well-structured proposal against what you've received, book a 20-min intro and bring the document. We review them regularly as a free sanity check. For current rates and what each tier includes, see Daasign pricing. For the full guide, read our ui/ux design agency pricing overview.