First-touch list draft

Sales / AUTOMATE.md

When a lead enters first touch, post the first message draft with the contact's role and the one company fact behind it.

This is the whole automation. Run it as it is, or change any word, including the tools it names.

  • Faster first touches
  • Research done before the send

How it runs

  1. 1. Starts

    When a lead reaches the first-touch stage in HubSpot

  2. 2. Delivers to

    SlackDocuments

  3. 3. You decide

    Approve each time, or let the steps you trust run. Your choice.

Why sales teams set this up

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. Nobody keeps an account brief, so the person who ends up building one at eight in the morning is the rep, working from a social profile, the company news page, and a colleague's memory. A first touch built on a stale title costs the whole cadence, not just the first email.

See the whole job: Account research briefs

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

First-touch list draft

Approve before it posts in Slack and saves the document?

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.

Other setups for the same job.

Account call recap

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.

After each call with a target account

Account record refresh

Every Monday at 6:30am, refresh the target accounts that changed size or ownership, and post a short list of what moved.

Every Monday at 6:30am

First-touch account brief

When a new target account is added to the CRM, research the company, draft a one-page account brief with its fit, recent news and a first message, and send it to me to review.

When a new target account is added

Pre-meeting account snapshot

One hour before a first meeting, read the account's history and recent news, list the key people and two angles worth raising, and post the snapshot to me.

1 hour before a first meeting

Weekly trigger scan

Every Monday at 9am, check each target account for news of funding, hiring or leadership changes, and email me a short digest with a reason to reach out to each.

Every Monday at 9am

Zoho CRM daily brief

Every weekday at 8am, list the leads in Zoho CRM that have gone cold, add a one-line summary and a suggested next step to each, and email me the list.

Every weekday at 8am

Related workflows

Discovery prep pack

Arrive at a discovery call with the stakeholders mapped, the questions already answered, and the gaps worth spending the limited time on.

1 automation

Fit scoring assistant

Score every account against the same written firmographic and intent criteria, so two reps reach the same answer about whether it is worth working.

Write your own

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.

macOS — coming soon