Unified Startup Enablement & Growth Platform

42% of Startups Fail Building Something Nobody Wants

42% of startups fail because they build something nobody wants. MVP planning forces you to validate before you invest months of engineering time. The purpose of an MVP is not to build a small product — it is to answer a specific question about your market with the least possible effort.

The word "minimum" in MVP is not about low quality. It is about minimum scope to test a maximum learning hypothesis. Indian startup teams often skip MVP discipline because building feels more productive than the discomfort of hearing "no" from the market. It is not.

ONE core problem: If your MVP solves more than one problem, it solves none well enough to validate
6-12 week scope: If it takes longer, you're building a product, not an MVP
Measurable success criteria: Define what "validated" means before you build, not after
Ruthless prioritisation: MoSCoW framework — Must Have, Should Have, Could Have, Won't Have

What Makes a Good MVP

Solve ONE Core Problem

The most common MVP mistake is scope creep disguised as comprehensiveness. Founders think: "If we launch with just this one feature, customers won't take us seriously." The opposite is true — a product that does one thing brilliantly is more impressive and more usable than a product that does ten things adequately.

Define the single job your MVP does. Write it in one sentence: "Our MVP lets [specific user] do [specific action] so that [specific outcome]." If you need more than one sentence, you have more than one MVP worth of scope.

Shippable in 6-12 Weeks

If your MVP takes more than 12 weeks of engineering time to build, reconsider your definition of "minimum." Break it down until you find the version that can ship in 6 weeks. That version teaches you more and costs less. The larger version can be built after you've validated the core hypothesis.

For Indian startups with lean engineering teams of 2-4 people, a 6-week MVP typically means: one core user flow, basic auth, essential data persistence, and just enough UI to be usable. Not beautiful. Usable.

Measurable Success Criteria

Before writing a single line of code, define what success looks like. Without pre-defined criteria, every outcome gets rationalised as a learning — even complete product-market mismatch. Be specific and be honest.

Wrong: "We'll see if people like it"
Right: "10 users will complete the core flow at least 3 times in the first 2 weeks without prompting"
Wrong: "We'll get feedback and iterate"
Right: "50% of beta users will say they would be very disappointed if the product went away (Sean Ellis test)"

MoSCoW Prioritisation

Category	Definition	Example (B2B SaaS MVP)	% of MVP
Must Have	Without this, the MVP fails its core hypothesis and cannot be tested. Non-negotiable.	User login, core workflow (e.g., invoice creation), basic data save/retrieve	60-70% of engineering effort
Should Have	Important but not critical for the initial test. Include if time permits.	Email notifications, basic search, CSV export, simple dashboard	20-25% of engineering effort
Could Have	Nice-to-have features that won't affect test validity if absent.	Dark mode, keyboard shortcuts, advanced filters, integrations	5-10% of engineering effort
Won't Have	Explicitly excluded from this MVP. Document them so the team stops discussing them.	Mobile app, multi-language support, enterprise SSO, advanced analytics	0% — defer to post-validation

MVP vs Prototype vs POC

Proof of Concept (POC)

A POC answers the question: "Can this be built?" It is purely technical — no UI required, no user involved. Indian deep-tech and fintech startups building on novel infrastructure (blockchain, ML pipelines, hardware integration) often need a POC before committing to product development. A POC takes days to weeks and is internal-only.

Indian example: An agritech startup building AI-based crop disease detection first builds a POC that classifies images with 80%+ accuracy using a Jupyter notebook — before touching any app design.

Prototype

A prototype answers the question: "Does this feel right to users?" It simulates the product experience without full backend functionality. Figma prototypes, clickable wireframes, or static HTML pages — the goal is usability feedback, not technical validation. A prototype takes 1-3 weeks and is shown to 5-10 target users for qualitative feedback.

Indian example: An EdTech startup shows a Figma prototype of their tutoring platform to 8 parents in Noida before writing a line of backend code. Three of their core UX assumptions are wrong. They redesign before building.

MVP

An MVP answers the question: "Will people actually use this to solve their problem?" It is a real, functional product — not a mockup — used by real users in real conditions. The bar for MVP is: users can complete the core flow independently, data persists, and you can observe real behaviour. Takes 6-12 weeks and is used by 20-100 early adopters.

Indian example: A B2B logistics startup builds an MVP that lets warehouse managers create, assign, and track tasks — nothing else. 15 warehouses use it for 4 weeks. Task completion rates and re-use data validate the core hypothesis before Series A fundraising begins.

MVP Success Metrics by Type

