How Loom Went From Zero to $975M Without a Traditional Sales Team
By Creatives Takeover · April 27, 2026
Viral video messaging built Loom’s success.
Most startups hire a sales team and hope the product follows. Loom did the opposite. They built a product so deeply embedded in how people work that the product itself became the most effective salesperson in the company. By the time Atlassian acquired them for $975 million in 2023, Loom had over 21 million users across 200,000 companies worldwide. The majority of those users arrived without a single cold call, a quota-carrying rep, or a structured outbound motion.
This is the story of how that happened. More importantly, it is the story of what it means for how you think about growth as an early-stage founder.
Three Founders, One Problem, and a Product That Should Not Have Worked
Loom was not supposed to be Loom.
Shahed Khan, Vinay Hiremath, and Joe Thomas started building in 2015 under the name OpenTest, a platform for user testing. The idea had logic behind it. The execution did not produce results. After months of trying to make it work, they shut it down and went back to the problem beneath the problem: how do people communicate clearly and efficiently when they are not in the same room?
The answer they kept circling back to was video. Not video calls, which require scheduling, attendance, and real-time availability from both sides. Not written documentation, which takes too long to produce and often fails to capture nuance. Something in between. A way to record yourself explaining something, send it as a link, and let the other person watch it whenever they were ready.
On paper, this sounds obvious. In practice, it was an idea the market had tried and failed with before. Video messaging tools had existed in various forms for years and had never found meaningful adoption outside of specific enterprise use cases. The conventional wisdom was that people did not want to be on camera, did not want to watch long videos, and did not want to add another communication tool to their already crowded workflows.
The founding team believed the conventional wisdom was wrong about the format, but right about the execution. The problem with previous video tools was not video. It was friction. Recording was complicated. Sharing was unreliable. Watching required effort. If you could reduce all of that friction to near zero, the behavior would follow.
That bet turned out to be correct. And the way they removed friction ended up being the same mechanism that drove all of their growth.
The Distribution Mechanic Hidden Inside the Product
Here is the insight that separates Loom from every other communication tool that tried and failed before it.
Every time a Loom user recorded a video and sent it to someone, that recipient clicked a link and landed on a Loom-hosted page to watch it. They did not need an account. They did not need to download anything. They just watched. And at the end of that experience, sitting directly beneath a video that had just demonstrated the product's value in the most practical way possible, was a simple prompt to record their own Loom.
This is not a growth hack. It is a distribution architecture. The product was designed so that every act of using it created a new potential user. Every team that adopted Loom became a network node that spread the tool to every team, client, and collaborator they communicated with. The more people used it, the more people encountered it for the first time. The more people encountered it, the more people started using it.
The technical term for this model is product-led growth. But the cleaner way to understand it is this: Loom made the product do the selling by ensuring that the best possible demonstration of its value happened at the exact moment a new person was most likely to be receptive to it. Not in a demo meeting. Not in a marketing email. In the moment of actual use, with real context, solving a real problem.
Sequoia, Kleiner Perkins, and Coatue all eventually backed the company. None of them were betting on a sales motion. They were betting on a mechanism.
The Moment the World Caught Up to the Product
By early 2020, Loom had solid traction but was operating in a world that had not fully understood why it needed asynchronous video. Most teams still worked in offices. The product was useful, but optional. Something people discovered and loved but rarely felt they could not live without.
Then the pandemic changed everything in a matter of weeks.
Remote work went from a niche arrangement to the default operating mode for hundreds of millions of knowledge workers overnight. Suddenly, the infrastructure of work that people had always taken for granted, the ability to walk to someone's desk, to point at a screen, to explain something in real time without scheduling a meeting, was completely gone. Loom had been built for exactly this world. It was ready before the world knew it needed it.
User numbers that had taken years to build doubled, then doubled again. The product spread through companies the same way it always had, one video at a time, one new viewer converted at a time, except now every knowledge worker on the planet had an urgent reason to need it. Loom raised a Series B at a $350 million valuation in 2020. Three years later, Atlassian paid $975 million to bring the company into its portfolio.
Not because a sales team closed that deal. Because 21 million people were already using the product every day and could not imagine going back.
What Founders Get Wrong About Sales
The word "sales" carries a very specific image in most founders' minds. It conjures a pipeline, a CRM, a team of reps working a list of leads, a VP of Sales brought in at Series A to build the function properly. This image is so dominant in startup culture that many founders treat it as inevitable. At some point, you will need a sales team. That is just how companies grow.
Sometimes that is true. But it is one version of truth among several, and applying it without examining whether it fits your product is one of the most expensive mistakes an early-stage company can make.
Sales is not a department. Sales is the process by which the right people discover your product, understand its value, and make a decision to keep using it. A team of reps running outbound is one way to execute that process. It is not the only way, and for many products it is not the most efficient or most scalable way. For some products, it is actively the wrong way, because it creates a dependency on human effort that the product itself could be doing better, faster, and at a fraction of the cost.
Loom never needed a rep to explain what Loom did, because watching a Loom video explained it perfectly. The demo was the product. The product was the demo. No rep could have delivered that message more clearly or more credibly than the experience of receiving a video from a colleague and realizing instantly why it was better than the email it replaced.
Finding the Mechanism Before You Build the Team
The lesson Loom teaches is not that sales teams are bad or that outbound is dead. Loom eventually built sales functions as it moved upmarket into larger enterprise accounts where buying decisions involve procurement, security reviews, and contract negotiations that products cannot navigate alone. The lesson is about sequence, and about clarity.
Before you think about who will sell your product, you need to understand how your product naturally moves through the world. Who experiences it first? What do they do after they experience it? Who do they share it with, and what motivates that sharing? What is the moment of clearest value demonstration, and how close to that moment does a new potential user encounter the product?
If you can answer those questions with specificity, you have the beginning of a sales methodology. And a methodology is what scales. A sales team without a methodology is expensive headcount running in a direction nobody has validated.
The founders who grow fastest are rarely the ones with the most aggressive sales culture. They are the ones who identified the right distribution mechanism early and built their entire go-to-market around it. For Loom, the mechanism was the video link. For Slack, it was the team invitation. For Dropbox, it was the shared folder. For Calendly, it was the booking page sent to schedule a meeting. In every case, the product created a moment where a non-user encountered the full value of the product in a real context, without friction, without a pitch, without a rep. That moment converted better than any sales call in history.
Your job as a founder is not to hire people who can explain your product. Your job is to build a product that explains itself, to the right people, at the right moment, through the natural act of being used.
When you get that right, the revenue follows. Not because you built a sales team. Because you built the right mechanism.
And mechanisms, unlike headcount, never sleep.