How to scope an MVP in two weeks (without shipping junk)

“Two-week MVP” is not a dare. It is a forcing function to discover whether anyone cares — before you fund twelve months of roadmap fantasy.

Teams that miss the window usually failed at scope, not at engineering talent.

Step 1: One sentence outcome

Finish this sentence:

After two weeks, we will know whether __________ by measuring __________.

If you cannot fill both blanks, you are not scoping an MVP — you are scoping a prototype museum.

Examples that work:

• “Whether ops teams will connect Slack” → measure connected workspaces
• “Whether users complete onboarding” → measure activation rate on a single path

Examples that fail:

• “Build the full platform”
• “Make it feel premium” (without a metric)

Step 2: One golden path

Draw a single user journey on one screen:

1. Land
2. Sign up (or demo request)
3. Core action
4. Success state

Everything not on this path is v2. Park integrations, admin panels, and “nice reports” unless they are required for step 3.

Step 3: Cut integrations brutally

Each third-party integration is a mini-project:

• Auth provider
• Payments
• Email
• Analytics

Pick the minimum. Stripe + email + one analytics tool beats five half-working integrations.

Step 4: Budget one week of buffer

A two-week calendar with no slack assumes:

• No production bug on day nine
• No stakeholder “small tweak” that costs three days
• No API documentation that lied

Plan ten days of build and four days of hardening — or extend the timeline honestly.

Step 5: Define “done” in writing

“Done” includes:

• Deployed to production URL
• Error monitoring on
• One rollback plan
• Founder can demo without engineer in the room

Who should build it

Early MVPs often ship faster with a senior dev partner than with a first hire still learning your domain. Compare models in dev subscription vs full-time hire.

After launch: read the signal

If metrics are flat, resist the urge to “add features” before you talk to ten users. The MVP did its job — it told you the hypothesis was weak.

Start a project conversation if you want help scoping before your next sprint.