From MVP to profitable product

“Minimum viable product” is the most misread phrase in this trade. It doesn't mean a rushed version, a free version, or a prototype you throw away. It means the smallest thing a customer would agree to pay for.

Scope is defined by what you take out

Every opening feature list contains three essentials and twenty things that “will cost almost nothing”. It is those twenty that turn a three-month project into a nine-month one, and drain the cash before the first invoice is paid.

The rule we apply: the first version contains only what the product cannot be sold without. No admin interface if you can look at the database. No team management if your first customers work alone. No three pricing tiers when you don't yet know what people will pay. That is why our first deliverable is a written scope stating explicitly what we will not build — better to argue over that document at the start than over the invoice at the end.

Charge earlier than feels comfortable

A free sign-up proves nothing. People sign up out of curiosity, out of politeness, to be encouraging. The first time someone hands you money, you learn something true — and often it isn't what you thought you were selling.

Put payment in the first version, even at a low price, even for ten customers. One month of real billing will tell you more than six more months of building.

Profitable doesn't mean big

A product with thirty customers paying thirty euros a month supports a small team. It needs no funding round, no thirty per cent monthly growth, no investor's approval. Plenty of decent products die aiming at a model that matched neither their market nor their founder's actual ambitions.

The right question at the end of the first version isn't “how many users?”. It is: would anyone be upset if this stopped tomorrow?