Product Design
Interface as a lever for results, not as a finish. Two practices that start from the same principle: whatever blocks the user costs money, and you can measure how much.
Talk to a specialistAnyone can buy good-looking design. Design that moves a number, not so much.
When a digital product’s numbers do not add up, the conversation usually turns aesthetic: the screen looks dated, the typography is weak, the blue does not work. Redesigning on that basis burns budget and moves the number very little, because the problem was almost never there.
What kills conversion is concrete friction one step more than necessary, a field asking for what the person does not have to hand, an error that does not say what to do next. Product design is finding those points and removing them. That is why here it is measured in completion rate, churn and support tickets, not in opinions about the screen.
The two fronts
They share the same method, but what decides the result differs in each.
- UX/UI for Mobile Apps. An app lives on conversion and support. The work concentrates on sign-up, the revenue flow and error states the three places where friction costs most.
- UX/UI Strategic Design for SaaS. SaaS lives on renewal. The customer reassesses the decision every billing cycle, so the focus is shortening the path to the first real result and making visible what would justify paying more.
What we deliver
It applies to both fronts. What changes is where each step pinches.
- Funnel assessment. Where people drop out, at which step and in which profile. Product data first, opinion after.
- Research with real users. Watching five people use the product reveals in an afternoon what weeks of internal meetings do not because whoever built it can no longer see it the way a first-time user does.
- Information architecture. What appears on each screen and what goes. Much of the gain comes from removing, not adding.
- Interface and design system. Consistent components, with loading, error and empty states defined precisely where most products abandon the user.
- Accessibility. Contrast, touch target size and screen reader support. It is not only compliance: a small target lowers conversion for everyone, not just for people with impairments.
- Handoff to development. A specification the team implements without guessing: behaviour, measurements, edge cases and what happens when the network drops.
Where this meets the data practice
- Products that show data to the customer. Many SaaS products have to deliver a dashboard to their own users. That is where the two practices meet: the data architecture holds up the number, and the design decides whether anyone can understand it.
- An internal dashboard nobody uses. When the problem is adoption rather than technology, design and data literacy solve more than rebuilding the dashboard.
How we run it
We start with the product data you already have and with observation sessions with real users. That survey produces a list prioritised by impact on the metric you want to move not by aesthetic preference. Delivery runs in short cycles, critical screen first, so the result shows before the project ends.
How we measure results
The metric is agreed at the start and it is a product metric: completion rate, main flow conversion, drop-out by step, first-cycle churn and support ticket volume. We record the starting value before touching a single screen without it there is no way to prove the gain afterwards.
We now have a far more robust, fast and visual view of each management area’s results.
Sales director national fuel distributor
About this service
Do you build the product as well?
The practice is design: research, information architecture, interface and specification. Implementation stays with your development team, and the handoff is written so they do not have to interpret behaviour. If you do not have that team, we can talk about the squad model.
We already have a live product. Do you rebuild everything?
It rarely pays off. We start with the funnel assessment, which points at the few screens where money is being lost. A full redesign is a cost decision, and the prioritised version almost always delivers faster for less.
How does design turn into financial return?
Through two measurable routes: more people completing the flow that generates revenue, and fewer people contacting support because they do not understand the screen. That is why we record the starting point before beginning without it the gain becomes a story.
Do we really need user research?
It is the step most people want to skip and the one that changes the result most. Watching a handful of people use the product usually reveals problems no internal meeting would.
Do you deliver in Figma?
Yes, with the design system componentised and the behaviour specification alongside. The file stays with you, organised so your team can evolve it without depending on us.
Where is your product losing people?
A 30-minute conversation and your funnel data are usually enough to point at the first one.
We understand processes before recommending technology. Automation, data, artificial intelligence, and custom software for companies seeking efficiency, control, and scale.