RADAR
updated 2026-07-20
↻ Refresh
Auto-updates daily. To refresh now, tell Claude “run the radar”. Every change is version-controlled, so nothing is lost.
← back to Pulse

Read AI High impact ▲ approaching

Meeting AI / notetakers · on radar · open source ↗ · checked 2026-07-20
📍 shipped a move into our exact loop (red our-lane signal)

Why this matters to us

Huge and growing fast, and just moved its message to 'turn talk into action' — straight at our lane. But people hate its always-on bot, which is our opening.

Trajectory ▲ approaching

Shipped MCP/Claude connectors + 'Ask Read Actions for Sales' and an 'Ada' exec twin — moving from notes to agentic cross-surface actions, edging into real-time meeting→execution.

What they are

Turn conversations into action — recaps, Ask Read, cross-channel insights.

Who they sell to: Teams wanting one search/knowledge layer; grows by word of mouth then sells to enterprise.

Price: Free (5 mtg/mo) · Pro $19.75/$15 · Enterprise $29.75/$22.50 · Enterprise+ $39.75.

How strong they are

Money4
Users / scale4.5
Growth5
Fame4
Shipping speed4
Reach4.5
How close to us5
Our opening4.5

Where they beat us today

  • Raw scale
  • Funding
  • Big-name logos
  • Brand
  • Word-of-mouth growth

Their gaps

  • Search DNA, not goal-continuity
  • Not Microsoft-first
  • No human approval step
  • Intrusive always-on bot people dislike

How we win

  • We keep the goal alive across meetings, they search talk
  • Human-approved execution, not auto-agents
  • Microsoft / Azure DevOps depth
  • We don't need a bot in every call

What we caught (5)

2026-06-25 our lane
Homepage now says 'turn conversations into Action'
Why it matters to us: They are stepping onto our territory — 'action', not just notes. Watch closely.
Positioning shifted explicitly into the execution lane.
read.ai homepage ↗
Our move
Say: Read searches your talk; Collabix keeps the GOAL alive across meetings and ships it to your Jira/ADO.
Ship: Action Queue: critical-only filter.
Sell: 'Why not Read AI?' → goal-continuity + approval step + no bot in every call.
2026-06-25
Loved on G2 (4.6) but hated on Trustpilot (1.4)
Why it matters to us: Their weak spot is OUR content: the market already dislikes the always-on bot and privacy. We avoid both.
~85% 1-star on Trustpilot — intrusive bot + privacy complaints.
Trustpilot/G2 ↗
Our move
Say: Content: 'The meeting bot nobody asked for' — show goal tracking with no bot in the call.
Ship: Make 'no persistent bot' explicit on site.
Sell: Privacy-first line for EU buyers.
2026-05-27 our lane
Read AI becomes a Claude connector — meetings, action items & calls as building blocks in Claude
Why it matters to us: Read AI is turning its meeting data into a context layer other AIs build on (Claude AND ChatGPT), and it is getting real adoption (~40% WoW). That is the memory/context-layer land-grab near our turf — but it is recall/context, not goal-tracking or approved execution.
Read AI blog (27 May 2026): meetings, action items and customer conversations become building blocks inside Claude (a Claude connector) via three plug-and-play skills. Also has an OpenAI/ChatGPT connector — and Read AI says MCP + ChatGPT-connector usage is compounding ~40% week-over-week (doubling WoW at launch), i.e. the context-layer play is gaining real traction.
Read AI blog ↗
Our move
Say: Read AI makes your meetings searchable inside Claude; Collabix keeps the goal moving — its decisions, risks and the approved next step — across meetings.
Ship: Show the goal advancing across meetings with provenance, not a Q&A over past calls.
Sell: For ‘we will just query meetings in Claude’ buyers: that is recall; we drive the goal to done with a human approval gate.
2026-02-01 our lane
Read AI adds 'Ask Read Actions' (CRM) + native Linear issue creation + cross-meeting memory
Why it matters to us: They now create Linear issues from meeting content and run actions into Salesforce/HubSpot, plus 'Large Meeting Models' that remember across thousands of meetings — straight at our memory + execution turf.
'Ask Read Actions' updates CRMs, sends emails and triggers workflows from search; a native Linear integration creates issues from meeting content; LMMs expand context from one meeting to thousands.
Read AI blog ↗
Our move
Say: Read can open a Linear issue; Collabix keeps the goal that issue serves — with the decisions and risks behind it — across every meeting, into Jira/Azure DevOps too.
Ship: Show the goal→work link in the demo, not just a single auto-created issue.
Sell: 'Why not Read AI?' → recall/search + an always-on bot people dislike; we govern the goal across meetings with an approval step.
2024-10-28
Raised $50M Series B (total ~$81M, ~$450M value)
Why it matters to us: They are well funded and scaling — they can out-spend us, so we win on focus, not force.
Smash Capital led; ~1M new users/month at near-zero marketing.
TechCrunch ↗