The ratio is the model

The team total looks fine.

Then a renewal comes up. The CSM who owns it is on leave. The colleague qualified to cover it already has three renewals that week.

Finance asks for the hours behind the plan.

The spreadsheet has a ratio.

The meeting becomes a debate about whether that ratio still holds.

Customer Success Collective’s 2026 survey findings show how surveyed teams set capacity:

• 37% use account revenue.
• 37% have no formally defined model.
• 5.5% use risk or adoption signals.

A ratio is a model. It compresses a book into a number.

ARR can help define a service tier. Accounts per CSM can support a staffing budget. On their own, those measures cannot establish whether a particular person can cover a particular renewal next week.

The same book can become different work

An account moves into implementation.

Another enters its renewal window.

A third has a late project and a sponsor who has stopped responding.

The account count holds. The revenue holds. The work changes.

The CSM may need to coordinate a delivery review, rebuild the renewal plan or bring an executive into the conversation. Each creates work for a person in a period. Several can land in the same week.

The team may still have spare capacity in total. The available person may lack the account knowledge, role or time to take over safely.

A signal needs an effort assumption

The CRM may hold the renewal date. The roster may hold the owner and leave dates. The project system may hold the delayed milestone.

Having those records still leaves work for the review. Someone has to connect them and decide what they imply.

In his commentary for Customer Success Collective’s 2026 report, Raymond Otero argues for using signals such as risk, adoption and executive engagement to direct human attention where it can influence outcomes.

The qualified colleague is already carrying three renewals that week, and the account-to-CSM ratio has no way to see that.

A delayed project might call for a delivery review before renewal outreach. The company needs an assumption for the preparation, coordination and follow-up that review requires.

Those hours are an estimate. They should appear as modeled workload, with the assumption visible for someone to challenge.

The same applies to available capacity. Leave, recurring duties and existing commitments all affect how much time a person has available that week.

Make the model available to the review

The operating model for Customer Success connects those assumptions: the work an account requires, the people qualified to carry it and the capacity available when it lands.

It also records who can approve a change.

Part of that model may sit in a spreadsheet. Part may sit in a leader’s head. A staffing review depends on whether someone can explain the assumptions, inspect the evidence and revise the plan when conditions change.

The renewal still needs an owner.

The project is still late.

The qualified colleague is still carrying three other renewals that week.

An explicit model lets the review test the options:

• Move work.
• Add qualified cover.
• Revisit the commitment.

Each option has consequences for another account, another person or another date.

The person with authority makes the call.

The next review needs to see what was decided and whether the assumptions still hold. A deal closes. A project slips. Someone extends their leave. The plan needs to reflect that change.

Who covers this renewal, in this week, and what else must change?

OpX is the decision runtime for customer operations, starting in Customer Success. It connects renewals, account coverage and team capacity so people can inspect the constraint behind the team total.

Sources

• The real reason your customer success coverage model isn’t working, Grace Gupta, Customer Success Collective, August 5, 2026. Includes the 2026 survey figures and Raymond Otero’s commentary.
• State of Customer Success Report, 2026 edition, Customer Success Collective.