Lab · Product Discovery
Validate before you build.
Product Discovery helps you test assumptions, understand users and reduce wasted product investment.
What discovery includes
Learn first. Build second.
Problem framing
Get clear on what you're actually trying to solve, and for whom.
User interviews
Structured conversations with the people closest to the problem.
Opportunity mapping
Where the real product bets are — and where they're not.
Prototype testing
Low-cost prototypes used to learn, not to ship.
Market validation
Signal on willingness, demand and the path to first revenue.
Concept design
Translate validated insight into a buildable product concept and brief.
Best for
Where discovery pays back fastest.
Startups
Pre-product teams choosing what to build first.
NGOs
Programs deciding whether a digital product is the right intervention.
Innovation teams
Internal teams testing a new bet before asking for budget.
FAQ
Common questions.
Are discovery sprints actually running?
Pilot discovery sessions are opening in Kigali. Slots are limited while we onboard the first cohort of partners.
How is Discovery different from Product Lab?
Discovery answers should we build this and what should we build first. Product Lab builds it. Many teams do Discovery first to de-risk the build.
What does intake look like?
A short scoping session to align on the problem, users and decision you're trying to make, followed by a written proposal.
What happens after I book?
We confirm receipt within 2 business days, run the scoping session, then open the pilot discovery sprint in Kigali on the agreed start date.
How long does Discovery take?
Typical sprints run 3–4 weeks, ending in a decision-ready recommendation on what to build, what to kill and what to test next.