Quick answer
The flywheel model represents growth as accumulated momentum around customer value. HubSpot adapted the metaphor into three connected motions: Attract suitable people with useful context, Engage them on appropriate terms, and Delight customers through successful outcomes so retention, advocacy and learning support future growth. Teams add force by improving valuable experiences, remove friction from broken handoffs and protect momentum through retention. A flywheel is a strategic and operating map, not a physical equation or proof of causation. Define actors, value outcomes, feedback paths, owners, delays, quality and economics, then measure the connected system by cohort.
What is the flywheel model?
The flywheel model represents business growth as momentum created by connected customer experiences. HubSpot adopted the mechanical metaphor to move beyond a funnel whose diagram ends at purchase. Customers remain central because their retention, feedback and advocacy can strengthen future acquisition and delivery.
HubSpot organizes the model around Attract, Engage and Delight. These are not rigid journey stages. A customer can be attracted to a new use case after purchase, engage through support and delight another participant through helpful community contribution. The model emphasizes continuity across organizational boundaries.
Why the flywheel challenges the funnel
A funnel is useful for measuring conversion through a bounded process. Its usual visual form treats customers as an endpoint and encourages functions to optimize their own stage. Handoffs can then create friction, while post-purchase learning remains disconnected from marketing and product work.
The flywheel adds feedback and accumulated state. Retained customers, trusted knowledge, product capability and reputation can carry momentum into later cycles. The metaphor should complement, not eliminate, funnel analysis: teams still need detailed conversion diagnostics inside each motion.
Attract, Engage and Delight
Attract means earning attention from people whose problem the organization can solve. Engage means helping them evaluate and act through appropriate content, product or human interaction. Delight means delivering reliable outcomes, resolving friction and supporting continuing value after the transaction.
Feedback completes the operating logic. Customer evidence informs product, service and future communication; satisfied customers may voluntarily recommend. Each return path needs a mechanism, owner and quality threshold. A general belief that happy customers create growth is not yet a measurable flywheel.
Attract
Help suitable people discover trustworthy information and a relevant promise.
- Whom can we genuinely help?
- Does the content reduce uncertainty?
Engage
Enable evaluation and action on the customer's preferred terms.
- What decision is the customer making?
- Where is friction necessary or avoidable?
Delight
Deliver the promised outcome reliably and resolve problems with low effort.
- Did the customer succeed?
- Would they choose and recommend again?
Feedback
Turn customer learning and voluntary advocacy into improved future inputs.
- What returns to the system?
- Is sharing informed and optional?
Momentum
Measure force, friction, cycle time, quality and economics across the cycle.
- Where does energy leak?
- Does improvement persist by cohort?
Translate force and friction into business terms
Force is an investment or change that improves customer movement or value, such as clearer proof, faster setup or reliable support. Friction is delay, effort, mistrust, rework or a broken handoff. Some friction is protective, including security review and informed consent, and should be improved rather than blindly removed.
The metaphor's mass can represent retained customers, useful content, capability or relationships, while speed can represent cycle time. Do not pretend these form a literal engineering equation. Define observable business measures and use the metaphor to organize hypotheses and ownership.
How to build a customer flywheel
Map the customer journey and the outputs that can support another cycle. Interview customers and frontline teams, inspect cohorts and identify handoffs where context, time or trust is lost. Choose a central customer-value outcome and name the major Attract, Engage, Delight and feedback mechanisms.
Assign cross-functional owners, instrument the important transitions and prioritize one friction or force hypothesis. Test the change, monitor delayed and downstream effects, and update the map. Keep separate views for segments whose journeys and value cycles differ materially.
- Customer value at center
- Target participants explicit
- Attract mechanism defined
- Engage outcome observable
- Delight tied to customer success
- Feedback path named
- Friction includes handoffs and delay
- Protective friction preserved
- Owners cross functions
- Cohort and cycle time measured
- Advocacy remains voluntary
- Economics and quality governed
Flywheel model example
LanternDesk's hypothetical map turns support success into structured learning and permission-based proof. The flywheel does not depend on every customer becoming a promoter. Better issue knowledge can improve product and content even when a customer never refers anyone.
The example also distinguishes activity from momentum. More tickets, guides or demonstrations can add friction if quality is weak. Reliable resolution, retained customer value and feedback that improves future journeys are closer to the mechanism the model intends to capture.
LanternDesk is a hypothetical customer-support platform for growing online retailers. Marketing, sales, onboarding and support currently optimize separate handoffs, while customer learning rarely returns to content or product decisions.
LanternDesk publishes evidence-based guides for retailers facing repeat support issues. Qualified readers can inspect workflows and limitations without giving up unnecessary personal information.
A retailer evaluates a relevant workflow in a sandbox or assisted session, reaches a first successful resolution and receives clear security and pricing information. The route matches complexity rather than forcing every prospect through one form.
Onboarding and support focus on reliable resolution quality, accessible agent workflows and low customer effort. Recurring problems are fixed at the product or process level instead of being celebrated as ticket activity.
With permission, successful patterns inform better guidance and optional case evidence. Product teams receive structured issue themes. Customers are never pressured to provide a review as a condition of support.
A cross-functional review examines cohort activation, resolution quality, retention, advocacy, cycle time, complaints and contribution. The team removes the largest system friction rather than optimizing a decorative circle.
LanternDesk and all outcomes are hypothetical. Customer support data can contain sensitive information and requires appropriate access, retention and consent controls.
Measure flywheel momentum
For Attract, measure qualified reach, expectation quality and entry into a value path. For Engage, track activation, decision progress, time and fit. For Delight, examine outcome quality, effort, retention, expansion and issue resolution. For feedback, measure usable learning and qualified voluntary advocacy.
Connect these measures by cohort and preserve delays. A content improvement may affect retained value months later, while support quality can change renewal and word of mouth. Use a North Star and guardrails to prevent one motion from inflating its local metric at another's expense.
Organize around friction and feedback
Run reviews around the largest customer or system constraint rather than departmental reports. A slow security review may require sales, product, legal and security; recurring onboarding questions may require product design and content, not more customer-success capacity.
Create closed-loop feedback with evidence standards and response ownership. Frontline observations should be coded and linked to decisions without treating anecdotes as prevalence. Tell teams and customers what changed so the system can learn and trust can accumulate.
Govern customer advocacy and service quality
Delight must not become surprise gifts masking unreliable basics. Define service outcomes, accessibility, complaint handling and remedy. Request reviews or referrals only after appropriate value, disclose incentives and never make support conditional on public praise.
Protect customer data as it moves across teams. Limit sensitive access, record consent for case stories and remove identifying details from general learning. Incentives should reward durable customer outcomes and collaboration, not handoff volume or manipulated satisfaction scores.
Limitations and common flywheel mistakes
The flywheel can become a vague circle that hides sequence, leakage, finite demand and external shocks. Customer advocacy is not automatic, retention can result from switching barriers, and momentum can reverse when quality fails. The model also does not estimate causal effects by itself.
Common mistakes include renaming funnel stages, treating all friction as bad, placing delight after purchase only and reporting activity without feedback. Use detailed funnels, growth loops, cohorts and financial models beneath the flywheel. Its distinctive value is aligning the organization around customer continuity and reinvested learning.
A real flywheel connects customer value to retained learning and future value. A circle without a feedback mechanism is only a diagram.
Frequently asked questions
What are the three stages of HubSpot's flywheel?
Attract, Engage and Delight. They describe connected customer-centered motions rather than a rigid one-time sequence.
What is the difference between a flywheel and a funnel?
A funnel emphasizes conversion and loss through a bounded journey. A flywheel emphasizes retained customers, reduced friction and outputs that support future cycles. Teams can use both.
What creates force in a business flywheel?
Investments that improve customer value or movement, such as stronger product outcomes, useful information, better onboarding and reliable service, provided their downstream effects are measured.
What counts as friction?
Avoidable customer or organizational effort, delay, mistrust, rework and broken context. Protective review or informed consent can be necessary friction and should not be removed blindly.
How is flywheel momentum measured?
Measure qualified transitions, cycle time, retention, customer outcomes, feedback reentry, advocacy quality, contribution and guardrails by cohort. There is no universal single momentum formula.
Sources and further reading
- HubSpot: The Flywheel Model ↗First-party definition of the customer-centered flywheel and organizational momentum
- HubSpot: How the Flywheel Killed the Funnel ↗Detailed first-party implementation of Attract, Engage, Delight, force and friction
- Journal of Marketing: Service-Profit Chain Meta-Analysis ↗Meta-analytic evidence on links among internal service, customer outcomes and business performance
- Reforge: Growth Loops Are the New Funnels ↗System framing for outputs that can be reinvested in future growth