24–30
Ready to build
The product is well framed. Lock the first-release scope, agree the architecture and start with the riskiest workflow.
Product Engineering · 15 factors
Are you ready to build this product?
Score how ready your web, mobile or SaaS product is to go into development. Ten minutes that can save the first months of a build.
Before you score
Describe the first release
Score the first version you would pay to build, not the full vision. 'A booking app for salons with online payment and reminders' beats 'a platform for the beauty industry'.
Optional. Stays in your browser unless you send the form below.
- 0Unknown / absentThe requirement is unclear, unavailable, or unowned.
- 1Partially readySome evidence exists, but material gaps remain.
- 2ReadyEvidence, ownership and controls are sufficient for the next step.
Score evidence, not optimism. If you cannot point to the data, owner, metric or control, score it 0 or 1.
-
Problem evidence
Real users have described the problem, and the cost of not solving it.
-
Target user
The first user group is named and reachable.
-
First-release scope
The first release has a clear boundary and a written not-now list.
-
Success measure
Launch success is defined as a number, not a feeling.
-
Core workflows
The main user journeys are mapped screen by screen or step by step.
-
Non-functional needs
Expected users, speed, uptime and devices are written down.
-
Integrations
Payments, email, maps or other services the product needs are known.
-
Data and content
Where the data comes from, and who writes the content, is agreed.
-
Platform choice
Web, mobile or both is decided for a reason.
-
Architecture approach
How the product will be built and hosted has been considered.
-
Budget range
A realistic budget range exists for build and the first year of running.
-
Timeline
The launch date is tied to a reason and has room for testing.
-
Delivery team
Who builds, reviews and decides is agreed.
-
Compliance
Privacy, accessibility or industry rules that apply are known.
-
Launch and support
Who supports users after launch and how releases continue is planned.
Turn the score into a decision
What your total means
16–23
Scope before you build
The idea is promising, but gaps will surface mid-build as cost. Close the lowest-scoring factors before signing a build contract.
0–15
Not ready to build
Building now risks paying to discover the product. Validate the problem, the user and the first release before development.
Your weakest factors
Your next three actions
- 1Name the biggest unknownWrite down the lowest-scoring factor that could change the budget.
- 2Shrink the first releaseCut the first version to the one workflow that proves the product.
- 3Get a realistic rangeTurn scope into an estimate before you commit to a team or a date.
Next step
Want a blueprint before you pay for a build?
The Product Blueprint Sprint turns your idea into a scoped feature map, architecture, budget and timeline in two weeks.
Product Blueprint Sprint$3,900 · 2 weeks
Discuss my score
Your score and weakest factors are added to the message for you.
Get your personal report
Score every factor, then get a PDF of your product scorecard built from your answers: your total and result, your weakest factors, all fifteen scores and the next steps. (Before every factor is scored, you get the blank scorecard.)