Retention
Getting a new customer to value
Customers buy and then go quiet.
Signals to look for
- onboarding
- activation
- setup
- go quiet
- never used
- first value
Questions to answer
- What is the first moment a {unit} gets real value?
- How long does it take today, and what blocks it?
- What does the customer have to supply, and do they know that before buying?
- Which customers reached value fast, and what was different?
Evidence required before committing
- time from purchase to first value per {unit}
- which steps stall
- retention by time-to-value
Likely constraint
- A dependency on something the customer must provide
- No owner of the first two weeks
How the decision branches
- IfFast-to-value customers retain betterThenTime-to-value is the retention lever; attack it directly.
- IfThe same step stalls every timeThenRemove it, do it for the customer, or move it before payment.
- IfNothing is measuredThenInstrument the first two weeks before redesigning anything.
What to test
Take the next five {unit}s through a written, owned two-week sequence and record time to first value against the previous five.
Read after 30 days.
What success looks like
- Time to first value falls
- All five reach the defined first value
What means stop
- No change in time to value — the block is in the product, not the process
Typical next move
- Time to value falls → Make the sequence the default and watch retention over the next quarter.
- It does not → Escalate to product instrumentation.
Who does the work
Aury can carry out: read company, prepare document, create task, file memory. Specialists involved: operations, product.
Where this stops being true
Requires a definable first value. If nobody can define it, that is the finding.
Five customers show direction, not a retention effect. Retention takes a quarter or more to read.
Provenance
- Sourced operator experience: Activation and onboarding practice across recurring-revenue businesses
- Aurygine synthesis: Aurygine synthesis across founder journeys
Confidence: high. Last reviewed 2026-08-25. Your company's own recorded results override this playbook whenever the two disagree.