Discovery research
User interviews, market and competitor scans, jobs-to-be-done analysis. The output is a prioritised opportunity map — not a 60-page report nobody opens.
Product Discovery & Design
Find the right problem. Then design for it.
Validate before you build. We pair discovery research, UX/UI design, and product strategy so the thing you ship is the thing your customers actually need — not the thing your roadmap assumed.
- 01 Discover
- 02 Design
- 03 Validate
When this is for you
"We have ideas — we just don't know which one to build first."
You need opportunity sizing and prioritisation, not a brainstorm.
"We built it, but users aren't adopting it."
You need diagnostic discovery — usually a journey audit, occasionally a full re-prioritisation.
"We're about to commit a big engineering budget to a hunch."
You need cheap validation upstream of the build, before the cost of being wrong compounds.
"Our product surface has grown faster than its UX could keep up."
You need a coherent UI system and a redesign roadmap that doesn't break power users.
What we do
Product strategy
Positioning, value proposition, pricing-shape sketches, north-star metric definition. We frame the strategic bets so leadership can make decisions, not just receive options.
UX & UI design
From low-fidelity sketches to production-ready Figma. Design systems where they pay off; bespoke flows where the journey is the differentiator.
Prototyping & validation
Clickable prototypes for stakeholder alignment. Coded prototypes when we need real users on real interactions to surface what static mockups can't.
How we work
Most engagements run 6–12 weeks in three overlapping phases. We start narrow — five user conversations and a journey map — and only expand when the evidence demands it.
Weeks 1–3
Frame the problem
Stakeholder interviews, user research, opportunity mapping, riskiest-assumption identification. Output: a one-page brief that names the problem and the success criteria.
Weeks 3–8
Design the answer
UX flows, UI design, interactive prototypes. Weekly stakeholder reviews; bi-weekly user tests. Output: a validated prototype and a build-ready spec.
Weeks 8–12
Hand off to build
Design system handover, engineering pairing, success-metric instrumentation. We stay close to the first build sprints so the design intent survives implementation.
What you walk away with
- Opportunity map — prioritised problems with evidence backing each one.
- Validated prototype — clickable or coded, tested with real users.
- Build-ready spec — engineering can pick it up without re-discovering the rationale.
- Design system or pattern library — proportionate to your team size and growth path.
- Success metrics — instrumented from day one, not retrofitted.
- A team that knows why — discovery insights transferred, not locked in our heads.