- Industry
- IT Company
- Department
- Sales
- Team
- Deal Conversion
- Kind
- Investigator
- Approver
- Account Manager
- Code
- SAL-14
It flags upcoming renewals of SaaS subscriptions and managed-service contracts and explains why a renewal is at risk: falling usage or seats, SLA breaches and P1 incidents, an unhappy sponsor, a champion who left or a competitor in the account. It records the risk and a renewal offer on the opportunity for the account manager. **The problem it solves:** Why a renewal is at risk: which signals, since when and how strong, and whether usage, service quality, sponsor change, complaints, competition or budget explains it.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the subscription billing system: subscriptions, seats, usage trend and renewal dates, with SLA breaches and P1 incidents from the ticketing and service management system..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Account Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CRM: it creates or updates the renewal opportunity with the risk, causes and proposed offer. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The renewal playbook: renewal windows, health signals and their weights, service-credit history, the save offers allowed and the renewal pricing rules.
Reads from
the subscription billing system: subscriptions, seats, usage trend and renewal dates, with SLA breaches and P1 incidents from the ticketing and service management system.
Acts in
the CRM: it creates or updates the renewal opportunity with the risk, causes and proposed offer.
Hands back
A list with one entry per account, each with name, renewal_date, arr_usd, risk (low, medium or high), causes (a ranked list with cause, evidence and confidence), offer (a short description, or null) and next_steps.
Asks a person when
A save offer exceeds 10 percent, or an at-risk renewal is above the account's tier threshold.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Look ahead (days) | 120 | Renewals within this many days are reviewed. |
| Usage drop that signals risk (%) | 20 | A drop this large over the last quarter is a risk signal. |
| Largest save discount (%) | 10 | Save offers above this need the approver. |
| SLA breaches that signal risk | 2 | This many breaches in the last six months is a risk signal. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Review every renewal within 120 days.
- Weigh the competing causes of risk: usage down 20 percent or more, 2 or more SLA breaches or P1 incidents, a sponsor change, an unresolved complaint, a competitor, or budget cuts; say what would confirm each.
- Fix the service cause first; a save discount above 10 percent needs the Account Manager.
- Service credits owed are settled before the renewal offer.
- Never contact the client; the account manager owns the conversation.
See the Renewal Sales Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.