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.
No ready-made setup for this job yet.
Describe the job in a sentence, the way you would brief a colleague: when it should happen, what to check, and what to hand you. That sentence is the automation.
The job, and what good looks like.
An account doubles its seats over a quarter and sales finds out from the customer's support team, because the signal sits in product analytics while the account plan stays unchanged. This workflow keeps a watch list and checks it on a schedule. It compares usage against the level the account was bought at, new teams appearing in the product, hiring signals, invoices that stopped being routine, and support tickets that concentrate on one problem. Each crossing is written as a dated trigger with the number behind it, so the account owner can see the change rather than take an opinion. Triggers are grouped by account rather than fired one at a time, which stops a fast-growing account generating six separate alerts. An account already covered by an active expansion conversation is marked covered instead of being handed to a second rep. A human still decides whether the change is worth a real conversation, what to propose, and whether the timing suits the renewal sitting underneath it. The workflow spots the moment; it does not judge whether the moment is good.
When it is handled
- Every expansion trigger has an owner
- No growth signal noticed after the fact
- Conversation opened before the customer asks
- Account plan updated with the change
Works with tools like
- Stripe
- Shopify
- Zendesk
- Salesforce
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.
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.
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.
1 automation
Win-loss insight capture
Turn every closed deal, won or lost, into a written reason with the evidence attached, so the pattern is visible instead of guessed at.
Write your own
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.