tenure

Results

Every save in revenue, straight from billing.

A save counts when billing confirms it, and its money when the renewal is paid, so your numbers match your billing and hold up in front of a cofounder or an investor.

Revenue kept

$312

collected

Offers accepted

10

of 14 shown

Cost of offers

$41

discounts, full run

From 14 cancel clicks · Aug 26 – Sep 25 · counted, not estimated

Waiting on renewal

Which saves has billing confirmed with a paid renewal?
  • Recorded: a renewal invoice was paid3 saves
  • Renews in the next 30 days4 saves
  • Renews in 31 to 90 days2 saves
  • Ended first1 save

Did the save last?

Still subscribed 3 billing periods on

5 of 6

No percentage below 20 customers.

The problem

Most retention numbers count clicks, not money.

  1. 01

    “Saved” means “clicked accept”

    Even if they leave next month.

  2. 02

    Percentages on tiny samples

    “50% saved” from four customers isn't a result.

  3. 03

    Lift with no comparison

    Cause needs a group that didn't get the offer.

How it works

What Tenure does, step by step.

  1. 01

    What it was worth

    Revenue kept, offers accepted, cost of offers, each with its count and dates: “counted, not estimated”. Discounts are costed for their whole run.

    What it was worth

    Aug 26 – Sep 25 · from 14 cancel clicks
    • Revenue kept3 saves with a paid renewal$312
    • Offers acceptedof 14 shown10
    • Cost of offers3 discounts$41

    counted, not estimated

    Cost of offers · $41

    Each discount costed for its whole run
    • $5 off× 3 months$15
    • $4 off× 3 months$12
    • 50% off a $28 month× 1 month$14
  2. 02

    Money counted at the paid renewal

    Each save waits, with its renewal date, until the renewal is paid. Upcoming renewals show your billing's own quote; nothing counts until it's paid.

    Waiting on renewal

    Which saves has billing confirmed with a paid renewal?
    • Recorded: a renewal invoice was paid3 saves
    • Waiting on renewal6 saves
    • Renews in the next 30 days4 saves
    • Renews in 31 to 90 days2 saves
    • Ended first1 save

    From 10 saves · recorded + still to confirm + ended first

  3. 03

    Did the save last?

    Still subscribed three billing periods after a cancel click, two after a trial or a check-in. Refunds and repeat cancels count against it.

    Did the save last?

    Did customers who accepted stay?
    MomentChecked afterStill subscribed
    Cancel click3 periods5 of 6
    Trial ending2 periods4 of 4
    Going quiet2 periods2 of 3
    Win-back3 periods1 of 2

    Rates show once 20 customers have been through · refunds count as not staying

    Left within one period

    1

    Clicked cancel again

    0

The details

What’s in it.

Never a save
Keep button, help card, check-in email.
In their words
Themes from what customers typed.
How each offer did
Shown, accepted, confirmed, lasted, cost.
Nothing missed
Cancels that bypassed Tenure are flagged.
Exports
Every save and decision, as CSV or by API.
Every currency you bill in
Offers and figures stay in each customer's own currency, under limits you set for it. Nothing is converted.

What setup needs

To start, no code

  • An email address you can confirm. Tenure sends a 6-digit code when you sign up.
  • Your Stripe or Chargebee API key, pasted in (for Stripe, a secret or restricted key).
    • Your workspace starts in test mode: a live key lets Tenure draft from your real customers, and Tenure only reads with it until you switch to live; a test key works too, with test data.
    • After you switch to live, Tenure changes billing only to carry out what a customer chose (an offer they accepted, or their cancellation), or a refund that an API key with the Runtime scope asks for, within your refund limit.
    • Billing on your own backend? Tenure calls your billing service or sends it a signed webhook, for cancellations and the seat, add-on or pack offers your service supports. A pause, discount or plan change needs Stripe or Chargebee.

To switch to live

  • Point your app’s cancel link or button at your Tenure page. No code needed. Or have a developer add the widget.

Later, optional

  • Customer emails: your own Resend account and a verified sending domain. This may need DNS access, and Resend’s costs are separate.
  • Check-ins when customers go quiet: usage events, or a connected source of last-active dates.

You can review your whole draft before installing anything.

Good to know

  • Results never claims an offer caused a save. Nobody is held out of offers yet, so there is no lift figure.

Questions about this part.

Something else? Talk to us.

Why not show a save rate?
Below 20 customers a rate misleads, so Results shows counts. From 20, the rate appears beside its count.
Is test activity counted?
No. Test mode and simulated activity never appear in live figures.
Can I see the evidence behind one save?
Yes: the facts, the customer's words, the offer, and the billing event that confirmed it.

See the plan Tenure would draft for your app.

Your cancel flow, offers and emails, drafted from your site and billing.

Drafting your plan starts with a free account, then you connect billing.

Free during early accessStripe, Chargebee or your own billingQuestions first? Talk to us