Renewal risk pulse
Watch usage, support load, and champion movement on every account in its renewal window, so the save starts months before the decision.
When a renewal account opens a priority ticket, post the account owner, the ticket summary, and the days left on the contract.
The job, and what good looks like.
A renewal is decided before the renewal conversation begins, because usage fell in the second quarter and the champion left in the first, and neither appeared on anybody's list. This workflow keeps a health read on every account inside its renewal window. It tracks usage against the level the account was bought at, the volume and severity of support tickets, invoices left unpaid, and accounts whose own research activity has dropped or shifted toward a competitor's category. A change in the contacts on the account counts as a signal in its own right, because a departed champion leaves nobody to champion anything. Each account gets a short note naming what changed, when it changed, and the days left on the contract, so the owner has a reason to act rather than a status. Signals that resolve themselves are marked and dropped, keeping the save list to the accounts that need a person this month. A human still decides what the account is worth keeping, whether the issue is commercial or technical, and what to offer.
When it is handled
- Every renewal has a current health read
- Champion changes noticed the same week
- Saves started before the renewal call
- No discount offered for lost trust
Works with tools like
- Zendesk
- Stripe
- Salesforce
- 6sense
Ready-made automations. Pick the one that fits.
Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.
You stay in charge.
At every step.
It does the legwork. You decide what reaches a customer.
- Nothing reaches a customer unasked
Replies and follow-ups wait in your drafts until you send them, or until you pre-approve them.
- Undo what you don't want
Every step is recorded, and a file it changed can be put back.
- Only the CRM and inbox you allow
Each automation reaches only the apps and folders you connect for it.
Support escalation flag
Approve before it posts in Slack?
Before you download.
- Where does it run?
- On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
- How does it connect to our CRM and other tools?
- Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
- Does it run when my computer is asleep?
- It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
- How does my team use it?
- Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
- Do I need anyone technical to set it up?
- No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.
Already have tools for this? Here is the difference.
Your CRM's workflow rules
Updating fields and assigning records the same way every time.
They can't read a call, research a company or write a follow-up that sounds like you.
Flowchart automation tools
Moving data between apps at high volume.
Every exception becomes another branch someone has to build and maintain.
AI chat assistants
Drafting a reply when you ask for one.
Nothing happens until you come back and ask again, and the routine lives in a chat.
AUTOMATE.md
Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.
Related workflows.
Expansion trigger finder
Name the accounts where usage, headcount, or a new project points at more business, and route one to the account owner with a reason attached.
Write your own
Deal risk alerts
Flag a deal the moment it goes quiet, loses a stakeholder, or slips its date, while a rep can still act on it.
5 automations
Start with one job.
Make it your own.
macOS — coming soon- 1
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 3
Try it, then turn it on
Run it once and check the result. It only runs on its own once you switch it on.