Ship an MVP on a foundation you did not rebuild

An MVP's job is to answer a business question under time pressure. Rebuilding session rotation rarely answers that question. A kit compresses the commodity layer so your calendar can hold the workflow that makes the product yours.

Define the bet before you shop

Write one sentence: who, painful job, promised outcome. Write a second: the single workflow that proves the outcome. Everything in the kit that does not serve those two sentences is a candidate for deletion.

Four-week operating plan

1. Week 1: buy or select the kit, pass the clean-machine setup, deploy staging, replace branding.
2. Week 2: implement only the proving workflow end to end.
3. Week 3: invite 10–20 ICP users, instrument drop-offs, fix onboarding copy and empty states.
4. Week 4: enable paid Checkout or a measured waitlist; decide kill, iterate, or expand.

If week 1 consumes the month, either the kit failed the selection checklist or you improvised instead of following setup docs. Restart with the checklist, not with more features.

Keep versus cut

• Keep: auth, entitlement path, email primitives, env structure, deploy notes.
• Keep: a thin authenticated home if your workflow lives behind login.
• Cut: demo analytics, unused CRUD, second marketing themes, sample tenants.
• Defer: multi-org, affiliate systems, complex roles - unless they are the bet.

Risks that look like progress

• Polishing the dashboard while the proving workflow is still a stub.
• Adding a second payment provider before the first webhook is trusted.
• Inviting friends who are not ICP and mistaking kindness for demand.

30-day scoreboard

• At least one paying user or a waitlist with reply evidence from ICP contacts.
• Error volume low enough that you are building product, not fighting installs.
• A short list of learnings that did not require rewriting auth.

Start in SaaS starter kits on the market, filter to your stack, and treat setup instructions as week-1 scope - not optional reading.