# Playbook — The Flywheel

**Derives from:** HubSpot, adapting Jim Collins's flywheel concept (*Good to Great*, 2001) into a post-funnel growth model. See MANUAL §4.10.

## Thesis

Reject the funnel's "customers fall out the bottom" framing entirely. Instead: **remove friction and add force at every stage so customers themselves become the acquisition channel** — advocacy and promotion aren't a final funnel stage, they're the engine that re-feeds the top. Momentum compounds; each satisfied, retained, referring customer makes the next acquisition cheaper. This is the layer that sits *after* a funnel has already produced happy customers — it doesn't replace acquisition mechanics, it multiplies them.

## When to use it

- You already have retention, real product/service satisfaction, and customers who spontaneously talk about you — the flywheel formalizes and accelerates something already happening, it doesn't manufacture advocacy from nothing.
- You're past the point of needing a single acquisition funnel to prove itself and are now optimizing the whole system for compounding momentum rather than just next-quarter conversions.
- You want to diagnose *where friction is silently taxing momentum* (slow support response, confusing onboarding, no easy referral mechanism) rather than where a funnel stage is leaking.

## When NOT to use it

- Used as a cold-acquisition model on its own — it explicitly assumes you already have happy customers to spin the wheel; a business with no customers yet has nothing to apply flywheel force to. Build a funnel first (any other playbook in this set).
- Retention and satisfaction are actually poor — applying flywheel thinking to a leaky bucket just means friction-removal work gets wasted because customers churn before advocacy can develop.
- There's no simple, low-friction way for a happy customer to actually refer/advocate — if the mechanism to spin the wheel doesn't exist (no referral program, no easy share action, no community), "add force" has nothing to act on.

## Step-by-step build

1. **Audit friction at every existing customer touchpoint** — onboarding, support response time, billing clarity, product usability, community access. Each friction point is a place momentum silently bleeds (this pairs directly with `customer-value-journey`'s Excite/Ascend stages).
2. **Identify existing "force" moments** — where customers already refer, testify, or advocate unprompted. These are your highest-leverage template to formalize and scale, not invent from scratch.
3. **Design the referral/advocacy mechanism explicitly** — a named, low-friction action (a share link, a referral code, a "bring a friend" incentive, a public review ask timed to a genuine win). This is the flywheel's literal mechanical connection back to the top of the funnel.
4. **Install habit loops in the post-purchase experience** (Eyal's Hook Model — trigger/action/variable-reward/investment, §2.10) — the more a customer is invested in the product/community, the more naturally advocacy follows.
5. **Reduce friction before adding force** — per Thaler/Sunstein choice architecture (§2.7), the default path for an existing customer should be the path of least resistance toward continued engagement and easy advocacy; friction should only exist at exits you don't want (e.g., cancellation flows, not referral flows).
6. **Stage Map (flywheel variant — cyclical, not linear)**: Delighted Customer → Frictionless Continued Use → Advocacy Prompted → Referral/UGC Generated → New Prospect Enters (loops back to whatever acquisition funnel is running).
7. **Conversion Math**: % of customers who advocate unprompted, % who advocate when prompted, referral→new-customer conversion rate, cost-per-acquisition via referral vs. paid channels (the number that proves the flywheel is actually cheaper than paid acquisition).
8. **Instrumentation**: `nps_survey_completed`, `referral_link_generated`, `referral_link_shared`, `referred_prospect_entered_funnel`, `referred_prospect_converted`.
9. **Failure Exits (flywheel-specific)**: a customer who doesn't advocate isn't a "failed stage" the way a funnel drop-off is — the exit here is simply "continues as a retained customer without becoming a channel," which is fine; the diagnostic question is whether *friction* (fixable) or *genuine indifference* (a product/satisfaction problem, out of this master's scope) explains the non-advocacy.

## Worked mini-example

- **Situation:** ZIION members at Passport Level 5+ (already ascended, already retained) — the flywheel applies here, not to the cold top-of-funnel.
- **Friction audit finding:** no existing referral mechanism at all — advocacy is currently happening informally (word of mouth) with zero formal capture.
- **Force added:** a simple "invite a builder" referral link inside the member dashboard, rewarding both referrer and referee with a Passport level-boost.
- **Habit loop:** the dashboard itself already has a variable-reward mechanic (readiness score updates) — the referral action is added as an "investment" step inside that existing loop, not a bolted-on separate ask.
- **Conversion Math:** % Level 5+ members who'd advocate unprompted (measure via a quick NPS/referral-willingness survey) — currently unmeasured `[guess: unknown — first thing to instrument]`; referral link→new signup conversion, once live, becomes the number that proves this channel's CAC against paid acquisition.

## How the verify gate applies

This deliverable is best framed as a `funnel-audit` (MANUAL §8.4) even though it's forward-looking, because the flywheel's entire premise depends on **measured** existing behavior (current unprompted-advocacy rate) rather than assumed numbers — building "add force" tactics on a `[guess]` about how much advocacy already exists is building on sand. Every friction point identified needs a named cause (a B=MAP attribution, §2.6 — almost always "unable," i.e., there's no easy mechanism) and a prioritized, effort-tagged fix, per the audit linter. Because this style is cyclical rather than linear, the "no orphan stages" rule still applies but points backward — the Referral/UGC stage's "next stage" is explicitly the top of whatever acquisition funnel is running, and that connection must be named, not implied.