Account research briefs

Keep a one-page brief per target account: the people who matter, what changed there recently, and the reason to reach out this week.

Sales / AUTOMATE.md

After each call with a target account, draft a recap with the takeaways and next steps, add anything new to the account brief, and post both for me to check.

Ready-made: Account call recap

The job, and what good looks like.

The first email to a target account goes out from whatever the CRM happened to record, and the reply three days later says the person left in March. This workflow keeps a one-page brief per target account and refreshes it on a schedule. It pulls company facts and people from the sources the team already pays for, then checks each one against the date the record last changed. Funding, a new leader, a product launch, a job posting that names a problem you solve: each is captured as a dated line rather than a memory. The brief states who runs the account, what moved in the last thirty days, and the single strongest reason to reach out now. Records that contradict each other are listed for a person to settle rather than smoothed over into something plausible. A rep still decides who to contact first, what to lead with, and whether a trigger is worth breaking the pattern for. The brief supplies the reason; the send is still their call.

When it is handled

  • No first touch without a current brief
  • Each brief names one reason to call
  • Stale titles caught before the send
  • One page, not a research tab

Works with tools like

  • ZoomInfo
  • Clay
  • LinkedIn Sales Navigator
  • 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.

Account call recap

Approve before it saves the document and posts in Slack?

ReviewApprove

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.

Start with one job.
Make it your own.

macOS — coming soon
  1. 1

    Get the app

    It runs on your computer, next to your files.

  2. 2

    Add the automation

    Paste the instructions into the app, or save them as a file next to your work.

  3. 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.