Stop Letting Meeting Notes Disappear Into Slack

Last week, I sat through a 45-minute product meeting. Three action items came up. One person was supposed to send a design mockup. Another needed to check with legal. I was supposed to draft an SOP for onboarding.

By the next day, I'd forgotten what I committed to. The design person never sent the mockup. We had the same conversation again two weeks later.

Then I discovered this: Fathom automatically records and transcribes your meetings. Claude reads the transcript, extracts action items, and turns them into follow-ups and step-by-step processes. No manual transcription. No hunting through Slack threads. No repeating yourself.

Here's what I built in 20 minutes: A system that turns every meeting into a document with clear owners, deadlines, and next steps. I went from "did anyone actually write down what we said?" to "here's who's doing what by when."

How This Actually Works (The Simple Version)

You don't need to understand how AI works to use this. Here's the flow:

  1. Install Fathom in your calendar (takes 2 minutes)
  2. Join a meeting — Fathom records and transcribes automatically
  3. After the meeting, copy the transcript
  4. Paste it into Claude and ask it to extract action items, owners, and deadlines
  5. Use Claude to turn the raw notes into an SOP or follow-up document
  6. Share with your team

That's it. The magic is in step 4 and 5 — Claude reads thousands of words in seconds and pulls out what matters.

Step 1: Set Up Fathom (Literally Just Connect It)

Go to fathom.video, sign up with your Google or Microsoft account, and authorize it to access your calendar.

You'll see a prompt to add Fathom to your meeting. Click it. Now Fathom will automatically join your next meeting and start recording.

Pro tip: Fathom works with Zoom, Google Meet, and Teams. It sits quietly in the background — your team won't even know it's recording.

You can also manually start a recording by opening Fathom and clicking Record Meeting. I do this for 1-on-1s that pop up unexpectedly.

Step 2: Let the Meeting Happen (Seriously, Just Talk)

This is the easiest part. Fathom is recording. You don't have to do anything differently.

I used to assign one person to take notes. Now nobody has to. We all just talk, and Fathom captures everything.

After the meeting ends, Fathom automatically transcribes it. This takes 5-10 minutes for a 45-minute meeting.

Step 3: Extract Action Items (This Is Where Claude Shines)

Once your transcript is ready, open it in Fathom and copy the full text. Then go to claude.ai and start a new conversation.

Paste the transcript and ask Claude to do the work:

"Extract all action items from this meeting transcript. For each one, list: (1) What needs to be done, (2) Who's responsible, (3) When it's due, (4) Any dependencies or blockers."

Claude will read the entire transcript in 3 seconds and give you a clean list. Here's what came back from one of my meetings:

Action Item 1: Design product mockup for new dashboard
Owner: Sarah
Due: Friday, Jan 19
Blocker: Waiting on brand guidelines from Marketing

Action Item 2: Check legal requirements for data retention
Owner: Marcus
Due: Wednesday, Jan 17
Blocker: None

No back-and-forth. No "wait, who was supposed to do that?" Claude pulled it straight from the conversation.

Step 4: Turn Action Items Into Follow-Up Emails

Now ask Claude to write a follow-up email. Paste those action items back and say:

"Write a short follow-up email to the team summarizing this meeting. Include the action items with owners and deadlines. Keep it to 1 paragraph — be direct."

Claude writes something like this in 10 seconds:

Hi team, thanks for the productive meeting. Here's what we're moving forward with: Sarah will have the product mockup ready by Friday (pending brand guidelines from Marketing), and Marcus is checking legal requirements by Wednesday. I'll follow up next week with next steps. Let me know if you hit any blockers.

Copy that. Send it. Everyone knows what they're doing.

Step 5: Build an SOP From Your Meeting (The Real Time-Saver)

Here's where this gets powerful. If your meeting was about HOW to do something — not just WHAT to do — Claude can turn it into a step-by-step process.

I had a meeting about our customer onboarding process. Instead of someone writing it from memory, I asked Claude:

"Based on this transcript, create a step-by-step SOP for customer onboarding. Format it as a numbered list. Include any tools mentioned and any approval steps."

Claude gave me this in 20 seconds:

Customer Onboarding SOP

1. Send welcome email with login credentials and product tour video (done by Sales, within 24 hours)
2. Schedule kickoff call with customer (30 min, within 48 hours)
3. Complete product setup in Salesforce (Owner: Success team)
4. Send resource library and documentation (Owner: Success)
5. Schedule 30-day check-in call (Owner: Success)
6. Gather feedback survey (Owner: Success, send after 30 days)
7. Escalate to account management if NPS < 7

I had scattered notes from the meeting. Claude turned them into a usable, step-by-step process in seconds. One team member actually used this the next day to onboard a customer without asking any questions.

Step 6: Share and Assign (Make It Real)

Copy Claude's output. Paste it into a Slack channel, Google Doc, or your project management tool.

Tag the people responsible. "Sarah — see your action item below. Due Friday." This makes it impossible to forget.

I started adding one line at the top of every follow-up: "Last updated: [date]. If anything changes, reply here." This creates accountability and a paper trail.

One More Thing: Ask Claude to Find Risks

Before you send the follow-up, ask Claude one more question:

"Based on this transcript, what could go wrong? What risks or dependencies should we watch for?"

This catches things you missed. In one meeting about a product launch, Claude flagged that we were waiting on a vendor who had been slow before. We proactively reached out and avoided a 2-week delay.

The Honest Limitations

Claude is incredible, but it's not perfect.

Sometimes Claude misses context. If someone says "we talked about this last week," Claude doesn't know what "this" is. You need to add that context: "In our previous meeting, we decided to pause the redesign. Here's today's transcript..."

It can't read tone. If someone says "yeah, we'll try that" sarcastically, Claude might mark it as a commitment. Always scan the output and use your judgment.

Fathom isn't perfect at transcription. If someone has an accent or speaks quickly, you might get a few words wrong. I've seen "quarterly review" transcribed as "quarterly reviews" which changed the meaning. Skim the transcript before sending it to Claude.

This doesn't replace good facilitation. If your meetings are rambling and unfocused, even Claude can't save you. But if you're running decent meetings, this is a game-changer.

What Changed For Me

Before this system, I'd spend 30 minutes after every meeting writing up notes, assigning tasks, and sending a follow-up email. I'd still miss things.

Now? I spend 5 minutes copying the transcript and pasting it into Claude. Claude does the heavy lifting. I spend another 5 minutes reviewing what it pulled and sending it out.

That's a 20-minute time save per meeting. If you have 4 meetings a week with action items, that's 80 minutes of your time back.

But the real win is consistency. Every meeting now has documented action items, owners, and deadlines. No more "I thought you were doing that." No more repeating conversations.

What to Try First

Do this in the next 10 minutes:

Join your next meeting with Fathom running. Doesn't matter if it's important. Even a casual standup works. Let it record and transcribe.

When the transcript is ready, copy the whole thing. Go to Claude and paste it with this exact prompt:

"Extract action items from this meeting. For each one, list: (1) What, (2) Who's responsible, (3) When due."

See what Claude pulls out. Compare it to what you remember. You'll be surprised how much it catches.

That's your baseline. From there, you can add follow-up emails, SOPs, and risk analysis. But start with action items. That alone will change how your team operates.

Your next meeting is coming. Use it as your test.

Now go build something. — Jake Copilot