Pirate Metrics AARRR

Origin & evolution

Dave McClure introduced AARRR in August 2007 in a presentation titled "Startup Metrics for Pirates," first delivered at Ignite Seattle. The framing was deliberately irreverent, but the underlying argument was precise: most early-stage teams track a single vanity number for "growth" and cannot say where users drop off, what a good first experience looks like, or which lever to pull next. McClure's five-stage decomposition forces those questions into the open. The SlideShare version (under his 500 Hats account, dmc500hats) spread rapidly through the startup community and became the default funnel⬇️FunnelGrowthA conversion funnel tracking user progressionView reference → template for growth teams. Since then the framework has been extended: Reforge and Brian Balfour introduced RARRA, which puts Retention first, for products where viral acquisition is irrelevant or where the team has not yet nailed habit formation. The five stages remain the standard starting point regardless of reordering.

How it works in practice

The framework defines five sequential stages. Acquisition: a user discovers the product through some channel. Activation: that user has a first experience valuable enough to count as "getting it." Retention: the user returns. Revenue: the user generates economic value, through a subscription🔂SubscriptionSales & RevenueA recurring subscriptionView reference →, purchase, or any monetisation event the business defines. Referral: the user brings others.

The discipline is in the precision. Every stage needs🫀NeedUserA user need, pain, desire, or constraintView reference → a definition specific to your product. Activation in a note-taking app might be "user creates and retrieves a note within the first session"; Activation in an analytics tool might be "user connects a data source🛢️Data SourceData & AnalyticsA data source or integrationView reference → and views a chart." Generic definitions produce generic results.

A worked example. A SaaS tool has 10,000 monthly signups (Acquisition). Of those, 3,000 reach the activation moment (30% activation rate). Of activated users, 1,800 are still using the product thirty days later (60% thirty-day retention). Of retained users, 900 are on a paid plan (50% revenue conversion). Of paying users, 180 referred at least one new signup in the same period (20% referral rate). The team now has five numbers, five conversations, and a map of where their biggest drop sits. In this case: Activation at 30% is the bottleneck worth attacking first.

When to use it (and when not)

AARRR earns its keep when growth feels diffuse and the team cannot articulate which stage is costing them most. The five-stage structure forces specificity. It also works well as a common language across product, marketing, and engineering, because it connects their work to the same funnel.

It is less useful in two situations. First, in B2B enterprise sales where the "user lifecycle" is a six-month deal cycle with many stakeholders🧑‍💼StakeholderTeam & OrganisationA person with influence over the productView reference →: the funnel stages still apply in principle but the metrics require significant adaptation. Second, early in a product's life before there is enough data to estimate any stage rate reliably. At that point the framework is useful as a hypothesis🧪HypothesisValidationA testable belief about a solutionView reference → structure, not as a ranking tool.

The failure mode most teams hit is conflating stages. Activation defined as "user signed up" collapses Acquisition and Activation into one measurement and makes the most important transition invisible. Treating Referral as a separate growth programme ignores that modern products embed viral loops inside Activation itself, for example via sharing a generated output or inviting a collaborator during onboarding. Measure Referral as a property of each stage, not only as a separate phase.

In the Unified Product Graph

Pirate Metrics is a funnel⬇️FunnelGrowthA conversion funnel tracking user progressionView reference → framework in the growth category. Each of its five stages maps to a metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → entity, where the metric captures the stage name, the definition of what counts as reaching that stage, and the current conversion rate.

• Acquisition rate tracks how users arrive, expressed as a metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → tied to the channels feeding it.
• Activation rate is a metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → that defines the first-value moment, the most product-specific definition in the funnel and the one that most directly predicts long-term retention.
• Retention rate becomes a metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → with a chosen time window, thirty days, ninety days, or weekly active use, depending on the product's natural cadence.
• Revenue rate is a metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → connecting the funnel to commercial outcomes🏆OutcomeStrategyA desired business or user outcomeView reference →.
• Referral rate is a metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → that closes the loop back to Acquisition.

Modelling all five as metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → entities in the Unified Product Graph means each stage can connect forward to the experiments🧫ExperimentValidationA test designed to validate a hypothesisView reference → being run against it and backward to the hypotheses that motivated them. The funnel is no longer a spreadsheet column; it is a set of live, linked nodes that carry their own context.