How to build an MVP: one SaaS in a day, every credit counted
An MVP, in the words of Eric Ries who named it, is the version that lets you “collect the maximum amount of validated learning about customers with the least effort.” I built one on Lovable on 26 September 2026 and logged every step: a SaaS foundation, an SEO review, a security review, a phone install and a landing page, 20.4 credits in total. Below is that ledger, the brief that comes before it, four MVPs built here with what each taught, and the three famous MVP stories traced to their sources.
By Marco Kohns · Ledger from 26 September 2026; sources re-read 23 October 2026
20.4credits
5 prompts on one project in one day, balance read after each.
70%ran out of cash
The top reason in CB Insights' review of 431 failed startups; poor product-market fit 43%.
1change per prompt
Lovable's idea-to-app guide calls it the single most important habit.
Before the first prompt
How do you turn an idea into a brief Lovable can build?
One page that answers who it is for, the one job, the channel the first users come from, and the decisions Lovable would otherwise ask about.
Who and why
The one job
Channel first
Where users come from
The decisions
What Lovable will ask
Lovable's guide to building a product, read 23 October 2026: one change per prompt, verify in the preview, then move on; if a prompt says and more than twice, split it.
Measured
What did one MVP cost to build in Lovable, step by step?
20.4 credits over 5 prompts on 26 September 2026, one project called Cadence. Each row links to the prompt and its screenshots.
| Time | Step | Credits | Result |
|---|---|---|---|
| 12:26 | Foundation | 10.4 | Asked 4 questions, enabled Cloud, self-tested sign-up and invites, roles checked in the database |
| 14:29 | SEO review | 1.1 | 5 of 6 checks passing; the one failure was the sitemap, deferred until publish |
| 18:06 | Security | 1.3 | The chat ran its own checks (clean) and said the Deep scan must start from the Security tab; run there, free, 3 minutes, no findings; the dependency panel listed 2 known issues on one package |
| 18:36 | Installable | 3.1 | Manifest, icons, service worker gated to the published app, Add to Home Screen button; verified in the preview |
| 19:19 | Landing page | 4.5 | Five pre-build questions, six minutes to a preview; server-rendered, FAQ schema, one CTA type; 394 words |
The prompt for each step: foundation, SEO review, security, phone install, landing page. Billing comes after sign-ups: build a SaaS.
MVP examples
Which MVP examples were built here, and what did each teach?
Four, each from a library prompt pasted unedited, each with its credits read before and after.
| MVP | Credits | What came back | What it taught |
|---|---|---|---|
| Landing page with email opt-in | 1.8 | One round, all five priority features, inline success state, Cloud enabled | One prompt with five priority features produced all five in one round; the cheapest way to test an offer is a page that stores the email with its source. |
| States gallery for a UI | 9.5 | Asked 2 questions, built a /states gallery and a task list, verified slow load, failure and retry | The builder asked two questions before writing code; an MVP that specifies its empty, loading and error states costs more credits and fewer support emails. |
| SaaS foundation | 10.4 | Asked 4 questions, enabled Cloud, self-tested sign-up and invites, roles checked in the database | Four questions first, then a self-tested invite flow with roles checked in the database; the most upvoted prompt on the site is also the one whose safeguards cost the most to honour. |
| SaaS landing page, six sections | 4.5 | Five pre-build questions including a rendered design picker, six minutes to a preview, server-rendered with FAQ schema and one CTA type | The page is the MVP of the MVP: it exists to count sign-ups against visitors before the product earns its billing. |
The famous three
Are the famous MVP examples true?
Two have a source you can read; the third is repeated everywhere and missing from the company's own page.
| Company | The story | Source | Status |
|---|---|---|---|
| Airbnb | Two hosts welcomed three guests to their San Francisco home in 2007; the site launched at SXSW in March 2008 with two bookings and got 80 during the Democratic National Convention that August. | Airbnb newsroom, About us timeline | Company page |
| Dropbox | A three-minute demo video, released before the product, moved the beta waiting list from 5,000 to 75,000 people overnight, per Drew Houston. | Eric Ries in TechCrunch, 19 October 2011, quoting Drew Houston | Founder quote, secondary page |
| Zappos | The story every list repeats: in 1999 Nick Swinmurn photographed shoes in local stores, posted them online, and bought each pair at retail when someone ordered. | zappos.com/about, read the same day, says only that the company was founded in 1999 | Not found on a company page |
After the build
What is still missing after the MVP is built?
A first user. The ledger ends with a working app, a landing page and nobody sent to it.
Next
What the MVP needs now
- One channel and one week of trying it: the first 100 users
- Sign-ups counted against visitors on the landing page
- Billing only once people ask to pay
- One change per prompt while you learn
Not yet
What can wait
- A second product idea
- Features nobody asked for
- Three channels at once
- A redesign before ten users have used it
CB Insights' review of failed startups: of 431 companies, 385 gave reasons; ran out of capital 70%, poor product-market fit 43%, bad timing 29%, unsustainable unit economics 19%.
Start from the foundation prompt
Disclosure: if you create a Lovable account through links on this page, we may earn a commission. It costs you nothing and does not change what we recommend. Create a free Lovable account
Frequently asked
What is an MVP?
Eric Ries, who named it in 2009: the version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least effort. He adds that MVP, despite the name, is not about creating minimal products.
How much does it cost to build an MVP with Lovable?
My SaaS MVP took 20.4 Lovable credits over 5 prompts in one day: foundation, SEO review, security review, phone install and landing page. A single landing page cost 1.8 credits; the foundation alone 10.4.
How long does it take to build an MVP?
The ledger above runs from 12:26 to 19:19 on one day. That is the build; finding the first users is the longer part, and it starts with picking one channel.
How do I go from idea to app in Lovable?
Write a one-page brief (the user, the one job, the channel, the decisions Lovable would ask about), paste one structured prompt for the foundation, then add one change per prompt and verify each in the preview. Run the security scan before you publish.
Is the Zappos MVP story true?
Possibly, but I could not find it on Zappos's own page on 23 October 2026, which says only that the company was founded in 1999. The Airbnb story is on Airbnb's newsroom and the Dropbox numbers come from Drew Houston, quoted by Eric Ries in TechCrunch.
What do most startups that fail have in common?
In CB Insights' review of 431 failed startups, 70% ran out of capital and 43% cited poor product-market fit, the two reasons an MVP exists to test cheaply.
What we did not publish
- A first-user figure for the Cadence MVP; nobody has been sent to it.
- The original source for the Zappos shoe-photo story; it is not on the company page.
- A comparison with building the same MVP in Bolt or v0.
Sources
- Eric Ries: Minimum Viable Product guide, 3 August 2009, re-read 23 October 2026
- CB Insights: top reasons startups fail, re-read 23 October 2026
- Lovable docs: from idea to app, read 23 October 2026
- Airbnb newsroom, About us timeline, re-read 23 October 2026
- Eric Ries in TechCrunch, 19 October 2011, quoting Drew Houston, re-read 23 October 2026
- zappos.com/about, read the same day, says only that the company was founded in 1999, re-read 23 October 2026
- My ledger, 26 September 2026
Written by
Marco Kohns
Founder of ProtoBites - Venture Growth Studio
Growth PM at a Silicon Valley scale-up (a16z and General Catalyst backed), ex-Techstars where he consulted 13 early-stage startups, Reforge-trained. Every prompt on this site comes out of shipping ProtoBites' own portfolio products.
Related reading
- every Lovable guide, by build stage · Choose a tool, plan, prompt, build safely, launch.
- three prompts and what they built · The foundation run with its screenshots.
- SaaS landing page prompt · The last step of the ledger.
- Lovable security · The scan step, with the dependency finding.
- Lovable mobile app · The installable step.
- Lovable SEO · The review step.
- first 100 users · Where the story continues.
- product-channel fit · Why the channel comes before the next feature.
- Lovable pricing and credits · Plans read today and what one prompt costs in credits.
- the SaaS starter kit · The foundation as a schema.
- build a SaaS · The same build as a SaaS path, kit counted, billing last.
- what is vibe coding · The definition, the record, and where the line is.