# Product Discovery for Startups & Founders Tight-loop discovery sprints for founders: problem framing, hypothesis tests, technical feasibility, and a shipped clickable prototype in weeks. Canonical: https://www.metaborong.com/services/product-studio/product-discovery Service: product-studio/product-discovery ## Overview 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. ## What is it? 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 - Discovery report covering target user, problem framing, jobs-to-be-done, and competitive gap. - Clickable Figma prototype walking the riskiest user journey end-to-end. - Engineering build estimate ranged in weeks with assumptions and constraints documented. - Architecture sketch covering data model, third-party services, and integration boundaries. - Risk register naming the three assumptions most likely to break the product. - Stakeholder interview deck with raw transcripts and clustered insight themes. ## How we work 1. **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. 2. **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. 3. **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. 4. **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 Figma (Design), Maze (User Testing), Dovetail (Insight Synthesis), Otter.ai (Transcripts), Notion (Reporting), Miro (Workshops), Loom (Async Reviews), Linear (Backlog) ## When this fits ### Fits when - You have a problem you keep hearing from customers but no validated solution yet. - You are pre-build and want an outside read before committing engineering capital. - You have raised pre-seed or seed capital and need to defend the roadmap to a board. ### Does not fit when - You already have a shipped product and need help with retention or growth. - You want a brand identity or marketing site - that is design work, not discovery. - You need a fixed-bid build quote next week - discovery does not collapse that fast. ## FAQ ### How long does a discovery engagement take? 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. ### Do we have to use Metaborong for the build afterwards? 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. ### Can you sign an NDA before kickoff? 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. ### What if discovery shows the idea will not work? 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.