LensReading which lens this session carries.

Standard operating procedure · RO7C · Revenue Growth Management

Churn Cohort Analysis

Analytical procedure owned by Renewals & Churn Ops in Revenue Growth Management. 4 numbered steps, 1 of them a person deciding and 3 of them agent work …

Procedure code

RO7C

Analytical

Rule versions in force

v3.7 · v3.6

2 governing rules stacked over it

In force since

2024-12-18

Earliest effective date across those rules

Last reviewed

2026-05-01

Latest review date across those rules

Rules approved by

1

Director, Renewal Operations

Rule health

2/2

0 under review · 0 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run churn cohort analysis to one repeatable standard inside Renewals & Churn Ops, part of Revenue Growth Management.

Entry condition

Runs analytical. Starts when a drift signal breaches tolerance.

Exit condition

The unit clears leader review, released by Director, Renewal Operations.

In scope

  • Every unit of churn cohort analysis raised inside Renewals & Churn Ops, from the trigger below through to the final step.
  • 3 of the 4 steps, which run without a person present.
  • 1 decision that stops the line until a named person releases it.

Out of scope

  • Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
  • Work that belongs to another function. This line records no handoff, so nothing leaves it mid-flow.
  • Shared-spine work. This line has none; every step is done inside the function.

Who owns it

Runs the line

Renewal Ops Orchestrator

Accountable person

Director, Renewal Operations

The end of the escalation path. Above them sits RGM Chief of Staff for the function.

That team’s remit

Owns renewal record work end to end inside Revenue Growth Management.

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

85% now · ceiling 88%

Auto-renewal and cancellation processing are contractual mechanics that run touchless.

The procedure, step by step

4 numbered steps · 1 of them stop for a person

A step is one station on the line.

No.StepWho does itWhat happensSystem of recordTime on the stepIn flight
01

Segment churn

Agentworkflow

Renewal Calendar Agent

Renewal Calendar Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Customer Relationship Management14.2 hrsstandard 22.5 hrs45
02

Attribute cause

Agentworkflow

Auto-renewal Agent

Auto-renewal Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Enterprise Data Warehouse2.3 hrsstandard 4.3 hrs32
03

Draft finding

Agentworkflow

Churn Signal Agent

Churn Signal Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Configure, Price and Quote6.3 hrsstandard 12.8 hrs29
04

Leader review

HumanpolicyDecision

Director, Renewal Operations

Releases: Director, Renewal Operations

Work stops. Director, Renewal Operations reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the renewal record decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Customer Relationship Management14.5 hrsstandard 21.7 hrs7

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine.

Person1 station and 39% of the dwellAgent3 stations and 61% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Enterprise Data Warehouse
Configure, Price and Quote
Customer Relationship Management
Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it.

speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/4
the happy path, worked time0 min of 37 hrs
the same run against its allowance0 min of 2.6 days
Human
decides · 1
Agent
does the work · 3
GBS
shared spine · 0
run log

Nothing has happened yet.

where the worked time goes37 hrs a unit
Person15 hrs · 39%Agent23 hrs · 61%1 crossing between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 4 stations stop for a person and every one of them still does on this run.
  • Every one of the 1 decision is still taken by the person who holds it. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 88% autonomy ceiling and this run sits at 61% unattended, inside it.
  • 3 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
what would have to change

One decision, held by Director, Renewal Operations.

stays with a person
  • 04 Leader review — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
what this run is, and what it is not

This is a run, not a forecast.

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations.

The second clock is the allowance.

A decision may be handed to the agent lane only if two things hold …

The run reads the station rows only.

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything.

Run it again, going wrong

The same unit, the same stations, broken the way the estate already records breaking

This is the same unit on the same stations, breaking.

No break below was chosen.

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

4 stations, nothing waiting, nothing sent back

0 min of 37 hrs

now Segment churn · Renewal Calendar Agent · 14 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 39 hrs

now Segment churn · Renewal Calendar Agent · 14 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

2 counted categories land on this procedure.

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen.

Two clocks run. Worked time is the sum of the time the work is actually being done …

Roles and responsibilities

5 named parties

The responsibility grid is assigned by a rule, not lifted from a chart.

PartyRACIStepsDutyEscalates to

Renewal Ops Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to Director, Renewal Operations when a unit falls outside the envelope or confidence drops below the floor.

Renewal Calendar Agent

agent

A4% autonomy · ceiling A4%

99% clean · 1% overridden

Responsible1Runs the repeatable portion of renewals & churn ops inside the shared transaction spine at spine cost and spine controls.Escalates to Director, Renewal Operations when the unit falls outside the decision envelope or confidence drops below the floor.

Auto-renewal Agent

agent

A4% autonomy · ceiling A4%

93% clean · 5% overridden

Responsible1Executes the renewals & churn ops step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Renewal Operations when the unit falls outside the decision envelope or confidence drops below the floor.

Churn Signal Agent

agent

A3% autonomy · ceiling A3%

94% clean · 15% overridden

Responsible1Watches voice of customer continuously. Escalates to Head of Customer Experience when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Renewal Operations

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Director, Renewal Operations for the decisions held here.

Decision points and escalation

1 places this procedure stops

04 · Leader review

14.5 hrs

Held for a named human when the unit exceeds the renewal record decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

Director, Renewal Operations

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Renewals & Churn Ops.

The rules this procedure runs inside

2 governing rules

Renewals & Churn Ops Decision Envelope

active

RO7-POL-200 · envelope · vv3.7

Agents in this lane may act without a human when the renewal record sits inside the stated value, risk and confidence envelope.

Approved by Director, Renewal Operations · in force 2024-12-18 · reviewed 2026-04-30

Binds Renewal Calendar Agent, Auto-renewal Agent, Downgrade Processing Agent, Cancellation Agent

APAC

Renewals & Churn Ops Evidence Standard

active

RO7-POL-201 · evidence · vv3.6

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path.

Approved by Director, Renewal Operations · in force 2025-05-13 · reviewed 2026-05-01

Binds Renewal Calendar Agent, Auto-renewal Agent, Downgrade Processing Agent, Cancellation Agent

EU · UK

Systems this procedure touches

3 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Customer Relationship ManagementSalesforce Sales Cloudcrmcritical2modeled
Enterprise Data WarehouseSnowflakeanalyticscritical1modeled
Configure, Price and QuoteSalesforce CPQcrmhigh1modeled

0 of the 3 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 1 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

37.3 hrs

Summed from the time each step sits, standard 2.6 days — running at 61% of the standard.

Touchless

67%

Agent share

75%

A week

56

In flight

113

Effort a week

872 human minutes · 1,365 agent minutes

Volume multiplied by the time on each step.

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level …

GateWhat trips itWho releases itClockWaivable

Quote above $250,000

approval

Any quote exceeding $250,000 total contract valueDeal desk4 business hoursNo

Margin below floor

approval

Any configuration priced beneath the published margin floorDeal desk and Finance1 business dayNo

Territory change affecting 10+ sellers

approval

Coverage change touching more than 10 quota-carrying sellersSVP Revenue Growth Management3 business daysNo

Commission variance above 2%

escalation

Calculated payout deviating more than 2% from modeled expectationFinance controller2 business daysNo

What this document is and is not

These procedures describe the modeled estate.

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings.

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from.

Current distribution

2,748 steps

Agent, inside the function1,38951%
Agent, on the shared spine85131%
Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date.