Impact
How Oskar counts revenue that was recovered, added or protected after it flagged a customer, and what it deliberately doesn't count.
Impact shows what paying attention was worth: revenue that changed after Oskar flagged a customer. It's deliberately conservative. An outcome only counts when your billing data shows a change that came after the flag, and each flag counts once.
What the page shows#
For the last 90 days, Impact shows:
- MRR added after growth signals
- MRR recovered from failed payments
- MRR protected, marked "partly estimated" when some of it is
- How many outcomes were followed through
Below that is the outcome ledger: the date, the customer, what happened in plain words, the type, and the amount. Amounts are monthly recurring revenue (MRR) in the customer's own currency.
Each new outcome is also noted in Latest from Oskar, and appears in your email digest.
How each outcome is counted#
Oskar follows up every decision from the last 120 days that flagged a customer as needing something. Decisions that the customer looks normal are never counted.
Recovered#
When: Oskar flagged a payment problem, and a payment that had already failed before the flag was paid after it.
Amount: the customer's MRR.
A payment failed on 3 Mar and I flagged it on 4 Mar. It was paid on 6 Mar.
Added: growth#
When: Oskar flagged a possible expansion, and the customer now pays more than they did when the decision was made. Each decision records the customer's MRR at the time, so the comparison is exact.
Amount: the increase in MRR, not the whole subscription.
Added: trial converted#
When: Oskar flagged a customer on a free trial as needing help getting started, and they are now paying.
Amount: their new MRR.
Protected: cancellation withdrawn#
When: Oskar flagged a customer as worth checking in while their subscription was set to cancel, and they have since withdrawn the cancellation and are still active.
Amount: their MRR.
Protected (estimated): stayed after you checked in#
When: all of these are true:
- Oskar flagged a customer as worth checking in.
- Someone in your account marked that customer's decision as useful or already handled after the flag.
- At least 30 days have passed since the flag.
- Oskar's latest decision is that they look normal.
- Their subscription is still active and not set to cancel.
Amount: their MRR, always marked estimated. Nobody can be certain whether they would have left anyway, so Oskar shows this separately rather than mixing it in with revenue that came straight from your billing data.
What doesn't count#
- Revenue changes that happened before Oskar flagged the customer.
- Customers Oskar didn't flag. A customer who upgraded on their own isn't Oskar's doing.
- Flags older than 120 days.
- The same flag twice. Each flag counts once, and a customer can't be counted twice for the same kind of need from the same stretch of decisions.
- Customers whose subscription has ended, for growth and trial outcomes.
When Impact updates#
Oskar looks for new outcomes each time your billing data syncs and after each assessment. When Stripe notifies Oskar that a failed payment was paid, the next sync or assessment picks it up.
Using Impact#
Impact is there so you can judge whether Oskar is worth your attention. If it stays empty for a while, it usually means one of:
- customers on your focus list haven't been followed up yet
- decisions haven't been marked as useful or handled, which is what the estimated protected outcome needs
Marking decisions honestly, including wrong ones, makes both the decisions and this page more accurate. See Decisions and feedback.