2. 1. A Taxonomy of Built-In Growth
Not all growth loops are created equal. "Viral" is a lazy word that collapses several distinct mechanisms into one. Here are the five real patterns:
| Pattern | Mechanism | Classic Example | CAC Impact |
|---|---|---|---|
| User-Generated SEO | Users create pages that rank on Google | Stack Overflow, Reddit, Quora | CAC approaches $0 over time |
| Embeddable Widgets | Product appears on other people's websites | YouTube embeds, Typeform, Calendly | Every embed is a free ad |
| Data Network Effects | Product gets better with more users, creating lock-in | Waze, Clearbit, ZoomInfo | Switching cost rises with scale |
| Workflow Contagion | Using the product forces others to use it | Slack, Figma, Notion, DocuSign | Users recruit users through work |
| Public Output | Product output is visible and attributable | Substack, Carrd, Webflow | Every customer is a billboard |
The strongest startups combine two or more patterns. Notion has workflow contagion (you share docs) and user-generated SEO (public Notion pages rank). Figma has workflow contagion (designers share files) and embeddable output (Figma embeds in docs). The compounding effect of stacking multiple growth patterns is what separates $10M companies from $10B companies.
3. 2. Pattern 1: User-Generated SEO Machines
The most powerful growth engine on the internet: your users create content, Google indexes it, strangers find it, and they become users too. The company does zero content marketing. The users are the content marketing.
How It Works
- User creates a page (question, profile, listing, review, template)
- Page has a unique URL with relevant keywords
- Google indexes the page
- Someone searches for those keywords, finds the page
- That person signs up to interact (answer, buy, review, fork)
- They create more pages. The loop compounds.
Why It Compounds
Every new user adds pages. Every page adds search surface area. More surface area means more traffic. More traffic means more users. The math is exponential in theory and logarithmic in practice — but even logarithmic growth on a base of millions of pages is enormous.
Stack Overflow has ~58 million questions. Each one is a landing page. Reddit has billions of posts. Each one is a landing page. These companies don't do SEO — their users do SEO by asking questions and posting content. The company just provides the structure.
The Structural Requirements
- Unique URLs per user action: every question, listing, or profile needs its own page
- Keyword-rich by default: user-generated content naturally contains search terms
- Low duplication: each page needs to answer a distinct query
- Value for anonymous visitors: the page must be useful before sign-up
- Clear CTA for the visitor: after consuming the content, there's an obvious next step
Modern Opportunities
| Vertical | Content Type | Search Volume Signal |
|---|---|---|
| AI prompt libraries | Prompts + results for specific tools | "ChatGPT prompt for [X]" — exploding |
| Integration recipes | "How to connect [Tool A] to [Tool B]" | Zapier alternatives are trending |
| Compliance checklists | SOC 2 / GDPR / HIPAA step-by-step | Perennial, high-intent commercial queries |
| Salary/compensation data | User-submitted salaries by role/location | Levels.fyi model in underserved markets |
| API documentation wikis | Community-maintained API docs + examples | "[API name] example" queries are massive |
4. 3. Pattern 2: Embeddable Widgets
Your product lives on other people's websites. Every embed is a free impression. Every impression has a "Powered by [You]" link. Every click on that link is a zero-cost acquisition.
The Mechanics
YouTube understood this first: let anyone embed a video with an <iframe>.
The video plays on someone else's blog, but the YouTube logo is right there. The viewer clicks through.
They watch another video. They never leave.
Calendly perfected the B2B version: "Pick a time" links in emails and websites. Every scheduling link is a Calendly ad shown to the exact right audience — people who schedule meetings, i.e., professionals who might pay for Calendly. The targeting is flawless because it's not targeting at all. It's just use.
What Makes a Good Embeddable
- Solves a problem on someone else's site: forms, scheduling, chat, payments, analytics dashboards
- Visually present: the embed must be seen, not hidden (unlike analytics scripts)
- Branded subtly: "Powered by X" or a small logo — enough to attribute, not enough to annoy
- Free tier is the embed: paid tiers remove branding or add features, but the free version spreads
The Freemium Paradox
With embeddable products, your free users are not a cost center — they're your marketing budget. Every free Typeform on a website is a billboard. Every free Calendly link in an email signature is a sales pitch. The more free users you have, the more paid users you acquire. This inverts the usual freemium anxiety ("too many free users!") into a growth asset.
The math: if 1% of people who see a "Powered by X" link click through, and 5% of those sign up, and 3% of those convert to paid — then every 1 million embed impressions produces 15 paying customers. For free.
5. 4. Pattern 3: Data Network Effects
Every user makes the product better for every other user. Not through social features — through data. The more people use the product, the more data it accumulates, and the more accurate/useful/comprehensive it becomes.
How Data Network Effects Differ from Social Network Effects
| Property | Social Network Effect | Data Network Effect |
|---|---|---|
| Mechanism | More friends → more value | More usage → better product |
| User awareness | Users know they benefit from others | Users often don't realize |
| Defensibility | Strong but fragile (MySpace → Facebook) | Strong and durable (data is sticky) |
| Cold start problem | Severe — empty network is useless | Moderate — product can work with less data |
| Examples | Facebook, LinkedIn, Discord | Waze, Clearbit, Google Maps, Grammarly |
The Flywheel
- Users contribute data (often passively, just by using the product)
- Data improves the model/algorithm/database
- Better product attracts more users
- More users contribute more data
- Competitors can't catch up because they don't have the data
Waze is the canonical example: every driver's GPS data improves traffic estimates for every other driver. You don't "share" your data socially — you just drive, and the product gets better. The growth is invisible and inevitable.
Where Data Network Effects Are Underexploited
- Pricing intelligence: every user's pricing data improves benchmarks for everyone (see: PriceLevel, Vendr)
- Error monitoring: more apps reporting errors means better stack trace deduplication and auto-fix suggestions
- Contract review: every contract reviewed by AI improves the model for all future reviews
- Hiring assessments: more candidate data improves predictive accuracy of assessment tools
- Infrastructure cost optimization: more cloud bills analyzed means better optimization recommendations
6. 5. Pattern 4: Workflow Contagion
The most aggressive growth pattern: using the product forces other people to encounter it. Not because you "invite" them (that's just referral marketing with extra steps). Because doing your job with the product puts it in front of your colleagues, clients, or collaborators.
The Contagion Spectrum
| Level | Mechanism | Example |
|---|---|---|
| Exposure | Others see the product in use | Someone shares a Loom video |
| Interaction | Others must interact with the product | Someone sends a Calendly link |
| Collaboration | Others must use the product to work together | Someone invites you to a Figma file |
| Dependency | Others cannot do their job without it | Your whole team is on Slack |
Each level is stickier and more growth-generative than the last. Exposure is weak — you see the product but don't need it. Dependency is unbreakable — you can't quit Slack because your team is on Slack, and they can't quit because you're on Slack.
Why Workflow Contagion Beats Referral Programs
Referral programs say: "Tell your friend, get $10." Workflow contagion says: "Your colleague literally cannot review this document unless they sign up." One is a bribe. The other is physics. DocuSign doesn't need a referral program because every contract sent is a mandatory product demo for the signer.
Designing for Workflow Contagion
- Multi-party workflows: the product must involve at least two people
- External sharing: output goes to people outside the company, not just inside
- Frictionless onboarding for receivers: the person on the other end must be able to use it without a 20-minute setup
- Value demonstration on first contact: the receiver should immediately see why this tool is better
7. 6. Pattern 5: Public Output as Marketing
Everything your users create with your product is visible to the world — and visibly made with your product. Every Substack newsletter has "Subscribe on Substack" at the bottom. Every Carrd site has a tiny Carrd badge. Every Webflow site can be identified by anyone who views the source.
The Attribution Chain
- User builds something with your tool (website, newsletter, app, design)
- They publish it to the internet
- Others see it and think "this looks good, how was it made?"
- They find the attribution link and sign up
- They build something and publish it. The loop continues.
The magic: the quality of the user's output is your marketing material. If people build beautiful websites with your tool, those websites advertise you better than any landing page. Your customers are your portfolio.
Public Output + Quality Filter = Premium Positioning
Squarespace understood this: make it hard to build an ugly site, and every Squarespace site becomes a testimonial. The constraint is the feature. If your tool's defaults produce professional results, every user output says "this tool makes things look good" without you spending a dollar on ads.
The anti-pattern: tools where user output is ugly or generic. If every site built with your page builder looks the same, the attribution hurts rather than helps. The public output model only works when the output is something users are proud to share.
8. 7. 15 Startups with Built-In Growth
Each of these startup ideas has growth structurally wired into the product. Not "add a referral program later" but "the business model is the growth model."
| # | Startup | What It Does | Growth Pattern | Why Growth Is Built-In |
|---|---|---|---|---|
| 1 | OpenTerms | AI-generated plain-English summaries of any website's Terms of Service | UGC-SEO + Public Output | Every summary is a Google-indexed page. Users share "look how insane this TOS is" on social media. Each summary links back. Thousands of brand-name domains as long-tail SEO. |
| 2 | DemoReel | Record and share interactive product demos (click-through, not video) | Embeddable + Workflow Contagion | Sales reps embed demos in emails and landing pages. Every prospect sees "Made with DemoReel." Prospects who become sellers create their own demos. Demo links spread through sales pipelines. |
| 3 | PriceRadar | Anonymous SaaS pricing benchmarks from real invoices | Data Network Effects + UGC-SEO | Every submitted invoice improves benchmarks. "What does [Tool X] actually cost?" pages rank on Google. More data → more accurate → more users submit. Competitors can't catch the data moat. |
| 4 | StatusEmbed | Beautiful embeddable status pages for any SaaS | Embeddable Widget | Every customer's status page shows "Powered by StatusEmbed" to that customer's users. A SaaS with 10K users gives StatusEmbed 10K impressions/month. Growth scales with customers' growth. |
| 5 | ContractPilot | AI contract review that learns from every document | Data Network Effects + Workflow Contagion | More contracts reviewed → better AI. Lawyers send contracts to clients for signature through the platform. Every counterparty sees the product. Data moat deepens with every deal. |
| 6 | ChangelogHQ | Beautiful public changelogs with email/RSS subscriptions | Embeddable + Public Output + UGC-SEO | Every changelog is a public page indexed by Google. Users embed the widget in their app. "[Product] changelog" is a real search query. Each customer's users see the tool. |
| 7 | InvoiceFlow | Send invoices that recipients can pay in one click | Workflow Contagion (Dependency level) | Every invoice sent is a product demo. Recipients think "I want to send invoices this clean." The invoice footer says "Sent with InvoiceFlow." Recipient becomes sender. Pure DocuSign mechanics. |
| 8 | SnippetDB | Community-curated code snippet database with copy-paste examples | UGC-SEO | Every snippet is a page. "How to [do X] in [language Y]" is the most common developer search pattern. Contributors are motivated by reputation. Millions of long-tail pages possible. |
| 9 | FeedbackBar | Embeddable feedback widget for any website | Embeddable Widget + Data Network Effects | Widget appears on customer's site, visible to all their users. "Powered by FeedbackBar" on every widget. More feedback collected → better sentiment analysis → better product. Free tier maximizes spread. |
| 10 | BoardView | Public company dashboards (revenue, users, metrics) for transparent startups | Public Output + UGC-SEO | Founders share dashboards on Twitter/LinkedIn for social proof. "Open startup" movement drives adoption. Every dashboard is a public page. "[Company] revenue" becomes a search query. |
| 11 | ProposalKit | Interactive proposals that clients can comment on and approve inline | Workflow Contagion | Every proposal sent is a mandatory product demo. Clients interact with the tool to approve. Freelancers and agencies on the receiving end think "I want to send proposals like this." |
| 12 | WaitlistPage | One-click waitlist landing pages with referral mechanics | Embeddable + Public Output + Workflow Contagion | Every waitlist page is a "Made with WaitlistPage" ad. Referral mechanics make signups invite more signups. Founders share waitlist numbers publicly. The tool markets itself through its users' launches. |
| 13 | CertBadge | Verifiable certification badges (SOC 2, ISO 27001, GDPR) that companies embed on their site | Embeddable Widget | Every badge on every customer's website is an impression. Enterprise buyers click badges to verify, landing on CertBadge. Trust is the product — the badge must be visible to work, which means the embed must be public. |
| 14 | RecruitProof | Candidate-verified company reviews (Glassdoor alternative with identity verification) | UGC-SEO + Data Network Effects | Every review is a "[Company] reviews" page. Identity verification makes reviews more trustworthy than competitors. More reviews → more trustworthy → more traffic → more reviews. Recruiters share positive profiles with candidates. |
| 15 | SupportWidget | AI-powered support chat widget trained on your docs | Embeddable Widget + Data Network Effects | Widget lives on customer's site, visible to all visitors. "Powered by SupportWidget" on every chat window. More conversations → better AI responses. Free tier for small sites maximizes widget spread across the web. |
9. 8. The Economics: Why Built-In Growth Wins
CAC Comparison
| Strategy | Typical B2B SaaS CAC | Trend Over Time |
|---|---|---|
| Paid ads (Google, LinkedIn) | $200–$2,000 | Increases as competition rises |
| Outbound sales (SDR team) | $500–$5,000 | Increases with salary inflation |
| Content marketing | $100–$500 | Decreases slowly (compounding) |
| Referral programs | $50–$200 | Flat (cost per referral is fixed) |
| Built-in growth | $5–$50 | Decreases rapidly (compounding) |
The difference is structural. Paid ads get more expensive every year because you're bidding against more competitors for the same keywords. Built-in growth gets cheaper every year because each new user adds surface area that brings in more users. The curves go in opposite directions.
The LTV/CAC Flywheel
When CAC is near zero, almost any LTV produces a healthy ratio. A $50/month product with $10 CAC has a 60:1 LTV/CAC ratio at 12-month retention. This means you can offer an aggressively generous free tier (which drives more built-in growth) and still print money on the paid tier. The free tier isn't charity — it's your cheapest marketing channel.
Why VCs Love This Model
Startups with built-in growth have three properties investors obsess over:
- Capital efficiency: less money spent on sales and marketing means higher margins and longer runway
- Predictable scaling: growth is a function of usage, not ad spend, so it's more predictable
- Defensibility: data network effects and workflow lock-in create moats that competitors can't buy their way through
10. 9. Anti-Patterns: Growth That Looks Built-In But Isn't
"Invite Your Friends" Is Not Built-In Growth
A modal that says "Invite 5 friends to unlock premium features" is a referral program, not built-in growth. Built-in growth happens without the user thinking about growth at all. When a Calendly user sends a scheduling link, they're not "promoting Calendly" — they're scheduling a meeting. The growth is a side effect of the use case, not a deliberate action.
"Powered By" Badges on Invisible Products
A "Powered by" badge on a backend analytics tool that end users never see is worthless. The embed model only works when the product is visible to the right audience. A support widget works because customers see it. A database optimization tool doesn't because it runs in the background. Know which category your product is in.
Social Sharing Buttons
Adding "Share on Twitter" to your product is not built-in growth. Nobody clicks those buttons. Real public output growth comes from the user's core workflow producing shareable artifacts, not from bolted-on share buttons. Substack newsletters get shared because the content is interesting, not because there's a share button.
Network Effects That Aren't
Many products claim "network effects" when they really just have economies of scale. The test: does one user's activity directly improve the experience for another user? If yes, that's a network effect. If the product just gets cheaper per-unit at scale, that's economics, not a growth loop.
11. 10. Builder's Playbook: Designing for Built-In Growth
Step 1: Identify the Growth Surface
Ask: "When my user uses this product, who else sees it?" If the answer is "nobody," you don't have built-in growth. Redesign until the answer is "their clients," "their audience," "their colleagues," or "Google."
Step 2: Make the Free Tier the Growth Tier
The free tier should be the version with maximum visibility: branded embeds, public pages, "Powered by" badges. The paid tier removes branding and adds features. Free users are your distribution. Paid users are your revenue. Don't cripple the free tier — brand it.
Step 3: Design for Zero-Friction First Contact
The person who encounters your product through built-in growth (the scheduling link recipient, the embed viewer, the search result visitor) is not looking for your product. They're doing something else. The first contact must be:
- Instant (no loading screens, no sign-up walls for viewing)
- Self-explanatory (they understand what the tool is in 3 seconds)
- Impressive (the quality of the experience makes them want it)
Step 4: Stack Multiple Patterns
One growth pattern is good. Two is great. Three is a machine. The 15 startups above were deliberately designed to combine patterns:
- ChangelogHQ: Embeddable + Public Output + UGC-SEO (triple stack)
- WaitlistPage: Embeddable + Public Output + Workflow Contagion (triple stack)
- ContractPilot: Data Network Effects + Workflow Contagion (double stack with moat)
- PriceRadar: Data Network Effects + UGC-SEO (double stack with moat)
Step 5: Measure the Right Thing
Built-in growth companies should track:
| Metric | What It Measures | Target |
|---|---|---|
| Organic signup % | % of signups from non-paid channels | >70% |
| Viral coefficient | New users generated per existing user | >0.5 (every 2 users bring 1 more) |
| Embed impressions | Monthly views of embedded widgets | Growing faster than user count |
| UGC pages indexed | User-generated pages in Google's index | Linear or super-linear growth |
| Time-to-value for receivers | How fast a non-user can interact with the product | <30 seconds |
If your organic signup percentage is below 50%, your built-in growth isn't working yet. Go back to Step 1.