When a Dedicated Tool Meets a Feature Quietly Doing Its Job
Loom built its entire identity around one idea: asynchronous video messaging for teams. Record your screen, share a link, skip the meeting. For a few years, that was a genuinely useful wedge in the enterprise software market, especially as remote work made synchronous communication feel expensive and exhausting. Atlassian acquired Loom in late 2023 for nearly $975 million, a price that signaled serious confidence in async video as a standalone category.
That confidence is looking shakier now.
Notion’s Clips feature, which lets users record short screen videos directly inside their docs and wikis, has been quietly pulling the rug from under Loom’s core use case. It does not have Loom’s polish, it lacks transcription depth, and it is not trying to be a full video platform. But it is embedded where teams already work, and that friction reduction matters more than most product managers will admit publicly.
Context Wins the Async War
The problem with Loom was never the product itself. Recording a video and dropping a link is genuinely faster than writing a detailed Slack thread. The friction was always the context switch – you record in Loom, switch back to Notion or Confluence to paste the link, and then hope your teammates actually click through. Every step between creating content and embedding it into a workflow is a step where someone drops off.
Notion Clips solves exactly that. A team member writing a product spec can record a 90-second walkthrough directly in the document, inline, without leaving the page. The viewer doesn’t open a new tab. They don’t have to manage a separate inbox of video links. The recording is part of the doc, not appended to it. That integration is deceptively powerful for everyday team communication, which rarely needs broadcast-quality async video – it just needs to be quick and contextual.
Notion’s broader strategy of building workflow tools that keep users inside its ecosystem is well documented. Notion’s growing feature set has already been putting pressure on Atlassian’s Confluence, and the pattern repeats here. Rather than building a competing async video tool, Notion built a clip recorder that fits inside a document. The distinction sounds minor. The competitive effect is not.
What Loom Is Actually Losing
The segment Loom is losing first is not the power user who records detailed product demos and shares them with a hundred stakeholders. That use case still benefits from Loom’s longer recordings, viewer analytics, CTA buttons, and transcription exports. Atlassian is betting on that layer – customer-facing communication, onboarding libraries, cross-team broadcasts.
What Loom is losing is the casual internal use case: the quick screen share to explain a bug, the two-minute clip to walk a new hire through a process, the async reply that is easier to record than type. These are the moments that drove Loom’s viral adoption inside companies in the first place. Users did not pay for Loom because they needed enterprise video infrastructure – they paid because it was the fastest way to explain something visually without scheduling a call. Notion Clips now covers that exact scenario at zero marginal cost for anyone already on a Notion plan.
Losing the casual, frequent use case is more dangerous than losing a feature battle at the enterprise level. Casual use is what drives habitual product adoption. Once a team builds the reflex to clip inside Notion, the question of whether to open Loom at all starts getting asked more often. And once that question gets asked enough, purchasing decisions follow.
Atlassian’s Tricky Integration Problem
Atlassian’s plan to integrate Loom deeper into Jira and Confluence has logical merit. Embedding video updates inside tickets and project pages mirrors exactly the strategy that makes Notion Clips effective. If it works, Loom becomes as contextual on the Atlassian side as Clips is inside Notion. But Atlassian’s integration track record with acquired products is mixed at best – and teams that live in Notion rather than Jira see no benefit from that roadmap at all.
The timing also matters. Notion has been iterating on Clips steadily, and the feature is available to users on paid plans without a separate license. Loom’s free tier was significantly restricted after the Atlassian acquisition, which removed one of its strongest growth mechanics – the frictionless viral loop where a recipient receives a Loom, has a good experience, and signs up. Restricting that entry point while a competitor offers similar functionality inside a tool teams already pay for is a difficult position to defend.
None of this means Loom is finished. The product still does things Notion Clips does not, and for teams with heavy external video communication needs, those differences are real. But for internal async communication – the bread and butter of Loom’s day-to-day usage – the gap between “good enough inside Notion” and “marginally better in a separate tab” is closing fast, and closing in the wrong direction for Loom.
Atlassian paid nearly $975 million for a product whose most frequent use case is now a checkbox feature inside a competitor’s document tool – and its best strategic counter depends on users preferring Jira over Notion as their daily collaboration home.
