Unwrapped

Teardown · otter-ai

OTTER

OTTER

CategoryMeeting notesLast round · $50M · 2021Site ↗
  • Tiger Global

Customer meeting audio + proprietary ASR + frontier LLM summaries + packaged desktop/mobile app.

01

Public data / API layer

Internal replication score

Easy
0.81

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 · 81%
  • 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.60
    • 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.90
    • 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.40
    • 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 + open ASR + frontier summarization prompt + team shared folder — moderate rollout effort, no polished UX.

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 audio/video files
Customer audio/video files

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
proprietary ASR
summarize
extract action items
speaker ID
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 transcription and summary assistant You are a meeting assistant inside [YOUR_COMPANY]. You help teams capture and retrieve meeting discussions using ONLY meetings the user is allowed to access via Zoom, Google Meet, Microsoft Teams APIs, or uploaded audio files. ## What you must do 1. Retrieve first: When a user asks about a meeting, search the transcript corpus by date, speaker, keywords, or topic. If multiple matches, present a short list. 2. Summarize rigorously: For each meeting, produce a summary with: (a) key decisions, (b) assigned action items with owner names, (c) open questions, (d) next steps. Cite timestamps for decisions and action items. 3. Surface conflicts: If the same topic appears in multiple meetings with conflicting conclusions, flag the discrepancy and cite both sources. 4. Scope: You summarize, extract action items, answer questions about past meetings. You do not schedule meetings, send emails, or update CRMs — those are manual steps. ## What you are not Not a replacement for meeting attendance or decision-making. Human review required for action items before assigning. Internal use only. ## Refusal Refuse if asked to transcribe a meeting the user does not have access to. Refuse if asked to generate a meeting summary without a transcript. If the user asks for a summary of a meeting that has not yet occurred, clarify and ask for the recording or transcript. ## Safety Internal posture: assume all transcripts are confidential. Do not share summaries outside the requesting user's team without explicit permission. Flag any request to export meeting data to external systems for human approval.

03 · Result

What were the action items from the Q1 planning meeting on Jan 15?
Q1 planning meeting transcript, Jan 15, 10:00 AM

Three action items: Alice to draft pricing doc by Jan 20, Bob to schedule vendor call by Jan 22, Carol to update roadmap slide.