# Absorb — Granola Independent public example · September 2026 Independent Absorb assessment using public information only. Not affiliated with or endorsed by Granola. ## 1. Product summary Bot-free meeting capture combined with transcripts, personal notes, searchable history and downstream integrations. **User / buyer:** Individuals and teams with frequent meetings; product, sales and enterprise teams are explicit use cases. **Core job:** Preserve what happened in meetings and turn conversations into memory, follow-ups and work items. ## 2. Evidence and unknowns ### Observed facts - Granola captures meetings without a bot, transcribes them and enhances user notes; meeting history can be queried later. [Granola — Product](https://www.granola.ai/use-cases/product) - Granola connects to calendars, CRMs, project tools, Slack, Zapier and AI assistants; MCP/API expose meeting notes externally. [Granola — Integrations](https://www.granola.ai/integrations) - Notes are private by default; users control sharing and can request deletion of their data. [Granola — Security](https://www.granola.ai/security) ### Assumptions - Longitudinal meeting history becomes materially more valuable over time. - Workflow integrations are used enough to create real switching friction. ### Critical unknowns - Retention by depth of meeting history and downstream integrations. - How often meeting-derived tasks or CRM updates complete a closed loop. ## 3. Score, verdict and confidence 58.75/100 — 🟠 At risk of absorption. Confidence: medium. This is not a probability of survival. ## 4. Eight weighted dimensions Weighted points = score / 4 × weight. ### Absorption Resistance Score 2/4 · Weight 20 · Points 10 Transcription and summaries are model-native; accumulated meeting context preserves some value. ### AI Progress Advantage Score 2/4 · Weight 15 · Points 7.5 Better AI improves output while making the same capability easier for incumbents to bundle. ### Compounding Assets Score 3/4 · Weight 15 · Points 11.25 Private meeting history, notes and relationship context accumulate over time. ### Workflow Integration Score 2/4 · Weight 15 · Points 7.5 Usage is recurring, but execution usually finishes in downstream systems. ### Replication Difficulty Score 2/4 · Weight 10 · Points 5 The experience and integrations take work, but the core feature set is reproducible. ### AI-Expanded Problem Score 2/4 · Weight 10 · Points 5 AI does not clearly expand meetings as a problem; it mainly improves the capability sold. ### Model Independence Score 4/4 · Weight 5 · Points 5 Meeting state and UX can survive a model/provider swap. ### Defensive Path Score 3/4 · Weight 10 · Points 7.5 History plus integrations create a credible path toward memory and workflow, but not yet a control system. ## 5. Three reasons for the verdict - The visible promise—transcribe, summarize, extract actions—is commoditizing quickly. - Longitudinal meeting history is a real compounding asset. - Granola still sits mostly upstream of execution, leaving platform incumbents room to absorb the shell. ## 6. Biggest absorption risk Meeting platforms or general assistants bundle equally good capture and summaries into products customers already use. ## 7. Strongest defensible asset today Longitudinal private meeting memory tied to people, calendar context, user notes and downstream systems. Asset existence does not establish causal retention or switching cost. ## 8. Survival Design Proposed future capabilities are not counted as existing strengths. ### Absorbable Shell Transcription, generic summaries, action extraction, meeting Q&A and follow-up drafting. ### Defensible Core Accumulated meeting graph: private history, notes, relationship context and linked downstream records. ### Value Migration From better notes to durable memory and action continuity: what was decided, who committed and what happened next. ### Own the Source, Not the Interface Become the authoritative meeting-memory source other AI tools query through MCP/API. ### Reality Anchor Participants, chronology, user notes, transcript history, CRM/task links and resulting work items. ### Workflow Evolution Prepare → capture → extract commitments → update work systems → observe completion → bring outcome into next meeting → repeat. ### AI as a Channel MCP and API already provide a concrete channel for external AI to query Granola’s private meeting history. ### Time to Moat The moat appears when months of history link to downstream outcomes and are reused in future meetings. The risk is incumbents bundling the shell first. ### Redesign Recommendation Shift from AI notepad to meeting system of record: persistent relationship memory plus closed-loop commitment and outcome tracking. ## 9. Build decision Validate defensibility first The defensible direction is plausible, but Granola must prove that accumulated history and workflow continuity materially raise retention and switching cost. ## 10. Decisive question Do customers with six months of history and active integrations retain materially better because that accumulated state is painful to replace? ## Seven-day validation plan Proposed experiment only. No research results claimed. Small-sample thresholds are discovery hypotheses, not proof of demand or defensibility. ### Days 1–2 **Do:** Invite five existing teams with at least three months of meeting history. Ask each to retrieve a past decision and its owner, using their normal tools. **Ask:** Show me the last commitment you had to recover from an earlier meeting. What happened next? **Measure:** Record the task, time, source and result for all five teams. Do not score willingness from compliments. **Decide:** If no team has this recurring problem, stop the proposed commitment-tracking build and interview a different segment. **Owner:** **Observed evidence:** **Actual result:** **Next decision:** ### Days 3–5 **Do:** With consent, manually prepare a commitment brief for each team’s next meeting: decision, owner, due date and linked task. Use existing notes and tools; build no new integration. **Ask:** Which item from this brief changed what you did in the next meeting? **Measure:** At least three of five teams use a past commitment and identify one concrete action it changed. **Decide:** If fewer than three use it, revise the workflow before investing in tracking features. **Owner:** **Observed evidence:** **Actual result:** **Next decision:** ### Days 6–7 **Do:** Offer a second brief for the following meeting. Ask teams to choose between their usual summary and this continuity brief; record actual reuse. **Ask:** Which would you keep if your meeting app included equally good summaries for free? **Measure:** At least three teams request another brief, and at least two link a commitment to a completed task. These are proposed discovery thresholds, not statistical proof. **Decide:** If both pass, prototype one commitment-to-task workflow. Then measure retention over multiple months; seven days cannot establish a moat. **Owner:** **Observed evidence:** **Actual result:** **Next decision:** ## Method and limitations Absorb scoring guide. Fixed verdict bands: 80–100 Grows with AI; 60–79.99 Needs stronger defensibility; 40–59.99 At risk of absorption; 0–39.99 Likely to be absorbed. The build decision is reasoned separately. Dated public-information assessment. Not an audit or a forecast of market demand, revenue or financial performance.