What Is an MVP (Minimum Viable Product)?
An MVP — minimum viable product — is the smallest complete version of a product that delivers real user value and returns real learning about whether the product is worth building further. It is not a prototype (which tests feasibility), not a demo (which sells the idea), and not a version-one of the full product (which commits to the whole roadmap before validation).
How it works in practice
An MVP is defined by a single core user journey — the one thing the product must let a user do to prove the concept is valuable. Everything else is out of scope. In practice this means picking one primary user persona, one core problem, and one measurable success signal (activation rate, retention, willingness to pay), and shipping the leanest possible implementation that lets you observe that signal. A well-designed MVP typically ships in four to eight weeks for a focused team. It includes auth, the core workflow, minimal admin, and just enough analytics to answer the validation question. It excludes secondary personas, edge cases, and anything the founder is convinced is 'obvious' but has not been validated.
When to use it
MVP thinking fits when the product concept is new, the target market is not yet validated, and shipping a full version-one would consume six-plus months of runway on assumptions that might be wrong. It is the wrong frame when you are building the tenth version of a well-understood category (an MVP CRM is just a bad CRM), when the customer contract requires a full product from day one (regulated industries, RFP-driven sales), or when the actual constraint is engineering capacity rather than product uncertainty. The most common mistake is calling something an MVP that is not minimum, not viable, or not designed to return learning — the label becomes an excuse for a rushed version-one instead of a discipline for shipping a validation instrument.
Frequently asked questions
- How is an MVP different from a POC or a prototype?
- A proof of concept tests whether something is technically feasible — a working demo that a specific approach can be built. A prototype tests whether the design and user experience make sense — often clickable Figma or a non-production build. An MVP tests whether real users will use and pay for a working product in production. POC and prototype are internal artifacts; the MVP is the first thing a user actually uses.
- How much does an MVP cost to build?
- In 2026, a focused MVP built by an onshore US team runs $10,000 to $60,000 depending on scope, integrations, and required compliance posture. The lower end is achievable when the scope is genuinely minimum and the team is disciplined; the upper end reflects MVPs in regulated verticals or with heavy third-party integration. Anything over $75K is usually not an MVP — it is a version-one wearing the label.
- What should not be in an MVP?
- Secondary user personas, edge-case flows, admin sophistication beyond what the founder needs to run the pilot, custom design polish beyond what looks credible, and any feature that has not been requested by a real prospective user in the discovery interviews. If it is not required to test the core hypothesis, it goes on the roadmap for post-MVP.
Start your project request
Tell us what you're building — engineering capacity, AI, QA, cloud, or a fixed-scope software engagement. Our NYC team responds within one business day.
- Response within 1 business day
- 30-minute discovery conversation
- Recommended engagement model & pricing
- NYC-focused — in-person available
Inbound sales only. All form information is encrypted in transit.