B2B customer expansion & retention engine
lifecycle

B2B customer expansion & retention engine

  • lifecycle
  • retention
  • expansion
  • customer-success

Read every paying account's health from what customers actually do, act on risk months before renewal, run reviews buyers attend, and grow accounts from their own usage.

6 Steps in the flow
5 Tools orchestrated
5 Human checkpoints
Weekly Run cadence
every paying account, weekly Accounts with a health verdict

The objective

What this system is built to do

Revenue you already won is the cheapest revenue you will ever grow. Read each account's health from what customers do, act on risk months before renewal, and grow accounts from their own usage and words, never from a pitch.

Grow revenue from the customers you already have. Every week each paying account gets three separate reads (lifecycle phase, risk, expansion) taken from what they do in the product, what they pay and what they say. Risk is triaged by failure mode and worked from 120 days before renewal; expansion is worked from the customer's own usage or words; and the people who pay hear the value case in their own numbers before renewal comes round. Not doing: one blended health score, discount-first saves, or pitching a paying customer as if they were a prospect.

Cycle & hand-offs: Read account health runs weekly (Mon) and starts the cycle. Hand-offs: Read account health → Triage risk & run the save: once this week's health read flagged at least one account as at-risk (named in the run summary); Read account health → Run the expansion play: once this week's health read flagged at least one account as expansion-ready (named in the run summary); Run the renewal clock → Triage risk & run the save: once the renewal clock flagged a renewal inside 90 days as at-risk. Runs on its own rhythm: Run the renewal clock (weekly (Wed)); Hold business reviews (monthly); Learn & refine (monthly). Any other link waits for a person. Sign-off steps stay with a person; everything else can run on its own once armed.

How it runs

The steps your team follows

The workflow, exactly as it runs inside . It plays through step by step, or pick any node on the map.

1

Read account health

Weekly

Every Monday: give each paying account three separate reads, never one blended score. Read-only on every source.

  1. Pull the data in parallel for every active paying account (exclude free and internal accounts): subscription and renewal date from Stripe; usage from (core-action count and last date over 30 days, active people over this and the previous 30 days, whether the key setup step is in place); deal, owner and contacts from ; the latest calls from Granola. If one source fails, log it, treat that signal as missing for everyone, and carry on.
  2. Lifecycle phase from first paid date: *activating* (first 60 days, default), *established* (after that), *leaving* (cancellation pending).
  3. Risk tier, first match wins. High: cancellation pending; no core action in 30 days; last core action over 21 days ago; key setup step missing past day 14; established usage down by more than half month on month. Medium: usage down 30–50%; last core action 14–21 days ago; active people halved; outputs produced but nobody reviewing them. Defaults: tune every threshold against your own churned accounts. Only read momentum above a minimum activity floor.
  4. Expansion tier (active accounts only): near or over plan limits, repeated top-ups, new teams or use cases appearing, a stated ask for more.
  5. Write all three reads to the CRM with the reason each changed. Only a change of tier triggers anything downstream.
  6. Alert on change: a new high risk goes to the account owner today via ; a new high expansion goes to the expansion owner. Everything else waits for the weekly digest.

Output: three reads per account in the CRM, change alerts, and a weekly digest of movers.

2

Triage risk & run the save

Weekly

For every high-risk account, and every renewal inside 120 days: name the failure mode, then run the play that fits it. A save aimed at the wrong failure mode speeds the churn up.

  1. Classify: value gap (they use it and cannot show it is worth the money) · adoption gap (stopped using it, or never started) · champion loss (your person left) · sponsor shift (new decision-maker or strategy) · competitive displacement (an alternative is in the building).
  2. Match the play: value gap → a value recap built from their own system data, walked through with whoever pays; adoption gap → relaunch only the one workflow that hurt when they bought; champion loss → treat it as a new sale to whoever inherited the problem, and route the departed champion to your warm-outreach system; sponsor shift → executive-to-executive re-anchoring on the new agenda; displacement → a switching-cost case and a dated roadmap commitment from someone senior.
  3. Save or release: is the fit still right, is the problem still real, are the economics still sensible? Two of three, fight. Otherwise release well: a clean exit, a data handover and a standing reason to come back.
  4. Commercial levers, in order: right-size the scope, restructure the term, add service, pause rather than cancel, and only then a price concession, always traded for something real.
  5. Draft every message and the plan for the account owner. Human approval before anything reaches the customer.
  6. Log every loss, fought or released, with its failure mode, the first signal and the days between signal and first action.

Output: a named failure mode, a save plan and drafted touches per at-risk account.

3

Run the renewal clock

Weekly

