Quick answer: The minimum viable product is the smallest release that tests the core assumption of the business. It exists to learn, not to be complete. The launch is the experiment.

Define the assumption first

Before the MVP, state the assumption in one sentence:

  • The specific customer.
  • The specific problem.
  • The willingness to pay or to use.

The MVP is the product that tests the assumption.

Scope the MVP

The MVP contains:

  • The one core workflow that delivers the value.
  • The minimum to take the customer through that workflow.
  • The simplest path to the result.

The MVP cuts:

  • The secondary features.
  • The settings and the customizations.
  • The edge cases.
  • The polish that doesn't affect the core job.

The scoping question is whether the feature is required to test the assumption.

The build

  • Use the fastest stack that supports the workflow.
  • Keep the interface narrow.
  • The rough edges are acceptable if the core works.
  • The support can be manual in the first version.

The soft launch

The MVP goes through a soft launch to the first segment:

  • The design partners use the product.
  • The founder watches the workflow.
  • The onboarding is fixed.

The public MVP launch

The launch week reaches the broader audience:

The developer tool follows the developer-tool launch and the API launch paths.

The metrics

The MVP measures the validation, not the vanity:

  • Does the customer reach the first value?
  • Does the customer return?
  • Does the customer pay?
  • Does the customer recommend the product?

The traction slide turns these signals into the investor evidence.

What to avoid

  • The MVP that is the full product delayed.
  • The feature list built before the assumption.
  • The launch hidden forever.
  • The vanity metrics (signups without usage).
  • The redesign before the core workflow is proven.

The decision after the MVP

The launch produces one of three signals:

  1. The core works. The team expands the product.
  2. The core partly works. The team narrows the segment.
  3. The core doesn't work. The assumption is changed; the product is not pushed.

Frequently asked questions

How small is the MVP? Small enough to test the core workflow, not smaller. Can the MVP be manual? Yes; the concierge or the manual version tests the willingness before the build. Does the MVP need the polish? It needs the core job to work; the polish is later. Is the MVP launch the same as the public launch? The MVP is usually soft-launched first, then publicly launched.

Ship the smallest release that tests the core assumption, watch the first customers, and treat the result as evidence.