How it works

From your address to a renewal that’s paid.

Five steps. The first two take minutes; the third depends on your app; the last two run on their own, within the limits you approved.

01
Give it your address and connect billing
Type your site address. While Tenure reads your site in the background, connect Stripe or Chargebee and write a short brief. With Stripe, your last 24 months of cancellations are read too, so you can see where customers leave before Tenure has done anything.
- Four screens: address, billing, brief, look
- Subscribers imported, webhook created for you
- Starts in test mode
01 · Address
yourapp.com
Site read in the background
02 · Billing
Stripe connected
Subscribers imported, webhook created
03 · Brief
“Rather pause than discount”
Text, pasted docs, or a file
04 · Look
Match my app
Accent, corners, fonts, light or dark
Prepare my plan
usually about a minute
02
Approve the plan it drafts
Tenure drafts About your app, a Cancellations plan with offers, terms and wording, and suggested limits and costs. You confirm what it got right, change what it didn't, approve the limits, and publish, first as Preview only if you like.
- Your brief wins: “pause, not discount” means no discounts
- Nothing reaches a customer until you publish
- Agents and API keys can't publish
About your app
Looks right?
Confirm
Limits and costs
A pause costs you $0 · budget per month
Approve limits and costs
Cancellations
Preview only, or Running
Publish (Running)
Coding agent → publish not allowed
Agents can’t publish. Only a person does.
03
Install it one of three ways
Point your existing cancel link at a hosted page (no code), add one script tag to the page with your cancel button, or paste a prompt into your coding agent, which proposes the install for you to review. Each path ends on the same checks, read from evidence.
- Hosted page, one script tag, or a coding agent
- Six checks, ticked only by real evidence
- Your own cancel path runs if Tenure can't
$ 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 and verify
Six checks, ticked only by real evidence.
Billing is talking to Tenure
We know who your users are
Your app is telling us what happens
Customers can see it
A test change went through
Emails will arrive
04
It decides one customer at a time
At each moment, code gathers the customer's facts and their own words, one read answers plain questions and picks among the offers you published (or none), and code applies every limit. The customer sees at most one offer, and a full-size way out.
- No scores, tiers or segments
- Hardship stands down; billing trouble holds offers
- Every decision is logged with its reasons
01 · What goes in
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 words
02 · Typed questions, one read
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 the offers you published, or none
03 · Code checks, then shows
Eligible for this plan
Within your budget
Cooldown since the last offer
No payment being retried
Margin floor holds
Never computed
churn score · risk tier · segment
05
It counts what billing confirms
A save is booked when the provider confirms the change, and its money is confirmed when the next renewal invoice is paid. Every figure names how many customers it rests on, and no causal lift is claimed without a comparison group.
- Still to confirm until the renewal is paid
- Did it last? three billing periods on
- Rates only from 20 customers up
Still to confirm
Which saves has billing confirmed with a paid renewal?
Recorded: a renewal invoice was paid3 saves
Still to confirm6 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

Is it really working?

Six checks, read from evidence.

Simulations, previews and Tenure's own test pages never count. A path that skips a check shows what it would unlock, never a tick.

01
Billing is talking to Tenure
A signed receipt from Stripe or Chargebee
02
We know who your users are
A signed identity that resolves to a customer
03
Your app is telling us what happens
An event for each fact you confirmed
04
Customers can see it
The widget loading on your own page
05
A test change went through
Confirmed by the provider's own event
06
Emails will arrive
A test email accepted from your verified sender

Details for developers and coding agents are on the developers page.

Questions, answered plainly.

Do I need to write code?

No. The hosted page needs only your billing connection and a link. The widget and agent install add the in-app flow and your app's events, which going quiet needs.

Can I try it before customers see anything?

Yes. New workspaces start in test mode, every experience can be published as Preview only, and “Try it as your customer” runs the real flow without billing anyone.

What happens to customers while I set it up?

Nothing. Until you publish an experience as Running, customers cancel exactly as they do today.

See the plan Tenure would draft for your app.

Give it your site address. It reads your pricing and your Stripe catalogue, drafts a retention plan in about a minute, and waits for you. Nothing reaches a customer until you publish.

Starts in test modeStripe or ChargebeeQuestions first? Talk to us

From your address to a renewal that’s paid.

Give it your address and connect billing

Approve the plan it drafts

Install it one of three ways

It decides one customer at a time

It counts what billing confirms

Six checks, read from evidence.

Questions, answered plainly.

See the plan Tenure would draft for your app.