Discovery recap and CRM updates

Sales / AUTOMATE.md

After each discovery call, draft a recap with the pain, the impact, the people involved and the next steps, list the CRM updates it suggests, and send both to me to approve.

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

  • Recaps written while the call is fresh
  • CRM updated only after you approve

How it runs

  1. 1. Starts

    After each discovery call

  2. 2. Reads

    discovery call

  3. 3. Delivers to

    DocumentsEmail

  4. 4. You decide

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

Why sales teams set this up

The notes from a discovery call live in the rep's own document, so a manager reviewing the deal sees an empty field and a handoff to another rep starts with a phone call. What gets lost is the written recap carrying the next step, and the person who chases it is the manager, usually a week later, in a pipeline review. Decisions taken on the call then get re-litigated on the next call, because nobody wrote down what was actually agreed.

See the whole job: Opportunity recap notes

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.

Discovery recap and CRM updates

Approve before it saves the document and sends the email?

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.

Decision log draft

When a transcript is linked to a deal, pull the decisions, open questions, and commitments into a decision log row.

When a transcript is linked to an opportunity

Decision log from notes

When a call summary is added to a deal, pull out the decisions and the open questions, and post a short log for me to check.

When a call summary is added

Gong recap draft

After each recorded call in Gong, draft a recap with the decisions and the next steps, and post it for me to approve.

After each Gong call ends

Next-step missing digest

Every Friday at 9am, list the open deals with no next step, and email me the list with a question about each.

Every Friday at 9am

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

Deal risk alerts

Flag a deal the moment it goes quiet, loses a stakeholder, or slips its date, while a rep can still act on it.

5 automations

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