1. LandOffer
  2. Blog
  3. All articles
  4. Fathom Review for Small Teams: Free Capture, Premium Notes, and Shared Meeting Libraries

AI at Work

Fathom Review for Small Teams: Free Capture, Premium Notes, and Shared Meeting Libraries

An individual and a three-person team map Fathom subscriptions and a fictional customer call into shared-library requirements, separating advanced notes, paid seats, folder visibility, and clip permissions.

9 min readLandOffer team

Fathom Free can suit an individual who needs meeting capture, transcripts, and ordinary summaries. Premium adds individual advanced-note features; a Team subscription addresses a different problem: colleagues finding and working with a shared meeting library. For a new team, count the members who need library access; one paid recorder does not establish free team seats.

This LandOffer.ai review uses official documentation checked October 27, 2026 and two completed fictional buying and permission records. No meeting was recorded, account connected, or summary generated. Public descriptions establish candidate capabilities; they do not establish recording permission, transcription accuracy, or the quality of a team's decisions.

Colleagues distinguish personal meeting notes from material selected for a shared team library.

Free capture and Premium notes solve an individual need

The current pricing page separates individual Free and Premium from Team, Business, and Enterprise. Free includes unlimited recordings and transcriptions with ordinary summaries. Unlimited capture is a quantity allowance, not proof that every meeting should be recorded or retained indefinitely.

Fathom's individual-plan comparison, updated June 2026, says Free supplies advanced summaries for the first five calls each month, followed by its General/Enhanced template. Premium supplies advanced summaries across the individual's meetings and additional AI features. An ending advanced-note preview does not end all recording access.

In our first fictional record, Ari, a product consultant, has twelve eligible meetings per planning month. Five advanced summaries would leave seven meetings using the ordinary template if he stays Free. He does not need a team library yet. His completed decision is retain Free while checking whether the ordinary summary is sufficient for those seven calls. Check the ordinary summaries before paying solely because the call count increased.

Ari's review procedure is specific. For each selected meeting, he will check the speaker, the actual decision, any condition attached to a proposed date, and whether a named person accepted an action. If the conversation asks whether Friday is possible, record the proposal date as unconfirmed rather than assigning a Friday delivery commitment. That is an editorial acceptance rule for future approved testing, not a Fathom error observed here.

Premium becomes a plausible candidate if Ari needs the advanced format repeatedly, or requires an included individual feature that Free does not supply. It does not turn his private call history into a governed team library. The folders documentation explicitly excludes individual Free and Premium licenses from its shared full-call folder feature.

The current page also distinguishes Mac bot-free capture, marked beta, from bot capture. Verify the actual device and capture experience before arranging a trial. This case assumes company-approved desktop Macs and a future permitted meeting; no platform compatibility, calendar behavior, or capture experience was tested.

Build the complete individual and three-person bill

For the team scenario, Ari works with Bea and Chen. Each hosts calls that the others need to review: twelve, eight, and four per month respectively, totaling twenty-four. They need a common place for approved full-call records and a smaller set of selected feedback clips. They do not need automatic CRM field updates, sales coaching scores, or organization-wide retention enforcement for this initial evaluation.

The public price cards contain both billing options. Their retrieved page source binds Premium $16 to the yearly rate and $20 to monthly; Team $15 and $19 respectively; Business $25 and $34. Team and Business each list a two-user minimum. These are displayed dollar amounts and public source-code cadence labels, not an exercised pricing selector or a completed checkout. Verify billing currency, tax, renewal terms, and the account's actual quote before purchase.

Here is the completed base-subscription model, excluding tax, add-ons, mid-cycle changes, and implementation work:

Requirement and configuration Annual-billing base Monthly-billing base Recorded decision
Ari alone, ordinary summaries sufficient Free: $0 $0 Keep Free; seven calls beyond the advanced allowance do not automatically require payment
Ari alone, advanced individual notes required $16 × 12 = $192/year $20/month Premium candidate; no team-folder entitlement inferred
Two people need a new Team workspace 2 × $15 × 12 = $360/year 2 × $19 = $38/month Meets the stated two-user minimum; not a one-seat team purchase
Ari, Bea, and Chen need the shared library 3 × $15 × 12 = $540/year 3 × $19 = $57/month Team candidate for all three members
Three individual Premium subscriptions 3 × $16 × 12 = $576/year 3 × $20 = $60/month Does not supply the required team folders merely because all three people pay
Three Business users 3 × $25 × 12 = $900/year 3 × $34 = $102/month Hold; the additional business workflow is not currently required

The three-person Team annual base is $36 below three individual Premium annual subscriptions at these rates. This subscription difference establishes neither feature equivalence nor measured return. Twelve unchanged Team monthly payments total $684, versus the annual-billing base of $540. A commitment should follow the chosen cadence, not whichever number looks smaller in a screenshot.

Do not import old free-seat assumptions. Fathom's October 19 legacy-seat guidance explicitly distinguishes older Team Edition Standard/Pro from newer Team/Business. The new plans do not support free seats. Thus “two paid hosts plus Chen as a free team reader” is not this new-plan budget, even if a legacy workspace once supported that arrangement.

