Product and engineering
Complex products made easy to use, designed and built by one team.
Product design, internal tools and engineering for companies shipping software, by the same people from the first flow to the last commit.
The product is where every promise gets tested.
We design the flows and interfaces, build the internal tools your team keeps asking for, and engineer the systems underneath. It sits at the centre because brand makes the promise, marketing brings people in, and the product is where they find out if it was true. Our studio is in Sydney, Australia, and we work between Sydney and New York with companies shipping software.
How it meets the other two
Why the company exists, and how it sounds.
- Product design Customer experience
- People learn what a brand means inside the product, not on the homepage. So the onboarding, empty states and error messages get the brand’s voice.
Who hears about it, and how they find it.
- Engineering SEO / GEO
- Search engines and AI answers read your pages, not your pitch. Speed, structure and markup are engineering, so they go in from the first commit.
- Engineering Web
- The site and the product usually drift apart. We build both from the same components, so when the product moves, the site keeps up.
What people use every day.
Start with a product sprint.
One problem, a fixed length, and a working prototype in front of your users at the end. If it’s worth building, you’ll know. If it isn’t, you’ll know that cheaper.
- One product or flow
- Fixed length
- Price agreed upfront
Audit
An audit of the product or flow as it is
Prototype
A clickable prototype of the fix
Test
What your users did with it, in their words
Plan
A build plan and estimate, yours to keep
What we do, in detail.
Product design
The flows and screens people use, and the design system that keeps them consistent as the product grows.
- Flows
- Screens and states
- Design system
Internal tools
Tools for your own team, not your customers. Software shaped around how your company works, so the repetitive jobs get done without hiring more people for them.
- Operational interfaces
- Connected workflows
- Brand tools
Engineering
The systems and integrations underneath, built to take the load once people depend on them, and easy for your team to build on.
- Front end
- Back end and integrations
- Handover
Let’s fix it before your users find it.
Tell us where you are. We’ll tell you whether we’re the right team, and what we’d do first.
Explore more services
The same team, on the other two parts of the job.
From the blog
- 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.
- What is a product sprint, and when should you run one?A product sprint takes one product problem and a fixed length, tests a working prototype with the people it’s for, and ends with evidence and a build plan.
- 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.
Questions we get asked
If yours isn’t here, ask us. We’d rather answer it before you sign anything.
Yes, and we’d rather. We can design alongside your engineers, build with them, or take one piece of the product end to end and hand it back in a state they can keep building on.
Usually. We look at what you run before we scope anything, and if something sits outside what we do well, we’ll say so rather than learn it on your time.
No. A lot of our work starts with one flow, one internal tool or one integration. The product sprint exists for exactly that.
Both. The people who design it also build it, so nothing is lost between a design file and the code.
Both. We work with teams from pre-seed to the S&P 100. What they share is a product that has to work for people who rely on it.
Fixed, for a defined piece of work, or as a team over time for a product that keeps moving. We agree which before we start.
Product design starts from $10,000 a month. An embedded team, our designers and engineers inside your sprints, costs from $10,000 to $30,000 a month. A project is scoped together and billed in stages, and a product sprint has a fixed length with the price agreed upfront.
A focused piece of product design on one area usually takes four to six weeks. A full product design engagement usually takes ten to sixteen weeks. An MVP, or a build of that size, usually takes eight to twelve weeks. We agree the scope and the timeline before we start.
You do. The designs, the code and the documentation are yours.
We can stay on and keep improving it, or hand it over with what your team needs to run it. Your call either way.