MVP in 4-6 weeks without fake speed

§ 01Define the riskiest assumption

Before scope, name the assumption that can kill the product: demand, payment, retention, operational cost or integration feasibility.

Everything that does not test this assumption belongs to a later phase.

§ 02Cut by workflow

Keep one core user path: sign up, perform the key action, get the promised result. Remove secondary roles, advanced permissions, complex settings and rare edge cases.

Manual operations are acceptable behind the scenes if they reduce build time and do not break the user promise.

§ 03Four to six week plan

Week one is scope, UX and architecture. Weeks two to four are implementation of the core path. The remaining time is QA, analytics, deployment and fixes from first users.

Do not schedule launch on the last day of development. Leave time for operational issues.

§ 04Metrics after launch

Track activation, completion of the key action, payment or lead quality, support requests and retention. The MVP is finished only when the data tells you what to build next.

If every metric is vanity traffic, the MVP did not test the business.