Twelve practical lessons on referrals, partners, return visits and reusable resources. Each chapter includes an example, something to try and a mistake to avoid.
0 of 12 chapters marked read
CHAPTER 01 / ACQUISITION THAT BUILDS ON ITSELF
The loop begins with one useful result
The most useful acquisition systems make the next customer easier to reach.
A flywheel is not a magic machine that produces customers while you sleep. It is a repeatable cycle: you help someone, that experience creates something useful, and you use that outcome to make future introductions or sales easier. At the beginning, every turn still requires deliberate work. The advantage is that earlier effort can support the next attempt.
For example, a small software maker helps a client solve a specific reporting problem. With permission, the maker turns a general lesson into a tutorial. Future prospects see the tutorial, understand the work and ask better questions. The useful lesson was earned once but may be reused.
REALISTIC EXAMPLE
Picture this
A freelance accountant produces a plain-English tax-season checklist after helping a client understand common mistakes. They offer it on a public resource page and include a simple way to ask for help.
FIELD EXERCISE
Put it to work
Pick one useful thing you have already created. Write who it helped, whether you can share it, and the specific person who may need it next.
COMMON MISTAKE
Avoid this
Do not assume a testimonial, permission to share or a referral exists simply because a customer was pleased. Ask clearly and respect a no.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: A flywheel starts with a useful result, not a clever diagram.
CHAPTER 02 / ACQUISITION THAT BUILDS ON ITSELF
Find the repeatable trigger
Identify the event that creates a good reason to return or recommend.
The strongest loops usually have a clear trigger. It might be a completed project, a customer milestone, a renewal, a seasonal need, a new resource or a question someone frequently asks. Without a trigger, the plan becomes an instruction to “promote more,” which is difficult to repeat and measure.
Describe who notices the trigger, what they need at that moment and why sharing, returning or introducing someone would be useful rather than awkward. Your first test should be small enough to observe.
REALISTIC EXAMPLE
Picture this
A gardening service finishes a spring maintenance visit. At the end, it provides a short seasonal care guide a homeowner can keep and pass along to a neighbour.
FIELD EXERCISE
Put it to work
Write an event in your business that happens at least occasionally. Sketch the invitation you could offer at exactly that moment.
COMMON MISTAKE
Avoid this
Sending an automatic request to every customer at an arbitrary time can feel like spam. Match timing to genuine usefulness.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: Repeatability comes from timing and value, not just frequency.
CHAPTER 03 / ACQUISITION THAT BUILDS ON ITSELF
Referrals that feel natural
Make recommending you helpful rather than uncomfortable.
A referral is someone voluntarily introducing your work to another person. Asking for one works best when the original customer genuinely understands what you helped them achieve and can identify someone with a related need. Make it easy to explain the problem you solve in one clear sentence.
Offer an optional introduction link, a short descriptive paragraph or a genuinely useful resource. If you reward referrals, explain the terms accurately and consider local rules about disclosure. Never invent customer praise or pressure people to share contact details.
REALISTIC EXAMPLE
Picture this
An independent bookkeeper sends a useful new-business checklist after a successful onboarding and invites the client to pass the resource to a friend opening a business.
FIELD EXERCISE
Put it to work
Write a one-paragraph invitation. Ask: would I feel comfortable receiving this after a good experience?
COMMON MISTAKE
Avoid this
Avoid implying a customer endorsement where none was given, and do not ask people to upload friends’ private details without permission.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: Make the introduction easy to give and easy to decline.
CHAPTER 04 / ACQUISITION THAT BUILDS ON ITSELF
Partners make new doors
Work with complementary businesses serving the same kind of buyer.
A partner does not have to resell your work. They might co-create a resource, introduce your expertise to their audience or help complete a customer journey. Start with complementary value: what useful result can you offer their people without asking the partner to risk trust?
Effective partnerships begin with a small, verifiable proposal, clear responsibilities and a sensible opt-out. A useful trial might be one workshop, one shared checklist or a guest demonstration. Document where enquiries came from only when you can actually know.
REALISTIC EXAMPLE
Picture this
A local fitness coach and a physiotherapist co-author a general guide to returning to movement, each reviewing their own contribution and clearly identifying who does what.
FIELD EXERCISE
Put it to work
List three non-competing businesses your buyer already trusts. Draft one short shared-value idea for each.
COMMON MISTAKE
Avoid this
Do not assume someone has agreed to endorse or distribute your work. Confirm consent, usage rights and any incentive disclosures.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: Start with shared usefulness, not a request for access to someone’s list.
CHAPTER 05 / ACQUISITION THAT BUILDS ON ITSELF
One asset, several routes
Extend the useful life of good work without publishing duplicates everywhere.
A well-made customer answer may have several responsible uses. A public FAQ can support enquiries, a shorter version can help partner introductions, and a visual extract might fit a permitted community. This is not about posting the same message everywhere. Adapt the context, format and invitation to each audience.
Keep one canonical source so updates do not get lost. Make sure old claims, policies or contact details are corrected wherever the content was reused. Reuse the thinking; adjust the presentation.
REALISTIC EXAMPLE
Picture this
A software company turns a detailed installation walkthrough into a searchable help page, a short email answer and a checklist linked from its product description.
FIELD EXERCISE
Put it to work
Choose one piece of existing content. Map three audiences and specify what each would actually find useful.
COMMON MISTAKE
Avoid this
Repetition without audience fit damages trust and may violate community rules.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: A strong asset travels because it helps, not because it is everywhere.
CHAPTER 06 / ACQUISITION THAT BUILDS ON ITSELF
Customer success into useful proof
Document outcomes carefully and show only what you can verify.
Trust is easier to build when people can inspect real examples of work, processes and practical outcomes. You do not need a dramatic testimonial. A before-and-after explanation of a problem solved can be compelling when it is accurate and appropriately anonymised or approved.
Separate the deliverable, the customer’s reported result and your own interpretation. Ask permission before using identifiers, quotes, logos or private work. Record when the example was last checked. A small honest case study is better than a large unverifiable claim.
REALISTIC EXAMPLE
Picture this
A designer shows the structure of a booking-page overhaul using their own sample screenshots and describes the navigation problem rather than claiming an unmeasured revenue lift.
FIELD EXERCISE
Put it to work
Write a 150-word case example around one real task. Mark what you can show publicly, what needs permission and what must remain private.
COMMON MISTAKE
Avoid this
Never turn correlation into proven causation or assume one customer’s result is typical.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: Useful proof explains what changed and how you know.
CHAPTER 07 / ACQUISITION THAT BUILDS ON ITSELF
Build a return path
Offer a sensible reason for earlier visitors or customers to come back.
Not everyone buys on the first visit, and some customers need your expertise again later. A return path is a genuinely relevant update, a useful reminder, an improved resource or an invitation tied to the person’s situation. The point is continuing service, not relentless follow-up.
A practical cadence starts from consent and relevance. Record which messages you actually send and what recipients voluntarily do. If someone opts out, respect that immediately. Match your promise to your capacity.
REALISTIC EXAMPLE
Picture this
A training provider tells past attendees when the updated course handout is available, with an optional route to the next class.
FIELD EXERCISE
Put it to work
Draft one follow-up message that contains a new useful thing and a clear opt-out or preference route where appropriate.
COMMON MISTAKE
Avoid this
Avoid using expired or unrelated offers as a pretext to reopen a conversation.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: Returning attention must be earned again.
CHAPTER 08 / ACQUISITION THAT BUILDS ON ITSELF
Make sharing safe and easy
Remove friction without collecting data you do not need.
Even willing customers may not share a complicated explanation or broken link. A good referral page tells the reader who it helps, what it offers and what happens after clicking. The person sharing it should be able to explain it without sounding like a salesperson.
Keep optional sharing tools simple: a copyable public URL, readable message and working contact route. Ghost’s invitation builder creates a static page; it cannot secretly send invitations, capture responses or track private shares. Hosting and outreach are separate real actions.
REALISTIC EXAMPLE
Picture this
A consultant creates a short partner introduction page with a two-sentence explanation, an example service and a link to book a real discovery call.
FIELD EXERCISE
Put it to work
Write your offer in one sentence for a friend. If it still needs a long speech, simplify the offer before designing the page.
COMMON MISTAKE
Avoid this
Never preload another person’s contact information into public HTML or claim invisible tracking.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: Low-friction sharing is a kindness to both people.
CHAPTER 09 / ACQUISITION THAT BUILDS ON ITSELF
Measure loops without pretending
Track a few real signals and leave unknowns blank.
A loop diagram is a hypothesis about how one action might encourage another. It is not evidence of growth. Start with actions you can count honestly: invitations requested, links shared with consent, partner conversations, completed referrals, qualifying enquiries or repeat orders. Some numbers will be unknown, and that is fine.
Compare outcomes over time with enough context to avoid attributing everything to one tactic. If you observe three enquiries after publishing a new resource, that does not prove the resource caused all three. Record the possible route and other changes.
REALISTIC EXAMPLE
Picture this
A business logs five confirmed partner introductions and two enquiries that explicitly say they came through those partners. It does not convert that into a promised conversion rate.
FIELD EXERCISE
Put it to work
Choose one loop and write which step you can actually observe this month. Identify one missing data point you will not estimate.
COMMON MISTAKE
Avoid this
Avoid forecast dashboards that manufacture certainty from guesses or tiny samples.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: A good loop report shows both the evidence and the gaps.
CHAPTER 10 / ACQUISITION THAT BUILDS ON ITSELF
Find and repair the weak link
The step between useful action and new opportunity is often where the loop breaks.
A referral system can fail even if customers are happy. They may not know who to recommend you to; a referral page may be unclear; or a partner may be uncertain what happens after introduction. Diagnose the specific handoff before building more materials.
Look at each stage: useful result, reason to share, accessible path, relevant recipient and clear next step. Which handoff is visibly failing? Fix one and retest. Rebuilding the whole system may obscure what actually mattered.
REALISTIC EXAMPLE
Picture this
A partner sends interested people to a landing page, but the contact link goes to an outdated inbox. Fixing that route matters more than designing another partner deck.
FIELD EXERCISE
Put it to work
Walk through the full journey as a newcomer using a phone. Write the first concrete obstacle you encounter.
COMMON MISTAKE
Avoid this
A low number of replies is not proof of a broken headline if no one saw the invitation.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: Repair the actual handoff before increasing the volume.
CHAPTER 11 / ACQUISITION THAT BUILDS ON ITSELF
Create a small repeatable system
Turn a successful single test into a practical routine.
When an experiment produces useful evidence, document how it happened: trigger, audience, invitation, asset, responsible person, next step and review. Create a simple checklist so the next attempt is easier. Keep the system small until you know it deserves more time.
Set a review cadence you can sustain. Your routine might mean checking a referral link monthly or writing one partner update each quarter. The strongest routine is one people actually follow.
REALISTIC EXAMPLE
Picture this
A freelance developer records a template for asking permission to share a case study, the handout used in follow-up and a checklist to refresh the page after project completion.
FIELD EXERCISE
Put it to work
Write five steps you could repeat next month, each with an owner or calendar prompt. Identify which still need proof.
COMMON MISTAKE
Avoid this
Do not automate sending messages or collecting personal data before understanding consent and platform restrictions.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: Consistency means repeating proven useful work, not endlessly automating guesses.
CHAPTER 12 / ACQUISITION THAT BUILDS ON ITSELF
Compound without losing the human
Grow a network of useful interactions while keeping trust central.
The best long-term acquisition advantage may be trust that accumulates: reliable answers, a body of useful resources, well-served clients and a small group of partners who understand your work. These gains are rarely perfectly measurable, but they can reduce wasted effort when you continue earning them.
Your work should become easier to explain, find, evaluate and share. Review every loop periodically: does it still help the audience, is its claim current, and can the next person use it without your intervention? Keep ownership of the assets while respecting collaborators and audiences.
REALISTIC EXAMPLE
Picture this
A niche educator updates a freely accessible glossary once a quarter, adds a new example from genuine questions and gives partners a stable link rather than a constantly changing sales pitch.
FIELD EXERCISE
Put it to work
Choose your most promising loop. Describe how it could still be useful twelve months from now, then name the first action you can complete this week.
COMMON MISTAKE
Avoid this
More content is not automatically compounding. Relevance, maintenance and human trust make the difference.
CONNECT THE LEARNING
Make a real test
Use Flywheel Foundry to map one step you can try. Record actual observations in the Observatory; if you have no evidence yet, label the idea as a hypothesis.
Remember: Long-term advantage is built from usefulness people choose to pass on.