MVP Type	Key Metric	Target
Landing Page MVP	Email signup conversion rate from visitors who see the value proposition	>5% signup rate from cold traffic; >25% from warm/referred traffic
Concierge MVP	Customer willingness to pay for the manually-delivered service	At least 3 paying customers at target price point within 4 weeks
Wizard of Oz MVP	User task completion rate and repeat usage without knowing it's manual	>70% task completion; >50% return within 7 days for a second task
Functional MVP	Weekly active usage rate and Sean Ellis score (% "very disappointed" if gone)	>40% WAU of registered users; >40% very disappointed on Sean Ellis test

Frequently Asked Questions

How do we know when our MVP is "done enough" to ship? +

Your MVP is done enough when a target user can complete the core workflow independently, without hand-holding or workarounds, and you can observe real usage data. Not when it is beautiful, fully documented, or feature-complete. The test: take 5 people from your exact target segment, hand them the product with no instructions, and watch what happens. If they complete the core flow — it is ready. If they cannot — it is not, regardless of how polished it looks.

Should we charge for our MVP or offer it free? +

Charge — even a nominal amount — from day one if you are building a B2B product. A customer who pays Rs.5,000 per month gives you far richer signal than a customer who uses a free product. Willingness to pay is the strongest validation signal available. For B2C consumer products, free is often necessary to reach sufficient scale for meaningful data. For enterprise B2B, free pilots with no commitment create low-engagement evaluations — paid pilots create genuine stakeholder involvement and real feedback.

What is the minimum number of users needed to validate an MVP? +

For qualitative validation: 5 users is enough to identify 85% of usability issues (Nielsen's Law of Diminishing Returns). For statistical confidence on quantitative metrics: 20–50 users over 4–6 weeks gives meaningful retention and engagement data. For the Sean Ellis test (PMF measurement): you need at least 40 responses to get a statistically meaningful "very disappointed" score. Do not wait for hundreds of users to draw conclusions — the insights from 20 engaged users are more valuable than shallow data from 1,000 disengaged ones.

My co-founder wants to add more features before launch — how do I manage scope creep? +

Return to your hypothesis. Every feature request during MVP development must answer: "Does this feature test our core hypothesis or distract from it?" If the feature does not directly test whether your core value proposition is true, it goes in the backlog. A useful framing: give each proposed feature a MoSCoW classification (Must Have, Should Have, Could Have, Won't Have). Any feature classified below "Must Have" does not ship with the MVP. This is a conversation about the purpose of the MVP, not about whether the feature is a good idea.

Key Takeaways

"Minimum" refers to scope, not quality — your MVP must be usable, not just functional.

The most damaging MVP mistake is building something so stripped down that users cannot evaluate whether they would use the real product. The MVP must be minimal in scope but good enough in execution that users can genuinely engage with the core value proposition. Unusable does not mean lean — it means you wasted 6 weeks building something that tests nothing.

Define your success criteria before you write a line of code.

Without pre-defined criteria, every outcome gets rationalised as a learning — even complete product-market mismatch. Write down: "We will consider this MVP validated if X users do Y behaviour Z times in W weeks." If the criteria are met, double down. If not, pivot or kill. This discipline is what separates structured product development from endless iteration without direction.

Ship in 6-12 weeks or your MVP has become a product.

An MVP that takes longer than 12 weeks of engineering is not an MVP — it is a product being built without validation. When scope creep pushes the timeline beyond 12 weeks, stop and cut scope until you have a 6-week deliverable. The version that ships in 6 weeks teaches you more and costs less than the version that ships in 6 months — even if the 6-month version has more features.

Inside Corpfy MVP Planning

Corpfy's MVP Planning dashboard combines a feature board, RICE prioritisation scoring, sprint planning with capacity management, and a Build-Measure-Learn cycle tracker — giving technical founders a structured way to decide what to build first and then measure whether it worked. No separate Notion, Jira, or spreadsheet required for early-stage planning.

What you get in the dashboard

Feature	What it does	Founder benefit
Feature Board	Tracks features by status (Backlog / Planned / In Progress / Done / Blocked) with P0/P1/P2 priority and S/M/L effort sizing	Every engineer knows exactly what is in scope for the current sprint — no ambiguity
RICE Prioritisation	Scores each feature on Reach, Impact, Confidence, and Effort — calculates RICE score automatically	Defend your build order to investors and co-founders with a framework, not an opinion
Sprint Planner with Capacity	Plans sprints with total capacity in story points and tracks what is committed vs what is complete	Stops the classic pre-launch problem of over-committing and under-delivering each sprint
Build-Measure-Learn Tracker	Documents hypothesis, build action, measurement method, and learning per experiment cycle	Forces rigour on what you're testing and whether you actually validated the assumption
Blocker Management	Surfaces blocked items with resolution paths so bottlenecks are visible to the whole team	Blockers don't hide until a sprint retrospective — they're visible the day they appear