You have a list. Twelve features, three audiences, and someone said MVP. An agency quoted a platform. What I actually put in a first version of a product is smaller than that list, and more finished than a clickable demo — one named person, one job, a URL that is still there on Tuesday.
I build this as SaaS and web products, and the brief I write before I quoteis where the list gets cut. If you haven't named whether it's a website or a web product, stop and do that first — the first version of the wrong noun is just an expensive stall. The rest of this is what I put above the line once the noun is right.
What a first version of a product actually is
An MVP, as sold, is often a demo with a login. Screens that look like the product. A click path for a pitch. Nothing that has to survive a real Monday. That is useful for a slide. It is not a first version.
A first version is software someone can finish a job in, without you in the loop, on a URL you don't have to babysit. It is allowed to be ugly. It is not allowed to be pretend. The difference is whether the job actually completes — booking exists, money moves, the file is still there next week — not whether the palette is finished.
What belongs in a first version
Three things have to be real. Everything else is a candidate. This is the same ownership line I wrote down for what a full-stack developer actually owns — interface, the system behind it, production — applied to one job instead of a roadmap.
- 01
One job a named person can finish
Not "the platform." The thing they open it to do. Book the visit. Send the invoice. Approve the proof. If I can't name the person and the job in one sentence, there is no first version yet — there is a wish list.
- 02
The records that job creates
If they come back, something has to still be theirs: the booking, the order, the file. That means a real store, not a form that emails you. Skipping this is how you ship a demo and call it a product.
- 03
A URL that stays up on Tuesday
Hosting, a domain, a deploy you can repeat, backups if money or data moves. A first version on someone's laptop is a rehearsal. I don't hand you a zip. If it has to exist, it has to stay up.
If those three are true, you have a product. A thin one. That is the point. You can see this shape in work that already shipped — not every case study started as a platform. Most of them started as one job that had to work.
What I cut from a first version
Cutting is the actual work. Anyone can add a feature to a list. The first version is the list with a line through it, agreed before week three, when everyone is tired and the extra audience starts to sound reasonable.
- 01
The second audience
Customers and an internal tool and a partner portal. Pick the person who pays, or the person who runs the shop. The other one waits. Building both "since we're in there" is how neither works.
- 02
The platform for later
Multi-tenant, every role, every market, "so we don't have to rebuild." You will rebuild the parts you guessed wrong. Ship the job. Earn the platform.
- 03
The iOS and Android app
Stores come after a web product someone already returns to. A first version that starts in TestFlight is two extra release processes before you know if the job is right.
- 04
An admin that mirrors the whole product
You need to see the records and fix a stuck one. You do not need a second copy of every screen. Admin is a few sharp tools, not a shadow app.
- 05
Anything "just like Stripe, but for us"
That sentence is a company, not a first version. I wire Stripe. I don't replace it in v1. Same for the CRM, the courier, the thing you already pay for.
Above the line
The job, the records, production
One person can finish it without you. It stays up. That's the first version.
Below the line
Real work, dated, deferred
Not forgotten. Not "later" as a fog. A list you already agreed to wait on.
When a first version is the wrong first move
Sometimes the honest cut is not inside the list. It is the list itself. A first version of a product is the wrong first move in three cases I see constantly.
- 01
You needed a website
A stranger has to understand you and act once. No return visit, no records that have to stay theirs. Building a first version of a product is the expensive way to ship a brochure.
- 02
You already have a product
Users, payments, a repo. Starting a first version beside the live one is a rewrite wearing a friendlier name. Repair what's there. Don't parallel-build a cleaner copy while Monday still has to run.
- 03
You can't name the first user
"Small businesses" is not a person. If nobody will do the job in week one, the first version has nothing to be first for. Write the brief, or wait. Don't pay for software in the meantime.
A first version is a product someone can finish a job in. Everything else is a candidate, not a promise.
If the thing already exists, that's taking over an existing product without a rewrite. If you're staring at a list and calling it v1, send the list — not a deck. And name who owns the product after launch before the launch email, or you have a demo with a domain. The rest of first versions is that cut from different angles, and most of shipping comes back to the same line: what actually has to work on Monday, and what can wait.
