tenure

Re-engage inactive customers

Hear the quiet weeks before the cancel click.

Tenure spots paying customers going quiet, and new ones who haven't reached the step that goes with staying, and sends a short check-in in your voice. Two at most.
app.trytenure.co/customers

A customer on Pro, monthly

Facts from billing and your app · no score
Paid so far
$294
Last active
23 days ago
Usage, 30 days
−46%
MarAprMayJunJulAugSep

Check-in sent, in your voice

From your domain · 1 of at most 2

At the cancel click

Switch to Basic at renewal, Oct 25

Nothing changes until then. Cancel stays one button away.

Waiting on renewalcounts when Oct 25 is paid

The problem

By the cancel click, the decision is made.

  1. 01

    Quiet looks like nothing

    No ticket, no complaint. Just fewer sessions each week.

  2. 02

    Alerts turn into spam

    An email for every dip teaches people to ignore you.

  3. 03

    Dashboards don't write back

    A chart shows the drop. It doesn't reach the customer.

How it works

What Tenure does, step by step.

  1. 01

    Two triggers, confirmed twice

    By default, use down 40% on the month before, or none for three weeks, confirmed a day later; you can change both. Or a new customer who hasn't reached your milestone in time.

    Weekly use, one customer

    From your app’s own events
    −46% vs prior 30 days
    8 weeks steadyScan 1 · Scan 2, a day later

    Check-in 1

    Sent, from your sending domain

    Check-in 2

    Only if still quiet

    A third

    Never. Two is the cap.

  2. 02

    A check-in, not a campaign

    A short note from your sending domain, with no button: they reply to you. Two at most per quiet spell and per 90 days.

    From Sam at YourApp <sam@yourapp.com>

    Quick check-in

    Hi, it’s been a few quiet weeks on your account, so I wanted to check in.

    If something got in the way, just reply and tell me. I read every answer.

    Sam

    No button, they reply1 of at most 2Quiet hours respected
  3. 03

    Which early steps go with staying

    Early steps that go with still paying at 90 days, from your own events. Both shares and their counts, labelled “A pattern, not proof”.

    Created 2 or more projects in their first week

    A pattern, not proof
    Still paying 90 days after they started
    Did it81% · 118 of 146
    Didn't47% · 92 of 196

    Milestone email · day 5

    To new customers who haven’t done it yet. One email, in your voice, no offer.

    Counts: sent · did it afterwards · still paying
  4. 04

    One milestone email

    Pick a step and a day. New customers who haven't taken it get one email in your voice, with no offer. Results counts what followed.

    Created 2 or more projects in their first week

    A pattern, not proof
    Still paying 90 days after they started
    Did it81% · 118 of 146
    Didn't47% · 92 of 196

    Milestone email · day 5

    To new customers who haven’t done it yet. One email, in your voice, no offer.

    Counts: sent · did it afterwards · still paying

The details

What’s in it.

Paying customers only
Trials get their own email.
Runs on your usage data
Events, PostHog, Segment, or a last-active column.
Workspace limits
By default 1 email a week, 3 a month, quiet hours.
Preview first
Records what it would send, sends nothing.
From your domain
Your Resend account, your verified sender.
20 on each side
Or the step isn't shown.

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

  • Going quiet needs usage data: your app's events, PostHog or Segment, or a last-active date from your own database, a Google Sheet or a CSV. A last-active date catches use that stopped, not use that fell. Everything else needs only billing.

Questions about this part.

Something else? Talk to us.

Why only two emails?
A third rarely helps and often costs you their attention for good. The cap is enforced at send time, across both triggers.
Does it find what makes people stay?
It finds early steps that go with staying, and shows the counts behind each. That's a pattern, not proof, and the page says so.
What if I don't send product events?
Connect PostHog or Segment, or a last-active column in your own Postgres, Supabase or MySQL database, a Google Sheet or a CSV. With no usage data, going quiet stays off and everything that runs on billing still works.

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