Pulse — who is getting closer to us · last 30 days

8high impact

10approaching ▲

12on the radar

colour = impact on us (🔴 high · 🟠 medium · 🟢 low) closer ring = competes more directly bigger dot = stronger company tail = where it came from (◦ start → ● now): outward tail = approaching us, inward = backing off on the radar = closeness 4+ OR a shipped move into our loop · hover a dot for why

Summary · last 30 days

Governance is the new front. Fellow now lets admins password-lock shared recaps, and Atlassian confirmed a Rovo bug (ROVO-297) that posted an internal note to a customer in public — an agent that wrote with no human OK. Our approval-first, goal-across-meetings pitch just got two proof points.

🔴 Platforms still own execution — Zoom's ZoomMate ($20/user/mo) finishes meeting work across Jira, Salesforce & ServiceNow; Atlassian Rovo runs agent work into Jira from any surface (5M tool-calls/day); and Microsoft keeps pulling the Planner board into Outlook + the Copilot app. We defend on the goal kept across meetings with a human approval gate.
▲ Newest move — the fight shifted to governance (both 17 Jul). Fellow added admin-enforced password-protected recaps, competing on the trust story we lead with. And a staff-confirmed Rovo bug (ROVO-297) posted an internal JSM comment publicly with no confirmation before the write — proof that agentic execution without a human OK is risky.
🟢 Still ours — the business GOAL kept across meetings, with its decisions, risks and dependencies, driving human-approved cross-stack execution. A tailwind holds: AI notetakers sat in on 1 in 3 US meetings but only a third of people were asked first — the trust gap our approval-first, no-forced-bot pitch is built for.

12 on radar · 8 high-impact · 19 new signals in last 30 days

Run health · 2026-07-21 · coverage 72% · 3 need a look

DAILY FULL pass, 1-day delta (last_checked was 20 Jul). NotebookLM Deep Research WORKED as the primary engine — one ephemeral notebook, deep web sweep returned 115 sources across all 12 on-radar competitors + discovery; notebook deleted after. Anthropic-backed WebFetch/WebSearch were 529-Overloaded the entire pass, so every figure was verified by direct curl of the primary source instead (Fellow news page + the Atlassian Community ROVO-297 thread both read cleanly). LinkedIn via CDP-connect: connected headed and logged in (verified on /feed/, authwall:false), but the headed browse server was very unstable — nav timeouts, page-URL drift (loads landed on the wrong company), then a hard authwall after a few company-page loads. Usable social coverage: atlassian (right page — brand/PR post, quiet) and the fellow-ai page (loaded under a drifted nav; live-corroborated Fellow's password-recap ship). The other 9 profiles authwalled / went unresponsive / loaded the wrong company — all logged failed[], NOT treated as quiet. RESULT: 2 new material governance signals, both dated 17 Jul and both missed by the 20 Jul pass (Fellow was authwalled; the Rovo bug never surfaced): (1) Fellow shipped admin-enforced password-protected public recaps (17 Jul, news.fellow.app) — a rival hardening the trust story we lead with [amber, our_lane:false — consent/sharing security, not goal/decision governance; won't move Fellow toward center]; (2) Atlassian-confirmed Rovo bug ROVO-297 (17 Jul, community.atlassian.com) — Rovo posted an INTERNAL JSM comment PUBLICLY with no confirmation before the write; a staff moderator confirmed it a known bug [amber, our_lane content-opening — the single best proof for our human-approval-gate wedge]. VERIFIED-DROPPED to noise: Zoom 20 Jul (AI Companion→native + ZoomMate marketplace consolidation + iOS mobile recording + Voice Translator GA) = capture/translation/packaging polish, ZoomMate orchestration already logged; Webex Jul Control Hub (admin provisioning, 15-language AI assistant, AI Agent Studio multi-agent) = contact-center/admin, out of lane; Planner custom templates + Project Online retirement = PM templating + migration, native-suite gravity already captured; Productboard Spark version-history/context-visibility = dated 8-13 Jul, older than last_checked and minor. DROPPED-UNVERIFIED: a Reddit r/microsoft365 claim that Teams Facilitator lets owners edit/delete transcripts with no immutable original — good provenance angle, but Reddit returned network-blocked to fetch, so not asserted (no fabrication). DISCOVERY: meetergo/Spokenly (local no-bot dictation) = low proximity, not intake-worthy; Tana remains the standing intake candidate. All 12 on-radar last_checked refreshed to 2026-07-21.

⚠️ WebFetch / WebSearch (Anthropic-backed) 529 Overloaded for the entire pass — could not use. Worked around by curling primary sources directly; every stored figure is still verified against a real source URL. · open ↗
⚠️ LinkedIn — 9 on-radar profiles authwalled / unresponsive / wrong-page Session was logged in (read atlassian + fellow-ai OK) but the headed browse server drifted URLs and LinkedIn threw authwalls after a few company-page loads. Not covered live this pass — eyeball manually: read-ai (/company/readinc), microsoft (/company/microsoft), productboard (/company/productboard), otter (/company/otter-ai), zoom (/company/zoom), spinach (/company/spinach-io), fireflies (/company/fireflies-inc), sembly (/company/semblyai), webex (/company/webex). Substance for all 12 was still covered by NotebookLM Deep Research. · open ↗
⚠️ X / Twitter Not run this pass — LinkedIn prioritized per runbook step 2 and the browser was fragile; X login state unverified. Surfaced so it is not a silent skip. Top handles to eyeball: @otter_ai, @ReadAI_, @sembly_ai, @Zoom, @Atlassian, @firefliesai. · open ↗
⏳ GoRetro changelog no update since May 2023 — product likely stalled (off-radar/background)

