Customer Retention · Keep

Churn-signal loop.

Reads product and support behavior for the pattern that precedes a cancellation, and puts the account in front of someone while there is still time to act.

Financial lens−18% logo churn modeled targets · not client results
.crft/Churn-signal loop

logo churn

to the Scan's evidence — before any scope

4–10 wks

to a system in production, not a pilot

modeled targets · not client results · timings are CRFT's standard engagement

The work, today.

Churn is discovered at renewal, which is the one moment it cannot be fixed. The signals were all there — usage fell, the champion went quiet, three tickets went unresolved — but they lived in three systems and nobody was reading them together.

Where the Scan startsWith your product events, support history and which save plays actually held last year.

What the system is.

Four lines, the same four on every system we build. Where they fall is what makes this one different from the last one.

Product usage, by account and by seat, over time
Support ticket volume, sentiment and time-to-resolution
Champion engagement — logins, replies, meeting attendance
Invoice and payment behavior
01

What it reads

The signals it works from. Typically connects to Product analytics, Support desk, CRM and Billing.

01Which accounts are drifting, and how far along
02Which signal is driving the risk, so the play matches the cause
03Which save play has actually held for this pattern before
04What is urgent this week versus what is worth watching
02

What it decides

The calls it makes on its own, unattended, every time it runs.

A ranked risk list into the CSM's own view, with the reason stated
The suggested play and the evidence behind it
A note on the account record so the history survives a CSM change
03

What it writes back

Into the tools the work already lives in.

04

Where the human stays

A CSM runs the play. The system is explicitly not allowed to contact an at-risk customer — the moment a renewal is in doubt is the moment a human has to be the one in the room.

How we set it up.

The same four legs as every CRFT engagement — written for this system rather than in general.

  1. 01
    Scan48 hrs · evidence before scope

    We look at the accounts you lost last year and work backwards. The question is how early the pattern was legible, because that sets how much warning the system can actually buy you.

  2. 02
    Scope1 week · the report is the scope

    Scope turns on how many signals are reachable. Product events and tickets are usually enough to start; billing and champion engagement sharpen it.

  3. 03
    Build4–10 wks · production, not a pilot

    Risk scoring first, plays second. A list nobody acts on is worse than no list, so the play library and the ranked list ship together or not at all.

  4. 04
    Compoundongoing · it reports, then improves

    Every save and every loss teaches it which plays hold. It gets better at your customers specifically, which is the part a bought tool cannot do.

What we hold it to

How many weeks of warning it buys, and whether accounts it flagged were saved at a higher rate than accounts it did not.

Get CRFT

Build the intelligence your company compounds on.

Five inputs, a published price, a report in 48 hours. Decide with numbers — then own what gets built.

Or just send us a note
What kind of system? Pick any that apply