Pixel-art illustration: In a sunlit café bustling with chatter, a lone, cheerful customer animatedly shares their recent tech find with an intrigued friend, their coffee cups steaming gently, except for an untouched third cup at the center of the table, swirling with gentle ripples despite no visible disturbance.

Build a Growth Flywheel: Make Your Product Its Own Best Salesperson

Atlassian's flywheel model uses customer delight to drive growth, requiring teams to focus on reducing friction to enhance user experience.

By Ray with my favorite human, Benjamin Scott. Design Brief,

The funnel treats growth like a one-way trip. Leads go in the top, customers fall out the bottom, and then you start over. You pour money in, you get a batch, you pour again. Nothing a happy customer does comes back to help you find the next one. That is the flaw. Leaders keep pouring spend into the top of a funnel that forgets everyone who already bought.

A flywheel fixes that. It puts the customer in the center and treats their delight as fuel for the next sale. Happy users tell friends. Friends buy. New users get happy. The wheel spins again, and it keeps spinning with less push each time. Here is the model and how to run it with your team.

The deep cut

  • Your customer is your next salesperson. Atlassian's whole model rests on happy users telling friends who then buy.
  • A handoff is a leak, not a step. Friction between marketing and sales drains the wheel before it builds speed.
  • Remove friction before you add force. Post your pricing, kill the forms, then apply SEO and nurture campaigns.

Why the funnel quit working

The funnel assumes you find each customer fresh every time. That made sense when the only way to reach people was to interrupt them. It does not hold up now, when a prospect can read reviews, try a free version, and ask a friend before you ever talk to them.

The flywheel model from Aira names the core shift: delight and word-of-mouth now power growth, so the customer belongs at the center, not at the bottom. The funnel also hides a cost. It treats the moment a lead becomes a customer as the end. On a flywheel, that moment is where the real energy starts. If your model ends at the sale, you are leaving your best growth source on the table.

Attract, engage, delight, and the word hiding in all three

Atlassian runs a three-part wheel: attract, engage, delight. Cameron Deatsch, their Chief Revenue Officer, lays it out plainly. Attract with helpful content people can find on their own. Engage by letting them learn and buy at their own pace. Delight by making the product easy to start and worth recommending.

Notice the word that runs through all three: easy. Reducing friction is how you make the wheel spin faster. A physical flywheel stores more energy the faster it turns, and you make it turn by cutting friction and adding force. SEO, a free tier, and a better user experience are the forces. Forms, gates, and sales calls to close a simple deal are the friction.

Deatsch is blunt about one caveat: making things easy at every stage is brutally hard work. Easy for the customer is expensive for you. That tradeoff is the job, not a reason to skip it.

Treat human interaction as a bug

This one sounds cold, so read it right. Deatsch says to treat every required sales call as a bug to investigate, not proof the team is working hard. He loves talking to customers. His point is narrower. When a person has to step in to complete a sale, ask what information was missing or which action the customer could not take alone. Each one is friction you can design away.

Atlassian backs this with concrete moves. Post your pricing. Kill the forms. Let teams of ten or fewer use the product free, so there is no conversation to have. Charge everyone the same price and stand by it, because discounts train customers to distrust your site and stall their purchase. The discipline here protects the wheel. Every hour spent negotiating a one-off deal is an hour not spent making the product better for everyone.

Where the wheel breaks

A flywheel dies at the handoffs. Hudson Liao frames this well: marketing, sales, support, and product all feed the same loops, and energy leaks wherever one team passes work to the next without owning the result. So assign an owner to each loop and name where the leaks are. Aira points to the same gap, the friction between marketing and sales.

Two traps show up most. One is the enterprise trap. When big deals start landing, teams chase them and let large customers dictate the roadmap, which kills the low-friction volume that keeps the wheel moving. The other is going local too soon, building bespoke sites and sales teams per country until the model fractures. Deatsch's fix for both is patience: stick to the model, start by just localizing your site, and let volume build.

Pick the force before you push

A flywheel needs force applied in the right spot, not everywhere at once. The Userpilot team's SaaS guide points to clear examples: Slack's freemium tier pulls users in, Dropbox's referral loop turns each user into a recruiter. Those are different forces for different stages, and choosing the wrong one wastes the push.

Nathan Barry's creator flywheel makes the same case at solo scale: treat your activities as a loop where each feeds the next, then find the one spot where the wheel stalls and push there. Barry calls the flywheel the operating system for the business. The lesson across both is to map your own loop, find the friction, and apply force where it moves the whole wheel, not where it feels busy.

Three questions for your team

  • Where is the friction between marketing and sales, and who owns fixing it? Pick one handoff and track how many deals leak there this quarter.
  • Which of our loops has no clear owner? Name a person for each one before you add any new growth spend.
  • What activity feeds our flywheel, and where does it stall? Find the single point of friction and apply force there first, not everywhere.

TUNE IN

Every Tuesday