Classes 68 through 70 built the parts: an audience that returns, a community that interacts, contributions that get organized, assets that rank. This lesson assembles them into the flywheel from the course outline — content to discovery to participation to contribution to assets to discovery again — and shows why the loop, once turning, beats any single campaign.

The loop, stage by stage

The outline gives the skeleton:

CONTENT → TRAFFIC → COMMUNITY → COMMUNITY CONTENT → MORE SEARCHABLE CONTENT → MORE TRAFFIC

Flesh each arrow with its mechanism:

Content → discovery. Your public work — lessons, teardowns, how-tos including community-derived assets — gets found through search, social, email forwards, or partnerships. Discovery is not virality; it is a stranger with a real problem landing on a page that solves it. Lesson 70.3's assets are purpose-built for this arrow.

Discovery → participation. A fraction of visitors take one low-friction step inside: ask a question, join the weekly thread, reply to the newsletter. This conversion depends on visible aliveness (Lesson 69.3) and a clear first action ("post one filing question"). Dead rooms convert nobody.

Participation → contribution. Repeat participants become contributors when the contribution card (Lesson 70.1) makes the ask small and the reward certain. The first contribution is the flywheel's hardest step — design it like an onboarding, with templates and fast feedback.

Contribution → assets. Organized contributions become digests (Lesson 70.2) and then gated, verified assets (Lesson 70.3). This is where AI leverage concentrates: sorting and summarizing at a scale no human team could afford, under human review.

Assets → discovery. New assets rank, get shared, and get cited — bringing the next wave of strangers with the same recurring problems. Each turn should widen the top of the funnel slightly while deepening the archive substantially.

A tailor's flywheel turns the same way: a public "rush-hem pricing guide" (asset) brings local searches (discovery), planners join the chat to ask about dates (participation), members post job photos (contribution), the best become a "wedding-season fabric guide" (asset), which brings next season's searches.

Why flywheels beat funnels

A funnel spends to acquire each visitor and starts at zero every month. A flywheel reinvests: today's community labor becomes tomorrow's discovery surface, which lowers next month's acquisition cost. Three properties follow. Compounding: the archive grows whether or not you publish this week. Defensibility: a thousand credited member examples cannot be copied by prompting a model. Self-selection: each turn filters for people with the recurring job, so the community gets more relevant as it grows, not noisier — provided the gates hold.

The cost is patience. A funnel shows results Friday. A flywheel shows wobble for months, then smooth acceleration. Founders who judge month two by funnel metrics ("why only 40 members?") dismantle the loop just as it starts storing energy. Judge early turns by flow, not size: is each arrow demonstrably working for even a few people?

Watch for two common stalls. The first is the participation cliff: discovery works and visitors arrive, but nobody posts because the room looks finished rather than inviting — solved by the visible first task and fast replies from Lessons 69.3 and 70.1. The second is the archive trap: contributions pile up unorganized, so assets never ship and discovery never compounds — solved by the digest workflow and publish-or-not gate from Lessons 70.2 and 70.3. Name which stall you are in before prescribing; pouring more discovery onto a participation cliff only deepens it. Energy stored in an organized archive forgives slow months; energy spent on unconverting traffic does not.

Mapping yours

A generic diagram inspires nobody. Map your specific loop: for each stage, name your actual venue, your actual artifact, and the handoff. "Newsletter teardown → forum join link → Friday wins thread → teardown card → monthly public guide → search." Then annotate each arrow with its current strength: flowing, weak, or broken. Most new flywheels have two flowing arrows and four hopes. That honesty is the map's value — it tells you where Lesson 71.2's experiment goes.

Exercise: draw the map

Create FLYWHEEL-MAP.md with six stages customized to your community: venue + artifact + owner for each, the handoff action between stages, and a flowing/weak/broken rating with one line of evidence ("3 of last 4 guides brought a join citing search"). End with the single weakest arrow and why you believe it is the constraint.

Finish line: a one-page map a collaborator could read and point to the constraint without your help.

Verify quickly: trace one real member's journey through all six stages. If no member has completed the full loop yet, mark which stages are proven versus projected.

Common failure mode: mapping the flywheel you wish you had — five aspirational arrows with no evidence. A thin true map beats a rich fantasy.

Check your understanding

1. What flows across each of the five arrows in the flywheel? 2. Why does a flywheel lower acquisition cost over time while a funnel does not? 3. Why should early flywheel health be judged by flow rather than size?

Next

Maps reveal breaks. Lesson 71.2 teaches you to diagnose the weakest arrow with leading versus lagging metrics — and fix it with exactly one experiment at a time.