Competitor monitoring
Watches a short list of competitor pricing pages, release notes, and ad libraries and reports what moved with the source, so nobody discovers a price cut from a customer.
Each weekday at 8:30am, check the tracked competitor pages for pricing or launch changes and post what moved, with the page it came from.
The job, and what good looks like.
Most teams keep a competitor list in a spreadsheet nobody opens, so a rival's price cut or a product launch is discovered when a customer mentions it. This workflow takes the tracked list and checks the parts that move first: pricing and plan pages, release notes and changelogs, the app store listing, and the pages their campaigns point at. It keeps the previous capture, so a change is shown as what it was and what it is now, with the date and the link. Moves that match something the team already cares about, such as a pricing change or a free trial, are raised the same day; the rest land in a weekly round-up short enough to read on a Monday. A note also flags where the team's own pages repeat what the rival now says, because that comparison is the reason for watching at all. What a human still decides is whether a move matters enough to answer, what the answer is, and whether the pricing page has to move with it; the workflow reports the change and never prices anything itself.
When it is handled
- Competitor moves seen the day they happen
- Every change keeps its source link
- No quote built on a stale price
- Sales hears it before a customer does
Works with tools like
- Brandwatch
- Semrush
- Ahrefs
- Slack
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 drafts and checks. You decide what goes out.
- Nothing published without you
Drafts wait for your review, in your voice and within your claim rules.
- Undo what you don't want
Every step is recorded, and a file it changed can be put back.
- Only the channels you connect
Each automation reaches only the apps and folders you give it.
Competitor Launch Alert
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 marketing platform's workflows
Sending sequences and scoring contacts inside one tool.
They stop at that tool's edge, and can't draft from a brief or explain a drop in results.
Flowchart automation tools
Moving data between apps at high volume.
Every exception becomes another branch someone has to build and maintain.
AI chat and writing assistants
Drafting copy when you ask.
Nothing happens until you ask again, and your brief, voice and checks live 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.
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.