Product design is for founders and product leads who are still deciding what to build. We work with you from the first assumptions to a tested, buildable design: discovery, prioritisation, prototypes, validation with real users and handoff to delivery. If the product already exists and you want to improve how it works, UI/UX design services are the closer fit.
When do you need product design rather than UI/UX design?
You need it when the hard question is what, not how. Two concepts compete and nobody has evidence for either. A pilot lost most of its users in the first session. A new product line has a budget and a date, but no agreed scope. Board or investor questions need an answer you can show.
You do not need it when the scope is settled and the product is live. Then the work is interface and usability, and a UI/UX project is faster and cheaper.
What does the work look like?
Discovery
We interview the people who would use the product, review what competitors and workarounds exist, and write down the riskiest assumptions. Founders usually know the problem well and the user poorly, so this step moves things most.
Prioritisation
We turn the findings into a short list: the users to serve first, the journeys that must work in release one, and what waits. This is the step that protects your runway. Features that do not serve the first journey leave the plan, with the reasoning written down.
Prototypes
Each live hypothesis becomes a clickable prototype detailed enough for a person to complete a task. When two ideas compete, we build both and test them in the same sessions, so the comparison rests on behaviour and not on opinion.
Validation
We run moderated sessions with people from the target group, record task completion and hesitation, and synthesise the result into a written decision: what won, what lost and which questions remain for after launch.
Design to delivery
The winning flow is rebuilt as components with named tokens and annotated notes. Your engineers, or ours, can start from a validated baseline instead of a static mockup. Designers stay on call through the first build iterations, because the first questions from developers are where designs usually break.
What does a product design engagement deliver?
A UK-based seed edtech had a working backend, two competing ideas for its core learning flow and a pilot where most learners left in the first session. We ran a five-day design sprint, built a prototype for each idea and tested both with six learners. The case study reports ~40% reduction in learner drop-off at beta, ~35% faster task completion in the tested flow and 8 weeks from concept to beta launch, as directional figures. Read it here: product design sprint for an early-stage edtech.
What does it cost to own?
Price is driven by the number of user groups, how many hypotheses need prototypes, how many testing rounds you want and whether the same team continues into the build. We scope it after a short call about your idea and your users. A founder who already has user evidence can skip some steps and pay for less.
Who works on it with you?
A product designer leads, with a researcher for interviews and testing when the scope needs one. An engineer joins early to check what the design costs to build, so the plan you get is one your developers can estimate. You see work in progress at every stage, and decisions are written down with their reasons, so a new stakeholder can follow how you got there.
How does this connect to the rest of our work?
Product design often comes first in a sequence. It is followed by UI work on the screens that matter, and by a design system once several teams build on the product. Our product discovery approach describes the first stage in more detail, and design services maps all of it. If you want a designer on your side of the table, see how to hire a UI/UX designer.