Build Notes
What an MVP actually needs to prove
An MVP is not a compressed version of the eventual platform. It is a focused test designed to answer one important question before more time, money, and people are committed to the idea.
The purpose of an MVP is not to demonstrate how much can be built. It is to remove enough uncertainty for the founder to make the next decision with evidence rather than enthusiasm.
Before discussing features, name the question the first release must answer. Will the intended user complete the critical journey? Will they return? Will they pay, introduce it to someone else, or change an existing behaviour to use it?
That question should determine the scope. Authentication, administration, integrations, and automation may be necessary, but only when the test depends on them. Everything else can wait until real use proves that it deserves investment.
An MVP can be technically impressive and still be commercially useless. If nobody knows which assumption it was built to test, feedback becomes a collection of preferences and the product simply grows without becoming clearer.
A useful first release leaves the founder with a working product, observed behaviour, and a decision: stop, change direction, improve the critical journey, or invest in the broader platform.