North Metric

    Churn management:predict, act, prove.

    See which Stripe customers are likely to churn, approve the move to keep each one, and see the money you kept.

    Get your free churn report →Actions off until you turn them on
    IN SHORT

    A churn management process is the repeatable way a SaaS finds customers likely to leave, acts to keep them, and checks what worked.

    North Metric runs it on Stripe in three steps: predict who is at risk, act with a move you approve or a rule you set, and prove the money kept against customers left alone.

    THREE STEPS, ON STRIPE
    01PredictWho is at risk
    02ActA move you approve or a rule you set
    03ProveMoney kept vs customers left alone
    ✓Repeatable: it runs again every week
    01PREDICT

    Predict: who islikely to leave.

    Each paying customer gets Likely, Possible or Safe, a 0–100 risk score and up to three dated reasons. Read how churn prediction ranks them.

    CUSTOMER HEALTH · RANKED BY MONEY AT RISKEXAMPLE
    SIGNALSTRIPEUSAGERISKAT RISK
    CANCEL SETcancel scheduledusage −52%Likely95$2.1K/mo
    Cancel set for Oct 31 → Likely
    USAGE DROPseats 12 → 8−38% · 4 wksPossible58$1.2K/mo
    Seats cut, logins down 38% → Possible
    FAILED PAYMENTinsufficient_fundsusage steadyLikely84$640/mo
    Retries ended, no new card → Likely
    02ACT

    Act: the move,approved by you.

    One drafted move per customer, chosen by customer type and reason. You decide how it runs, with approvals and rules.

    Approve each
    ApproveEditSkip
    No CS team, a few hours a week, and every note to write yourself.Each move arrives drafted in your voice. Approve, edit or skip it in the Queue.1drafted move per customer
    Set rules once
    ConditionsSET ONCELimitsSET ONCEPreviewWHO IT WOULD ACT ON
    Approving the same kind of move every week gets old fast.Set conditions and limits once. Each rule previews the customers it would act on.Top 10accounts always ask, by default
    Locks and pause
    Pause everything
    Some changes are too big to run without you, like a price change.Price changes and discounts above your max always ask an Owner or Admin.1switch pauses everythingApprovals →
    03PROVE

    Prove: money kept vscustomers left alone.

    Kept MRR is tied to invoices; a comparison group, 10% by default, gets no move.

    WHO’S STILL PAYINGEXAMPLEOther at-risk customersHeld back, no moves$4.2KKept MRREARLY · FEW OUTCOMES
    STILL PAYING
    DAY 0DAYS SINCE FLAGDAY 90

    Stripe’s own recoveries are never counted, and results show as a range, labeled Early until there’s enough data. See how we measure money kept.

    See who is likely to churn in your own Stripe, ranked by money at risk.Get your free churn report →Actions off until you turn them onOr try the demo →
    04ONE CUSTOMER

    One customer,start to finish.

    One sample customer, from first flag to money kept. The comparison group shows if they’d have stayed anyway.

    Fernway$1.2K/moseats 12 → 8EXAMPLE
    THE USUAL WAYOn your own
    DAY 0Seats cut, 12 to 8Logged in Stripe. Nobody looks.
    DAY 20Logins still fallThe usage data sits in another tool.
    DAY 41Cancel scheduledYou see it in Stripe, after the fact.
    DAY 71Subscription ends$1.2K/mo gone, reason unknown.
    0 moves, 1 cancel−$1.2K
    NORTH METRICWith a move
    DAY 0Flagged PossibleScore 58: seats 12 → 8, logins −38%
    DAY 1Check-in approvedOne question, sent in your name.
    DAY 3Reply: setup stuckStored as the reason. You help them.
    DAY 61Still payingCounted as Kept MRR, tied to invoices
    1 note, 1 reply$1.2K
    05FAQ

    Questions abouthow it works.

    Moves for your first 5 customers are drafted once the trial's full sync finishes. A recovered payment counts when the invoice is paid; a check-in counts once the customer still pays 60 days later. The comparison stays labeled Early until both groups have enough closed outcomes.

    PREDICT · ACT · PROVE

    Start with who islikely to churn.

    Get your free churn report →Actions off until you turn them on