Products built around people, not features.
I think about the whole product — the problem, the user, the business model and the roadmap — not just the screen in front of me.
Why this matters.
Product design is strategy made visible. Before drawing anything I want to know who the product is for, what job it does for them, and how it makes money. That context is what turns a nice-looking screen into a feature that actually moves the business.
I have spent a decade inside product teams alongside managers, developers and stakeholders. I know how to scope an MVP, prioritise a roadmap, and make the trade-offs that keep a product shippable.
Deliverables & scope.
Clear problem framing, positioning and success metrics before design begins.
How the product is organised so it stays simple as it grows.
Flows, wireframes and high-fidelity UI for every key journey.
Scoping and prioritisation so you build the right things first.
How we work.
Define the problem, user and goals.
Architecture and core journeys.
Flows, screens and a design system.
Ship, measure, improve.
What this delivers.
- A product that solves a real, validated problem
- Faster decisions thanks to clear priorities
- Design that scales with the roadmap
Product Design questions.
How is product design different from UI/UX design?
UI/UX focuses on the experience and interface. Product design wraps that in business strategy — what to build, for whom, and why, plus how it ties to revenue and the roadmap.
Do you help define the MVP?
Yes. Scoping a lean, valuable first version is one of the most useful things I do for early-stage founders.
Can you work with our existing PM and devs?
Definitely. I have spent years inside cross-functional teams and slot in easily.
Do you cover both web and mobile?
Yes — SaaS web apps, marketing sites and native iOS/Android products.