Scoping an MVP is one of the hardest parts of building a product. Most delays are not engineering problems. They are scope problems dressed up as engineering. This guide walks through how Standen scopes SaaS MVPs so founders ship in weeks with fixed budget and full code ownership.
Start with one outcome, not a feature list
Write the outcome in one sentence: After using the product, the user can ___. If you need the word "and" more than once, you are already carrying two products. Pick the outcome that proves the idea to the next ten buyers.
Examples of sharp outcomes:
- Podcast host publishes one episode end-to-end without leaving the app.
- Ops lead sees live margin per client account without opening five tabs.
- Customer approves a deliverable in one link without email back-and-forth.
Fix time and budget, then scope
We work to fixed timelines, often 14 to 30 days depending on surface area. Once time and budget are set, we fit scope to that box. Features that do not serve the core outcome move to a roadmap column, not into version one.
This inversion feels uncomfortable if you are used to estimating after a wishlist. It is the main reason projects ship instead of drifting.
Map the workflow before the wireframes
List steps as a numbered flow: trigger, inputs, decisions, outputs, who gets notified. Circle the step that breaks today. That step is usually the spine of the MVP.
Only then sketch screens. UI that does not map to a workflow step is decoration.
Define acceptance criteria you can test
Each must-have story needs a pass/fail check. "Nice dashboard" is not acceptance criteria. "User with role Admin can filter projects by status and export CSV" is.
Integrations: must-have vs later
Stripe, email and one CRM integration cover most B2B MVPs. Everything else is a candidate for manual process or CSV until you have paying users. See our integrations guide for a priority framework.
What we cut from almost every first build
- Admin superpowers nobody has asked for yet.
- Multiple pricing tiers before one plan converts.
- Mobile apps before web workflow is proven.
- AI features that are not the core differentiator.
Handover is part of scope
Ownership means repo access, deployment runbook and documented env vars. If you cannot deploy a hotfix without the agency, you rented software. Scope handover explicitly in the statement of work.
Ready to turn your idea into a scoped, shippable MVP? Book a discovery call or read how to scope a first SaaS system in 14 days.