Start with what you don’t know.
Run experiments. Capture what happens. Understand what you learn.
How it works
Every experiment starts as a question.
Watch what happens to it.
Will people pay for this?
Active experiment
Will people pay for this?
Fact12 potential customers said they would pay.
ObservationMost wanted to see a working product first.
LearnedInterest exists, but stated interest didn’t equal commitment.
DecidedBuild the smallest working version before continuing validation.
Why are users leaving?
Active experiment
Why are users leaving?
ObservationDrop-off concentrates in the first session, not later.
LearnedThe problem is onboarding, not the product itself.
Should we spend more on ads?
Completed experiment
Should we spend more on ads?
FactAd spend doubled; signups grew 9%.
DecidedHold spend flat — the bottleneck isn’t acquisition.
Connected, not scattered
One traceable chain, not four disconnected notes.
What happened, what it meant, and what you did about it — Retenum keeps every step linked to the one before it, so the reasoning is still there when you need it again.
Fact
12 potential customers said they would pay.
Observation
Most wanted to see a working product first.
Learned
Interest exists, but stated interest didn’t equal commitment.
Decided
Build the smallest working version before continuing validation.
Intelligence
Don’t just finish the experiment.
Don’t just finish the experiment.
Understand what it taught you.
Retenum looks back at everything you captured — not what worked in general, what happened in yours.
You started here
“We believe creators will bring qualified users.”
Then this happened
- Creators generated significant attention.
- Signups increased.
- Completion dropped after onboarding.
What changed
The experiment suggests acquisition wasn’t the primary problem. Attention increased, but activation didn’t.
Derived from this experiment’s own facts and observations — nothing generic added.
What are you trying to figure out?
Bring your unknown. Retenum starts there.