The account goes quiet long before the renewal does.

Why do renewals keep surprising us?

The renewal goes quiet and nobody notices until it is gone. Not because your team was not paying attention — because the early signs lived in four different tools, none of which was the CRM where the renewal date sat.

The support queue knew in March. The calendar knew in April, when the monthly check-in silently became quarterly. By the time the health field turned yellow, the champion had stopped replying, and the save that would have been a conversation in Q2 is an escalation in Q4. A book run this way does not fail loudly; it leaks — one quiet account at a time.

What does my team actually work from?

Three surfaces, all built from evidence your tools already produce — nobody fills in a health colour, and nobody maintains the renewal spreadsheet by hand.

• A health queue, ordered by evidence

  Your accounts, ranked by what changed — not an alphabetical book you re-scan every Monday. The account whose meetings stopped and whose support tickets doubled rises to the top before anyone has typed a health colour into a field.

• Risk cases that carry their signals

  When an account turns risky, the case shows the support and delivery signals behind it — the escalation, the breached response time, the thread that went quiet — so the conversation starts from what happened rather than from a hunch.

• A renewal book that adds up

  Renewal deals in one place with the renewal value due totalled above them, each row carrying its date and its value, so "what is actually at stake this quarter" stops being a spreadsheet someone maintains by hand.

Alongside them sits a response-time watch: where you make service commitments to customers, breaches and near-breaches surface on the account before the customer raises them. The week starts from one queue with reasons attached, not from re-reading a book of accounts hoping the risky one stands out.

What is 'renewal value due', and why not just say ARR?

Because a deal value is not proof of recurring revenue, and a customer success leader gets asked to defend this number. When you tag renewals or connect a subscription source, the renewal book fills with your actual book of business; what it totals is presented as renewal value due — the value of the renewal deals on record, with each row keeping its date and value.

SalesSynq will not relabel that number ARR to make a dashboard look more finished. If a connected subscription source proves the recurring basis, the label can earn its way in. Until then, the honest name is the one on screen — which means that when you quote it in a QBR, it holds.

What will it refuse to do?

Four refusals, all deliberate. They are the reason the numbers this page describes are worth quoting.

• It will not call your renewal total ARR. Until a connected subscription source proves that basis, the number is presented as what it is: the value of the renewal deals on record.
• It will not invent account health. A view that nothing feeds yet says which source to connect or which deals to tag as renewals — instead of showing a number that came from nowhere.
• It will not score your CSMs. SalesSynq scores accounts, deals and teams; there is no individual scorecard to switch on, for you or for anyone above you.
• It will not act on your tools by itself. Sending a task into your helpdesk or anywhere else is a permission you grant per tool, and an action a person takes.