Competitive landscape
Where Conclave sits versus notetakers, team-knowledge, and personal-memory tools.
Everyone in this space is readable by their operator. That's the gap Conclave is built into.
The map
| Category | Examples | Team memory? | Operator-blind? |
|---|---|---|---|
| Notetakers | Otter, Fireflies, Granola | No (single meeting) | No |
| Team knowledge | Glean, Notion AI | Yes | No |
| Personal memory | Rewind, Limitless, mem | Cross-time, personal | No |
| Conclave | — | Yes | Yes |
Conclave is alone in the top-right: team memory that's operator-blind. See Why Conclave for the quadrant argument.
The legal tailwind
The thesis isn't hypothetical — incumbents are being sued on exactly the voiceprint-and-consent axis Conclave is designed around:
- In re Otter.AI Privacy Litigation — 5:25-cv-06911.
- Cruz v. Fireflies — 3:25-cv-03399.
Every such suit strengthens the "consent-gated, operator-blind" position and the Legal beachhead.
Why it isn't trivially copied
Operator-blindness is end-to-end or it's a lie — it requires owning capture, enforcing consent at the microphone, and attesting the enclave. A readable-by-default incumbent can't retrofit that without rebuilding their trust architecture and giving up the operator-side data access their own products depend on.
Source: Crazy Research/VFTE-PITCH-RESEARCH.md, pitching/Conclave-Pitch-Script.md.