5-day Product Discovery
Before coding, we decide. Five days, five deliverables: audit, interviews, benchmark, target architecture and quantified roadmap.
Most projects that derail derail at scoping. Too much scope, not enough field evidence, untested hypotheses dressed up as certainties.
Our Discovery lasts exactly five days. Not three (too short to dig into interviews), not ten (analysis paralysis). At the end you have a signed go/no-go and a roadmap actionable the following week.
What we deliver
Data & analytics audit
Funnel mapping, top 3 quantified leaks, priority hypotheses to dig into, drawn from GA4, Hotjar, support tickets.
Interview synthesis
Five user interviews (3 customers, 2 non-converted), jobs-to-be-done extracted, key frictions documented.
Target architecture
Technical schema, justified stack choices, debt identified, migration plan if rebuild.
90-day roadmap
Quick wins (1–3 wks), structural rebuild (4–8 wks), optimisation (9–12 wks) — quantified, prioritised by impact × effort.
How we work
- 01
Day 1 — Audit & analytics
We get inside the house. Analytics, dashboards, support — we map the funnel and note obvious biases.
- 02
Day 2 — Interviews
Five 30-minute conversations. No more. Whisper transcription, JTBD and frustrations extraction.
- 03
Day 3 — Stack & competitive
Technical audit, direct competitors benchmark, quantified positioning matrix.
- 04
Day 4–5 — Roadmap & restitution
Synthesis, target architecture, 90-day roadmap, restitution workshop with open challenge and signed go/no-go.
Use cases
Before a rebuild
Avoid redoing the same product with a fresh design — challenge product hypotheses first.
Before a build
Scope a realistic MVP, not the dream app from stakeholders' kick-off.
Quick diagnosis
When the product exists but KPIs stagnate — understand what's stuck without a 3-month audit.
Stack & tools
- GA4 / Plausible
- Hotjar / FullStory
- Whisper
- Notion
- Figma
- Linear