Meeting notes
Turns a recorded call into a written record with the decisions, the open questions, and the owners.
Finished transcript, write a notes page with the summary, the decisions, and the follow-ups, then post the page link for the owner to check.
The job, and what good looks like.
A meeting is agreed, everyone leaves, and the write-up is evening work that usually does not happen. The recording is the only record left, and it is the worst kind: forty minutes to find one sentence. It runs while the details are still recoverable. The transcript becomes three short blocks within the hour. Decisions are separated from discussion, and each decision says what was agreed, who agreed to it, and what would make it change. Open questions are listed with the person who has to answer them, because those are the sentences people search for a month later. Actions are pulled out into a list with one owner and one date each, and posted in the meeting's channel so nobody goes looking for the recording. The notes page is filed under the project rather than the calendar invite, and the same headings are used every week. Anything the transcript is unsure about is marked uncertain instead of smoothed over. A person still decides whether a discussion counted as a decision, checks the summary before it is treated as the record, and owns the wording sent to people who were not in the room.
When it is handled
- Notes posted within an hour of the call
- Decisions separated from discussion
- Every action has a named owner
- Recordings searchable by topic
Works with tools like
- Otter.ai
- Fathom
- Notion
- Slack
- Google Calendar
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.
Notes Summary To Slack
Meeting finished, take the summary and actions from the transcript and post them in the meeting channel.
5 minutes after every meeting ends
Transcript To Notes Page
Finished transcript, write a notes page with the summary, the decisions, and the follow-ups, then post the page link for the owner to check.
When a transcript finishes processing
You stay in charge.
At every step.
It sorts and reminds. You decide what to do.
- It never replies for you
Digests and reminders come to you. Anything that would send a message waits for your OK.
- Undo what you don't want
Every step is recorded, and a file it changed can be put back.
- Only what you connect
Each automation reaches only the inbox, calendar and notes you give it.
Transcript To Notes Page
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.
Built-in rules in your email and calendar
Filing messages by sender or subject.
They can't read what a message asks for, or follow up on it.
Flowchart automation tools
Connecting apps if you build and maintain the flow.
Every exception becomes another branch.
AI chat assistants
Summarizing when you ask.
Nothing happens until you remember to ask.
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.