How we scope a SaaS MVP in two weeks

An MVP is not a half-finished product. It is the smallest slice that proves a workflow for a real user role — something someone can finish a job with, not a gallery of unfinished screens.

Most SaaS budgets get burned when scope starts as a vision deck and ends as a feature catalogue. Softlinks runs a two-week scoping rhythm so you leave with a buildable plan, explicit non-goals, and enough clarity to say yes (or not yet) to a build.

What an honest MVP is

If a primary persona cannot complete one critical job without calling your team for help, you do not have an MVP yet — you have a demo. Softlinks scopes for that job first, then layers only the auth, admin, and telemetry needed to operate and learn.

• One paying (or soon-to-pay) persona — not every stakeholder’s wishlist
• One workflow that creates or protects revenue, time, or compliance
• A release you can put in front of real users within a defined sprint window
• Metrics that tell you whether the workflow worked after launch

Our two-week Softlinks rhythm

Week one is discovery and constraint. Week two is decisions and a shippable outline. We do not invent a 40-page requirements novel — we produce a scoped MVP you can estimate and staff.

• Days 1–3: stakeholder interviews, persona pick, job-to-be-done map, and “must / should / won’t” cut
• Days 4–7: screen and data-model sketch for the critical path only; flag integrations that block launch
• Days 8–10: admin/auth minimums, success metrics, and a written non-goals list
• Days 11–14: effort bands, sequencing, and a go / no-go recommendation for build

The Softlinks scoping checklist

Use this list in your own workshop or with us. If any line is fuzzy, stop and resolve it before writing code.

• One primary persona — name the role, their context, and what “done” looks like for them
• One critical job-to-be-done — the path they repeat weekly that justifies the product
• Auth + admin minimums only — sign-in, roles, and the few ops screens staff need on day one
• Instrumentation for learning — events or reports that show completion, drop-off, and errors
• Explicit non-goals written down — features, channels, and integrations you will not build yet
• Launch constraint — a date or budget ceiling that forces prioritisation
• Integration honesty — anything that must work live (payments, WhatsApp, email, ERP) is named early

What we deliberately leave out

Scope control is mostly about what you refuse. Softlinks typically parks these until after the first honest release:

• Multi-tenant white-label and partner portals before one tenant works end-to-end
• Every notification channel — start with the one your users already open
• Custom reporting suites when three operational metrics would teach you more
• Mobile apps for every platform when a focused web or single-store app proves the job
• “Nice” admin polish that does not unblock the primary workflow

What you walk away with

• A one-page MVP brief: persona, job, success metrics, non-goals
• A critical-path screen list and rough data entities
• An effort band Softlinks (or your team) can staff against
• A clear recommendation: build now, adopt an Industry OS, or wait

When to talk to Softlinks

Bring this checklist if you already have a product idea and need a disciplined cut. Or start a scoping conversation with us if you want Softlinks to run the two-week rhythm and hand you a build-ready plan — then optionally stay on for delivery, Care, or Care + Growth.

Ready for the next step? Start a project or book a short scoping chat — we typically reply within one business day.