What you are actually paying for
Design pricing confuses people because the deliverable is invisible until it exists. A quote is really a bet on how many decisions a product needs, and how expensive each wrong one would be later. Three inputs drive almost all of it: how many distinct user roles the product serves, how much of the behaviour is already known, and whether the screens have to survive a real engineering handoff.
Typical global ranges in 2026
| Engagement | Typical range (USD) | Usual duration |
|---|---|---|
| Landing or marketing page | $600 – $6,000 | 1–3 weeks |
| Marketing site (6–10 pages) | $2,500 – $20,000 | 3–6 weeks |
| MVP product design | $4,000 – $40,000 | 4–10 weeks |
| Full product + design system | $15,000 – $150,000+ | 3–6 months |
| UX audit / heuristic review | $800 – $10,000 | 1–2 weeks |
| Embedded designer (retainer) | $2,000 – $20,000 / month | Ongoing |
These are studio rates for senior work. A freelancer quotes below the floor of each band; a large consultancy quotes several times the ceiling. Neither is automatically wrong — they sell you different amounts of risk absorbed.
Why the same scope costs 5× more in one place than another
The single biggest variable is not skill, it is where the team sits. An identical MVP engagement looks roughly like this:
| Region | Senior hourly | Same MVP scope |
|---|---|---|
| North America | $120 – $250 | $30,000 – $80,000 |
| Western Europe, UK | $90 – $180 | $22,000 – $60,000 |
| Australia, Gulf | $80 – $160 | $20,000 – $50,000 |
| Eastern Europe | $45 – $90 | $12,000 – $30,000 |
| India, South & South-East Asia | $25 – $70 | $5,000 – $20,000 |
| Latin America | $35 – $80 | $9,000 – $25,000 |
What you should not assume is that the cheaper number buys less judgement. What it reliably buys less of is time-zone overlap and, sometimes, written communication. Those are the two things to test during a trial engagement rather than argue about in advance.
The four things that move a quote
- Number of user roles. A single-user app is one set of flows. A marketplace has at least two, an insurance platform can have four. Each role is close to a separate product sharing one visual language.
- Research depth. If you already have analytics, support tickets and users we can talk to, discovery is a week. If nobody has spoken to a customer, it is three — and skipping it is how teams pay twice.
- States, not screens. People scope by screen count. Cost lives in the states: empty, loading, error, permission-denied, partially filled. A ten-screen product can carry sixty states.
- Whether engineering is included. Design-only is cheaper up front and more expensive at handoff, unless the component library is genuinely documented.
Fixed scope or retainer?
Fixed scope suits a defined piece of work with a known shape — a marketing site, an audit, a feature. You get a number before you commit, and the risk of underestimating sits with the studio.
A retainer suits an ongoing product team where priorities move monthly. It costs more to start and far less to change direction. If you expect your roadmap to survive six months untouched, take fixed scope. Most roadmaps do not.
What a good quote looks like
It should name the phases, the deliverable at the end of each, the number of revision rounds, and who owns the source files. If a quote is a single number with no breakdown, you cannot tell whether it is expensive — only whether it is large.
Comments
Comments are not wired up yet. In the meantime, the conversation happens on LinkedIn — or write to hello@tagthose.in and we will reply.