A failed source shows here in red — “no news” is never assumed safe.

Look here first

On the radar = closeness 4+ OR a shipped move into our loop. Sorted by impact, then closeness.

High impact ▲ approaching Read AI 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. → Do: 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. shipped a move into our exact loop (red our-lane signal) High impact ▲ approaching Microsoft Planner Infra Collabix could feed, but strategically heavy: it's Microsoft's PM surface tied to Teams + Copilot where we operate. The new goals bucket lands in our goal-tracking positioning; ecosystem lock is the real risk. → Do: A 'goals bucket' is a list; Collabix keeps the goal's why — the decisions, risks and dependencies — alive across meetings and across tools. competes directly with us (closeness 4+) High impact ▶ steady Cisco Webex Assistant The most direct platform-native threat: its Task Agent extracts AND executes action items into Jira/Salesforce (GA Q1 2026) — overlapping our exact meeting→execution loop with huge distribution. We defend on cross-meeting goal memory + provenance. → Do: Webex opens a ticket from one call; Collabix keeps the goal — and the decisions and risks behind it — across every meeting, into your Jira or Azure DevOps. shipped a move into our exact loop (red our-lane signal) High impact ▲ approaching Zoom AI Companion Direct overlap with our core — and as of ZoomMate (Jun 2026) it now executes cross-stack, not just inside Zoom. We no longer defend on 'they stay in-ecosystem'. Our edge is the goal kept across meetings with decision provenance and a human approval gate; Zoom's lock-in is now the call platform (you must meet on Zoom). → Do: Zoom Companion runs work from a call; Collabix keeps the goal across meetings — its decisions and risks — and ships the approved next step into your trackers. shipped a move into our exact loop (red our-lane signal) High impact ▲ approaching Atlassian Rovo Our strongest rival on paper: an AI agent across Jira/Confluence that now executes work (Jira Agents assigned to work items) and added a 'Memory' feature plus auto goal/status updates. But it only sees Atlassian tools and still needs a human to publish goal updates — that handoff + lock-in is our wedge. → Do: Rovo's depth is its cage — it only sees Atlassian. Collabix keeps your goal alive across any stack (Jira + Azure DevOps + Slack + Teams). shipped a move into our exact loop (red our-lane signal) High impact ▲ approaching Microsoft (Copilot / Facilitator) Collabix's biggest direct threat — same meeting-to-tasks motion, free-riding on existing M365 Copilot seats. But its gaps are exactly our wedge: (1) single-meeting only — no goal/decision memory ACROSS meetings; (2) tasks land in Planner/Teams, NOT Jira or Azure DevOps; (3) locked to the Microsoft stack, not cross-vendor. → Do: Copilot summarizes one meeting; Collabix carries the goal across meetings and ships it to the trackers your devs use — Jira/Azure DevOps, not just Planner. shipped a move into our exact loop (red our-lane signal) High impact ▲ approaching Fireflies.ai Massive (≈$1B, 20M users) and very loud on LinkedIn. Different DNA (transcription), so watch for the day they ship real execution — that's when proximity jumps. → Do: Fireflies gives you 200 skills; Collabix gives you the one thing that matters — the goal, governed and remembered across meetings. competes directly with us (closeness 4+) High impact ▲ approaching Otter.ai Now a RED our-lane rival, not a notetaker: it turns meetings into cross-stack auto-execution (Salesforce/Gmail/Jira) + a memory layer other AIs build on (MCP). Overlaps our core loop at huge scale. We defend on the goal kept across meetings, decision provenance, and human-approved (not auto-run) execution. → Do: Otter turns meetings into a searchable knowledge base and fires off tasks; Collabix keeps the goal moving across meetings — its decisions, risks and the approved next step — not a pile of auto-actions. shipped a move into our exact loop (red our-lane signal) Medium impact ▲ approaching Productboard Closest to us on 'goals', and owns the Discovery→Delivery wording. But its goal dies when work hands off to Jira — we keep it alive. → Do: Productboard's provenance lives in product strategy; Collabix's lives in the meeting — every decision traced to the moment it was made. competes directly with us (closeness 4+) Medium impact ▲ approaching Spinach Closest to us in intent — an AI for standups/retros that already ships. Smaller and ceremony-bound; we win with a continuous goal across all meetings. → Do: A generic 'context layer' just stores talk; Collabix attaches context to the GOAL — decisions, risks, dependencies — so it drives work, not just recall. competes directly with us (closeness 4+) Medium impact ▶ steady Fellow Made the boldest move late 2025 (botless + MCP, auto-creates Jira/Asana/Linear tasks). It erodes our old 'no bot' edge — so we lead on goal memory, not 'no bot'. → Do: Fellow locks who can SEE a recap. Collabix controls who can APPROVE the work — a person says yes before any task runs, and the goal keeps moving across meetings. competes directly with us (closeness 4+) Medium impact ▲ approaching Sembly AI One of the most directly overlapping rivals: tracks decisions, dependencies and owners and regenerates roadmap/status deliverables across planning sessions. KEY: its 'Success Plans' are generated DOCUMENTS (re-made each cycle), not a persistent live goal object — so it approximates, but does not equal, our goal-context memory + decision provenance. → Do: Sembly remembers and documents meetings; Collabix drives the goal to done — decisions, risks and the approved next step across meetings and your trackers. competes directly with us (closeness 4+)