I was working with a connector — someone whose whole value is the introductions he makes and the relationships he manages. He was running 10 meetings a day. Investor calls, partnership conversations, warm intros, coffee chats.
He had transcripts. Good note-taking setup. Granola recording everything.
But the follow-ups weren't happening.
Introductions he'd promised in Monday's call were forgotten by Wednesday. His CRM was three weeks behind. People he'd met were following up with him, and he had no idea what they'd even talked about.
The problem wasn't capacity. He was showing up to every meeting. He was having the right conversations. The problem was post-processing — extracting what mattered after the conversation ended and turning it into action.
Most people have this problem. And most people treat it as three separate problems.
The Three Sizes of the Same Problem
Here's the mental model I use now:
There are three scales of meeting:
The 1-hour call — a recorded Granola meeting with one or two people. Well-defined agenda. Clear start and end. Usually has action items, follow-ups, and things to log.
The 2-hour social event — a happy hour, networking dinner, or group gathering. Less structured. Multiple conversations. New contacts made. Phone numbers exchanged. Looser on logistics but often higher-value for relationships.
The 3-day conference — a full event. Dozens of conversations. Formal sessions mixed with hallway conversations. Biggest input volume. Hardest to process but also highest stakes for follow-through.
The instinct is to treat these as completely different challenges. The 1-hour call feels manageable. The conference feels overwhelming. So people build elaborate systems for conference follow-up and ignore daily meeting notes, or vice versa.
But they're the same job at different scales.
Every one of them has the same post-processing task: extract the people you need to follow up with, the ideas worth keeping, the tasks you committed to, and the things others promised you — before they fade.
One Workflow, Three Scales
Once you see that it's the same workflow, the solution is cleaner.
Build one post-meeting processing system. Apply it at all three scales.
The core steps are the same regardless of input size:
- Pull the transcript — the recording, the notes, whatever captured the raw conversation
- Extract people — who did you meet, what's the relevant context, what follow-up do they need
- Extract commitments — what did you say you'd do, what did they say they'd do
- Extract ideas — anything worth thinking about later, seeds of projects, things to research
- Trigger follow-ups — draft the emails, queue the CRM updates, create the tasks
At the 1-hour call level, this takes a few minutes or can be fully automated. At the conference level, it takes longer — but it's the same five steps, just more inputs.
This is what I call the Transcript First principle. The transcript is the starting artifact. Everything useful that comes from a meeting — follow-ups, contacts, content, action items — flows from that single source. If you don't have a system that starts with the transcript, you're operating with low context quality and relying on memory to fill the gaps.
What This Looks Like in Practice
For the connector I mentioned: we built one workflow. When he says “I'll introduce you to someone” in a call, the agent flags it and drafts the intro email, dropping it in his inbox for review. After every call, key details get logged to his CRM. Same workflow at every meeting.
For conference follow-up, the same structure expands. Instead of processing one transcript, you're processing the Granola recordings from the week plus any notes you captured at sessions. The agent runs the same extraction — people, commitments, ideas, follow-ups — just over a larger input.
The output is the same shape. A set of drafts to review and send. A CRM that's up to date. A task list reflecting what you actually agreed to.
The thing I've noticed: 95% of meeting recordings just sit in people's archives, unused. The transcript is there. The context is there. It just never got turned into action.
Building even one post-meeting automation — just a follow-up email draft, nothing fancy — changes this immediately.
Starting Small
The place to start is your next 1-hour call.
After it ends: paste the transcript into a prompt that extracts three things. Commitments you made. People to follow up with. Ideas worth noting. That's it.
Do that a few times manually. See what the output looks like. Then automate it — a Lindy agent, a Zapier flow, a ChatGPT custom action — and have it run every time a meeting ends.
Once the 1-hour call workflow is solid, the same structure handles the happy hour, and eventually the conference. You're not building three systems. You're scaling one.
Same workflow. Different input size.
The 4-Day AI Sprint includes a full module on building meeting automation — transcript processing, follow-up drafts, and CRM updates. If you're still manually processing your meeting notes, that's a good place to start.
