What does a product discovery engagement typically cost?
Pricing varies depending on scope, team size, and the complexity of the product concept. A focused two-week discovery for a single product idea will cost significantly less than a six-week engagement covering multiple user segments and a complex technical architecture. We scope each engagement individually after an initial call, so you receive a clear proposal rather than a range that tells you very little.
How long does product discovery take?
Most engagements run between two and six weeks. A tightly scoped discovery for an early-stage concept can be completed in two weeks. A more complex engagement — covering multiple user personas, a regulated industry, or a significant technical unknowns — typically takes four to six weeks. We agree the timeline upfront and do not extend it without a clear reason.
What do we actually receive at the end of the engagement?
You receive a set of concrete, decision-ready documents. These typically include a validated problem statement, user research findings, a prioritised feature list, a technical feasibility report, wireframes or a prototype, and a phased delivery plan with effort estimates. Everything is formatted for internal presentation, so you can take it straight to a board meeting or investor conversation.
Who is product discovery for?
Discovery is well-suited to three types of buyers. Founders building a first product who need to validate an idea before committing development budget. Product leaders at scale-ups who are planning a significant new feature or a platform rebuild. Heads of engineering or CTOs at established companies who need a business case and a technical plan before going to the board. If you already have a clear, validated spec and an aligned team, you may not need discovery — we will tell you that on the first call.
How is discovery different from just starting the project?
Starting a project without discovery means your first sprint is built on assumptions. Discovery replaces those assumptions with evidence. The practical difference is that teams who complete discovery before development typically spend less time in rework, have fewer mid-project scope changes, and ship a first version that is closer to what users need. Discovery is a short, fixed-cost engagement; a mid-project pivot is neither short nor fixed-cost.
Do we need to have a technical team in place before starting discovery?
No. Discovery is designed to inform those decisions, not depend on them. Many clients come to us before they have hired engineers or chosen a technology stack. The technical feasibility work we do during discovery often informs exactly those choices — what skills to hire for, which infrastructure approach makes sense, and where to use off-the-shelf components versus custom builds.
What are stakeholder interviews and why do they matter?
Stakeholder interviews are structured one-to-one conversations we conduct with the key people inside your organisation who have a view on the product — founders, product managers, engineers, sales leads, and customer success teams. They surface conflicting assumptions, hidden constraints, and strategic priorities that rarely appear in a brief. Resolving those conflicts during discovery rather than during a sprint review saves significant time and budget.