Fathom

Fathom is an AI meeting assistant that records, transcribes, and summarises video calls on Zoom, Google Meet, and Microsoft Teams, and extracts action items automatically. It offers an unlimited free tier and paid plans aimed at individuals, sales, and customer-success teams, with CRM syncing and coaching features on higher tiers. It is suited to lean B2B teams that want hands-free meeting notes without manual write-ups.

Fathom is an AI meeting assistant that joins your video calls (Zoom, Google Meet, Microsoft Teams), records and transcribes them, and writes up a structured summary with action items afterwards. It captures the conversation so you can stay present instead of scribbling notes, then hands you a searchable transcript, highlights you can clip, and a recap you can share or push into your CRM.

Where it fits

Fathom earns its place if you live in back-to-back calls and want the notes to write themselves. It suits founders, sales and customer-success teams, consultants, and anyone who runs discovery or client calls and needs a reliable record plus a clean follow-up summary. The CRM sync makes it especially comfortable for sales-led teams who want call notes landing against the right contact without manual copy-paste.

It is less of a fit if your meetings are mostly internal and informal, where a bot joining every call feels like overkill, or if you are bound by strict policies on recording and third-party processing of conversations (always check the consent and compliance angle before you let a bot into client calls). It is also not a project-management or knowledge-base tool: it captures the meeting well, but the thinking about what to do with it still lives elsewhere.

The honest take

The real strength is that it gets out of your way. Setup is quick, the bot joins reliably, and the summaries are genuinely usable rather than a wall of raw transcript, which is where a lot of meeting tools fall down. Fathom is widely known for having a generous free tier, so you can run it on your own calls and judge the output before paying anything, and the paid plans add the team and CRM features. That low-friction "try it on a real call today" path is rare and worth a lot.

The trade-offs are the ones every recording assistant shares. Summary quality depends on audio clarity and how structured the conversation was: a rambling call produces a rambling recap, and you will still want to skim before trusting the action items. A visible bot in the call changes the room slightly, and not everyone is comfortable being recorded, so the consent conversation is on you. And like any tool in this category, you are putting your conversations through a third party, so the data-handling question matters more here than for most software.

INTERVIEW EWOUD: What is your personal verdict on Fathom, and your star rating out of five?

INTERVIEW EWOUD: Is Fathom in your own stack right now, and if so what do you actually use it for (and if not, what do you use instead and why)?

INTERVIEW EWOUD: What is the one line you would tell a peer who is deciding whether to try it?

Fathom records your meetings, transcribes them, and hands you a clean summary with the action items already pulled out, so you walk away from a call with notes instead of a vague memory of what was agreed. It is built for people who live in back-to-back meetings and want the recall without the busywork: founders, salespeople, consultants, and anyone running customer or client calls who would rather pay attention to the person than to their own scribbling. If you have ever ended a call and realised you wrote down nothing useful, this is the tool that fixes that.

Getting set up

You connect Fathom to your calendar and your meeting platform, and from that point it just shows up. When a meeting starts it joins as a notetaker, or it captures the call in the background depending on how you run it, and afterwards the recording, transcript, and summary land in your Fathom library ready to read or share. The first decision worth making deliberately is which meetings it touches: you can let it record everything on your calendar, or limit it to external calls, or trigger it manually per meeting. I would start narrow and widen once you trust it, because recording is a relationship decision as much as a software one.

The second thing to get right early is consent. Fathom will announce itself and there are settings that govern how it behaves when it joins, but you are still the one responsible for telling people they are being recorded. Decide your default, say it out loud at the top of external calls, and make it boring. Once your team is on it, you also want to agree where summaries are allowed to flow, because the whole point of the tool is that notes become easy to share, and easy-to-share is exactly when something private ends up in the wrong channel.

How to actually use it

The shift Fathom asks of you is small but real: stop taking notes during the call. That is the entire value, and people undercut it by half-trusting the tool and scribbling anyway. Let it run, stay present, and treat the call as a conversation rather than a transcription exercise. If something genuinely matters in the moment, mark it live so you can find it later, but otherwise let your hands stay off the keyboard.

After the call, your workflow lives in the summary, not the full recording. Open the summary, skim the action items, and confirm the ones that are yours actually belong to you and the wording is right, because an automated summary is a strong first draft and not gospel. The transcript is searchable, so when you half-remember that a client mentioned a budget number or a deadline, you search the words rather than scrubbing through audio. That search is where a lot of the time saving really lands. The clip and timestamp features are the other half: instead of forwarding a forty-minute recording, you grab the ninety seconds that matter and send that.

Power moves

The highest-leverage habit is sharing clips instead of whole meetings. When a prospect explains their problem in their own words, that clip is worth more to your team than any summary you could write, and it carries the authenticity a paraphrase loses. Build the reflex of clipping the moment something important is said, because you will never go back through the recording to find it later.

The second move is feeding the summaries into wherever your work actually lives. Action items are only useful if they leave Fathom and turn into tasks, and a CRM note attached to the right deal is worth more than a summary sitting in a meeting library nobody reopens. Wire that flow once and the tool stops being a recorder and becomes part of your operating system. If you run a lot of similar calls, pay attention to how the summary is structured and lean on whatever templating or custom-summary control is available, so a sales call and an internal sync produce notes shaped for their job rather than one generic block.

Where it fits your stack

Fathom is the capture layer that sits in front of everything else. The meeting happens, Fathom turns it into structured text, and that text should flow outward: into your CRM against the relevant contact or deal, into your task system as action items, and into your knowledge base or shared docs when a call produced something the whole team needs. It pairs naturally with a CRM for sales work and with a task manager for delivery work, and it removes the manual "write up the call" step that usually sits between a meeting and the system that should have captured it.

If you already run another notetaker, do not stack two of them on the same calls. Two bots in one meeting is awkward for the people on the other side and confusing for you afterwards, so pick one capture tool and let everything else consume what it produces.

Pitfalls to avoid

The biggest mistake is treating the summary as final. It is a fast, good first draft, and on anything that carries a commitment or a number you should read the relevant part of the transcript before you act on it. The second mistake is letting it record everything without thought, which buries the meetings that matter under a pile of internal calls you will never reopen and quietly raises your privacy exposure. Be deliberate about scope.

The third pitfall is the consent gap: relying on the bot to announce itself and skipping the human courtesy of saying so. That erodes trust fast, and trust is the thing you are on the call to build. The last one is hoarding: recordings and summaries pile up, and a library nobody curates becomes noise. Decide what gets kept, what gets pushed into your real systems, and what can simply expire, so the tool stays an asset rather than another inbox.

INTERVIEW EWOUD: Which meetings do you let Fathom record (everything, external only, or manual per call), and what is your actual consent line at the top of a client call?

INTERVIEW EWOUD: Where do Fathom summaries and action items flow afterwards in your stack (CRM, task system, Notion), and is any of that wired to happen automatically?

INTERVIEW EWOUD: What is your one real-world tip for getting value out of it, for example how you use clips with prospects or how you search transcripts during follow-up?

Solo founders and small B2B sales or customer-success teams who want automatic meeting notes and action items without manual note-taking.