Stage 2
If users do not return, the product has not cleared the stage.
Use this stage to separate real pull from launch momentum, incentives, and founder-driven demand.
Use this once users exist and retention, demand, or payment is still uncertain.
Diagnostic module
Stage doctrine
This semantic layer explains how ProductBooks reads demand and retention without modifying the evaluator or introducing runtime interpretation.
Methodology
Demand must survive without pressure
Product-Market Fit asks whether real users come back, pay, and refer without constant reminders, launch spikes, or founder intervention creating the appearance of pull.
Scoring
Behaviour outranks enthusiasm
Observed return behaviour, repeatable demand, and payment acceptance carry more weight than praise, interviews alone, or channel spikes that disappear after stimulation ends.
Decision boundary
Do not confuse motion with fit
If product pull depends on pressure, the stage remains unresolved. ProductBooks keeps the risk visible until durable demand is proven.
Diagnostic module
Problem to Product to Business Model
The system advances upward only when the lower layer holds under evidence.
Problem
01Problem–Solution Fit
If the problem is weak, every signal above it misleads.
Product
02Product–Market Fit
If users do not return, you do not have product–market fit.
Business Model
03Business Model Fit
If margins break at scale, the model fails.
If one layer breaks, every layer above it becomes less trustworthy.
- Weak problem evidence invalidates product confidence.
- Weak product pull invalidates business confidence.
Diagnostic module
Current Stage
Use this stage once real users already exist
Product layer
Product–Market Fit
System state
Current layer
Evidence quality
In review
Risk weighting
Moderate
Operational recommendation
If users only respond to pressure, the product has not reached fit.
Next action
After early usage appears, but before scale spend, team expansion, or channel ramp.
How ProductBooks works
- Run the evaluator.
- Identify what still scores zero.
- Generate the missing evidence.
- Re-run the same stage before moving on.
Diagnostic module
What this stage decides
Keep the decision boundary narrow. Everything outside it stays outside.
Decides
Whether users return without external prompting.
Does not do
Validate growth tactics.
Decides
Whether demand extends beyond launch noise.
Does not do
Predict total market size.
Decides
Whether payment behaviour is real, not stated.
Does not do
Help you "pass".
Diagnostic module
Evidence Rules
Strict rules only. No interpretation layer.
What counts
- Organic retention before prompted activity.
- Repeatable demand before campaign spikes.
What fails fast
- Observed payment behaviour before pricing opinion.
- Missing proof still blocks progression.
Diagnostic module
System references
Use the adjacent stages, reference rules, tools, and report path as one linked ProductBooks system.
Diagnostic module
Generate Missing Evidence
Operators generate proof. They do not soften the verdict.
Demand Reality Operator
GENERATEObserve whether new users arrive through repeatable channels without founder push.
Improves
The scoreable gaps this evaluator surfaced.
Payment Conversion Operator
GENERATEObserve whether users accept or reject a fixed paid offer.
Improves
The scoreable gaps this evaluator surfaced.
Retention Without Reminders Operator
GENERATEObserve whether users continue without reminders, nudges, or follow-up.
Improves
The scoreable gaps this evaluator surfaced.
Organic Pull Operator
GENERATEObserve whether users create demand through unsolicited referrals.
Improves
The scoreable gaps this evaluator surfaced.
Primary action
Run Product–Market Fit
Start with evidence you can show. Missing proof still scores zero.
Diagnostic module
Command path
Move to Business Model Fit only after product pull is real.
Once users return and pay without pressure, test whether the economics can support scale.
Go to Business Model Fit