How we scope an MVP in 48 hours

Most MVP conversations fail for the same reason: everyone agrees on “build something small,” then the backlog quietly grows into a product rewrite.

Here is the process Appfield uses after a discovery call — usually within 48 hours — to produce a fixed-scope proposal.

Start from outcomes, not features

Ask what must be true for the release to be useful: a signed pilot, a paid conversion, an internal handoff. Features are tools; outcomes are the contract.

Cut the happy path to one story

We write a single primary user journey. Everything else becomes backlog or a deliberate Phase 2. If two journeys feel equally “must,” the MVP is not ready.

Estimate in delivery slices

Instead of a monolithic hour dump, we break work into weekly demoable slices: auth, core object, one integration, polish. Clients see progress; risk surfaces early.

Price the uncertainty, not the optimism

Integrations, migrations, and compliance always cost more than UI. We call those out explicitly so the quote stays honest.

If you want this applied to your product, book a free discovery call — we reply within 24 hours.