Product Studio · Discover
Product Discovery
Product Discovery is a four-to-six-week strategy engagement that takes a founder's loose idea and exits with a tested concept, a build-ready scope, and a clickable prototype. We pair a senior product strategist with a designer and a technical architect. Together we frame the real problem, run two cycles of customer interviews, and prove the riskiest assumption with a working artefact. You walk away with a written discovery report, a Figma prototype, and an engineering estimate ranged in weeks. We do this for founders without a product team and for funded teams that need an outside read before committing capital. We run the work in two-week cycles with weekly written check-ins, so the founder stays in the loop without a daily call. The output is a go/no-go decision, not a pitch deck.
In short
What is Product Discovery?
Product Discovery is a four-to-six-week strategy engagement for founders that exits with a tested concept, a prototype, and a build-ready estimate. Metaborong delivers discovery from India for clients across North America, Europe, and APAC, with its delivery independently reviewed by clients on Clutch.
What we deliver
Concrete artefacts, not capabilities
- 01
Discovery report covering target user, problem framing, jobs-to-be-done, and competitive gap.
- 02
Clickable Figma prototype walking the riskiest user journey end-to-end.
- 03
Engineering build estimate ranged in weeks with assumptions and constraints documented.
- 04
Architecture sketch covering data model, third-party services, and integration boundaries.
- 05
Risk register naming the three assumptions most likely to break the product.
- 06
Stakeholder interview deck with raw transcripts and clustered insight themes.
How we work
Engagement phases
Problem framing
We start with a half-day workshop to write the problem statement in plain language. We then mine existing customer signal - sales calls, support tickets, founder DMs - for evidence the problem is real. We exit with a one-page brief, named user segments, and the hypotheses worth testing first.
Customer evidence
We run two cycles of customer interviews - eight to twelve conversations per cycle, recorded and clustered. Between cycles we tighten the script around the assumptions that did not break. Output is a synthesised insight document and a sharp definition of who would pay, why they would pay, and what they would replace.
Prototype the risk
We pick the one user journey that decides whether the product is viable. A designer builds a clickable Figma prototype walking that journey end-to-end. We test it with three to five target users on Zoom, watch where they hesitate, and rebuild the parts that confused them before sign-off.
Build-ready handoff
We close with a written discovery report, the prototype, an architecture sketch, and a build estimate ranged in weeks. If the right call is not to build, we say so on the record. Founders who proceed get a scoped engineering plan and an introduction to whoever should lead delivery.
Tech stack
What we build on
- FigmaDesign
- MazeUser Testing
- DovetailInsight Synthesis
- Otter.aiTranscripts
- NotionReporting
- MiroWorkshops
- LoomAsync Reviews
- LinearBacklog
- FigmaDesign
- MazeUser Testing
- DovetailInsight Synthesis
- Otter.aiTranscripts
- NotionReporting
- MiroWorkshops
- LoomAsync Reviews
- LinearBacklog
Scope
When this fits and when it doesn't
| This fits when | This doesn't fit when |
|---|---|
| You have a problem you keep hearing from customers but no validated solution yet. | You already have a shipped product and need help with retention or growth. |
| You are pre-build and want an outside read before committing engineering capital. | You want a brand identity or marketing site - that is design work, not discovery. |
| You have raised pre-seed or seed capital and need to defend the roadmap to a board. | You need a fixed-bid build quote next week - discovery does not collapse that fast. |
Related services
Adjacent engagements
- Product Studio
MVP Development
Zero-to-launch product builds - founder-led scope through first paying users.
- Product Studio
SaaS Development
End-to-end SaaS builds with multi-tenancy, billing, and observability baked in.
- AI
AI Consulting & Strategy
Use-case mapping, feasibility, and a sequenced adoption plan scoped to impact and operating cost.
Frequently asked questions
Four to six weeks, end to end. Shorter than that risks skipping a customer-interview cycle. Longer than six weeks usually means we should have stopped and shipped a smaller test instead. We agree the date for the build-ready handoff at kickoff and treat it as a hard deadline that the engagement closes against.
No. Roughly a third of discovery clients hand the report to their own engineering team or a different studio. We design the handoff for that case - the architecture sketch, estimate, and risk register are written for a competent third party, not gated on us. If you do want us to build, we discount the discovery fee against the build engagement.
Yes. We sign a mutual NDA before the first scoping call and route paid engagements through a short MSA. We do not name clients in marketing without written permission. Our engagements are independently reviewed by clients on Clutch; several others stay unnamed at the client request. Discovery work tends to touch unannounced strategy, so we default to confidentiality.
We say so, on the record, in writing. Roughly one in five discovery engagements ends with a recommendation not to build the proposed product. That is a successful outcome - you save twelve months of build cost and find out before the wrong commitment. The discovery fee is non-contingent and paid either way.
Tell us what you are building.
We build what large agencies under-deliver and freelancers can't architect, across Web3 protocols, AI agents, and SaaS products. Tell us what you are building. We will tell you how we would approach it, no pitch deck, no fluff, no commitment required.