Missing stakeholder ping
When a deal moves to the Pipeline stage with no technical contact on it, post the owner a short note naming the gap and who could make the introduction.
This is the whole automation. Run it as it is, or change any word, including the tools it names.
- Gaps in the buying group found early
- A named person to ask
How it runs
1. Starts
When a deal moves to the Pipeline stage2. Reads
Pipeline stage3. Delivers to
Slack4. You decide
Approve each time, or let the steps you trust run. Your choice.
Why sales teams set this up
A deal sits at the same stage for five weeks because one stakeholder stopped replying, and nobody raises it until the forecast call. What is missing is a current picture of who is engaged and when the deal last actually moved. The manager is the one who finds out, from a close date that has quietly moved to next quarter, and by then the rep has no story for why, so the risk gets reported in the review instead of fixed before it.
See the whole job: Deal risk alertsUse it as is. Or make it yours.
Edit it the way you would edit a note to a colleague. It follows the new version from the next run.
Change when it runs
Move it to another day or time, or start it when something arrives, like a new email.
Add your own rules
Limits, exceptions and what good looks like go in the same file, in plain words.
Decide what waits for you
Mark the steps that need your OK, and let the rest run.
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.
Missing stakeholder ping
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.
Other setups for the same job.
Close-date slip alert
When a deal's close date moves out, draft a short risk note with what changed and two suggested actions, and post it to the deal owner.
When a close date is moved
HubSpot risk ping
Every Friday at 9am, find the deals in HubSpot with no activity for ten days or more, and post each owner a short risk note with one suggested next step.
Every Friday at 9am
No-activity alert
Every weekday at 8am, list the open deals with no activity for ten days or more, and email me one suggested next step for each.
Every weekday at 8am
Stage regression watch
When an opportunity slides backwards, post the rep the previous stage, the date it moved, and a suggested reason to record.
When an opportunity moves back a stage in Salesforce
Related workflows
Pipeline follow-up tracker
Notice when a deal's next step has stalled and hand the rep one specific action, not another report on how the quarter is going.
1 automation
Opportunity recap notes
Write the deal record back from the call itself: the pain, the people, the decisions, and the next step with an owner and a date.
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.