Loom as Atlassian Value Amplifier

Atlassian bought Loom to make Jira and Confluence stickier, not to squeeze more dollars out of Loom itself. Loom already had bottom up adoption, with over 25 million registered users, 200,000 to 350,000 paying business customers, and about $50M ARR at acquisition scale, but Atlassian is now packaging Loom inside Teamwork Collection and wiring it directly into Jira issues, Confluence pages, and Rovo. That turns a screen recording into searchable work context, not just a standalone SaaS seat.

• Bundling changes the job Loom is doing. In Atlassian’s pricing, Loom sits beside Jira, Confluence, and Rovo as one collection, which means the product can justify itself by lifting suite adoption, expansion, and retention even if Loom ARPA falls.
  1 atlassian 2 sacra
• The workflow matters more than the video. Inside Jira and Confluence, teams can record bug repros, design walkthroughs, or project updates exactly where work is tracked, then turn that spoken context into pages, tickets, summaries, and action items.
  2 sacra 5 atlassian
• This is also how Loom defends against bundled competitors. Microsoft, Google, Slack, and Zoom can all offer basic recording, while Vidyard is strongest in sales analytics. Loom’s edge is that Atlassian treats video as raw material for documentation and execution systems.
  2 sacra 5 atlassian 6 sacra

The next step is for Loom to disappear as a separate buying decision and become part of how enterprise teams capture knowledge by default. As more recorded explanations flow into Atlassian’s search, docs, and AI agents, Loom becomes a data layer for teamwork, which should raise platform lock in across Atlassian’s installed base.