Loom as Documentation Capture Layer

The important shift is that Loom is moving from a communication tool to a system that manufactures documentation while people work. A product manager can record a walkthrough, an engineer can narrate a bug, or a support lead can explain a process, and Loom now turns that spoken context into transcripts, summaries, chapters, action items, and even draft Confluence pages or Jira tickets. Inside Atlassian, that makes video less like a message and more like raw material for a company knowledge base.

• This changes where Loom competes. Basic recording is easy for Slack, Zoom, Microsoft, and Google to bundle, but Loom is being tied to Jira, Confluence, and Rovo so the real product is captured context flowing into work tracking and searchable docs, not just a video link.
  1 sacra 2 sacra 4 atlassian 5 atlassian
• The workflow is concrete. Record a screen and voice explanation, let AI create the transcript and summary, then push that output into a Confluence page, step by step guide, or Jira issue. That removes the separate step where someone has to watch a meeting or demo and write notes afterward.
  1 sacra 2 sacra
• The strategic prize is compounding memory. Loom had about $50M ARR in October 2023, more than 25 million registered users, and roughly 88 million videos recorded in 2024, which means every new video can become another searchable artifact inside Atlassian’s broader knowledge graph.
  1 sacra 4 atlassian 5 atlassian

Going forward, Loom is likely to matter less as a standalone seat sale and more as the capture layer in Atlassian’s system of work. As more teams store narrated decisions, workflows, and edge cases in Confluence and query them through Rovo, Loom becomes part of the infrastructure that trains both human teammates and enterprise AI agents.