Quick Answer (TL;DR)
Most communication tools compete within established categories: messaging, email, video conferencing. Loom created an entirely new category: async video. The insight was simple but powerful. Many workplace communications that defaulted to meetings or long emails could be replaced by a short video recording. Every Loom video sent was also a distribution event, because the recipient needed to visit Loom to watch it. This viral mechanic, combined with a disciplined focus on a single use case, grew the product to 25 million users and led to Atlassian acquiring the company for $975 million in 2023.
The Origin: From OpenTest to Loom
Loom did not start as a video messaging tool. The company was founded in 2015 as OpenTest, a user testing platform. The original product let companies record and share video feedback from user testing sessions. The founders (Joe Thomas, Vinay Hiremath, and Shahed Khan) noticed something unexpected: people were using the recording feature not for user testing but for general workplace communication. Engineers were recording bug walkthroughs. Product managers were recording feature explanations. Designers were recording design reviews.
The team made a pivot decision that defines the company's story. Instead of building a better user testing platform (a crowded, well-served market), they built a tool focused entirely on the emergent behavior they had observed: recording and sharing short video messages.
This was a pivot from a specific solution (user testing) to a specific behavior (async video communication). The new product, renamed Loom, let users record their screen and camera simultaneously, then instantly share the recording via a link. No editing. No uploading. No rendering. Record, get a link, share.
Key Product Decisions
Decision 1: One Use Case, No Compromise
Loom's most defining product decision was what it chose not to build. The product was not a video editor, not a video conferencing tool, not a content creation platform. It was a tool for recording and sharing short video messages. Period.
This focus had specific product implications:
No editing. Loom recordings were designed to be shared as-is. Early versions had no trim, no cut, no effects. The philosophy was that the value of async video came from speed and authenticity, not polish. If you needed to edit your video, Loom was the wrong tool.
No downloading friction. Recordings were hosted by Loom and shared via link. The recipient did not need a Loom account, did not need to download a file, and did not need any special software. Click the link, watch the video.
No scheduling. Unlike Zoom, Google Meet, or Teams, Loom had no calendar integration and no meeting scheduling. The product was deliberately positioned against synchronous meetings. The message was clear: if this communication can be async, use Loom instead of scheduling a meeting.
This single-use-case discipline is rare in product management. Most teams expand their scope as they grow. Loom resisted this for years, and the focus paid off in product quality and market positioning.
Decision 2: Every Video Is a Distribution Event
Loom's viral growth was structural, not promotional. Every Loom video created was sent to at least one person who needed to watch it. That person clicked a link, landed on Loom's platform, watched the video, and encountered a prompt to record their own response or create their own Loom.
The math was compelling. If the average Loom video was viewed by 3-5 people, and even 10% of those viewers tried the product, every active user was generating a steady stream of new user acquisition. This was not a referral program or a growth hack. It was embedded in the product's core usage pattern.
The viewing page reinforced this mechanic. Below every video, Loom displayed a CTA: "Reply with a Loom" or "Get Loom for free." The viewer was already in the context of video communication, making the conversion prompt feel natural rather than interruptive.
This viral loop is one of the cleanest examples of product-led growth in action. The product's value delivery (sharing a video) was inseparable from its distribution (exposing new people to Loom). You can evaluate similar viral dynamics with the PMF Calculator to measure whether your product's usage naturally drives new user acquisition.
Decision 3: Browser Extension as the Trojan Horse
Loom's primary interface was a browser extension, not a desktop application. This decision lowered the adoption barrier significantly. Installing a browser extension takes seconds and does not require IT approval in most organizations. By contrast, installing desktop software often requires admin privileges, security reviews, and compatibility testing.
The browser extension also meant Loom was always accessible. A user could start recording at any moment: during a code review, while looking at a design mockup, while drafting a document. The recording tool was one click away from any browser-based workflow.
This "always available" presence increased usage frequency. Users who might schedule a Loom recording if it required opening a separate application would instead record spontaneously because the tool was right there in their browser toolbar.
Decision 4: Comments and Reactions Over Editing
When Loom did expand its feature set, the team prioritized collaboration features over production features. Instead of adding video editing, transitions, or effects, Loom added timestamped comments, emoji reactions, and threaded discussions on videos.
This was a deliberate product strategy choice. Editing would have repositioned Loom from "async communication tool" to "video content creation tool," a market with established incumbents (Camtasia, ScreenFlow, Descript). Comments and reactions kept Loom in the communication space and made videos more interactive and conversational.
The collaboration features also increased engagement. A video with comments and reactions generated notifications that brought users back to Loom, increasing retention and creating additional opportunities for viewers to become creators.
Growth Trajectory
Loom's growth accelerated in three phases:
Phase 1: Design and engineering teams (2017-2019). Early adoption came from teams that valued visual communication: designers sharing design reviews, engineers walking through code, and product managers explaining features. Usage was concentrated in tech companies.
Phase 2: COVID-era expansion (2020-2021). When remote work became mandatory, Loom usage exploded across industries and roles. Sales teams used Loom for prospecting. Customer success teams used it for onboarding. HR teams used it for company announcements. The product crossed from tech-only to mainstream business use. Loom grew from 1.8 million users in early 2020 to over 14 million by 2021.
Phase 3: Enterprise consolidation (2022-2023). As usage grew, Loom added enterprise features (SSO, admin controls, analytics) and built a sales team to convert bottom-up adoption into company-wide contracts. The company reached 25 million users before Atlassian acquired it for $975 million in October 2023.
The Atlassian Acquisition
Atlassian's acquisition of Loom for $975 million validated the async video category as a permanent part of workplace communication. Atlassian saw Loom as a natural complement to its existing products: Jira for project tracking, Confluence for documentation, and Loom for video communication.
The acquisition also highlighted a strategic reality of category creation: creating a new category is valuable, but defending it against larger players (who can bundle the capability into existing platforms) is difficult. Microsoft had added a Loom-like feature to Teams. Google added recording and sharing capabilities to Google Meet. Selling to Atlassian gave Loom distribution and integration depth that would have been expensive to build independently.
Lessons for PMs
1. Create a Category by Naming a Behavior That Already Exists
People were recording and sharing video messages before Loom existed. They were using Quicktime, screenshot tools, and even phone cameras. What Loom did was give this behavior a name (async video), a dedicated tool, and a streamlined workflow. The behavior was not new. The category was.
Apply this: Look for behaviors that your users are already doing with workarounds or repurposed tools. If a significant number of people are doing the same thing in a clunky way, there may be a category waiting to be named and served. The Product Launch Playbook covers how to position a new product in an undefined category.
2. Viral Growth Requires Structural, Not Promotional, Mechanics
Loom's virality was not the result of a referral program or clever marketing. It was structural: the act of using the product (sending a video) required the recipient to engage with the platform. This kind of growth cannot be replicated through incentives. It has to be built into how the product delivers value.
Apply this: Map your product's value delivery flow. Does using your product naturally expose non-users to the experience? If the answer is no, viral growth tactics will have limited impact. If the answer is yes, optimize the conversion moment when non-users first encounter your product.
3. Single-Use-Case Discipline Creates Stronger Positioning
Loom's refusal to become a video editor, a video conferencing tool, or a content creation platform kept the product focused and the positioning clear. When someone said "I need to send a quick video," Loom was the obvious answer because it was the only answer that did one thing exceptionally well.
Apply this: Resist the pull to expand your product's scope prematurely. Each new use case dilutes your positioning and spreads your team's attention. Build a product strategy that defines not just what you will build but what you will deliberately avoid building.
4. The Best Products Turn Users Into Distributors Without Asking
Loom users did not need to be incentivized to share the product. Sharing was the product. Every video sent was an advertisement delivered to the most relevant possible audience: a person who was receiving a video communication and might want to send one themselves.
Apply this: Design your product so that the natural output of usage is visible to non-users. Shared reports, public dashboards, embedded widgets, and collaborative links all create distribution surface area.
What You Can Apply
If you are creating a new category: Study how Loom named and productized an existing behavior. Category creation is not about inventing something new. It is about recognizing a pattern that already exists, building a purpose-built tool for it, and establishing yourself as the defining product before incumbents react.
If you are evaluating your viral loop: Measure how many non-users encounter your product through normal usage. For Loom, every video sent exposed 3-5 non-users to the platform. If your product's usage does not naturally reach non-users, your growth will depend on marketing spend rather than product-driven distribution.
If you are a startup considering acquisition offers: Loom's sale to Atlassian was not a failure of ambition. It was a recognition that category creators often face a build-vs-bundle challenge from larger platforms. The acquisition gave Loom distribution and integration resources that would have taken years to build independently.
This case study draws on public interviews with Loom co-founders Joe Thomas and Vinay Hiremath, Atlassian's acquisition announcement, reporting from TechCrunch and The Information, usage data from Loom's public disclosures, and analysis of the async video category from OpenView Ventures.
FAQ
How did Loom differentiate from Zoom recordings and similar features?
Loom was purpose-built for async communication, not adapted from synchronous video. The differences were in speed (instant recording and sharing), simplicity (no meeting scheduling, no editing complexity), and distribution (every video had a shareable link with a viewing page that prompted new signups). Zoom recordings required post-processing, downloading, and manual sharing.
Why was the browser extension so important to Loom's growth?
The browser extension eliminated two major friction points: installation barriers (no IT approval needed) and context switching (recording was one click away from any browser tab). This meant users could record spontaneously rather than planning to use the tool, which significantly increased recording frequency and viral distribution.
What percentage of Loom video viewers converted to creators?
Loom has not publicly disclosed exact viewer-to-creator conversion rates, but public statements from the team indicated that a meaningful percentage of viewers (estimated at 5-15%) tried the product after watching their first Loom video. Given that the average video was viewed by multiple people, this created a strong viral coefficient.
Did Loom's single-use-case focus limit its growth potential?
Paradoxically, the narrow focus expanded Loom's market. By being the definitive tool for async video, Loom became the default choice across industries and roles. A broader product (video editing plus conferencing plus messaging) would have competed with larger, better-resourced incumbents in each category. The focus created clarity in positioning and efficiency in product development.
What can we learn from Loom's acquisition by Atlassian?
The acquisition illustrates the category creator's dilemma: building a new category is valuable, but defending it against incumbents who can bundle the capability into existing platforms is expensive. Loom faced competition from Microsoft Teams, Google Meet, and others adding recording and sharing features. Joining Atlassian provided distribution, integration depth, and enterprise credibility that would have taken years to build independently.