Tactical playbook · Factor 5 of 7 · AUG v3

How to improve SaaS advocacy in 2026

A k-factor and viral-loop playbook for SaaS founders. 10 features ranked by k-factor contribution, worked examples from Discord (Advocacy 9), Notion (10), Linear (9), and why cash-incentive referral programs underperform product-aligned ones.

The short answer

Advocacy compounds when shares produce public artifacts (URLs, screenshots, embeds) rather than private interactions. The single highest-leverage move: ship embeddable widgets — every embed creates a permanent discovery channel from another site to yours + acts as a backlink + lifts Acquisition without paid spend. Second-highest: per-result share cards (1200×630 PNG + pre-composed tweet text). Every result becomes potentially shareable. Most SaaS founders under-invest in Advocacy because the ROI is invisible at ship-time but compounds at platform-time.

Diagnostic — is your Advocacy below 7?

On the GrowthFriction 1-10 rubric, you're below 7 if any of:

If any of those holds, you're leaving compound Acquisition on the table. Advocacy is the free-acquisition layer that turns every existing user into a Acquisition channel.

The 7 advocacy metrics (instrument all of these)

The 10 features ranked by k-factor contribution

  1. Embeddable iframe (+0.12 k-factor; compounds over years). Other sites embed your tool — each embed is a permanent discovery channel from their audience. GrowthFriction's embeddable badge is the canonical example: every embed shows the product's composite score + brand mark on a third-party page.
  2. Per-result share card (1200×630 PNG + pre-composed tweet)(+0.08). Every result page has a “Share as image” button. SVG-generated card with the specific result + brand watermark. Pre-composed tweet text with relevant hashtags. Linear, Figma, GrowthFriction all do this.
  3. Bookmarkable result URLs with title (+0.05). When users share URL, preview card (OG image) shows the specific result. The bookmark itself is the share mechanism — every URL paste in Slack/Discord/iMessage is potential recruitment.
  4. “Compare with friend” functionality (+0.04). User invites friend to do same comparison, calculation, or audit. Native viral mechanic. Strava's “follow your friends” is the prototype.
  5. Public collection / watchlist URL (+0.04). Users share curated lists they've built on your site. Lists are shareable artifacts that survive the original creator (curators get cited, lists get linked).
  6. OpenGraph images per page (not just homepage) (+0.03). Rich preview when any URL is pasted in Slack/Discord/iMessage/Notion. Every page becomes a preview-card recruitment vehicle. Most SaaS only ships homepage OG image — leaving 95%+ of share surface flat.
  7. Leaderboard / public rankings (opt-in) (+0.03). Users share their rank, position, score. Public-by-default with privacy toggles. GitHub contributors leaderboard, Strava activity feed, GrowthFriction Score rankings.
  8. Printable / PDF export (+0.02). Shared offline (teachers print class materials, chefs print recipes, founders print audits for board decks). PDF includes brand watermark + URL.
  9. Twitter intent URLs with pre-filled text + hashtags (+0.02). Lower friction than blank share. Pre-write the tweet with the result included. Default to readable, sincere text — avoid hashtag spam.
  10. Email-a-friend button (+0.01). Low-ceiling but zero-cost. Use mailto: with pre-filled subject + body. Works for users who don't use social.

Worked example — Discord (Advocacy 9, composite 39)

Discord scores Advocacy 9 via stacked viral mechanics:

  1. Server invites are the primary growth mechanism. Every user can create unlimited invite links. Servers self-recruit through their community network.
  2. k-factor estimated ~0.8 via cross-server adoption. Users in one server discover Discord, join, get invited to other servers, recruit friends to those servers.
  3. Public servers (linked from social, forums, Wikipedia) function as permanent Acquisition channels.
  4. Custom emoji and Nitro features create cultural in-jokes that propagate on Twitter/X + TikTok.
  5. The platform itself is a community discovery engine.

Result: Advocacy 9 + Acquisition 10 multiply into composite 39 even with Monetization 6 ceiling. Lesson: Advocacy 9 requires viral mechanics built into product architecture (invite primitives), not just share buttons added later.

Worked example — Notion (Advocacy 10, composite 27)

Notion scores the maximum Advocacy 10 with multi-channel compound:

  1. Notion templates are shareable artifacts. Users build templates, share publicly, recipients sign up to use them. Each template is permanent recruitment.
  2. Page-level sharing (any Notion page can be made public with URL) creates billions of indexable pages — many rank in Google, driving Acquisition.
  3. Cross-team sharing within Notion. One team member shows page to another team, team adoption follows.
  4. Education-program partnerships (free for students/teachers) created millions of early-life users who became professional advocates.
  5. Community-built integrations (notion.so/integrations) extended platform without Notion-built features.