Every Wednesday: walk every renewal due in the next 120 days through the same checkpoints. Healthy accounts take minutes; flagged ones go to *Triage risk & run the save*.

  1. List renewals inside 120 days from Stripe and .
  2. T-120: a named owner and a written verdict: clean, watch or at risk. No account without both.
  3. T-90: at risk goes to the save; watch gets a value-recap touch and a re-check at T-60; clean gets its renewal pack drafted.
  4. T-60: commercial terms on the table. If the price is changing, the customer hears it now.
  5. T-30: signature logistics only. A brand-new objection here is logged as a detection miss.
  6. Raise a task for the owner at each checkpoint that needs a person. Human approval before any pricing or term change is sent.

Output: every renewal inside 120 days with an owner, a verdict and its next checkpoint date.

4

Run the expansion play

Weekly

For every high-expansion account: build the conversation from their usage or their own words. They already know the product; never pitch them like a prospect.

  1. Read their last calls in Granola and their usage in before writing anything.
  2. Pick the play from the signal: repeated top-ups → show that the next plan costs less than the top-ups; they asked for more → answer with the options and a recommendation; near a ceiling with a new use case visible → lead with what their team started doing, not the meter; warm relationship but little value realised → confirm the value gap first, then lead with value before any upgrade, with different proof for the champion and the budget holder.
  3. One sequence per contact. Every message opens with something they did or said; numbers they can check; no "just checking in".
  4. The last step is internal: if no reply after the last customer touch (default 10 days), alert the account owner, never another nudge.
  5. Human approval the account owner to approve every message. Create the expansion deal in when the customer engages.

Output: drafted, owner-approved expansion sequences and expansion deals.

5

Hold business reviews

Monthly

Monthly: schedule and prepare the reviews that keep the people who pay convinced of value. Two meetings, two audiences.

  1. Segment: top-tier accounts get a quarterly operational review plus an executive review 90–120 days before renewal; middle-tier accounts get a review when a trigger fires (renewal inside 120 days, risk, expansion, sponsor change); the long tail gets a one-page written value summary each quarter instead of a meeting.
  2. Build the pack from the board, three panels: the look back in their numbers against a baseline agreed at onboarding (including what did not improve); the current state, with the same health verdict you hold internally; and next quarter's plan with goals, owners and dates, half of them the customer's.
  3. No agreed baseline yet: installing one is the first review's whole job. If a value recap cannot be built, send the account to *Triage risk & run the save* now.
  4. Human approval the account owner to review the pack. The executive review only runs with the budget holder in the room.
  5. Afterwards, record the updated plan and baseline, route risk and expansion signals, and note attendance: a sponsor who skips a review is a risk signal.

Output: review packs, agreed success plans and routed signals.

6

Learn & refine

Monthly

Monthly: check the reads were right and tighten them.

  1. Compare last month's risk tiers with what happened: which churned accounts were never flagged, which flagged accounts were fine.
  2. Report save rate by failure mode (never blended), signal-to-action lag, net and gross revenue retention, expansion MRR and concession cost per saved pound.
  3. Propose threshold and rule changes for *Read account health* with the evidence; Human approval before changing them.
  4. File each lesson into the playbook's Lessons.

Output: a monthly retention read and tuned health rules.

1 / 6

Setup

The stack

The tools this system drives, and the context you bring once. Connect your own accounts, or swap in your team's equivalent.

Tools to connect

Stripe Powers Read account health
PostHogFree – usage Powers Read account health Or Amplitude, Mixpanel
HubSpotFree – $90 / mo Powers Read account health Or Pipedrive, Salesforce
Granola Powers Read account health
SlackFree – $7 / mo Powers Read account health Or Discord, MS Teams

Context to bring

Your documents 4 files
  • Billing data Plan, price, first paid date and renewal date per account
  • Product usage events The core action, the human action and the key setup step
  • Account owners Who owns risk and who owns expansion, by tier
  • Agreed customer baselines What each customer measured success against at onboarding

Proven in market

Run by 115 teams, verified on real accounts

B2B customer expansion & retention engine is built and verified by Growth Division, the GTM team behind 130+ companies.

Built & verified by Growth Division

Get started

How to run this system

Live in an afternoon. Clone it, connect your tools, set your inputs, and turn it on.

  1. 1

    Add to

    Clone the B2B customer expansion & retention engine into your workspace, wired end to end.

  2. 2

    Connect your tools

    Stripe, PostHog, HubSpot +2 more.

  3. 3

    Set your inputs

    Your ICP, targets and brand rules, once.

  4. 4

    Turn it on

    It runs weekly on autopilot, checking in with you only where it matters.

~1 hr / week your time on autopilot · vs 6–8 hrs / week by hand
every paying account, weekly Accounts with a health verdict, produced for you
All growth systems

Next launch: Week of 3 Nov 2026 · 1 slot left

Run the B2B customer expansion & retention engine in your workspace.

In 30 minutes we find where your go-to-market is leaking and map the first system we’d launch. You leave with a plan whether or not you work with us.