Files
skills/public/program-examples.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

3.2 KiB
Raw Permalink Blame History

Referral Program Examples

Real-world examples of successful referral programs.

Contents

  • Dropbox (Classic)
  • Uber/Lyft
  • Morning Brew
  • Notion
  • Incentive Types Comparison
  • Incentive Sizing Framework
  • Viral Coefficient & Metrics (Key Metrics, Calculating Referral Program ROI)

Dropbox (Classic)

Program: Give 500MB storage, get 500MB storage

Why it worked:

  • Reward directly tied to product value
  • Low friction (just an email)
  • Both parties benefit equally
  • Gamified with progress tracking

Uber/Lyft

Program: Give $10 ride credit, get $10 when they ride

Why it worked:

  • Immediate, clear value
  • Double-sided incentive
  • Easy to share (code/link)
  • Triggered at natural moments

Morning Brew

Program: Tiered rewards for subscriber referrals

  • 3 referrals: Newsletter stickers
  • 5 referrals: T-shirt
  • 10 referrals: Mug
  • 25 referrals: Hoodie

Why it worked:

  • Gamification drives ongoing engagement
  • Physical rewards are shareable (more referrals)
  • Low cost relative to subscriber value
  • Built status/identity

Notion

Program: $10 credit per referral (education)

Why it worked:

  • Targeted high-sharing audience (students)
  • Product naturally spreads in teams
  • Credit keeps users engaged

Incentive Types Comparison

Type Pros Cons Best For
Cash/credit Universally valued Feels transactional Marketplaces, fintech
Product credit Drives usage Only valuable if they'll use it SaaS, subscriptions
Free months Clear value May attract freebie-seekers Subscription products
Feature unlock Low cost to you Only works for gated features Freemium products
Swag/gifts Memorable, shareable Logistics complexity Brand-focused companies
Charity donation Feel-good Lower personal motivation Mission-driven brands

Incentive Sizing Framework

Calculate your maximum incentive:

Max Referral Reward = (Customer LTV × Gross Margin) - Target CAC

Example:

  • LTV: $1,200
  • Gross margin: 70%
  • Target CAC: $200
  • Max reward: ($1,200 × 0.70) - $200 = $640

Typical referral rewards:

  • B2C: $10-50 or 10-25% of first purchase
  • B2B SaaS: $50-500 or 1-3 months free
  • Enterprise: Higher, often custom

Viral Coefficient & Metrics

Key Metrics

Viral coefficient (K-factor):

K = Invitations × Conversion Rate

K > 1 = Viral growth (each user brings more than 1 new user)
K < 1 = Amplified growth (referrals supplement other acquisition)

Example:

  • Average customer sends 3 invitations
  • 15% of invitations convert
  • K = 3 × 0.15 = 0.45

Referral rate:

Referral Rate = (Customers who refer) / (Total customers)

Benchmarks:

  • Good: 10-25% of customers refer
  • Great: 25-50%
  • Exceptional: 50%+

Referrals per referrer:

Benchmarks:

  • Average: 1-2 referrals per referrer
  • Good: 2-5
  • Exceptional: 5+

Calculating Referral Program ROI

Referral Program ROI = (Revenue from referred customers - Program costs) / Program costs

Program costs = Rewards paid + Tool costs + Management time

Track separately:

  • Cost per referred customer (CAC via referral)
  • LTV of referred customers (often higher than average)
  • Payback period for referral rewards