Pricing and quotation guide
User flow design cost
User flow design is often one of the least expensive parts of UX work, but its cost still varies. A single simple flow, such as a newsletter sign-up, takes little time. A complex flow with many branches, roles and system rules, such as an insurance claim or a multi-step booking, takes much longer to understand and draw. The number of flows, how much research and data review comes first, whether current flows are mapped as well as proposed ones, how many workshops are run and how flows are validated all shape the price. Because flows prevent expensive mistakes later, they tend to repay their cost.
It explains how the number and complexity of flows, workshops and validation shape the cost of flow design. No prices are given, because they depend on scope and provider; LetGetGrow sets out the cost for your project in a custom quotation.
Illustrative diagram
What drives flow design cost
- Number of flows
- Each task mapped separately.
- Complexity
- Branches, roles, rules.
- Research
- Analytics, tickets, interviews.
- Current and proposed
- Mapping both doubles some work.
- Workshops
- Preparation, running, write-up.
- Validation
- Developer and user checks.
Costs paid to third parties (separate from our fees)
- Whiteboard or diagramming tool licences
- Participant incentives for testing
Ask how complexity is assessed, since one complex flow can take longer than several simple ones.
Scopes compared
| Scope | What it covers | Relative cost |
|---|---|---|
| Single flow | One task, proposed flow only | Lower |
| Core journeys | Several tasks, current and proposed, one workshop | Moderate |
| Service blueprint | Many flows, roles and back-office steps | Higher |
Pricing models
Per flow
Suits you when
- Known list of tasks
Watch out for
- How complexity changes price
Short project
Suits you when
- Several related flows
Watch out for
- Workshops included
Part of a larger UX project
Suits you when
- Flows lead into design
Watch out for
- Time allocated to flows
Complexity
A flow with three steps and no branches is quick. One with several roles, approvals and system rules needs interviews, a workshop and several drafts. Ask the provider to estimate each flow's complexity rather than pricing all flows the same.
Workshops
A workshop needs preparation, a facilitator and a write-up. It also takes your team's time, which is a real cost. Well-prepared workshops save rounds of email and settle rules quickly.
Example: prioritising flows
Illustrative example — not a client case study
Situation: A booking business wants all its flows mapped but has a small budget.
- Support data shows rescheduling causes most calls, so it is mapped first in detail.
- Booking and cancellation are mapped more lightly, as proposed flows only.
- One workshop settles rules for all three.
What this shows: The budget went where problems were greatest. This example is illustrative.
Validation
Walking through flows with developers takes a short session; testing them with users through wireframes takes longer. Include at least the developer review, which often finds technical constraints early.
Comparing quotes
Check number of flows, complexity assumptions, research, current and proposed maps, workshops, validation, revisions and file ownership.
Keeping costs down
Share data and rules up front, bring decision-makers to the workshop and map the most problematic flows first.
Judging value
Value shows in fewer surprises during design and build, rules written down and agreed, and simpler journeys for users.
Where flows save money later
An edge case found while drawing a flow takes minutes to resolve. The same case found during development may mean redesigning screens and rewriting code, and found after launch it may also mean support costs and refunds. Flow design is a small cost compared with those.
Service blueprints
Some projects map not only the user's steps but also the staff actions and systems behind them. These blueprints take longer but show where hand-offs between teams cause delays.
Research before mapping
Reviewing analytics, reading support tickets and interviewing staff or customers takes time, but it decides which flows to map and what problems to solve. Without it, flows reflect assumptions. A light review of existing data is often enough for a small project; a larger product may justify interviews with users and staff. Ask what research the quote includes, and share any data you already have to reduce the time needed.
Keeping flows current
Flows go out of date as the product changes. Agree who will update them and whether the provider's files are editable by your team. Updating a flow when a feature changes takes little time and keeps the diagrams useful for onboarding new staff and planning later work.
Revision rounds
Flows change as rules are clarified. Agree how many rounds of revision are included, and gather feedback from everyone involved in each round to avoid repeated changes.
Handing over
Ask for a short walkthrough of the final flows for your designers and developers, so decisions are understood and carried into the screens.
Questions about user flow design cost
What affects flow design cost?
Number and complexity of flows, research, workshops and validation.
Are all flows priced the same?
They should not be; complexity varies.
Are workshops worth it?
They settle rules quickly when well prepared.
Should we map current flows?
Usually, for problems and a baseline.
How can flow design cost less?
Share data early and start with problem flows.
How do we know flow design was worth it?
Fewer surprises later and simpler journeys.
Request a Custom Quote
Ask about User flow design cost
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.