In venture capital, the phrase "network effects" is deployed so frequently that it has nearly lost meaning. Every second pitch deck I review claims that its product has network effects. Most of those claims are either false or, more charitably, referring to something much weaker than what the term technically describes. The result is that genuine network effects — the structural, compounding kind that produce the most durable competitive advantages in the history of technology — get obscured in a fog of buzzword imprecision.
This matters enormously for seed-stage investors, because genuine network effects are one of the few business model characteristics that reliably predict venture-scale outcomes. Companies with true network effects do not merely grow faster than their competitors; they grow at the expense of their competitors, because the value differential between the platform with network effects and the platform without them widens non-linearly over time. The gap between being first and being second in a network-effects market is not a matter of degree. It is often a matter of existence.
Three companies illustrate this principle with particular clarity: Slack, Notion, and Figma. Each achieved multi-billion dollar outcomes from seed rounds that valued them at a small fraction of their eventual worth. Each built competitive moats that their well-funded competitors could not penetrate despite years of trying. And each did it through a specific form of network effects that is increasingly relevant to the categories where Swarm Capital invests.
Slack: The Communication Layer That Became the Work Graph
When Slack launched publicly in 2013, it entered a market with well-established incumbents: Microsoft Lync, HipChat, and a dozen smaller enterprise messaging tools. The conventional wisdom at the time was that enterprise communication was a commoditized feature, not a standalone business. Microsoft, Cisco, and IBM had distribution advantages, IT relationships, and bundling leverage that a startup could not overcome.
What happened instead is now legend. Slack grew from zero to over 8 million daily active users in less than three years — a growth rate that, at the time, had never been achieved by any B2B software company in history. By 2019, it had 10 million daily active users and $630 million in annual recurring revenue. In 2020, Salesforce acquired the company for approximately $27.7 billion, one of the largest software acquisitions ever completed.
The surface explanation for Slack's success is that it had a better product than its competitors. The deeper explanation is that it had network effects that its competitors structurally could not replicate. Let me be precise about what those effects were and why they compounded so powerfully.
Slack's first-order network effect was direct: a Slack workspace becomes more useful to each member as more of their colleagues join. This is true of any messaging platform. But Slack layered on a second-order effect that was far more powerful: the integration ecosystem. Every app, workflow automation, and notification that a team wired into Slack made that team's Slack workspace more valuable and more unique. A team that had spent six months building custom integrations — connecting their CRM, their project management tool, their analytics dashboards, their customer support system — had effectively encoded their entire operational workflow into a single interface. The switching cost was not the cost of learning a new messaging tool. It was the cost of rebuilding an entire operational stack.
This is the pattern we call "workflow embedding" — the progressive integration of a platform into a team's daily operational practice until the platform is not a tool the team uses but the environment in which the team's work exists. Once a platform achieves workflow embedding, the network effect reverses polarity: leaving the platform becomes progressively more painful as the integration depth increases, regardless of whether any alternative offers a superior feature set.
At Swarm Capital, we track workflow embedding as one of the highest-conviction early indicators of durable competitive advantage. The key metric is integration breadth per active team — how many unique integrations has a given team connected? Teams with high integration breadth are both the highest-value customers and the customers with the lowest churn risk. At Slack's IPO, the company disclosed that customers using 10 or more integrations had 3x lower churn than customers using one or two. This is workflow embedding expressed in revenue retention data.
Notion: The Document Layer That Became the Company Brain
Notion's network effects are different in character from Slack's, and in some ways more instructive for thinking about where collective intelligence creates value in the SaaS market. Slack's network effects are fundamentally social: they derive from the communication patterns of people who work together. Notion's network effects are fundamentally epistemic: they derive from the accumulation of shared knowledge within a company or community.
When Notion raised its Series A in 2019, the company was valued at approximately $800 million — a figure that struck many observers as aggressive for a note-taking and wiki product. By 2021, the company had raised at a $10.9 billion valuation, a 13x increase in less than two years. The growth was driven by an expansion in Notion's use case from individual productivity tool to company-wide knowledge management platform, fueled by network effects that became visible only as team adoption increased.
The mechanism is worth understanding in detail. An individual Notion user gets a certain amount of value from the product as a personal productivity tool — better organization, more flexible page structures, a linked database. This value is real but not network-driven; a single user would get similar utility from any well-designed note-taking app. But when multiple members of a team begin using Notion, something qualitatively different happens: the platform becomes the company's shared knowledge graph.
Meeting notes link to project documentation which links to product requirements which links to team wikis which link to onboarding materials. Each new connection makes the existing information more valuable, because context compounds. A six-month-old decision memo becomes dramatically more useful when it is linked to the subsequent implementation documentation and the retrospective analysis that assessed the outcome. Knowledge in isolation has linear utility. Knowledge in a connected graph has exponential utility — this is the epistemic network effect that Notion monetizes.
The practical consequence is that Notion workspaces, like Slack workspaces, become increasingly irreplaceable as their content volume and connection density increases. Migrating a Notion workspace with two years of connected documentation is not a matter of exporting files; it is a matter of reconstructing a knowledge architecture that took years of collective contribution to build. The organizational memory stored in a mature Notion workspace represents value that no individual team member fully comprehends, because it is a collective artifact — exactly the kind of emergent intellectual property that our collective intelligence investment thesis predicts will be the most defensible asset class in software.
Notion's go-to-market strategy — building virality into the product through templates that users share publicly, and pricing that made individual adoption frictionless before upselling to team plans — was a masterclass in engineering network effect activation at the lowest possible customer acquisition cost. The template ecosystem alone, with millions of community-created templates spanning every use case imaginable, represents an extraordinarily difficult-to-replicate collective intelligence asset that reinforces Notion's market position independently of any product feature advantage.
Figma: The Design Collaboration Layer That Upended a Category
Figma's story is perhaps the most dramatic demonstration of collaborative network effects overcoming an entrenched market leader. When Figma launched in 2016, Sketch dominated the UI design tool market with what appeared to be an insurmountable position: beloved by designers, deeply integrated into agency workflows, and backed by years of feature development. Figma's proposition — move design to the browser, make it real-time collaborative, make non-designers into first-class participants — was dismissed by many as technically interesting but commercially marginal.
What happened is a case study that business school programs will teach for decades. Figma grew not by building better design features than Sketch — though it eventually matched and surpassed them — but by exploiting the structural disadvantage of Sketch's single-player, desktop-native architecture. In a world where product development involves designers, product managers, engineers, and stakeholders who all need to engage with design artifacts, a collaborative design tool is not incrementally better than a single-player design tool. It is categorically different, because it eliminates an entire class of coordination overhead that consumes enormous time and introduces errors at every handoff.
By 2022, when Adobe announced its acquisition of Figma for $20 billion, the company had achieved something remarkable: it had not just captured Sketch's market but created an entirely new market category — product design as a team sport — that Sketch's architecture made structurally impossible to serve. The $20 billion acquisition price, ultimately blocked by European and UK regulators on antitrust grounds in 2023, was essentially the market's assessment of the value of collaborative network effects in a design workflow context.
The regulatory block on the Adobe acquisition, far from being a setback for Figma, demonstrated the company's durability as an independent entity. Figma raised $600 million at a valuation of $10 billion post-termination and continued growing. The competitive moat built by its collaborative network effects — the fact that design, engineering, and product teams across hundreds of thousands of companies had built their entire product development workflow around Figma's real-time collaboration model — proved robust against both a well-funded acquirer's plans and regulatory intervention.
The specific network effect mechanism at Figma is what we call "cross-functional embedding": the platform becomes essential not just to the core user persona (designers) but to the adjacent personas (engineers, product managers, stakeholders) who interact with design artifacts. When multiple professional functions build their workflows around a single platform, the switching cost is not just the cost of retraining one team. It is the cost of re-coordinating the workflows of every team that has adapted to the shared platform. This is the most powerful form of workflow lock-in, because it requires organizational-level decision-making to reverse — not individual decisions.
The Architecture of Compounding Network Effects
Slack, Notion, and Figma each built distinct variants of network effects, but they share a common architectural principle that distinguishes their outcomes from the majority of SaaS businesses that claim network effects but do not exhibit them. The principle is this: their network effects operate at the team or organization level, not the individual level.
Most "social" features in enterprise software create individual-level stickiness: a user has their personal history, preferences, and saved content on a platform. This creates switching friction but not network effects, because the friction disappears the moment the individual decides to switch. Team-level network effects are fundamentally different because the switching decision is not individual: it requires organizational consensus that virtually no single user can force. The organizational switching cost is the product of individual switching costs multiplied by the coordination cost of aligning everyone in the organization — a number that grows faster than team size.
This is why Slack was able to sustain $27 billion in enterprise value despite Microsoft's aggressive bundling of Teams with Office 365. Microsoft had enormous distribution leverage, near-zero incremental sales cost, and a product that was, by any reasonable assessment, technically comparable to Slack within a few years of launching. But the organizational switching cost for teams deeply embedded in Slack — with hundreds of integrations, years of shared message history, and workflows built around the Slack interface — was prohibitive. Microsoft Teams grew primarily by capturing new customers rather than by converting established Slack users, which is exactly what the theory of team-level network effects predicts.
Implications for Seed-Stage Investment
Understanding the architecture of compounding network effects changes how we evaluate seed-stage SaaS companies at Swarm Capital. The question is not whether a product has any network effects, but whether those effects operate at the organizational level and whether the embedding mechanism creates switching costs that grow faster than the customer relationship ages.
The signals we look for in early-stage companies are: first, evidence that team adoption spreads virally within organizations once a single user joins (Notion and Figma both exhibited explosive within-organization spread as early as their beta periods); second, evidence that usage becomes entangled with other tools in the customer's stack through integrations or data exports; third, evidence of cross-functional adoption, meaning that personas beyond the core user type are actively engaging with the platform; and fourth, evidence of content or data accumulation within the platform that becomes more valuable over time.
None of these signals require large scale to be visible. At the seed stage, we are looking for them in the behavior of the first ten or twenty customers. If those customers show strong within-organization spread, integration depth, and content accumulation in the first six to twelve months of using the product, we have early confirmation that the network effect architecture is working as designed.
The companies that compound network effects into generational businesses — the way Slack, Notion, and Figma did — do not discover their network effects late in their growth journey. They design them in from the beginning, as architectural decisions about how the product creates and stores value. That is the pattern we back at the seed stage: not just products that users love, but platforms designed from the ground up to become irreplaceable to the organizations that adopt them.
