01Demand
Prove the product deserves intervention.
A demand-evidence protocol for founders who have software but cannot yet prove that a market wants it.
Open the playbook →Revenue repair library
Diagnosis without a repair plan is just labeling.
Five field playbooks for the five places a working software buyer path breaks. Baselines, audit steps, repair options, measurements, guardrails, and stop conditions included.
THE FIVE SURFACES
Fix the constraint. Leave the rest alone.
02Acquisition
Make one working channel visible and repeatable.
A practical acquisition repair for products with evidence of value but no reliable source of qualified new users.
Open the playbook →03Activation
Shorten the distance to first value.
An activation repair for products that attract the right people but lose them before the useful moment.
Open the playbook →04Monetization
Repair the path from intent to collected cash.
A monetization repair for products with real demand that lose buyers at pricing, packaging, checkout, or fulfillment.
Open the playbook →05Retention
Keep the promise after the first success.
A retention repair for products that activate or sell but fail to create repeated value, renewal, or durable use.
Open the playbook →THE GATE
No evidence of demand? Start there and spend nothing.
The other four playbooks assume somebody already wants the product. Demand is the only category where our default advice is not to buy a sprint.
Open demand evidence