Renewal exposure
$480K ARR
Renewal due on day 43.
Renewal Recovery / The first application
Connect revenue at risk with delivery readiness, team capacity, role fit, and decision authority. Review a feasible response before committing your team.
$480K ARR
Renewal due on day 43.
7 days late
Go-live forecast: day 50. The operating model requires go-live before renewal.
80%
96 hours of work ÷ 120 hours of effective capacity.
Account demand and effective supply use explicit assumptions. A roster count alone misses the effect of ramp.
Review an owner with available capacity and resolve the delivery gap before renewal. Available capacity alone does not make the renewal safe.
OpX frames the decision. Your team approves the response; people and existing workflows own execution.
Keep decisions current
An owner’s assigned book falls from eleven enterprise accounts to eight. Under the same model, workload falls from 110% to 80%.
The capacity-only case for reassignment no longer holds. The delivery risk still needs a plan. Retaining the earlier assessment makes the change explainable.
11 × 12 hours ÷ 120 effective hours
Review capacity-driven reassignment8 × 12 hours ÷ 120 effective hours
Withdraw the capacity-only recommendationBoth assessments stay in the history.
A scoped first engagement
Agree what a useful decision looks like before introducing more applications or broader automation.
Choose the renewal population, sponsor, review window and approval owner.
Reconcile authorized records and reviewed model assumptions. Identify missing or unsupported inputs.
Review recommendations with the operator. Measure effort, acceptance and outcomes against agreed criteria.
Before we start
COOs, Chief Customer Officers and Customer Success leaders who need to protect renewals while deciding where scarce delivery and executive capacity will have the most impact.
No. Those systems retain their source records. OpX connects their evidence with workforce context and explicit operating rules to support a decision across them.
A bounded package of authorized renewal, delivery, and workforce records, plus the capacity assumptions and approval rules reviewed with your team. Current intake uses authenticated file transfer.
Read about data handling →A recommendation is not permission to execute. Your team reviews the evidence and approval requirements. People and configured workflows own execution; OpX does not dispatch work to AI agents today.
No. The Acme case uses illustrative data and explicit model assumptions. A first engagement must validate source quality, operator usefulness and measurable outcomes on authorized customer data.
Start with one decision
One renewal. One authorized source package. One reviewable decision.