An MVP is not a smaller version of the product. It is the cheapest honest test of the riskiest assumption.
Founders often describe an MVP as 'the core features'. That framing produces a small, complete product that tests nothing in particular.
Name the assumption that would kill the business if wrong — demand, willingness to pay, a technical unknown — and build only what tests it. Everything else is deferred by design, not by budget pressure.
Instrument the test before launch. If you cannot state in advance which number decides continue-or-pivot, the build is not a test, it is a bet.
Plan the second version as a rewrite candidate. MVP code earns its keep by producing a decision quickly, not by lasting five years.
Growth & Engagement
Client success leads scope, staffing, and commercial models for engagements ranging from single MVPs to multi-team augmentation programmes.