One administrative line stays open in the record: who will notice a seat change before renewal? Bea accepts that review, while Chen confirms he needs the library as a member rather than merely receiving an occasional approved excerpt. If that need later changes, the team must revisit both access and billing. It should not downgrade somebody just because an invoice reminder arrived while assuming all previously shared material remains available in the same way.

The recorded buying decision is evaluate the three-member Team plan, with purchase held until approved access checks and the quote are complete. Bea accepts responsibility for the library's intended audience; Ari owns source review; Chen checks whether the resulting material can be found and understood. The same people have different responsibilities, but none is silently omitted from the membership budget.

Decide what belongs in the shared library

The second completed asset is a permission case built from one fictional twenty-eight-minute customer workshop. No audio file or transcript was uploaded. The written source packet divides it into four parts:

Segment Fictional content Intended disposition and reason
00:00–04:00 Introductions and project context Keep only with the approved full-call audience
04:00–12:00 Customer describes an export problem Candidate for a short product-feedback highlight after source and sharing review
12:00–18:00 A discount is discussed conditionally Keep within the authorized customer team; do not present it as an approved offer
18:00–28:00 Staffing constraints and next-step discussion Keep restricted; verify any action owner before circulating a summary

A folder organizes full calls, including their recording, transcript, and summary. A playlist organizes selected highlights. Bea therefore rejects the proposal to add the whole call to a broad “Product Feedback” folder merely to make its useful eight-minute segment discoverable. The complete conversation contains material that audience was not cleared to receive.

Her recorded replacement is a restricted customer-work folder for the full call, and a separately reviewed highlight candidate for the product audience. The highlight's exact start/end and access remain to be tested; a short clip still needs permission for its intended audience. No real folder, playlist, or link was created.

The folder rules contain a significant trap: adding a call can broaden its visibility, but a private folder does not narrow access already granted elsewhere. Removing it from a folder can restore previous standalone sharing, including earlier specific-team access. Bea must inspect existing call access before treating a proposed private folder as protection. Folder owners also receive administrative access to included recordings; choosing a folder owner is an access decision.

The completed access record is deliberately conservative:

Object Intended audience Accountable person Verification still required
Full workshop call Ari, Bea, and Chen as the authorized customer-work team Bea, proposed folder administrator Existing standalone shares, folder access, and a normal member's actual view
Export-problem highlight Approved product reviewers only Ari, content reviewer Exact clip boundary, permission for reuse, and intended recipient access
Conditional-discount summary Authorized customer-work team only Ari Condition retained; no price promise or automatic external email
Product-feedback collection Intended product audience Bea It contains approved clips rather than accidentally including the full restricted call

Chen's fictional readback asks, “If the call was already visible to everyone, does putting it in our private folder fix it?” Bea records no and leaves distribution blocked until existing access is checked. This resolves the design misunderstanding; it is not evidence that an account's permissions have been repaired.

A full-call folder and a small selected excerpt remain separate, illustrating that organizing content and authorizing its audience are different checks.

Check recording, sharing, and retention separately

Fathom's recording-consent guidance describes visible bot or bot-free notice and consent mechanisms. Bot-free is not a claim of silent recording. A tool's notice does not by itself settle an employer's policy or the participants' applicable recording requirements. In this case, the future test meeting needs prior organizational approval and an agreed recording approach; no participants were contacted.

The team also needs to inspect defaults beyond the folder. Fathom's organization-settings guide, updated October 2026, separates automatic capture, team visibility, and share-link access. It notes that turning automatic capture off still permits manual capture. Defaults may interact with team or user settings rather than representing one universal enforcement switch.

For Ari, Bea, and Chen, the proposed test starts with only the intended people added, no automatic external distribution, and no CRM or chat integration. Those are case requirements, not settings changed here. Enterprise-level controls such as a configured retention period or disabling downloads must not be assumed to come with the smaller Team purchase.

The distinction matters when a summary leaves the library. A copied paragraph, CRM note, or downloaded file may have a separate audience and lifecycle. Revoking a meeting link would not prove a recipient's previously obtained copy disappeared. The team needs an approved process for where derivative notes go and who corrects them if the source interpretation changes.

They also record a continuity question before buying: how will permitted recordings remain available when the host leaves? Fathom's October 21 account guidance says direct transfer or merging of recordings between accounts is not supported. It describes alternatives involving approved team-library sharing or an email-change request. Do not assume Chen can simply take over Ari's separate account history, and do not change identities as a shortcut without the organization's authorization.

Buy the missing capability, then test it honestly

Fathom is a plausible individual capture tool before it is a team-library purchase. Free can remain useful after an advanced-note allowance ends; Premium addresses a recurring individual need; Team adds the shared working context that three independent Premium subscriptions do not establish.

For this fictional team, the purchase gate is concrete: confirm the dated three-user quote, use approved synthetic meeting material, review the note against its source, and test the full-call and clip audiences as ordinary recipients. Keep a record of what was actually observed, including any missing context or inaccessible item. No transcription accuracy score or productivity saving is available from the research in this article.

Further workplace-tool comparisons are available at LandOffer.ai. Run the specified library-and-note evaluation with the required approvals; keep recording, sharing, and payment decisions separate.

Sources and Further Reading