How it works
Set up retention. Review it before it runs.
Steps 1–2 · Your site, Billing
Give it your address and connect billing
Paste your site, connect billing. With Stripe or Chargebee you also get a free churn report of your last 12 months of cancellations.
- Subscribers imported for you
- Starts in test mode
01 · Your siteyourapp.com
Read in the background
02 · BillingStripe connected
Subscribers imported
03 · Your plan3 offers, 3 emails
One approval
Prepare my plan
usually about a minuteStep 3 · Your plan
Approve the plan it drafts
Offers, wording, win-back emails and spending limits, drafted. Edit, or tell it “offer a pause, not a discount”, then approve.
- Draft again any time
- Agents and API keys can't approve
What your app does
One line, drafted from your site
Offers and emails
3 offers at the cancel click · 3 win-back emails
Spending limits
Never more than $790 a month in offers
Nothing reaches customers until you switch it on.
Approve planCoding agent → approve not allowed
Agents propose. Only a person approves.
Step 4 · Switch to live
Install it one of three ways
Pick one of three ways in. Each ends on the same checks, read from evidence.
- No codepoint your cancel link at a hosted page
- One tagadd the widget
- Coding agentpaste one prompt; it proposes, you review
- With the widget, your own cancel path runs if Tenure can't load
$ claude mcp add --transport http tenure \ "https://app.trytenure.co/api/mcp?profile=install" \ --header "Authorization: Bearer $TENURE_TEST_KEY" ✓ get_app_definition · get_verification✓ propose_facts · 7 facts, each with file:line✓ widget wired · simulate_decision→ submit_for_review. A person decides.
Install
Example checks; your setup determines which are required.- Billing is talking to Tenure
- We know who your users are
- Your app is telling us what happens
- Customers can see it
- Optional: test billing change
- Email sending is verified
After launch
It decides one customer at a time
What they pay, how they use your app and their own words decide which offer, or none. One offer at most, within your limits, and a full-size way out.
- Answers the reason they give, not a segment
- Hardship gets no offer; billing trouble goes to you
- Every decision is logged with its reasons
01 · What Tenure looks at- Plan
- Pro, monthly
- Price band
- $10–50 a month
- Subscribed
- 3–12 months
- Usage trend
- falling
“It’s a lot for us right now, we’re a team of two.”
Their words02 · Why they’re leaving- Billing error?no
- Hardship?no
- How-to question?no
- Moving elsewhere?no
- Price concern, in their words?yes
Pick: Switch to Basic at renewal
One of your offers, or none03 · Your limits, checked- Eligible for this plan
- Within your budget
- No repeat offer too soon
- No payment being retried
- Margin floor holds
After launch
It counts what billing confirms
A save counts when billing confirms the change, and its money when the next renewal is paid. Every figure names how many customers it rests on.
- Money counted at the paid renewal
- Checked again three billing periods on
- Rates only from 20 customers up
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
Switch to live only when every required check is green. Details for developers and coding agents are on the developers page.
Questions, answered plainly.
Something else? Talk to us.
Do I need to write code?
What does setup ask for?
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.
Can I try it before customers see anything?
What happens to customers while I set it up?
See the plan Tenure would draft for your app.
Your cancel flow, offers and emails, drafted from your site and billing.