How much does product design cost in 2026?
Our product design starts from $10,000 a month, and an embedded design team runs $10,000 to $30,000 a month. What moves the number, and how to compare quotes.
Product design with us starts from $10,000 a month. An embedded design team, meaning our designers working inside your product team, costs from $10,000 to $30,000 a month. A focused piece of work on one area of a product usually takes four to six weeks, an MVP eight to twelve weeks and a full product design engagement ten to sixteen weeks.
Those are our own published prices and lengths. They are not a market average, and we have not tried to make one up. Our studio is in St Leonards, Sydney, and we work from Flatiron in New York. Our prices are written with a plain dollar sign. Further down are the figures four other Australian studios print for the same kind of work, and what each one counts.
1. What does product design include?
Product design is the UX and UI of software: how a task works, what each screen shows and how the parts behave together. A complete piece of product design work usually hands over these things, though a given project may need only some of them.
- Audit findings for the existing product, in the order to fix them.
- Flows and a prototype for the journeys in scope, with the decisions, permissions and recovery paths mapped.
- Interface designs for every screen and state, including loading, empty and error states.
- A design system: the components and the rules for using them, in Figma and, where it is in scope, in code.
- Review of the built product with your engineers, so what ships matches what was designed.
The build is a separate question. Some studios design and hand over to your engineers. Others design and build. We do both, and scope design and build separately or together. If a quote covers design only, budget for the engineering on top of it.
2. Should you pay by the month or for a fixed scope?
Studios price product design in two ways, and many offer both. The choice depends on whether you can define the work before it starts.
By the month
You pay for a team’s time over a month, and the team works on whatever matters most that month. It suits product work where the problem is still being defined, or a product that keeps moving after launch. Our embedded team runs this way, and we agree where you sit in the range, who is on the team and any minimum term or notice before the first month. Ask any studio what a month includes: which people, how many days of each, and what happens in a quiet week.
For a fixed scope
You pay an agreed price for a defined result, such as a redesigned onboarding flow or a first version of a product. It suits one project with a clear end. A fixed price needs a scope that can be written down. If the users, the task or the technical constraints are still open, a studio that fixes the price anyway is guessing, and the guess comes back to you as change requests. In that case, pay for the step that settles the open question and price the rest afterwards.
We do not charge by the hour under either model. An hourly rate tells you little about what the result will cost, because the number of hours is the part nobody knows in advance.
3. What moves the price?
Four things set where a product design quote lands. They apply to any studio, and they are the four we price against.
The journeys involved
A journey is one task from start to finish, such as setting up an account or approving an invoice. Each one in scope has to be traced, designed in every state and checked with the people who do it. A project on one area of the product is the four to six week piece. Work across the whole product, with many roles and tasks, is the ten to sixteen week engagement.
Research access
Design goes faster and lands better when the team can talk to the people who use the product and see how they use it. If users have to be recruited, or a customer’s permission is needed for every session, that time is in the quote. If there is no access at all, explanations stay hypotheses for longer, and the design needs more rounds.
Technical constraints
An old codebase, a component library the engineers want to keep, permissions enforced on the server, integrations that return messy data: each one narrows what a design can do, and finding the limits takes time with your engineers. A new product with no code yet has fewer constraints and more decisions.
The deliverables
Screens in Figma are the smallest version. A clickable prototype, a documented design system, components built in code and review of the implementation each add work. So does a build, if the studio is writing the product as well. List the deliverables you need in the brief, because two studios can quote the same project and mean different things by it.
One thing on your side moves the price too. A project needs one person who can make a decision in a review. Without them, work waits, and on a monthly arrangement you pay for the waiting.
4. What do other Australian studios charge?
When we checked product design studios in Australia on 14 November 2026, most did not print a price. Of the twelve that passed the test for our list of product design agencies for B2B SaaS, ours included, four published one. A fifth, Ippon Australia, did not pass that test and prints prices for its product work. We read each page again on 15 November 2026 and the figures were the same. Each is as the studio printed it.
| Studio | City | Monthly price as printed | Other prices as printed | Currency and tax |
|---|---|---|---|---|
| Refract | Sydney | From $10,000 a month. Embedded team $10,000 to $30,000 a month | A one-week trial piece of work, $2,500 | Plain dollar sign |
| Ippon Australia | Melbourne | Monthly retainer starting at $10k | A two-week product discovery sprint at $32k | No currency stated |
| Morphic | Melbourne | $3,499 for 60 hours, or $6,499 for 120 hours | None | No currency stated. From its own article |
| Raw.Studio | Sydney | Design team from $8,400. Design and web development from $12,000 | None for product design | Plus GST. One page marks Australian dollars |
| UntilNow | Sydney | Retainer starting at 18K, typically 2.5 to 5 days a week | Projects starting at 7K a week, for 4 to 12 weeks | US dollars, by its own footnote |
The figures do not sit on one scale. Morphic sells hours. UntilNow sells days of a team’s week, in US dollars. Raw.Studio’s prices exclude GST. Ippon’s monthly figure is a starting point, with tiers up to a dedicated squad embedded in your team. Before you compare any two, ask each studio what a month buys: the people, their seniority and how much of their time.
5. Studio, in-house hire or freelancer?
The monthly figures above are often weighed against a salary. That comparison only works when the two buy the same thing. A designer on staff gives you continuity on one product. A studio gives you several people with different skills for as long as the work needs them. A freelancer is usually one person, which is fine for a defined set of screens in a system you already have and harder when the work also needs research, a design system and engineering.
We have set out the full comparison, including design subscriptions and how the choice changes as a company grows, in a separate guide, linked at the end of this piece. The short version for product design: hire when design is needed every day on one product and someone on your side can manage a designer, and bring in a studio when you need more range than one person covers, or need it before a hire could start.
6. How do you compare two product design quotes?
Put both quotes in one table with a row for each of these, then look at the totals.
- Model: by the month or for a fixed scope, and what happens if the scope changes.
- Journeys: which ones are in scope, by name.
- People: who does the work, by name, and how much of their time a month includes.
- Research: who recruits users, how many sessions, and what happens if access is slow.
- Deliverables: screens, prototype, design system in Figma or in code, documentation, review of the build.
- Build: included, quoted separately or left to your engineers.
- Length: the number of weeks, and what it assumes about your side.
- Terms: minimum term, notice, currency, tax and when payments fall due.
- Ownership: who owns the files, components and code at the end, and whose accounts they sit in.
Where one quote fills a row and the other leaves it empty, ask the second studio to price it or confirm in writing that it is excluded. Most of the gap between two totals usually turns out to be rows like these.
7. When is the cheaper route the right one?
A studio is not the answer to every design need. These are the cases where we would tell you to spend less.
- You have a queue of small, well-defined requests in a style that already exists. A design subscription is built for that.
- You need a handful of screens added to a design system you already have. A good freelancer can do it.
- Design is needed every day on one product, and you can manage a designer. Hire one.
- You want one screen restyled this week, or the product to look newer and behave exactly as it does now. That is a smaller job than product design.
- Nobody on your side can make decisions. Fix that first, because any paid option will stall without it.
8. What we saw on Keeyu and Lumos
Two of our product design engagements show how the work runs when it is not a fixed scope. Neither record gives a price or a length, so we give neither here.
Keeyu had raised a pre-seed round when we began. We were embedded in its team, started in its staging environment and met its product and engineering team in a working session every week. We designed the product and built its design system in code, and Keeyu’s engineers built the product. Work like that suits an arrangement by the month, because the problem is defined as you go.
Lumos, at seed when we began, ran as a retainer on one part of its platform, the tool campaign planners use to buy media. We audited the tool end to end, then designed the high-fidelity screens, a reusable component library and the specifications the engineering team built from, along with the design system. The audit came first because it showed how much had to change before anyone designed a screen.
9. What should you ask before you sign?
10. How do you start product design with Refract?
Send us the product, the problem and your budget range, and we will recommend an engagement to fit. We agree the scope, the price and the timeline before we start, and we can usually begin within a couple of weeks. Most of the companies we work with have raised a seed or Series A round, and we take on earlier companies where we can see a long partnership.
If you would like to try working with us before you commit to a month, one week on one problem, such as a UX audit or a product sprint, costs a fixed $2,500. If more work with us starts within 60 days, the $2,500 comes off its price.
11. Questions
Refract, a studio in Sydney, prices product design from $10,000 a month and an embedded team from $10,000 to $30,000 a month. Of other Australian studios that print a figure, Morphic lists $3,499 a month for 60 hours, Raw.Studio’s design team is from $8,400 a month plus GST, Ippon Australia’s retainer starts at $10k a month and UntilNow’s retainer starts at 18K a month in US dollars.
At Refract, a focused piece of product design on one area of the product usually takes four to six weeks, an MVP eight to twelve weeks and a full product design engagement ten to sixteen weeks. What moves it is the scope: how many journeys, kinds of user and connected systems. Agree the scope and the timeline with the studio before work starts.
Pay by the month when the problem is still being defined or the product keeps moving, because the team can work on whatever matters most. Pay for a fixed scope when you can write down the users, the task and the deliverables, and the work has a clear end. If the scope is still open, fix the price of the step that settles it first.
Ours costs from $10,000 to $30,000 a month. Where you sit in that range, who is on the team and any minimum term or notice are agreed before the first month. It runs by the month and you can change it as the work changes. Other studios describe similar arrangements as a retainer, team augmentation or a design team plan.
It should list the journeys in scope, the people doing the work and how much of their time you get, and the deliverables: flows, a prototype, screens for every state, a design system in Figma or in code, and review of the build. It should also say whether engineering is included, the length, the terms and who owns the work at the end.
Written on by