Most growth-loop articles recycle the same four B2C examples: Pinterest pins, Dropbox referrals, Airbnb listings, Slack invites. This piece maps 11 working B2B SaaS growth loops with the specific input, action, output, and reinvestment step for each. You'll see how Figma's collaboration loop, Notion's template loop, Loom's video-share loop, Stripe's docs loop, Calendly's invite loop, Gong's data network loop, Linear's power-user loop, Vercel's framework loop, Webflow's published-site loop, Typeform's response loop, and Intercom's chat-widget loop actually compound, with a downloadable diagram template at the end.
What is a growth loop and why do B2B SaaS companies need one?
A growth loop is a closed system where the output of each user cycle becomes the input that acquires the next user, so growth compounds without proportional new spend. Funnels are linear (money in, customers out). Loops are circular (customers in, more customers out).
According to Reforge's Brian Balfour, every durable high-growth company runs on at least one compounding loop, not a funnel. Funnels hit a ceiling when ad costs rise. Loops keep compounding because each cycle's output is the next cycle's input.
B2B SaaS companies need loops because:
- CAC inflation: paid B2B CAC has roughly doubled since 2019, making funnel-only growth unaffordable
- Buyer behavior: B2B buyers research in dark social, AI engines, and peer networks where you cannot buy your way in
- Defensibility: a loop creates a flywheel that competitors cannot copy by spending more
The four archetypes you'll see in the 11 examples below are viral loops (user-to-user spread), content/UGC loops (search and discovery), paid loops (revenue funds ads), and data-network loops (more usage = better product = more usage).
What are the best growth loop examples from real B2B SaaS companies?
Below are 11 worked B2B SaaS growth loops, each diagrammed as Input -> Action -> Output -> Reinvestment. Pick the one closest to your product shape and reverse-engineer it.
| # | Company | Loop Type | Core Mechanic |
|---|---|---|---|
| 1 | Figma | Collaboration (viral) | Browser-link sharing |
| 2 | Notion | Template / UGC (content) | User-created templates rank in Google |
| 3 | Loom | Video-share (viral) | Recipient watches, signs up |
| 4 | Stripe | Developer content (content) | Docs rank, devs cite |
| 5 | Calendly | Meeting-invite (viral) | Every link exposes one new person |
| 6 | Gong | Data network (defensibility) | More calls = better AI |
| 7 | Linear | Power-user social (advocacy) | Shortcut delight = Twitter posts |
| 8 | Vercel | Framework (open source) | Next.js usage pulls in hosting |
| 9 | Webflow | Published-site (content) | Sites rank in Google with badge |
| 10 | Typeform | Response (viral badge) | Every form respondent sees brand |
| 11 | Intercom | Chat-widget (embedded) | 'We run on Intercom' on customer sites |
How does Figma's collaboration loop work?
Figma's loop turns every shared design file into a viral surface. Because designs open in a browser with no install, the cost of pulling a non-designer into the product is a single link.
Figma's collaboration loop:
- Input: Active designer creates a file in Figma
- Action: Designer shares a browser link with a PM, engineer, or exec to comment or view
- Output: Recipient creates a free Figma account to comment, becoming a new active user
- Reinvestment: New account holders invite their own teammates, expanding Figma inside the company
The key design choice: Figma's free plan allows unlimited viewers and commenters, only editors pay. The people who spread the product never hit a paywall. Per First Round's analysis, this collaboration loop is what let Figma expand from design teams into entire product organizations.
This is also why competitors with desktop-only tools (Sketch, early InVision) lost: their files could not become a one-click viral surface.
How does Notion's template loop work?
Notion's template loop is the canonical B2B content loop. Power users build a workspace they love, package it as a template, submit it to the public gallery, and Google indexes the result.
Notion's template loop:
- Input: A power user builds a useful internal workspace (CRM, OKR tracker, content calendar)
- Action: Power user submits the workspace as a public template, often to drive newsletter signups or template sales
- Output: Google and AI engines index the template page, which ranks for queries like 'notion crm template'
- Reinvestment: New visitors duplicate the template, become Notion users, and eventually publish their own templates
The scale is staggering. According to Minuttia's analysis, Notion's template gallery ranks for over 60,000 organic keywords in the US and pulls over 287,000 monthly organic visitors. The creators are not paid by Notion. They build templates because Notion's distribution converts their audience.
This loop also runs at Webflow, Figma, Airtable, Canva, Miro, and Adobe Express. The pattern: any product where users build artifacts can run a UGC content loop, provided the gallery is indexable and the templates are duplicatable in one click.
How does Loom's video-share loop work?
Loom turned async video messages into a viral B2B distribution channel. Every recipient is a potential new sender.
Loom's video-share loop:
- Input: A user records a screen + face video to send instead of a meeting
- Action: User shares a Loom link with a colleague, customer, or prospect
- Output: Recipient watches the video on Loom's branded player, sees 'Get Loom for free' CTA, signs up to send their own
- Reinvestment: New senders share Loom videos with their networks, expanding the surface
Loom amplifies the loop with a constraint. On the free plan, users can store roughly 25 videos. Once they hit the cap, they either pay or invite teammates to unlock more, per the Eleken teardown of PLG strategies. This converts the cap from a limitation into a referral trigger.
Like Figma, Loom's loop only works because the playback experience requires zero install and brand presence is unavoidable.
How does Stripe's developer-content loop work?
Stripe runs a content loop powered by developers, not marketers. Every doc, code sample, and SDK becomes an indexable asset that pulls new developers into the product.
Stripe's developer-content loop:
- Input: A developer integrates Stripe and reads the docs
- Action: Developer copies a code sample, blogs about the integration, or answers a Stack Overflow question with a Stripe-shaped answer
- Output: That blog post / answer / GitHub repo ranks for payment-integration queries
- Reinvestment: New developers searching for 'how to add subscription billing in Next.js' land on developer-written content, sign up, integrate, write more content
Stripe's docs are famous for the three-column layout with live, runnable code samples for every endpoint. Per Will Larson's teardown, Stripe's growth strategy was product-led, developer-centric self-service from day one, where startups could integrate without ever talking to sales.
The loop's reinvestment step is the underrated piece: every developer who integrates becomes a multiplier through their personal blog, conference talks, employer's engineering blog, and open-source contributions.
How does Calendly's meeting-invite loop work?
Calendly is the cleanest viral loop in B2B SaaS because the act of using the product unavoidably exposes a non-user to it.
Calendly's meeting-invite loop:
- Input: User wants to schedule a meeting without back-and-forth
- Action: User sends a Calendly scheduling link via email, signature, LinkedIn bio, or website
- Output: Recipient books a slot, sees Calendly's interface, recognizes the value (no scheduling ping-pong)
- Reinvestment: Recipient signs up to send their own Calendly link, often within days of receiving one
Per OpenView's analysis, there is no single-player version of Calendly. The product only delivers value when at least two people are involved, which guarantees every active user is also a marketer.
The scheduling link spreads passively through email signatures and LinkedIn profiles, exposing thousands of non-users per active user per year. The 'powered by Calendly' badge on every booking page acts as a perpetual ad.
How does Gong's data-network loop work?
Gong runs a B2B data-network loop, the rarest and most defensible loop type. More usage produces better AI, which produces more usage.
Gong's data-network loop:
- Input: Customer connects calls, emails, calendar, and CRM to Gong
- Action: Gong's AI analyzes interactions, generating deal insights, coaching, and forecasts
- Output: Better predictions and call summaries make Gong stickier, customers connect more data sources (Gong integrates with 300+ tools across the revenue stack)
- Reinvestment: Aggregated, anonymized patterns improve models for every customer, raising the floor for new customers
Per VentureBeat's coverage of Gong's research, AI-using sales teams generate 77% more revenue per rep. Gong CEO Amit Bendov argues the company's decade of accumulated revenue data is the moat: 'Anybody that would want to build something like that... it's not a small feature, it's 10 years in development.'
Data-network loops take 12-24 months to compound. They are not appropriate for early-stage SaaS without scale, but they are the strongest moat once they kick in.
How does Linear's power-user social loop work?
Linear does not run a viral or content loop in the classic sense. It runs a power-user advocacy loop where product polish generates social posts that feed inbound demand.
Linear's power-user social loop:
- Input: Engineer or PM uses Linear's keyboard-shortcut-driven interface
- Action: User experiences a moment of delight (cmd+K, instant search, clean keyboard nav) and posts about it on Twitter / Hacker News / Reddit
- Output: Other engineers see the praise from peers they trust, evaluate Linear, switch from Jira
- Reinvestment: New users post their own delight moments, compounding social proof
Linear's keyboard-shortcut-first design (cmd+K command palette, single-key issue actions) is engineered for this loop. The company invests in craft and animation polish that other PM tools treat as cosmetic, because that polish is the loop's input.
This loop only works in tooling categories where the user is also the buyer (developer tools, design tools, data tools). It does not work in HR or finance SaaS where end-users do not control purchasing.
How does Vercel's framework loop work?
Vercel runs a framework-driven open-source loop. The free, open-source framework (Next.js) creates inbound demand for the paid hosting product.
Vercel's framework loop:
- Input: Vercel's team builds and maintains Next.js as open-source software
- Action: Developers adopt Next.js for personal projects, then bring it into their employer's stack
- Output: When those developers need to deploy Next.js apps, Vercel is the path of least resistance (built by the same team, optimized integrations)
- Reinvestment: Hosting revenue funds more Next.js development, which expands adoption, which expands the funnel for hosting
Next.js has become one of the most-used React frameworks, and per Vercel's case study on Cursor, companies are now building their own internal growth iteration loops on top of Vercel's primitives (Microfrontends, Flags, Edge Config). The loop has expanded from individual developers to platform teams.
Framework loops are slow (12-18 months minimum) and capital-intensive but extremely defensible once entrenched.
How does Webflow's published-site loop work?
Webflow runs a published-site loop where every customer site shipped becomes a distribution surface.
Webflow's published-site loop:
- Input: Designer or agency builds a site in Webflow
- Action: Site goes live, often with 'Made in Webflow' branding visible to visitors and indexable in HTML
- Output: Site visitors who like the build click the badge, see Webflow's homepage, and explore the platform
- Reinvestment: New designers sign up, build their own sites, ship more Webflow-powered URLs into the world
Per Webflow's customer story, Typeform itself migrated to Webflow and now publishes up to 100 site updates per day, with technical SEO health rising from 48 to 95. Each of those updates is another Webflow-built page in Google's index.
The 'Made in Webflow' badge is removable on paid plans, but the showcase gallery and template ecosystem (which mirror Notion's UGC loop) keep compounding regardless.
How does Typeform's response loop work?
Typeform's response loop turns every form respondent into a brand exposure event.
Typeform's response loop:
- Input: A user creates a survey, lead form, or quiz in Typeform
- Action: User shares the form via email, embed, or link to their audience
- Output: Every respondent fills out the form, sees Typeform's distinctive UX (one question at a time, conversational), notices the 'Powered by Typeform' badge
- Reinvestment: A subset of respondents (often marketers and founders) sign up to build their own Typeforms
The loop is high-volume, low-conversion. A single Typeform with 10,000 respondents may yield only 50-100 signups, but the cost per impression is zero. The badge can be removed on higher tiers, which means the loop is strongest at the bottom of the customer base where new prospects are.
This loop pattern (embedded-badge in a customer-facing artifact) is the same one Intercom, Webflow, Mailchimp, and Squarespace use.
How does Intercom's chat-widget loop work?
Intercom's loop is the cleanest example of an embedded-badge loop. Customers install the chat widget on their site and Intercom's brand rides along.
Intercom's chat-widget loop:
- Input: A SaaS company adds the Intercom chat widget to their site for support
- Action: Site visitors interact with the widget, see Intercom's UX, notice 'We run on Intercom' (especially in earlier years and lower-tier plans)
- Output: A subset of those site visitors are themselves SaaS founders or product managers who recognize Intercom's product and sign up
- Reinvestment: New customers install the widget on their own sites, expanding the surface area
Per How They Grow's analysis, Intercom's customers become distributors the moment they add the widget. The early 'We run on Intercom' link drove visitors back to personalized landing pages with dynamic keyword insertion based on the referring site's category.
The loop weakened as Intercom grew upmarket and removed the badge from higher-tier plans, but it was instrumental in getting Intercom to its first $50M ARR per BDOW's profile.
What is the difference between a viral loop and a content loop?
A viral loop spreads user-to-user inside the product (Figma file shares, Calendly invites, Loom videos). One user's action directly exposes a specific other person to the product. Cycle time: hours to days. K-factor (new users per existing user) is the key metric.
A content loop spreads through search and discovery (Notion templates, Stripe docs, Webflow showcase). User activity creates indexable assets that pull strangers in via Google or AI engines. Cycle time: weeks to months. The key metric is content velocity multiplied by ranking conversion rate.
| Attribute | Viral loop | Content loop |
|---|---|---|
| Spreads via | Direct user-to-user | Search / AI / discovery |
| Cycle time | Hours-days | Weeks-months |
| Compounding visible | 30-90 days | 6-12 months |
| Key metric | K-factor (>1.0 ideal) | Content velocity x conversion |
| Best fit | Multiplayer products | Artifact-creating products |
| Examples | Figma, Loom, Calendly | Notion, Stripe, Webflow |
Many B2B SaaS products run both simultaneously. Figma has a collaboration loop (viral) and a community plugins / templates loop (content). Notion has a template loop (content) and a referral loop (viral).
Which growth loop type fits an early-stage B2B SaaS?
Early-stage B2B SaaS companies (pre-Series A, under $2M ARR) should default to a viral or collaboration loop because they compound fastest and require zero distribution budget. Pick based on your product shape:
- Inherently multiplayer product (collaboration, scheduling, sharing): build a viral loop like Figma, Loom, or Calendly. The loop trigger should be inseparable from the core feature.
- Single-player product that creates artifacts: build a UGC / template loop like Notion or Webflow. Make artifacts public-by-default and indexable.
- Developer tool: build a docs / framework loop like Stripe or Vercel. Invest in code samples, SDKs, and runnable examples.
- Has structured customer data: skip the data-network loop until $20M+ ARR. The minimum data scale to make the AI loop work is too high for early-stage.
Avoid paid loops until you have repeatable LTV:CAC above 3:1 and a clear payback period under 12 months. Avoid content-only loops until you have at least 5 loop-aware writers shipping weekly, or you'll just be doing slow blog SEO.
How long does a growth loop take to compound?
Growth loops compound at different rates depending on type. Plan accordingly.
- Viral loops: 30-90 days to show clear compounding, assuming K-factor above 0.5. If you're at 0.3 after 90 days, the loop has a leak (usually in the recipient experience or signup friction).
- UGC / template loops: 6-12 months. Google indexing and AI citation pools take time to refresh. Notion's template gallery took roughly 3 years to reach its current 287K monthly visitor scale.
- Developer-content loops: 6-18 months. Same SEO compounding curve, plus you need a critical mass of integrators publishing externally.
- Embedded-badge loops (Typeform, Intercom): months to a year. Volume of customer-site impressions is the input, so you need a few thousand active customers before the loop is visible.
- Data-network loops (Gong): 12-24 months. The moat depends on accumulated training data crossing a quality threshold.
Per Brian Balfour's framing, loops behave like compound interest: the first 6 months feel slow, months 12-24 produce the visible breakout. Most teams kill loops before they compound. Don't.
How do I diagram my own growth loop?
Use the same 4-bullet structure shown for each company above. Force yourself to fill every slot before you ship a single experiment.
The 4-bullet diagram template:
- Input: What user action or asset enters the loop? (e.g., 'a designer creates a Figma file')
- Action: What does the user do that exposes the product to a new person? (e.g., 'shares a browser link')
- Output: What does the recipient experience, and what's the conversion event? (e.g., 'opens link, comments, creates account')
- Reinvestment: How does the new user feed back into step 1? (e.g., 'invites their own teammates')
Validation checklist before you build:
- [ ] The action is part of the core workflow, not a bolt-on referral CTA
- [ ] The recipient gets value before being asked to sign up
- [ ] The output is measurable (link clicks, signups, indexed pages)
- [ ] The reinvestment step closes the loop within one cycle, not three
- [ ] You can name the metric that, if it doubled, would visibly accelerate growth
If any box is unfilled, you don't have a loop yet, you have a marketing campaign. Map two or three candidate loops and pick the one with the shortest cycle time and highest output multiplier.
| Loop Type | Company Examples | Primary Input | Compounding Output | Time to Compound |
|---|---|---|---|---|
| Collaboration loop | Figma, Loom | Active editor | Invited viewers/commenters | Weeks |
| Template / UGC loop | Notion, Webflow | Power user creates template | SEO traffic + new signups | 6-12 months |
| Content / docs loop | Stripe, Vercel | Developer reads docs | Backlinks + Google ranking | 6-18 months |
| Embedded badge loop | Typeform, Intercom, Webflow | End-user encounter | Branded click-through | Months |
| Meeting/invite loop | Calendly | Scheduling link sent | Recipient signs up | Days |
| Data network loop | Gong | Customer data ingested | Better AI = more usage | 12-24 months |
| Power-user social loop | Linear | Shortcut/feature delight | Twitter/Reddit posts | Weeks |