@Dash Kestrel Logistics renews in 40 days. What is the risk read?
Live in Slack or Microsoft Teams
Draft a renewal risk brief from CRM and tickets
Before a renewal conversation Dash assembles what actually predicts the outcome: usage trend, open tickets, what was promised at the last review, and who has gone quiet, with the source behind each line so the brief can be checked.
Get started for free Chat with Dash, the AI teammate that works inside Slack and Microsoft Teams.
Medium risk, and the reason is usage rather than sentiment.
- Active users last 30 days · 47 of 80 licensed · down from 68 in the spring
- Open tickets · 3 · oldest 22 days, the export issue
- Last review · 12 June · three commitments made, two delivered
- Champion · last active in the shared channel 31 days ago
The undelivered commitment from June was the reporting rollout to their finance team. It was scoped, then paused when their project owner changed in July, and nobody restarted it. Finance was 20 of the 80 licences, which is most of the drop.
The sentiment signals are all fine, which is the trap. Calls are positive, the support scores are good, and the champion is friendly. The number that predicts a renewal problem here is 47 of 80, and it has been falling for four months without anyone raising it.
Every line links to where it came from.
What would you put in front of them?
Not the usage number as an opener. The honest read is that we paused their finance rollout and did not restart it, so leading with their low adoption invites the obvious answer.
Drafted a two page brief that opens with the finance rollout, offers a date to restart it, and puts the licence conversation after that rather than before. The export ticket needs a real answer before the call or it will be the first thing raised.
Teams @Dash Kestrel Logistics renews in 40 days. What is the risk read?
Medium risk, and the reason is usage rather than sentiment.
- Active users last 30 days · 47 of 80 licensed · down from 68 in the spring
- Open tickets · 3 · oldest 22 days, the export issue
- Last review · 12 June · three commitments made, two delivered
- Champion · last active in the shared channel 31 days ago
The undelivered commitment from June was the reporting rollout to their finance team. It was scoped, then paused when their project owner changed in July, and nobody restarted it. Finance was 20 of the 80 licences, which is most of the drop.
The sentiment signals are all fine, which is the trap. Calls are positive, the support scores are good, and the champion is friendly. The number that predicts a renewal problem here is 47 of 80, and it has been falling for four months without anyone raising it.
Every line links to where it came from.
What would you put in front of them?
Not the usage number as an opener. The honest read is that we paused their finance rollout and did not restart it, so leading with their low adoption invites the obvious answer.
Drafted a two page brief that opens with the finance rollout, offers a date to restart it, and puts the licence conversation after that rather than before. The export ticket needs a real answer before the call or it will be the first thing raised.