Discovery is the phase where an idea becomes a buildable, priceable plan — and the phase most often skipped by buyers in a hurry and vendors eager to start billing. Skipping it does not save the time; it relocates the confusion into the expensive part. Here is what real discovery produces, and what it should cost.
What discovery actually is
One to three weeks (sized to project complexity) of structured questioning before commitment: users mapped, workflows walked, integrations listed, risks surfaced, scope carved into must/later. Not a sales ritual — a working phase with named deliverables you own regardless of who builds.
The deliverables that matter
| Artifact | Why it matters |
|---|---|
| Scope document | Features as stories with acceptance criteria — the fixed price's foundation |
| User flows | The 5–8 critical paths sketched screen-by-screen — cheap to argue about now |
| Architecture note | Stack, integrations, data model shape, tenancy and compliance calls |
| Risk register | The messy data, the undocumented API, the approval nobody mentioned |
| Phased plan + fixed price | MVP line drawn, timeline honesty, a number that means something |
The under-appreciated one is the risk register: every project has three surprises, and discovery's job is meeting them on paper instead of in week nine.
What good discovery feels like
Uncomfortable, mildly. A real discovery pushes back — cutting your feature list (the MVP test), questioning the workflow you assumed, surfacing the integration that doubles effort. Discovery that agrees with everything is a sales process wearing a lanyard.
Cost and the honest deal
₹25k–1.5L depending on complexity — typically credited against the build if you proceed. The deal that keeps everyone honest: you own the deliverables, walk-away allowed. A vendor who holds discovery output hostage told you everything about month six.
Skipping discovery is rational exactly once: when scope is genuinely tiny and known (a landing page needs a brief, not a phase). For anything with roles, integrations, or money flows, the week pays for the quarter.
Book a discovery conversation — we will tell you in the first call whether your project even needs the full phase, and the deliverables are yours either way.
Frequently asked questions
What is a product discovery phase?
One to three structured weeks before commitment: users mapped, workflows walked, integrations listed, risks surfaced, scope carved into must/later — producing a scope document, user flows, architecture note, risk register, and a phased fixed price you own.
How much does product discovery cost?
₹25,000–1.5 lakh depending on complexity, typically credited against the build if you proceed. The honest arrangement: you own all deliverables and can walk away — vendors who hold discovery hostage have told you about month six.
Can I skip discovery to save time?
Only for genuinely tiny, known scope. Otherwise skipping relocates confusion into the expensive build phase — the surprises arrive in week nine as change orders instead of on paper in week one. A day of clarity saves weeks of rework.
What does good discovery feel like?
Mildly uncomfortable: real discovery cuts your feature list, questions assumed workflows, and surfaces effort-doubling integrations. Discovery that agrees with everything is a sales process wearing a lanyard.