Video testimonial from Eric Fan, Founder and CEO, Lumos.
Product design
Products people can work out on their own.
UX and UI design for software with a lot going on. We help product teams make setup, everyday tasks and difficult decisions easier to follow.
In short
What you get
Audit findings in the order to fix them, flows and a prototype for the journeys in scope, interface designs for every screen and state, and a design system in Figma and, where it is in scope, in code.
What it costs
Product design starts from $10,000 a month. An embedded team is $10,000 to $30,000 a month. To try working with us first, you can take one week, such as a UX audit or a product sprint, for a fixed $2,500.
How long it takes
Four to six weeks for a focused piece on one area of the product. Ten to sixteen weeks for a full engagement across it. A first piece of work is one week.
When it’s not a fit
You need one screen restyled this week, nobody on your side can make a decision, or you want the product to look newer and behave exactly as it does now.
Inside product design
Narrower pieces of this work, each one you can start with.
- UX auditOne journey in your product, the problems in order and what to change.
- Product sprintOne problem, a working prototype in front of your users and a build plan.
- Design systemsThe parts your product is built from, in Figma and in code.
- Mobile app designFlows, screens and components for an app, tested on the device.
- Embedded design teamOur designers inside your product team, on your board and in your reviews.
In their words.
The system behind the screens
At Keeyu, the work centred on the relationships between setup, operations and the customer’s next action. Reusable patterns helped connect those journeys. A design system should carry those decisions forward along with the typography, colour and components.
Inventory the patterns people already use and identify where they behave differently.
Document when a pattern applies, what content it needs and how it responds to errors.
Agree component behaviour with the people implementing and maintaining it.
How we work through a difficult task
Understand
Agree the user, task and success criteria. Review the live product and the evidence available.
Explore
Map the flow and prototype the decisions that carry the most uncertainty.
Review
Test with representative users where the scope allows, and review feasibility with engineering.
Refine
Resolve the states and details, document the pattern and review it in implementation.
Ways to start
Bring a product link, one difficult journey and the decision your team needs to make.
A UX audit
A focused review with prioritised findings, evidence and the next changes to investigate.
A product sprint
A defined problem, a prototype and a plan for what to test or build next.
An embedded design team
Design support alongside your product and engineering team as the work develops.
Related services
Questions before we start
Yes. We can begin with one journey or an audit of the existing experience. That may lead to a redesign, or to a smaller change in structure, wording or behaviour.
The flows, interface designs, relevant states and reusable component guidance we’ve scoped. We settle the prototype format, documentation and implementation review with your team before starting.
It can be. Design and build can be scoped separately or together. We can work with your engineers, or build it ourselves: the people who design it also build it, so nothing is lost between a design file and the code.
Product design starts from $10,000 a month. The price depends on the journeys involved, research access, technical constraints and deliverables. Send us the product, the problem and your budget range and we’ll recommend an engagement to fit.
A focused piece of product design on one area of the product usually takes four to six weeks. A full product design engagement usually takes ten to sixteen weeks. We agree the scope and the timeline before we start.
Three ways. A UX audit is a focused review with prioritised findings, evidence and the next changes to investigate. A product sprint takes a defined problem to a prototype and a plan for what to test or build next. An embedded design team works alongside your product and engineering team as the work develops. The audit and the sprint have their scope and price agreed upfront.
Pick a measure tied to the task, such as successful setup, recovery from an error or support demand. If there’s no baseline, working out what to instrument is part of the job. A polished prototype alone is not evidence of improvement.
Yes. Our studio is in Sydney, and most of our product design has been for young software companies. Keeyu and Atrium had each raised a pre-seed round when we began, and Lumos and Managed were at seed. We usually work with companies that have raised a seed or Series A round, and take on earlier ones where we can see a long partnership.
Yes. On Keeyu we worked inside the team, beginning in their staging environment and meeting product and engineering every week. An embedded team costs from $10,000 to $30,000 a month. It runs by the month and you can change it as the work changes.
Yes. We built the design systems for Keeyu, Lumos, Managed and Atrium in code, alongside the design work in Figma. A design system can be one part of a product design project or a piece of work in its own right, which suits a product that has grown one component at a time.
Yes. We designed the DoughPro app, and on Atrium the mobile product was designed as part of the same system and tested on the device. For Lumos we designed the planning surface, including its asset map, measurement dashboard, scheduler and reporting table.
An audit finds the problems in the product you have and puts them in order. A redesign changes the product. The audit comes first because it shows how much has to change. Sometimes that is a new structure, and sometimes it is a short list of changes to wording, order and behaviour.
A closer look at the work
- Designing complex SaaS workflows: lessons from KeeyuHow relationships, progress and contextual guidance shape a usable product, and how to apply those lessons to your next difficult workflow.
- How to run a UX audit that leads to useful fixesA UX audit follows real tasks through your product, records where people get stuck and ranks fixes by user impact, evidence and the effort required.
- Prototype vs MVP in 2026: what should you build first?A prototype tests a question. An MVP is a usable first product. Choose the next build by the uncertainty you need to resolve and what real use requires.
Is one task in your product harder than it should be?
Send us the product and tell us which task. We’ll say what we’d look at first.
Most teams start with a call, then a sprint or an audit.
The people you’d work with, from the first call to launch

