The Loom success story involves two pivots, a maxed-out credit card, a nearly failed acquisition of a domain name, and a product that sold itself to 25 million users without a traditional marketing budget. It also involves one of the cleanest product-led growth flywheels ever assembled in enterprise software, and an exit that validated a bet on human communication that most investors initially did not understand.
The company started as something else entirely. It almost died at least twice before it found the thing that worked. And then when it found it, the growth was so organic and so embedded in the way the product actually worked that Loom barely needed to sell itself at all.
Every video sent was an advertisement. Every recipient was a potential new user. The product marketed itself through normal usage in a way that almost nothing in B2B software had done before it.
This is that story.
Three Founders, Six Ideas, One Whiteboard
Joe Thomas, Vinay Hiremath, and Shahed Khan got together in 2015 and wrote down six ideas on a whiteboard. They were not looking for a problem to solve in a grandiose sense. They were looking for something real, something they could build, something that enough people had enough pain around to pay for.
The idea they chose was a user testing marketplace. Companies could connect with expert reviewers who would give them structured feedback on their products. They called it Opentest. They began building.
Seven months later they had made $600.
Not $600,000. Six hundred dollars. In seven months of actual work.
What they had learned, which turned out to be valuable despite the financial disappointment, was that companies cared less about feedback from third-party experts than they cared about hearing directly from their own users. The marketplace model was wrong. But something they had built inside it was right.
Opentest had a feature that let you record a short video of your screen while explaining a piece of feedback. Reviewers were using it. Companies receiving the videos were responding positively. Not to the structured user testing product, but to the videos themselves. The videos were direct. They were fast. They conveyed things that words in an email would take five paragraphs to communicate.
The founders made a decision: kill the user testing marketplace and build the video recording feature as a standalone product.
They launched it as a Chrome extension called Openvid on Product Hunt in June 2016. The first day produced 3,000 signups. More than the previous six months of Opentest’s entire existence, combined.
Two Weeks of Runway
Before the Product Hunt launch, things had gotten extremely close to over.
The team had maxed out their credit cards. Runway was measured in two weeks. Most rational observers looking at the situation from outside would have said: time to call it. The user testing idea had generated almost no revenue after months of work, and there was not enough money left to keep going much longer.
They launched Openvid anyway. The response told them something unambiguous: people wanted this. Not the feedback marketplace. The video.
That response was enough to keep going. It was also enough to unlock the first real investor interest, and eventually to close the seed funding that bought them more runway. But the near-death experience shaped the culture of the company in specific ways. There is a different kind of urgency and customer obsession in a founding team that has been two weeks from closing the business. Every user feedback signal matters more when you have almost run out of time to act on it.
Shahed Khan has described the lesson as: the most common pitfall for founders is investing too much time looking for the perfect solution before they start. Every idea you start with is imperfect. The work is iterating toward the right thing, which usually means talking to the people using what you have built, watching how they use it, and following the signal.
They followed the signal. Openvid became Loom.
The Domain Story
The name Openvid was a stopgap. As the product grew and the positioning sharpened, the founders wanted something more resonant. Something that captured the idea of weaving communication through video. They landed on Loom.
There was one problem. They did not own loom.com. A textile machinery company had it. They launched on useLoom.com, which cost $10, because that was what the budget allowed.
Shahed eventually tracked down the textile company and opened negotiations. The initial offer was $50,000. The company hesitated but agreed to $75,000. Shahed was ready to sign.
Then nothing. Emails went unanswered for weeks. Then the reason emerged: a competing startup had come in with a higher offer and VC backing that could go to $500,000. Loom could not win a bidding war.
So they did what founders who have been two weeks from running out of money learn to do: they got creative. Shahed figured out what the competitor actually feared. It was not losing money. It was losing time. They were pre-product, pre-launch, and every week the loom.com domain was tied up in negotiation was a week they could not move forward.
Loom made an offer that addressed that fear: lower price, faster close. The textile company preferred the certainty. They sold to Loom for $75,000 on a compressed timeline, and the competitor with the deeper pockets lost the domain because speed mattered more than price.
It is a small story in the context of a $975 million exit, but it captures something about how the company operated throughout its life. They competed on craft, on speed, and on understanding what the person on the other side actually needed, not just on resources they didn’t have.
What the Product Actually Was
Loom’s core product concept is deceptively simple to describe and surprisingly hard to build well.
You click a button. A video starts recording your screen, your face in a small bubble in the corner, and your audio simultaneously. When you’re done, you stop recording. Within seconds, you have a link you can share with anyone. The recipient clicks the link, the video plays in their browser, no download required, no account required to watch. If they want to reply or record their own Loom, they can sign up for free.
That’s the product. You’ve described it in four sentences. The difficulty is in the dozens of engineering decisions required to make the recording seamless, the upload instantaneous, the playback smooth across every device and connection speed, and the sharing frictionless enough that a non-technical person will actually use it instead of defaulting to typing an email.
Shahed Khan’s background as a product designer and the founding team’s obsessive focus on the user experience from day one was, by Joe Thomas’s own assessment, the secret ingredient. It was not just that Loom was useful. It was that using Loom felt good. The interface was clean. The recording flow was smooth. The end result looked professional even when you had done essentially nothing to make it so. When you sent a Loom video, the recipient could see it was polished enough that they wanted to make one themselves.
That aesthetic quality drove adoption in a way that pure utility could not. Engineers, product managers, designers, salespeople, customer support reps: people who were already proficient in written communication were willing to add video because using Loom did not feel like extra work. It felt like a better version of a thing they were already doing.
Joe Thomas, when describing behavior change products, made the point directly. Asking someone to record a video instead of typing an email is a behavior change. Behavior change products live or die on design. If the friction of the new behavior exceeds the friction of the old one, people do not change. Loom’s design eliminated enough friction that the new behavior felt natural, sometimes easier, than the email or meeting it was replacing.
The Viral Loop That Required No Marketing Budget
The growth mechanism inside Loom is one of the clearest product virality loops in enterprise software history.
User A records a Loom and sends it to User B. User B watches the video in their browser. User B sees how easy and professional it looks. User B signs up for a free account. User B records a Loom and sends it to Users C, D, and E. The cycle repeats.
Every video sent was an acquisition channel. Every view was a product demo. Every recipient who signed up for free became a new sender who would trigger the loop again.
The key design decisions that made this loop work at scale deserve examination. The viewing experience required no account. If you had to sign up before you could watch a video, the friction would kill the loop before it started. Loom let anyone watch immediately, then offered signing up as a natural next step for people who wanted to record their own.
The recording interface was a Chrome extension, meaning it lived in the browser and required no separate download or app install. Zero-friction adoption at the recording end matched zero-friction consumption at the viewing end. The entire experience from “I want to explain something” to “they are watching my explanation” could be accomplished in under two minutes on the first use.
The free tier was generous enough to deliver genuine value while constraining enough to create natural upgrade incentives. Free users could record up to five minutes per video, which covers the vast majority of everyday communication use cases. Power users, sales teams, anyone who needed longer recordings or more storage, hit the ceiling naturally and had clear reasons to upgrade.
The conversion rate from free to paid was roughly 12%. Industry standard for freemium SaaS is 2-5%. Loom was 2-6x better than the category average. That rate reflects how well the free product was calibrated: useful enough that people formed habits around it, limited enough that people who relied on it heavily had genuine reasons to pay.
By 2019, Loom had a million users. The product had been growing almost entirely through word of mouth, through the viral loop embedded in its own usage, without a traditional marketing team. By 2021, 14 million users. 58 million videos recorded in that year alone.
The Pandemic Made It Inevitable
Loom’s timing in relation to COVID-19 is often described as luck. That is partially true and mostly incomplete.
The team had been building an async video communication tool since 2016. They had validated that people wanted it, grown to a million users, and proven the viral mechanism. The pandemic did not create the product. It validated the market at a scale and speed that would have taken a decade to reach organically.
When offices closed in March 2020 and remote work became the default overnight, the problems Loom was solving stopped being niche inconveniences and became the defining challenges of how work happened. How do you explain something complex to a colleague you cannot walk over to? How do you onboard a new employee you will never meet in person? How do you give feedback on a design without scheduling a video call that everyone has to block time for and dial into?
The answer, for tens of millions of people simultaneously, was: you record a video and send a link.
Loom had the product. It had the infrastructure. It had the free tier that let anyone try it without a credit card or a procurement process. It had the viral loop that spread it through organizations through normal usage. And it had the timing.
User growth from 4 million in early 2020 to 14 million by the end of 2021 was not luck. It was a decade of product work colliding with a structural shift in how people worked. The structural shift would have arrived eventually without COVID. The pandemic compressed the timeline from years to months.
The repositioning that the team executed during this period was sharp. Before 2020, Loom’s primary description was “free screen and video recording software,” which was accurate but undersold the actual use case. They shifted to “video messaging for work,” which communicated the real behavior they were enabling and the real problem they were solving. They launched “Loom for Teams” with features designed specifically for enterprise collaboration: centralized video libraries, enhanced security, admin controls. The product that had been growing as a bottom-up individual tool started to look and function like an enterprise communication platform.
This repositioning was not a pivot away from what was working. It was a sharpening of the message and the product to match the scale of adoption that was happening. The individual users who had been recording and sharing Looms for years were now inside companies that wanted to standardize on the tool. Loom needed to be ready for that enterprise conversation.
$200M Raised, $1.5B Valuation, Then the Market Turned
By 2021, Loom had raised $203 million across multiple rounds from Andreessen Horowitz, Sequoia Capital, Kleiner Perkins, Coatue, and ICONIQ. The 2021 Series C valued the company at $1.53 billion.
The fundraising history reflects both the quality of the business and the particular moment in which it happened. 2021 was the peak of the pandemic-era valuation bubble for SaaS companies. Companies with strong growth metrics and defensible product positions were valued at multiples that assumed a decade of continued hypergrowth. Loom had genuinely strong metrics: 14 million users, 200,000 companies, viral growth dynamics, and a product that had become indispensable for remote teams around the world.
But raising at a $1.53 billion valuation in 2021 meant that any future exit would be measured against that number. When Atlassian acquired Loom in October 2023 for $975 million, the headline was often written as “below valuation,” which was technically true. The more complete framing is that $975 million is an extraordinary outcome for a company that had been two weeks from closing down seven years earlier, and that had raised only $203 million in total, and that had grown almost entirely through product virality rather than expensive marketing or sales infrastructure.
The acquisition valued the company at a healthy multiple of its $50 million in ARR at the time of the deal. The 2021 peak valuation was a reflection of market conditions, not an intrinsic assessment of what Loom was worth as a business. Atlassian’s price reflected the business.
Why Atlassian Made Sense
Atlassian is the company behind Jira, Confluence, and Trello. Its core products are used by engineering and product teams to manage work, document processes, and track issues. The customer base overlaps almost completely with Loom’s heaviest users.
The strategic rationale for the acquisition was clear from both sides. Atlassian gets a best-in-class async video communication layer that integrates naturally with its existing suite. A Confluence page where you can embed a Loom video explaining a design decision. A Jira ticket where a product manager has recorded a two-minute explanation of requirements. A Trello board where a team lead has left a video update instead of a written comment.
Every one of those use cases is more valuable with Loom embedded than without it, and every integration deepens the stickiness of both products simultaneously. Atlassian was also, notably, already a Loom customer. The enterprise team at Loom had signed Atlassian on a paid plan before the acquisition conversation began. The acquirer had been using the product. They knew what it did.
From Loom’s perspective, the Atlassian platform represented distribution at a scale that would have taken the independent company years to replicate. Atlassian had tens of millions of users across its products. Getting Loom in front of those users through native product integration was worth more than any marketing campaign Loom could have run.
What the Loom Story Gets Right That Most Companies Miss
The growth playbook Loom executed is studied now because it worked so cleanly. But the mechanics are only part of the story.
The more important thing is the sequence. They started with something wrong, watched carefully, found the thing inside it that was right, stripped everything else away, and rebuilt around the right thing. That process, which sounds simple, requires the kind of intellectual honesty about failure that most founding teams struggle to practice.
Shahed’s observation about founders is directly relevant here: the common pitfall is spending too much time looking for the perfect idea before building anything. Opentest was not the right idea. But building Opentest was what revealed Openvid, which became Loom. If they had been waiting for certainty before starting, they would never have found the thing that worked.
The viral loop worked because the product earned it. Every video shared was a demonstration, and the demonstration was compelling enough to make recipients sign up. That compellingness was not accidental. It required the design obsession that Joe credited Shahed with bringing, the technical excellence that Vinay brought to the recording and delivery infrastructure, and the user research culture that kept the product improving constantly based on what real users were doing and saying.
The enterprise motion followed naturally from the bottom-up adoption. Loom never needed to convince IT departments to evaluate it. By the time procurement got involved, there were already hundreds of Loom users inside the company who had been sending videos for months. The sales motion was essentially: formalize something that is already happening.
And the timing, while partly luck, was also partly preparation. The team had been building the product for four years before the pandemic validated it at scale. The viral loop was already running. The enterprise features were already in development. When the world shifted, Loom was ready.
Twenty-five million users. Acquired by Atlassian for $975 million. Built on a Chrome extension launched when the company had two weeks of runway left.
The two weeks turned out to be enough.
Leave a Reply