Scoping
How to scope an AI MVP you can launch in 14 days
Five scoping rules that keep an AI MVP small enough to ship in two weeks — with a worked example and a checklist you can use today.
By the Jerrax team · · 7 min read
Most MVPs that take months didn’t need to. They grew because nobody drew a line around them. Scope is the single biggest factor in how fast — and how affordably — a first version ships. These are the five rules we use to keep an AI MVP small enough to launch in two weeks.
Rule 1: One core workflow
Write the product’s job as one sentence in the form “a [user] does [X] and gets [Y]”. For example: a solicitor uploads a contract and gets a plain-English summary with the key dates.
If you need two sentences, you have two workflows. Pick the one that proves your idea and park the other for version two.
Rule 2: Five screens or fewer
Most single-workflow products fit into five primary screens:
- Sign up / sign in
- The main workspace, where the user provides their input
- The result or detail view
- A history or simple dashboard
- Basic admin, if you need to manage users or content
If your list is longer, something on it belongs in a later version.
Rule 3: One AI step, using an existing model
Decide exactly what the AI does — summarise, classify, extract, draft or answer — and use an existing model through its API. Fine-tuning, custom training and multi-step agents can come later, once you know the simple version is valuable. If you’re not yet sure the model can do the job, test that first (see MVP vs prototype vs proof of concept).
Rule 4: One type of user
Build for the person who gets value from the core workflow. Teams, roles, permissions, invitations and billing tiers each add real work; a simple admin view is usually all a first version needs.
Rule 5: Decide what success looks like
Pick one signal that tells you the MVP is working — for example, users come back to run a second document within a week. It keeps everyone honest about which features matter, and it tells you what to build next.
A worked example
Here’s how those rules turn an idea into a scope. (This is an illustrative example.)
| Idea | AI contract summaries for small law firms |
|---|---|
| Core workflow | A solicitor uploads a contract and gets a plain-English summary with key dates and obligations |
| Screens | Sign in · Upload · Summary view · Document history · Admin (user list) |
| AI step | One model call that returns a summary and a structured list of dates |
| Users | Solicitors, plus one firm admin |
| Success signal | A solicitor uploads a second contract within seven days |
| Left for later | Clause comparison, team folders, e-signature integration, mobile app |
What to leave out of version one
- Multiple user roles and detailed permissions
- Subscription billing and plan tiers
- Native iOS and Android apps — a responsive web app works on phones
- More than one integration
- Custom model training
- Settings pages for things nobody has asked to change yet
Scope checklist
- The core workflow fits in one sentence
- Five screens or fewer, listed by name
- One AI step, using an existing model API
- One type of user, plus basic admin if needed
- At most one integration with another system
- One success signal you’ll check after launch
- A written list of what’s deliberately left for later
If every box is ticked, your idea fits our Starter package: a working product on a live URL in 14 days for $699.
Ready? Start your project — the brief at checkout asks for exactly the things above.
