What an MVP actually is
A minimum viable product is the smallest version of your product that real users can sign up for, use, and pay for. It exists to answer the question you are least sure about, usually whether anyone wants this enough to change what they do today.
That makes it a product, not a demo. It needs accounts, payments if you charge, a way for you to support the people using it, and enough reliability that a stranger's first attempt works. What it does not need is every feature on your list.
MVP, prototype or full product?
| What you need | What it is | Typical time |
|---|---|---|
| Prototype | Clickable screens to test an idea or show investors, no working backend | Days to two weeks |
| MVP | A real product doing one job well, with sign-up, payments and support tools | 8 to 12 weeks |
| Full product | Multiple user types, integrations, roles, reporting, scale | 4 months and up |
Founders sometimes ask for an MVP and describe a full product. Discovery exists to catch that before it becomes a budget problem.
The list of what we leave out
The most valuable document we produce in week one is not the feature list. It is the list of things we are deliberately not building yet, with the reason next to each. It ends arguments in week seven, and it is why our projects land on time.
Things that usually wait: a second platform, admin dashboards with charts, granular permissions, in-app messaging, referral systems, and any integration that only one imagined customer has asked for.
Our MVP development process
- Discovery, week 1. The job, the buyer, the one risky assumption, and the smallest thing that tests it. You leave with a scope, a fixed price and the not-building list.
- Design, weeks 2 to 3. Flows, screens and a clickable prototype. We push it in front of five to ten people who look like your users, and change it before it costs anything.
- Build, weeks 4 to 10. Weekly demos of working software. The riskiest piece goes first, whether that is a payment flow, an integration or an AI feature that has to be good enough to be useful.
- Launch, weeks 11 to 12. Store or web launch, analytics live, onboarding that works without you, and a month of fixes included.
The same week-by-week logic, and what makes timelines slip, is in how long an MVP takes.
What we build MVPs on
The same stack we use for products meant to last: Next.js and React for web, Flutter or React Native for mobile, Node or Python behind them, PostgreSQL for data. We skip scope in an MVP, never engineering quality, because a first version that succeeds and then has to be thrown away is the most expensive outcome there is.
If your product is mobile-first, see mobile app development. If it is a platform with accounts and subscriptions, see web and SaaS development.
Measuring whether it worked
Before launch we agree three or four numbers that will tell you the truth: activation, the core action, retention at week two or four, and revenue if you charge. They go into analytics before launch, not after, so your first investor conversation is about evidence rather than anecdotes.
If the AI is the product
Building an AI product has its own risks: cost per user, response time, and whether the model is reliable enough for the job. That is a different process, with a prototype scored against a test set before anyone commits to a build, and it is on the AI MVP development page.
We have been on your side of this
We have taken six products of our own from idea to launch, including Crodo, a voice assistant for Mac, and Decornoa, which turns a room photo into interior designs. We paid the model bills, watched the sign-up flow lose people, and priced things wrong before pricing them right.
That is why our MVP estimates tend to hold, and why our first questions are about your buyer and your unit costs rather than your feature list. The rest of the products are on the products page.
What it costs
MVPs with us usually run 8 to 12 weeks, at a price fixed after discovery. The three things that move the number most are the platform, whether you take payments, and how many outside systems you need on day one. The market ranges are in our app development cost guide.