MVP scope: what to cut so you can launch in eight weeks

An MVP is not a small version of the whole product. It is the smallest thing that lets a real customer pay you and tells you whether they will keep paying. Most scope creep comes from forgetting that second half.

We start every SaaS engagement by writing down the one job the product must do for its first ten customers. Then we cut everything that does not serve that job: settings pages, secondary roles, integrations nobody has asked for, and the admin dashboard the founder wants to look at.

What we do not cut is the foundation. Authentication, billing, multi-tenant data, and deployment pipelines are cheap to build in from the first sprint and painful to retrofit. A fast launch on a foundation that has to be rebuilt in six months is not a fast launch.

Eight weeks is achievable for most B2B products when discovery is done properly and the scope is held. The discipline is saying no to good ideas until there are customers to test them on.