The Problem Nobody Can Name
"Where are we with the Johnson project?"
Watch what happens next. Your team member pauses. They construct an answer from scratch—pulling context, remembering details, translating their mental model into words you might understand.
"Well, we finished the proposal and they signed last week. Now we're waiting on some information from their team before we can start the actual work. Oh, and accounting needs to send the first invoice."
Three sentences. No shared vocabulary. No standard stages. Just a narrative constructed on the fly.
Now multiply this by every project, every customer, every team member. Every status update requires a story. Every handoff requires a translation. Every time you ask "where are we?" someone has to build the answer from raw materials.
You sit down with your leadership team and try to figure out why growth feels so hard. Marketing says leads are coming in. Sales says they're closing. Operations says they're delivering. And yet: customers aren't sticking around, cash flow is unpredictable, and every project still feels like it's being figured out for the first time.
The root cause is almost always the same. There's no shared language for the work. No common vocabulary across departments—or across your own thinking—for describing where things happen, where they break down, or where the opportunity is hiding.
This is the vocabulary gap—and it's costing you more than you realize.
Why "Air"?
The AAAERRR Framework is pronounced "AIR." That's not accidental. We're giving air to the challenges that owners and operators have a hard time identifying—or articulating.
Think about the last time you tried to explain a persistent business problem to a partner, a board member, or a key hire. Maybe you talked around it for ten minutes. Maybe you described a handful of symptoms and hoped they'd see the pattern. Maybe you said "I don't know, things just aren't working" and watched the room go quiet.
That's suffocation. Your business can't breathe because you can't name what's choking it.
AAAERRR gives you oxygen. When you can say "we have an Activation problem—people are signing up but we're not aligning expectations before we commit resources"—you've given air to something that was previously just a vague sense of unease. And once it has a name, it has a solution.
Three Structural Zones
Before we name the seven stages, we need to understand the three zones they live in. This is the structural insight that most business frameworks miss entirely.
Every customer relationship moves through exactly three zones—not two. Most businesses design the first two. The third is where the most preventable value loss occurs.
The Funnel
Awareness → Acquisition → Activation
The acquisition motion. All work whose purpose is to move a person from having no relationship with your organization to making a commercial commitment. The Funnel ends the moment a purchase is made or a contract is signed—not a moment before, not a moment after.
The Flywheel
Engagement → Retention → Revenue → Referral
The value delivery and compounding motion. All work whose purpose is to deliver the product or service, confirm the customer received value, collect payment for that value, and convert satisfaction into new demand. The Flywheel is circular—Referral feeds back into Awareness and Acquisition.
The Off-Ramp
The deliberately designed exit zone. All work whose purpose is to manage a customer's departure. The Off-Ramp is not a failure state. It is a required zone. Every value stream that omits it has an undesigned exit experience by default.
Off-boarding Path
Triggered when an engagement completes as designed. A final pass through Engagement→Retention→Revenue→Referral, calibrated to a successful conclusion. The highest-probability advocacy moment in the entire value stream.
Emergency Exit Path
Triggered by churn signals—disengagement, health score drop, or an early exit request. A time-bounded intervention runs first. If recovery succeeds, the customer returns to the Flywheel. If it doesn't, a designed Engagement→Retention→Revenue→Referral exit ensures the door stays open.
Most businesses spend years perfecting their Funnel. Many invest in their Flywheel. Almost none deliberately design their Off-Ramp. That asymmetry is a structural error—and the customers who leave through an undesigned exit are the ones who take their referrals with them.
The Seven Stages
Every customer moves through the same seven stages. Every single one. The question is whether your team can name them—and whether your organization has designed what happens at each one.
The AAAERRR Framework
(pronounced "AIR")
Zone 1 — The Funnel
They know you exist. Not shopping, not comparing—just aware that your business is out there. The organization's work: reach the right people with a message that creates recognition.
They raise their hand. A form submission, an inquiry, a demo request, a reply to outreach. They are now a lead in your system. The organization's work: capture expressed interest, qualify it against your ICP, and decide whether to pursue.
They commit. Money changes hands or a contract is signed. This is the conversion event—the exact moment a prospect becomes a customer and the Funnel becomes the Flywheel. Note: kickoff calls, onboarding, and first delivery are not Activation—they're the beginning of Engagement.
Zone 2 — The Flywheel
You deliver what was purchased. This is the operational delivery motion—the thing that was promised is being provided. Engagement runs in two distinct loops: Onboarding (runs once, ends at the First Value Moment) and Recurring Delivery (runs as many times as the business model requires).
You confirm the customer is experiencing value. This is stewardship, not delivery—checking in, validating outcomes, and monitoring for early signals of disengagement. Retention is where churn is prevented before it starts, not after.
You collect payment for delivered and confirmed value. This is invoicing, billing, subscription charges—the economic formalization of value delivery. The sequence is inviolable: value delivered, value confirmed, then payment collected. Payment always follows proof.
A satisfied customer becomes an advocate. A testimonial, a review, a peer introduction, a case study. Referral is the compounding mechanism—the stage that makes the entire value stream self-sustaining. Referral outputs route back to Awareness (proof assets) and Acquisition (referral introductions), closing the loop.
Here's what I've come to appreciate most about this structure: it creates precise, atomic language for what is often muddy. When someone asks "what stage is this customer in?" the answer shouldn't require three paragraphs of context. It should be a single word—or two: "We're in Activation." "This is a Retention conversation." "They've moved to Off-Ramp." Each of those sentences takes two seconds to say. Everyone immediately understands what it means.
One Framework, Three Lenses
In 1913, Ford took the Model T from 12.5 hours to 93 minutes to build. By any operational measure, it was one of the most successful process redesigns in industrial history. By one other measure — the human one — it was a catastrophe. Ford turned over a workforce of 14,000 people 3.7 times in a single year. The work had been optimized. The people doing it were leaving as fast as they could be replaced.
This is what happens when you design the Operation Map for throughput, design the Customer Experience for satisfaction, and never once ask what the work is doing to the team delivering it. Two of the three lenses were sharp. The third wasn't in the frame at all.
AAAERRR holds all three simultaneously. As an owner or operator, you live at the intersection of three perspectives that must be in alignment. The Operation Map is the foundation — the designed structure of how work actually gets done, specific to a product or service. The two experience lenses are what you hold up to it: one facing outward toward the customer, one facing inward toward the team.
Looking Outward
The Customer Experience
Externally, AAAERRR maps the path your customer travels as they experience your business from first impression to lasting advocacy.
The touchpoints, the moments of truth, the feelings at each stage. Where do they feel welcomed? Where do they feel confused? Where do they feel compelled to tell someone about you?
Looking Inward
The Team Experience
Internally, AAAERRR maps what the work asks of the people doing it — at every stage, in every handoff, across every delivery cycle.
Where is the team stretched beyond design? Where is heroic effort baked into the model? Where do people feel ownership — and where do they feel like they're improvising in the dark?
The Foundation
The Operation Map
The Operation Map is what both experience lenses are pointed at. It maps 1:1 with a specific product or service and contains the workflows, stages, and steps that describe exactly how work gets done inside each AAAERRR zone.
The AAAERRR Framework tells you what kind of work is happening. The Operation Map tells you what actually happens. You cannot improve what has not been designed — and you cannot hold the two experience lenses up to work that has never been made visible.
If you've encountered the term value stream in lean manufacturing, operations literature, or earlier Deliberate Work content — this is the same concept, with a better name. Value stream is accurate but abstract. Operation Map says what it actually is: a map of how your operation runs, specific to one product or service. We're making the switch because the name should do the work of explaining itself.
The power of this structure is in holding all three simultaneously. When you look at Activation only through the Customer Experience lens, it's about confidence — does the customer feel certain they made the right choice? When you look at it only through the Team Experience lens, it's about clarity — does the team know what they've committed to deliver? The Operation Map is where those two questions meet: is the work between commitment and kickoff actually designed to answer both?
Ford answered one question brilliantly and ignored the other two. Most businesses are doing a version of the same thing — just at smaller scale, with slower consequences, and without the assembly line to make it obvious.
Three lenses misaligned produces three distinct failure modes: a great Operation Map that delivers a poor customer experience. A great Customer Experience delivered by a team that's burning out. And a team that loves the work but produces inconsistent results because the Operation Map was never designed in the first place. All three are common. All three are fixable — but only once you can see them. We'll go deep on building the Operation Map in a dedicated piece. The Team Experience lens gets its own treatment too.
Zone 1: The Funnel in Depth
The Funnel is linear by nature. Someone becomes Aware of you, raises their hand through Acquisition, and commits through Activation. Every new customer passes through this sequence exactly once.
The most common Funnel design error isn't in any single stage—it's at the boundary between Activation and the Flywheel. Teams routinely classify post-commitment work as Activation: kickoff calls, onboarding preparation, first delivery meetings. These are all Engagement. The moment the contract is signed, the customer has left the Funnel. Every step that follows happens in the Flywheel.
Why does this boundary matter? Because the Funnel and Flywheel have different owners, different questions, and different failure modes. When you blur the Activation/Engagement boundary, accountability dissolves. Sales thinks their job extends into onboarding. Operations thinks commitment is already secured before they have full context. The customer ends up re-explaining their situation to a delivery team that hasn't received the handoff.
The Activation → Engagement Handoff Contract
Every Funnel-to-Flywheel crossing requires a formal handoff. Before the delivery team takes ownership, Sales must produce:
- → The executed commercial agreement
- → A complete contact list (decision-maker, day-to-day owner, billing contact)
- → A plain-language scope summary—what was actually committed
- → Timeline constraints and hard deadlines
- → Risk flags—anything the delivery team needs to know that could affect success
Delivery work MUST NOT begin before this package is confirmed complete. Starting on an incomplete handoff is not a Delivery problem—it's a Funnel design failure.
Businesses that only focus on the Funnel are on a treadmill. They're constantly filling the top, constantly acquiring, constantly spending energy getting new customers in the door—because nothing on the other side is spinning. No Retention. No Referral. Just a leaky bucket and a marketing budget that never stops growing.
Zone 2: The Flywheel in Depth
The Flywheel begins the moment a commercial commitment is made and ends when the customer's relationship with your organization concludes. It is circular—Referral outputs feed back into Awareness and Acquisition, making the Flywheel the engine of compounding growth.
But before Referral can feed Awareness, you have to get through Engagement.
Engagement Has Two Distinct Loops
Loop 1 — Onboarding
Runs once per customer. Transforms a newly committed customer into an actively delivering relationship. Ends at the First Value Moment—the specific, defined event at which the customer first experiences the core value of what they purchased.
Example: not the kickoff call—the first time the customer says "yes, this is working, this is what I bought."
Loop 2 — Recurring Delivery
Runs N times. The ongoing provision of the product or service after First Value has been established. Each cycle produces a delivery event that Retention validates.
Onboarding failure and recurring delivery failure have entirely different root causes. Confusing them produces the wrong diagnostic and the wrong fix.
After Engagement delivers, Retention validates. This is stewardship, not delivery—checking that the customer is actually experiencing the value of what was provided. Retention includes at least one sentinel: a monitoring mechanism that watches for absence signals and automatically routes to the Off-Ramp when recovery hasn't happened within a defined window.
Concept: The Sentinel
Your early warning system for churn — defined before you need it.
A sentinel is a defined condition — not a feeling, not a hunch — that tells your team a customer relationship may be at risk. Its job is to convert an invisible problem into a visible trigger before the customer has already decided to leave.
Most businesses discover churn after the fact. A client goes quiet. Someone notices. Someone follows up. Maybe. The sentinel replaces that accidental process with a designed one — a specific, agreed-upon signal that says: something is wrong, and we have a defined window to respond.
What a sentinel watches for:
The time window.
When a sentinel fires, it opens an intervention window — a defined period in which your team attempts recovery. The window does two things: it creates urgency (someone owns this and the clock is running) and it creates a boundary (when the window closes without recovery, the Off-Ramp activates automatically). Not when someone decides. Not when it becomes obvious. When the window expires. That automaticity is what separates a designed sentinel from a good intention.
In a manual operation, a sentinel is a team agreement.
You do not need a CRM with health scoring to have a sentinel. You need a defined answer to one question, agreed upon by the team before any specific customer triggers it:
"At what point does silence become a signal — and what do we do when it does?"
In practice: "If a client hasn't responded to two consecutive check-ins within 10 business days, that account is flagged. The account owner has five business days to re-establish contact. If contact isn't re-established, the account moves to the Off-Ramp intervention workflow." That's a sentinel. It lives in a shared doc, a CRM field, or a standing agenda item in your weekly ops meeting. The tool is irrelevant. The agreement is everything.
Then Revenue collects. The sequence is not negotiable: value delivered (Engagement), value confirmed (Retention), then payment collected (Revenue). Invoicing before value confirmation is not just an operational error—it's a retention risk. Every Revenue invoice should reference what was delivered. Invoice-only billing that doesn't acknowledge delivery creates friction in a relationship that is still fragile.
Finally, Referral earns advocacy. Not assumes it. Referral must not be triggered until Retention has confirmed value and Revenue's financial relationship is clean. Asking for a testimonial during an unresolved billing dispute or before the customer has confirmed they're getting value is a structural error that damages the relationship rather than compounding it.
In recurring businesses—SaaS, retainers, subscriptions—the Flywheel loops. Engagement→Retention→Revenue→Referral cycles repeatedly. In project-based businesses, it runs once. But even in a single-project engagement, the quality of ERRR determines whether you get Referral or Reset. A great Engagement experience that flows into genuine Retention leads to Revenue that feels fair and Referral that's organic. A poor ERRR experience means you're filling the Funnel from scratch, every time.
Zone 3: The Off-Ramp
This is the zone that most businesses haven't designed.
Every customer relationship ends. The ending might be unplanned—a customer who went quiet, stopped engaging, or chose to exit early. Or it might be planned—a project that completed, a contract that reached its term, a service fully delivered. Both are exits. Most organizations handle both the same way: reactively, inconsistently, and without intention.
The Off-Ramp changes that. It treats departure with the same intentionality as acquisition. And it is built on a single structural principle that most organizations miss entirely:
Both Off-Ramp pathways run through Engagement → Retention → Revenue → Referral.
Not as a formality. As a deliberately designed exit experience—calibrated to the context of the exit, but always complete. Every customer who leaves your organization goes out through a final Engagement, a final Retention conversation, a clean financial close, and a Referral ask. No exceptions.
The Off-Ramp contains two structurally distinct pathways—both required, both built on this same Engagement→Retention→Revenue→Referral foundation. What differs between them is the character of each stage, not whether it happens.
| Stage | Emergency Exit Path Client self-selected out | Off-boarding Path Engagement completed as designed |
|---|---|---|
| Engagement | Wrap up what exists. Transfer whatever work product, documentation, or access has been completed to date. Leave nothing stranded. The client gets everything they've paid for, in a usable state. | Final delivery and knowledge transfer. The last mile of operational work—deliverable submission and sign-off, documentation handoff, access transfer. The engagement's operational obligations are complete. |
| Retention | An honest, unhurried conversation. Acknowledge what happened. Don't defend. Find out what the client needed that they didn't get. Capture it—not for the argument, but for the design improvement. Close the relationship with warmth. | Formal acceptance and relationship close. Did the work meet the agreed criteria? Capture satisfaction quantitatively and qualitatively. Recognize the client's team for their role in the success. Acknowledge the conclusion with genuine gratitude. |
| Revenue | Settle fairly. Invoice only for work completed and delivered. Resolve any outstanding balances, retainer credits, or overages cleanly. Send a final statement. Make the financial close as clean as the relationship close. | Complete financial settlement. Final invoice, all balances reconciled, payment collected, financial records archived. The commercial relationship closes at zero. Referral does not begin until Revenue is settled. |
| Referral | Still ask. Not for a glowing testimonial—for an honest reflection. "If you were advising someone considering working with us, what would you tell them?" A client who left early but was treated with dignity will remember that distinction. They will refer you—eventually—precisely because you didn't disappear when it got hard. | The highest-probability advocacy moment in the entire value stream. Full value delivered, finances clean, experience fresh. Testimonial, review, case study, referral introduction. This Referral moment is worth more than any mid-engagement ask. Don't leave it undesigned. |
Pathway 1 — The Emergency Exit Path
Triggered by disengagement or explicit exit request
The Emergency Exit Path activates when a customer is leaving against the design intent of the value stream. Four sentinel conditions trigger it: the customer has dropped below your defined engagement threshold; their account health score has fallen below the circuit breaker; an intervention window has closed without successful recovery; or the customer has explicitly requested cancellation or pause at any point before the final Engagement step.
Before the Exit Path's Engagement→Retention→Revenue→Referral begins, a time-bounded intervention runs. If the intervention succeeds within the defined window, the customer returns to the Flywheel. If it doesn't—or if the customer has explicitly requested exit—the Engagement→Retention→Revenue→Referral sequence activates. The intervention MUST have a defined time boundary. When that boundary expires without recovery, the Off-Ramp activates automatically. Not when someone notices. Automatically.
Clients who self-select out of an engagement early are often doing so because something didn't work. How you respond to that moment is a marketing decision, not just an operational one. A competitor who handles the same exit badly becomes your best sales tool. A client who left you—but was treated with dignity, given their work product cleanly, settled fairly, and asked for an honest reflection—will remember you when their next provider inevitably disappoints them.
Pathway 2 — The Off-boarding Path
Triggered by successful completion of the final Engagement step
The Off-boarding Path activates when a customer is leaving as designed—the engagement has concluded, value has been delivered, and the relationship is transitioning to close. The client is satisfied. The goal is to honor that satisfaction with a final experience that matches the quality of everything that preceded it.
The Off-boarding Referral moment is the highest-probability advocacy ask in the entire value stream. The client has received full value. The financial relationship is clean. The experience is fresh. An off-boarding path that terminates at Revenue financial close without a designed Referral workflow is leaving the highest-return advocacy opportunity undesigned—and it happens at scale, invisibly, in every professional services and project-based business that doesn't have one.
Off-boarding Referral produces two classes of output with distinct routing:
- → Advocacy outputs for new contacts (testimonials, case studies, referral introductions) route to Awareness as proof assets and to Acquisition as qualified inbound demand.
- → The former client themselves, should they wish to re-engage, re-enters at the beginning of Activation. Not Awareness. Not Acquisition. Awareness is established. Fit is proven. The only open question is whether they're ready to commit to a new engagement.
The final impression of your organization is set during the exit—not during delivery. A client who exits through a designed Off-Ramp will remember you. A client who exits through no Off-Ramp at all will remember that too. So will the next three people they talk to about finding a provider.
The Emergency Exit Path and the Off-boarding Path are mutually exclusive—a customer cannot be in both simultaneously. If a customer triggers a sentinel condition before the final Engagement step, they route to Emergency Exit. If they complete the final Engagement step, they route to Off-boarding. This boundary must be designed explicitly. In most organizations, it doesn't exist—which means every exit is effectively the same: unintentional.
Diagnosing Pain Points Across All Three Lenses
Here's where the zone structure combined with the three lenses becomes a diagnostic tool. When you break AAAERRR into its zones and look at each stage through all three perspectives, you start to see problems you couldn't see before — because most of them are hiding in the gap between two lenses that have never been looked at together.
These are the kinds of conversations I have with founders, GMs, and operators every week. See if any of them sound familiar.
Funnel Pain: "We get plenty of leads but nothing converts."
Operation Map: Your Awareness is working—marketing is generating demand. But your Acquisition stage has no qualification criteria. Every lead gets the same treatment regardless of fit. Qualified ones wait too long and go elsewhere.
Customer Experience: The customer felt attracted by your message but confused by the next step. They filled out a form and heard nothing for a week. Or got a generic response that didn't acknowledge their specific situation. The experience didn't match the promise that created the Awareness.
Flywheel Pain: "We do great work but clients never come back."
Operation Map: Your Engagement stage is strong—the work itself is excellent. But Retention doesn't exist as a defined stage. Once the project is delivered, there's no follow-up system, no check-in, no mechanism for maintaining the relationship.
Customer Experience: The customer loved the work. But after delivery, they felt abandoned. No one asked if things were working. When they needed something else six months later, they didn't think to call you—because you disappeared.
Zone Boundary Pain: "Projects always start messy."
Operation Map: There's a gap between Activation and Engagement—the handoff contract doesn't exist. A contract gets signed and then... what? Sales to operations is improvised every time. Your people start work without knowing what "done" looks like.
Customer Experience: The customer had a great sales experience. Then they met the delivery team and had to re-explain everything. The confidence they built during Activation evaporated in the first week of Engagement.
Off-Ramp Pain: "We finish strong but rarely hear from clients again."
Operation Map: There's no Off-boarding Path. The final invoice goes out and the relationship ends by default. No designed final delivery experience, no formal acceptance, no satisfaction capture, no advocacy ask. The engagement simply... stops.
Customer Experience: The customer experienced excellent work throughout. Their final interaction with your company was receiving an invoice. That's the last impression. That's what they remember when a colleague asks if they should hire you.
Team Experience: Nobody owns the exit. The delivery team hands off the final asset and moves to the next project. There's no designed moment to capture what worked, what didn't, or what the client would say about you. Institutional knowledge walks out the door with the relationship.
Team Experience Pain: "We deliver great work but can't keep good people."
Operation Map: Heroic effort is baked into the delivery model. The work gets done, but only because individuals absorb the gaps that the design never accounted for. There are no defined handoffs, no clear completion conditions, no sense of where one person's responsibility ends and another's begins.
Customer Experience: Clients love the output. The relationship feels personal, attentive, high-touch. What they don't see is that "high-touch" is code for "someone is working nights to make this look effortless."
Team Experience: Your best people leave first — because they have options and they know what sustainable looks like. What remains is a delivery model that depends on whoever hasn't burned out yet. Ford turned over 14,000 people 3.7 times in a year. Your version is quieter. The math is the same.
Notice the pattern. The three lenses reveal different dimensions of the same problem. The Operation Map shows you the structural breakdown. The Customer Experience shows you the emotional consequence for the person paying you. The Team Experience shows you the human cost of the gap. You need all three to truly understand what's happening — and to design a solution that actually holds.
How to Apply This Today
You don't need a six-month initiative to start using AAAERRR. You need a whiteboard, your leadership team (or your direct reports, or just yourself on a Sunday morning), and an honest conversation. Here's where to begin.
Name your stages—honestly.
Walk through all seven stages and describe—in your own words—what each one looks like in your business today. Not what you wish it looked like. What actually happens. If a stage doesn't really exist yet, say so. An absent stage is useful information—it tells you exactly where to focus.
Look at each stage through both lenses.
For each stage, ask two questions: "What does my team do here?" (value stream) and "What does my customer experience here?" (customer experience). Write both answers down, side by side. Where they align, you have a working stage. Where they diverge, you've found a problem worth solving.
Check your zone boundaries.
Ask three questions: Does a formal handoff package exist between Activation and Engagement—and does delivery never start without it? Does Retention have a sentinel—an automatic trigger that routes to Off-Ramp when defined conditions are met? Does an Off-boarding Path exist for completed engagements, with a designed Referral advocacy workflow? If any of these is missing, you've found your highest-leverage design opportunity.
Find the constraint.
Look at your seven stages and ask: where does the most friction live? Where do things slow down, fall apart, or require heroic intervention—usually yours? In almost every organization I've worked with, there's one stage that's quietly strangling everything downstream. Name it. That's your starting point.
Assess your flywheel—and your Off-Ramp.
Ask: is Referral generating new Awareness? Are past customers re-entering at Acquisition or Activation? And when customers leave—planned or unplanned—what does that experience look like? If the answer to that last question is "it just kind of... happens," you don't have an Off-Ramp. You have an undesigned exit.
A Shared Language Changes Everything
There's a moment in every engagement I have with an owner or operator where the vocabulary clicks. They stop describing problems in essays and start naming them in a word. More importantly, their team starts using the same words—and suddenly, leadership meetings get shorter, cross-functional alignment gets easier, and the real issues surface faster.
"Our Activation-to-Engagement handoff is broken—customers are re-explaining their needs to the delivery team."
"We're strong in Engagement but we have no Retention stage at all. People love the work, but we disappear after delivery."
"Our Off-boarding Path doesn't exist. We're finishing engagements and walking away without a Referral ask."
"Our flywheel isn't spinning. We're 100% funnel-dependent."
Each of those sentences takes five seconds to say and an entire team immediately understands what it means. Compare that to the twenty-minute explanation you'd need without the vocabulary.
That's what a shared language does. It compresses complexity into clarity. It makes the invisible visible. It gives every level of your organization—from the front line to the C-suite—permission to point at something and say "this is where the problem is" without needing three meetings of context to get there.
You can't improve what you can't name. AAAERRR gives you the names. The three lenses give you the perspective. The three zones tell you where to look. And the Off-Ramp reminds you that how you end things matters as much as how you begin them.
That's when the real work—the deliberate work—begins.
Give your business air.
Three zones. Seven stages. One language. Name them, see them from both sides, find the constraint—then design the fix.
Where This Framework Came From
Credit where it's due: AAAERRR builds on Dave McClure's 2007 "Pirate Metrics" framework—AARRR—which became the lingua franca of SaaS growth teams everywhere.
McClure's Original Five:
- Acquisition — How do users find you?
- Activation — Do they have a good first experience?
- Retention — Do they come back?
- Revenue — Do they pay?
- Referral — Do they tell others?
It was elegant, memorable, and designed for one context: tracking users through a software funnel. But as I spent years helping businesses systematize their work—from solopreneurs to organizations with thousands of employees—drawing on the convergence of expertise research and work design that shaped Deliberate Work—I found the vocabulary almost universally applicable but structurally incomplete.
Awareness was missing at the start. Before someone can find you, they need to know you exist. Engagement was missing in the middle—the actual work of creating and delivering value was glossed over entirely. And perhaps most critically, the exit was missing from the end. Every business model has exits. Not one of them was designed.
AAAERRR adds those missing pieces—two stages and a complete third zone—transforming a growth-hacking tool into a shared language for how work gets done across the full arc of every customer relationship.
Sources & Further Reading
- On the original Pirate Metrics: McClure, D. (2007). "Startup Metrics for Pirates: AARRR!" 500 Startups. Original blog post.
- On value stream thinking: Rother, M. & Shook, J. (1999). Learning to See: Value Stream Mapping. Lean Enterprise Institute. The foundational text on understanding how value flows through organizations.
- On customer experience design: Kalbach, J. (2016). Mapping Experiences. O'Reilly Media. A practical guide to understanding interactions from both organizational and customer perspectives.
- On the importance of the Engagement stage: Reichheld, F. F. (2003). "The One Number You Need to Grow." Harvard Business Review. Research showing that the quality of ongoing engagement predicts business outcomes better than acquisition metrics alone.
- On clear vocabulary and systems: Meadows, D. H. (2008). Thinking in Systems: A Primer. Chelsea Green Publishing. Demonstrates how the right language shapes how we see and manage complex systems.
- On the complete methodology: For the full framework on designing deliberate systems, Deliberate Work covers the methodology in depth. Get on the early access list.