The short answer
- Moving from Fathom Team to whisper.cpp at 1 seat costs $122 more in the first year, after setup and upkeep time (Stackcut's model: modeled, not measured).
- whisper.cpp's official migration guide moves 1 partly; 4 things stay behind. What moves
- 3 public accounts of making this switch: 3 switched. Read them
What Fathom and whisper.cpp cost
List prices from each vendor's pricing page, as stored in the Stackcut catalog. Each price links its source.
| Plan | Billed monthly | Billed yearly (per month) | What you get |
|---|---|---|---|
| Fathom Premium (individual) | $20/user/mo | $16/user/mo | Advanced summaries, AI action items, meeting assistant |
| Fathom Team | $19/user/mo | $15/user/mo | Team Edition; 2 user minimum |
| Fathom Business | $34/user/mo | $25/user/mo | Team Edition; 2 user minimum; CRM sync, coaching |
- Fathom free plan: Free forever: unlimited recordings and transcriptions, instant AI call summaries, clips and search (no numeric caps published) fathom.ai
- whisper.cpp free plan: Free github.com
whisper.cpp's plans aren't in the Stackcut catalog yet; check whisper.cpp's own site.
Moving from Fathom to whisper.cpp
What whisper.cpp's importer carries over, what it leaves behind, and any help it offers switchers.
To whisper.cpp
Official guide github.com · Tools: whisper-cli, cmake / C++ toolchain, ffmpeg, whisper.cpp Docker images (ghcr.io/ggml-org)
Moves: Meeting audio (from exported Fathom MP4s) (partial). github.com
Doesn't move: Fathom AI summaries and action items — whisper.cpp is inference-only, no summarization; Speaker attribution — no built-in diarization (experimental tinydiarize only); CRM sync, folders, playlists, comments, keyword alerts; Nothing imports automatically — recordings must first be exported from Fathom. github.com
Watch out for:
- whisper-cli only accepts 16-bit WAV — MP4/M4A must be converted with ffmpeg first github.com
- The README never mentions Fathom; this path is assembled from Fathom's export docs plus the project's quick start github.com
- Inference only: no meeting capture, calendar integration, bots, or summaries — you rebuild the workflow github.com
Community guide thinkdifferent.blog · Tools: BlackHole 2ch virtual audio driver, ffmpeg / QuickTime recorder, whisper-cli (via brew install whisper-cpp), Ollama (local LLM summarization)
Moves: Live meeting audio (full); Meeting notes / summaries (partial). thinkdifferent.blog
Doesn't move: Speaker attribution — author calls diarization 'the weak point of every local setup'; MacWhisper Pro ~80-90% accurate, whisperX needs a Hugging Face token; Automatic distribution — notes are shared manually after a 90-second human review, unlike Fathom's auto-share. thinkdifferent.blog
Watch out for:
- The post never names Fathom — it argues against cloud bots as a category; pairing with Fathom's MP4 export is our synthesis thinkdifferent.blog
- Recording laws still apply to local capture; the author announces recording every time thinkdifferent.blog
- Diarization is the known weak point; stereo channel-splitting only works for two-party calls thinkdifferent.blog
From each destination's own migration docs and switching pages, plus community write-ups where no official guide exists, each checked against its page. Confirm terms on the linked page before you rely on an offer.
People who moved from Fathom to whisper.cpp
3 public accounts of leaving Fathom: 3 switched. Summaries are ours; each links the original, and each was checked against its page before it appeared here.
(Category-level account: the incumbents the author names are Otter and Fireflies, not Fathom; the destination is whisper.cpp itself.) A journalist describes leaving cloud meeting tools for a local whisper.cpp workflow on his MacBook — a drag-and-drop script, offline processing, transcripts in minutes. XDA Developers
(Category-level account: the incumbent named is Otter.ai and the destination is Speakr, a Docker-based self-hosted app that can run WhisperX — not whisper.cpp itself.) A journalist moved his daily call-and-interview transcription off cloud notetakers onto a self-hosted app on his home server, and uses it for all his calls. XDA Developers
(Category-level account) The author ditched cloud meeting bots after a friend's cloud bot emailed a candid post-client transcript to every attendee, and now runs a fully local pipeline — BlackHole capture, whisper-cli transcription, Ollama summarization — daily for over a year. He never names Fathom; recorded here as the closest detailed public account of the Fathom-to-whisper.cpp move. Think Different (Jakub Jirák)
FAQ
Is whisper.cpp cheaper than Fathom?
Modeled, not measured: moving from Fathom Team to whisper.cpp at 1 seat costs $122 more in the first year, after setup and upkeep time at $50/hour. It depends on your plan, seats and usage. the math
Can I move my Fathom data to whisper.cpp?
whisper.cpp's official guide moves: Meeting audio (from exported Fathom MP4s). It doesn't move: Fathom AI summaries and action items — whisper.cpp is inference-only, no summarization; Speaker attribution — no built-in diarization (experimental tinydiarize only); CRM sync, folders, playlists, comments, keyword alerts; Nothing imports automatically — recordings must first be exported from Fathom. github.com
Keep reading
Check your own stack
Get your free stack audit
Stackcut finds every software subscription in your inbox and shows what to cancel, what to pay per use, and what AI can replace, with a spec and a cost for each. Your stack audit is free and takes about 2 minutes.
Or ask your agent
Connect the Stackcut MCP server (https://stackcut.io/mcp, no API key) and ask: “We pay for Fathom. Should we move to whisper.cpp?”
find_alternatives({"vendor": "Fathom"})