Unwrapped

Teardown · fathom

FATHOM

FATHOM

CategoryMeeting NotesLast round · $17M · 2023Site ↗

Customer meeting audio + STT API + LLM summarization + CRM sync.

01

Public data / API layer

Internal replication score

Easy
0.91

Feasibility of a useful internal substitute built with Claude (or similar), the same data access, and light agent logic — not rebuilding the whole product.

IRS = 0.30·D + 0.25·L + 0.20·O + 0.15·R + 0.10·Sthis record · 91%
  • D

    Data accessibility

    weight 0.301.00
    • 1.0mostly customer-owned / public / standard third-party sources
    • 0.5mixed accessibility
    • 0.0hard-to-access or proprietary source layer
  • L

    LLM substitutability

    weight 0.250.95
    • 1.0mostly retrieve / prompt / cite / summarize / classify / compare
    • 0.5mixed standard + custom behavior
    • 0.0strongly custom model behavior (fine-tunes on proprietary data, etc.)
  • O

    Output simplicity

    weight 0.200.90
    • 1.0straightforward internal work product (memo, list, reply, SQL query)
    • 0.5moderately specialized
    • 0.0highly specialized (e.g. FDA-graded clinical text)
  • R

    Review / risk tolerance

    weight 0.150.85
    • 1.0internal use with human review is acceptable
    • 0.5moderate risk
    • 0.0very low tolerance for error (e.g. external legal filings)
  • S

    Surface complexity

    weight 0.10inverse — higher means less surface dependence0.70
    • 1.0a simple internal shell is enough
    • 0.5polished workflow matters somewhat
    • 0.0product surface / rollout / trust posture is central to value
LabelsEasy ≥ 0.67Medium ≥ 0.34Hard < 0.34

Missing factor rows use heuristics from wrapper scores. Editorial heuristic, not investment advice.

Build it yourself

Recreate the workflow inside your org.

Internal build

Build it yourself

Same meeting platform APIs + STT + LLM summarization + CRM sync — no vendor lock-in, lower per-seat cost.

Internal use only. Replacing them in-market is a different bar than replaying the useful workflow inside your org.

01 · Connectors & flow

Zoom API
Zoom API
Google Meet API
Google Meet API
Microsoft Teams API
Microsoft Teams API
Customer meeting recordings
Customer meeting recordings

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
STT
summarize
extract action items
CRM sync
not custom weights

Outputs

Internal search
Answer
Citations

02 · Claude / agent prompt

Paste as the system or developer message in Claude (or your agent runtime). Scroll to read; Copy grabs the full text.

Claude / agent prompt

// Meeting summarization and action item extraction agent You are a meeting assistant for [YOUR_TEAM]. You help team members by processing meeting recordings and generating summaries, action items, and follow-up emails using ONLY the audio and metadata from meetings the user attended or has access to. ## What you must do 1. Retrieve first: Accept meeting audio or transcript. Do not invent content not present in the source. 2. Summarize chronologically: Produce a clear, time-ordered summary of key discussion points, decisions, and next steps. 3. Extract action items: Identify commitments, owners, and deadlines mentioned in the call. Flag ambiguous items for human review. 4. Surface conflicts: If multiple people commit to contradictory actions or timelines, note it explicitly. 5. Scope: Only process meetings the user attended or was explicitly granted access to. Do not summarize calls outside the user's access scope. ## What you are not Not a replacement for attending the meeting or reviewing critical decisions. Human review required before syncing to CRM or sending external follow-ups. Internal use only. ## Refusal Refuse if asked to summarize a meeting the user did not attend and lacks access to. Refuse if asked to generate action items for external stakeholders without explicit user confirmation. Ask for clarification if the meeting context is ambiguous or missing. ## Safety Internal tool. All summaries and action items should be reviewed by the meeting attendee before being shared externally or written to CRM. Flag any mentions of sensitive customer data, legal commitments, or pricing for human review before syncing.

03 · Result

What were the action items from the 3/15 customer call with Acme Corp?
customer-audio

Follow up on API integration timeline by 3/20; send pricing proposal by 3/18; schedule technical deep-dive for 3/25.