How much does SaaS product design cost? What sets the price, and why quotes differ

There is no neutral public figure for what a SaaS product design project costs: the project ranges we found online were published by firms that sell the work or by platforms that sell introductions to them. The neutral figures that do exist price time. US federal ceiling rates for user experience roles have a median of about $138 an hour, and UK contract job ads for a UX designer a median of £448 a day. What turns time into your price is the shape of the engagement and a handful of drivers you can name before you ask anyone for a quote.

A range means little until you know the team, the scope and the definition of "done" behind it. This guide gives the figures that do not come from a seller, what each one measures, what moves the price, and a way to read two quotes side by side.

What the public data says, and what it does not

We looked for figures that are public, dated and not a design firm's own price list. Three survived. None is a price for your product; each measures something narrower.

How to read them:

• Federal ceiling rates are maximums, not prices paid. The CALC+ user guide describes them as not-to-exceed prices set to cover different order types, sizes and locations; an order can come in lower. They are useful because they are public, current and broken down by experience. We pulled the 272 records through GSA's public interface and calculated the medians ourselves.
• A day rate prices one person, not a team. The UK figure is for a single contractor whom you direct. It includes no research recruitment, no second discipline and no one directing the work but you.
• A salary is the floor of in-house cost, not the cost. The BLS median is pay alone, before employer taxes, benefits, recruitment, equipment and management time, and it buys one person's skills rather than a team's. Hiring is a separate decision, covered in how to hire a product designer for your SaaS product.

What we did not find is a neutral, dated source for the total cost of a design project, so we have left the seller-published project ranges out. That is why the rest of this guide is about the shape and drivers of the work: they are what make any total meaningful.

Three engagement shapes, three different things to price

Much of the confusion about cost comes from comparing different shapes of work as if they were the same purchase. Name the shape first.

The same five items decide what a quote leaves out: research, prototyping, a design system, front-end build, and quality checks on what engineering ships. A quote that is lower because it excludes three of them is not cheaper; it moves that cost to your team or to a later invoice.

Monthly arrangements come in several forms that buy different things: a reserved person you direct, part of a senior person's week, a request queue, or a led team. They are compared model by model in dedicated, fractional, subscription or senior-led team, so we do not repeat that here.

Eight things that move the price

Screen count is a poor proxy for SaaS design effort. As what a product design agency does argues, cost follows uncertainty. These are the drivers that create it.

1. Roles and workflows. Each user role brings its own permissions, views and edge cases. Two roles sharing one workflow is one design problem; six roles across a dozen workflows is a different order of work.
2. State and permission complexity. Empty, loading, partial, error, pending approval, read-only, archived. In business software each of these states has to be designed, not left to engineering defaults, and each one adds work.
3. Data density. Tables, filters, comparisons and charts have to be designed with realistic volumes and messy values. A product built around data takes longer to resolve than one built around forms.
4. How much research is needed, and whether users can be reached. A product with a settled model needs little discovery; a new one, or one losing customers for unclear reasons, needs more. The people who use business software can be hard to schedule, so ask who recruits them and who pays any incentives.
5. Whether the design is carried into code. A project that ends at a design file costs less than one where designers work in the browser, support engineers during build and check what ships. The second costs more because it also covers the gap between the design and what is built.
6. Regulated domains. Health, finance, public sector and other regulated products can need extra review cycles and documented decisions. Accessibility is a legal requirement in some markets: the European Accessibility Act has applied since 28 June 2025 to services including e-commerce and consumer banking in the EU.
7. Time-zone overlap. Fewer shared working hours mean more written decisions and longer waits for answers. That is a cost either in documentation time or in elapsed weeks, and a quote should say how it will be handled.
8. Seniority of the people who do the work. In the federal ceiling data, the median rate for user experience roles that require at least ten years' experience is about $185 an hour, against about $146 for five to nine years and about $122 for under five. The ten-year group is small (20 rates), but the direction is clear: seniority is priced, so it is worth knowing whose time you are paying for.

A rough way to see how a quote is built: the people involved, at their seniority, for the weeks the work needs, plus research costs, plus whatever allowance is made for change. Every difference between two quotes sits in one of those terms.

Why two quotes for the same product differ

When quotes for one brief are several times apart, look for these causes. Each can be found by reading the proposal rather than guessing.

• Different scope assumptions. One firm has priced screens from your brief; another has priced working out the product model, roles and states first. A proposal priced per screen is pricing the visual layer, not the decisions underneath it.
• Senior people sell, junior people deliver. The rates above show why this matters to price. Ask for the names of the people who will do the work and how much of their time is included.
• Change is left unpriced. Scope moves on many projects: in the Project Management Institute's Pulse of the Profession 2021, respondents estimated that 34 per cent of the projects their organisations completed in the previous 12 months experienced scope creep. That figure covers projects of every kind, not design alone, but it is a reason to ask how a change is priced before you sign.
• "Unlimited" can mean one at a time. Some design subscriptions advertise unlimited requests and work through them one at a time, so the monthly price buys a queue rather than capacity (the monthly-model comparison covers this). A queue suits steady production work better than product decisions.
• Items are missing. Research recruitment, participant incentives, accessibility review, design system documentation and build support are the items to look for when one quote is much lower than another.

How to put two quotes on the same footing

Before comparing totals, write each quote out against the same seven lines. The line you cannot fill in is the one to ask about.

1. The question it answers. In one sentence, what will you know or have at the end?
2. The people. Names, roles, seniority and share of time, including who you will speak to each week.
3. The scope. Roles, workflows and states covered, and which are excluded.
4. Research. How many sessions, with whom, who recruits, and who pays incentives.
5. The end point. Does the work stop at a design file, or continue into code and checks on the built product?
6. Change. How a change in scope is agreed and priced.
7. Stopping. Notice period, minimum term, and what you own if you stop halfway.

Two quotes that fill in all seven lines the same way can be compared on price. Two that differ on any line are buying different things, and the price gap is the cost of that difference.

How we price product design at Tcules

Tcules is a digital product design studio creating ambitious new software products and making established ones better. We do not publish price figures; the price follows the shape of the work and its scope:

• Audits and pilots: a fixed price agreed before we start. Our UX Product Audit is a bounded first step: it can focus on one critical workflow, a role boundary, a new capability or a cross-product pattern, and we agree the sample before the review.
• Defined projects: priced on their agreed scope.
• Ongoing work: our designers are dedicated to your product for the capacity we agree: a senior designer leads the work and deals with you directly, and we bring in specialists when the work needs them, for a fixed monthly fee. The lead may also lead work for other clients. You can change the team or end with two weeks' notice; there's no minimum term.

"Dedicated" here means committed to your product for the agreed capacity, not exclusive to it. How we work across these shapes is set out on how we work, and what the design work itself covers is on our Product Design page.