tenure

Solutions · Early growth

Fits your stack. Numbers that hold up.

Put Tenure's decision in your own screens and your support agent, and report retention numbers your board can check against billing.

Rather ask first? Talk to us

What matters at this stage

Three things, and what Tenure does about them.

  1. 01

    Your screens, your support agents

    Render the decision yourself with the headless SDK or REST, or give support agents the same decision over MCP. The exits and terms can't be changed.

  2. 02

    A record of every action

    Every decision, billing change, email and settings change goes into an audit log you can verify and export, and secrets are encrypted at rest.

  3. 03

    Numbers that hold up

    Saves booked only on the provider's confirmation, money confirmed at the paid renewal, exports of the ledger, and no lift claimed without a comparison group.

Developers

REST, headless, MCP and webhooks

Recommend, report what was shown, then enable, from your own UI or a support agent. Signed webhooks tell your backend what happened, retried up to eight times. OpenAPI 3.1 describes every endpoint.

Developers 
$ 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

Measurement as you grow

No lift claimed without a comparison group

Proving an offer caused a save needs customers shown no offer, in numbers big enough to mean something. Until you have them, Results reports only what billing confirmed, and says how far you are.

Results

A fair comparison

A fair comparison needs about 1,000 customers who click cancel; you have 212 from the last 90 days.

No lift is claimed. Results reports what billing confirmed.

Lift

not claimed

Saves

counted from billing

Coverage

Nothing missed quietly

Cancellations that happen in Stripe or Chargebee without passing through Tenure light an amber health signal, so a gap in the install shows up as a gap.

Results

Billing is talking to Tenure

Last signed receipt 4 minutes ago

Emails will arrive

Verified sender on yourapp.com

3 cancellations bypassed Tenure

Cancelled directly in Stripe this week

Good to know

  • Mobile apps open the hosted flow in a web view.
  • Exports are CSV files and an export API.

The same product at other stages

See pricing
Just launchedFirst paying customers. Set up in one sitting, no code needed.Learn more Small teamsRoles, approvals and spending limits for a team that shares the work.Learn more

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