Section 01 · 4 quick questions
Let's start with the basics.
A few details so we know who you are and the best way to reach you. Nothing here is shared outside our team.
Best way to reach youPick one or more
Section 02 · The why
What are you actually building?
A short, sharp answer here saves a hundred clarifying questions later. Plain language is fine.
One-sentence pitchMax 140 characters
Format that works well: "X is a Y for Z."
0 / 140
The problem you're solvingWho feels it, and how badly
Three products you admireURLs + a sentence each
Anti-examplesJust as useful as the above
Products you'd hate to be compared to, and why.
Section 03 · Who is this for
Tell us about your users.
Specific beats generic. "Working parents of T1D children, 30–50, comfortable with iOS" is far more useful than "everyone."
How many user types?We'll size role/permission system to this
Estimated active users at launchHonest guess is fine
Top three jobs the user comes to do
One per line. Use verbs.
What do users do today instead?The status quo we're competing with
Section 04 · Where it runs
Platforms & reach.
Each platform we add multiplies maintenance. Be honest about what you actually need on day one.
Platforms for the first releaseMulti-select
Public-facing or internal?
Languages at launch
Section 05 · The feature matrix
What ships, and what doesn't.
We use MoSCoW to force clarity. The Won't column is the most valuable — it protects scope for everything else.
MoSCoW feature matrix
Force clarity. The Won't column protects everything else.
Must · launch blocker
Should · in v1 if possible
Could · phase 2 backlog
Won't · explicitly out of scope
The killer featureIf you ship one thing, this
AI features neededMulti-select · "None" is a valid answer
Section 06 · Data & integrations
What's stored, what's connected.
This tells us what compliance regime applies, and where the integration risk sits.
Types of data stored
Sensitive or regulated data?Affects hosting choices
Integrations you already know you need
Section 07 · Look & feel
Brand & identity.
If you already have a brand, share it. If not, share references and we'll work backward to something that fits.
Brand coloursDrop hex codes or pick swatches
Brand voiceMulti-select
Section 08 · Money
How it pays for itself.
If money isn't involved yet, that's fine — say so. We'll plan for an upgrade path either way.
Monetisation modelMulti-select
Subscription tiers & pricesIf applicable
Geographic launch markets
Section 09 · Who runs it
After we ship.
A surprising number of projects launch without a clear answer to 'who answers the 3 a.m. email?' Let's lock it in now.
Existing infrastructure accounts
Section 10 · Reality check
Timeline, budget, success.
The last few questions ground the project in time and money. Honest answers help us scope.
Budget range
Top three risks you worry about
What would make this a failure at 12 months?Falsification framing
Anything else we should know?
Progress saved in this session