Fathom sale: check the notes path and log the decision

If your weekly meeting uses Fathom, the notes path may change. Superhuman bought Fathom, a Y Combinator-backed meeting notetaker. On September 14, 2026, Superhuman said it would fold Fathom's notetaking into its email, calendar, collaborative documents, and database apps and agents. The operational question is whether the transcript still lands where the owner can find it.

Superhuman also said the acquisition would let meeting notes and action items feed later work rather than stay isolated in separate tools. Fathom founder Richard White said the same day that Fathom's meeting context would move into Superhuman's inbox and docs.

Fathom's existing free and paid plans were to remain in place after the September 14, 2026 acquisition. Fathom's free plan is tied to more than 400,000 monthly active users.

After the acquisition, Fathom recordings, summaries, and action items were expected to show up inside Superhuman Mail and Calendar. The integrated notetaker can compose messages, refresh records, arrange follow-ups, and kick off AI-agent tasks from meeting data. The weekly cadence is the test for a usable record.

The data path is the real product

A notetaker only matters if the meeting output reaches the next task: a transcript in a separate app requires opening, copying, and remembering; a summary in the wrong inbox kills the follow-up; an action item with no owner produces no work.

The owner should check the inbox during the week, the next meeting should open the doc, and the decision record should explain why the team said yes. Verify the path you actually use.

The continuity check has five items

Use the checklist after any notetaker acquisition, not just this one. Run it before the next weekly. Each item tests a different failure. Pricing is part of the check because the plan can change even when the account remains.

• Confirm the plan still matches the account owner and any invoice.
• Check where transcripts land, including the folder, inbox, or document space.
• Verify follow-up actions appear in the owner's task list or calendar.
• Test data export for a recent meeting, including audio, transcript, and summary.
• Write a short decision log entry naming the tool, the owner, and the exit path.

Plan changes show up in billing, so the first item protects the account. A transcript in the wrong folder exists, but nobody opens it. An action item assigned in the meeting can vanish if it never enters the system. Export testing protects the team if the vendor changes terms, shuts down, or moves the data. The log entry gives the next person a starting point when they inherit the stack.

A notetaker comparison should include the exit path, not just summary quality. In a small-team stack, the notetaker is a data pipe. Before recording starts, the team should know who is being recorded and where the file will go. That keeps the meeting recording in a place the team can find.

The decision log makes the choice auditable

A decision log entry should be short enough to read in a meeting. It should say why the team chose the notetaker, who owns the account, where the data goes, and what happens if the vendor changes. It should also note any consent or retention limits the team agreed to before recording.

In June 2026, Mayer Brown identified documented governance measures as a way to demonstrate accountability for AI notetaker deployments. The practical note covers notice, consent, retention, and access. When a tool is acquired, the old choice may still be valid, but the assumptions behind it can shift.

Record the new data path, the account owner, and the date you ran the check in the decision log.