An MVP is an experiment dressed as a product: the smallest thing that puts the core assumption in front of real users and returns a real answer. 'Will shop owners re-order through a link instead of a call' needs a link and a button — not the inventory sync, the dashboard, or the native app, which is where MVPs most often fail: they grow to include the imagined final product's scaffolding, cost like it, and still answer nothing.
The discipline is subtraction ordered by risk: keep the feature that tests the biggest unknown, cut what tests nothing, and define the answer the experiment returns before building. An MVP done right is intentionally embarrassing in scope — the embarrassment is the proof that only the hypothesis was paid for.
Related terms
Discovery call
The first conversation before any proposal — where scope, budget reality and fit get established instead of guessed.
Retainer
An ongoing engagement — a reserved slice of engineering capacity per month instead of one-off projects.
SEO
Search engine optimization — making pages findable, indexable and worth ranking: technical health plus content people actually want.
The bench this belongs to
Full-stackIf you can describe it, we can build it. React and Next.js on the front, Python or Node behind, Postgres underneath, shipped to somewhere you can afford to run.