Result: Advocacy 10 lifts Acquisition 10 + Advocacy 10 to compound at scale. Lesson: product surfaces that generate shareable public artifacts are the highest Advocacy lever in B2B SaaS.

Advocacy anti-patterns (forbidden per AUG framework)

Measurement — what to track

The 60-day Advocacy sprint plan

  1. Week 1-2: Diagnose. Measure current k-factor (if not measured before, baseline = 0). Audit which shareable surfaces exist. Identify the top product surface that's privately consumed but should be publicly shareable.
  2. Week 3-4: Ship embeddable widget version of your core product. Each embed = permanent recruitment channel. Include attribution + brand watermark + return-link.
  3. Week 5-6: Ship per-result OG image + share-card system. SVG generation at build-time or runtime. Pre-composed share text with relevant hashtags.
  4. Week 7-8: Ship 2-3 additional Advocacy features from the ranked list above. Bookmarkable URLs, comparison shareable links, leaderboard or public collection.
  5. Day 60: Measure. k-factor + embed count + brand-search trend. Compound is slow at first (weeks 1-4 will show little); persistence to day 90-180 is where the lift becomes measurable.

The framework lesson

Advocacy is the free-acquisition layer. Each existing user becomes a Acquisition channel at $0 marginal cost. The compound: k-factor 0.15 + Acquisition 5,000/mo = 750 additional users/mo. Over 12 months, that's 9,000 referred users — equivalent to spending $50-200K on paid acquisition.

The trade is patience. Advocacy compounds over months, not weeks. Founders who ship Advocacy features in month 1 see returns in months 4-6. Founders who skip Advocacy find they need ever-rising paid spend to maintain growth — because every paid user is a leaf node, not a recruiter.

Related resources

Frequently asked questions

What is k-factor in SaaS growth?

k-factor = (invitations sent per user) × (conversion rate of invitations). A k-factor of 0.4 means each user brings 0.4 new users on average. k-factor ≥1.0 is technically viral (users replicate at >1× per generation). For SaaS in 2026, k-factor ≥0.15 is solid, ≥0.40 is excellent, ≥0.80 is rare. Linear scores k-factor ~0.6 via team adoption; Notion ~0.4 via cross-team sharing; Slack ~0.5 via channel invites.

Why is Advocacy multiplicative with Acquisition?

Each new user from Advocacy is acquired at near-zero marginal cost (no paid spend, no SEO investment). High Advocacy lifts the effective Acquisition rate without raising CAC. The compound: k-factor 0.4 + Acquisition 5,000/mo organic = 2,000 additional referrals/mo at $0 acquisition cost = effective Acquisition 7,000/mo. In the AUG composite formula, this shows up as both Acquisition lift AND Advocacy lift simultaneously — Advocacy 9 + Acquisition 8 compounds into composite 30+ even with mediocre other factors.

How do I measure SaaS advocacy?

Four primary metrics: (1) k-factor (referrals per user); (2) Share-per-session rate (% sessions triggering share action); (3) Referral-link click-through (% clicks on user-generated URLs); (4) Word-of-mouth attribution (% acquisition via direct/referral, not search/paid). Secondary: embed count for embeddable widgets, NPS-equivalent surveys, unprompted Reddit/X/LinkedIn brand mentions. Track monthly. The most durable signal is rising direct-traffic share over 6-12 months — it indicates brand-as-Advocacy compound.

What is the difference between viral and word-of-mouth growth?

Viral growth has a measurable mechanism (invite link, share button, embed widget) that operators control. Word-of-mouth is unprompted recommendation in conversation, on social, in Slack channels — operators can encourage it but not directly trigger it. Both feed Advocacy. The framework counts both but tracks them differently: viral via UTM-tagged share links, word-of-mouth via direct-traffic + brand-search growth. The strongest products have both.

Should I build a referral program?

Sometimes, but with discipline. Referral programs work when (a) the incentive is product-aligned (free month, more storage) not cash, (b) the share mechanism is one-click, (c) the recipient gets value from the share, not just the sender. Dropbox-style "give 2GB get 2GB" worked because the incentive was the product itself. Cash-incentive programs cheapen brand and attract low-quality acquisitions. The AUG framework prefers organic Advocacy (build a product people love) over engineered Advocacy (pay them to refer).

Cite this playbook: GrowthFriction. (2026). How to improve SaaS advocacy in 2026. https://growthfriction.com/how-to/improve-advocacy/. License CC-BY 4.0. Published 2026-05-18 · Methodology AUG v3.