Win-loss insight capture

Turn every closed deal, won or lost, into a written reason with the evidence attached, so the pattern is visible instead of guessed at.

No ready-made setup for this job yet.

Describe the job in a sentence, the way you would brief a colleague: when it should happen, what to check, and what to hand you. That sentence is the automation.

The job, and what good looks like.

Two deals are lost for the same reason in the same quarter and nobody connects them, because the loss reason sits in a free-text field or was never entered at all. This workflow makes the record part of closing a deal. When an opportunity is marked closed won or closed lost, it asks for one reason chosen from a list that reflects how deals actually end, plus one sentence of context. The relevant calls and notes are attached, so a claim about why a deal was lost can be checked against what was said instead of taken on trust. The same questions are asked of won deals, because a pattern only counts when both sides land on the same fields. Entries are grouped by segment, competitor, and product area over a rolling window, and anything appearing three times is written up for the team instead of being left as a filter somebody could run. A reason that cannot be evidenced is marked as the rep's read of it, keeping the difference visible. A human still judges which explanation is the real one, and decides what to change about the product, the price, or the pitch.

When it is handled

  • Every closed deal has a written reason
  • Reasons come with the call evidence
  • Patterns reported by segment, not anecdote
  • One library a rep can actually search

Works with tools like

  • Gong
  • Salesforce
  • Clari
  • Loopio

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.

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.