SaaS Growth Frameworks Compared: SaaS Science vs AARRR, PLG, Revenue Architecture, and OKRs

Every SaaS framework claims to help you grow. The uncomfortable truth is that different frameworks applied to the same business with the same data will produce different diagnoses, different priorities, and different investment recommendations — sometimes contradictory ones.

This is not a theoretical problem. A founder using AARRR who sees low activation will often invest in onboarding improvements. A founder using PLG logic who sees low activation may instead try to find a product-viral loop. A founder using Revenue Architecture may see the same activation data and invest in better sales-to-CS handoff. All three frameworks are looking at the same number and prescribing different interventions — because the underlying models are different.

Framework choice is a strategic decision. Getting it wrong at $50K MRR means 12 months of investment in the wrong lever. Getting it wrong at $300K MRR means burning millions on acquisition while the business has a structural retention problem.

This article compares five major SaaS growth frameworks with rigorous specificity: what each framework models, what it misses, and which growth stage and problem type each framework is actually designed for.

Why Frameworks Matter: The Same Metrics, Different Diagnoses

Consider a B2B SaaS at $180K MRR with the following metrics:

• New MRR per month: $12,000
• Monthly churn rate: 4%
• Trial-to-activation rate: 38%
• NPS: 32

Now apply each framework:

AARRR diagnosis: Low activation (38%) is the problem. Fix onboarding. Referral (NPS 32) is also weak. Build a referral program.

PLG diagnosis: NPS 32 suggests the product does not generate enough delight to drive organic growth. Invest in viral loops and product-qualified lead scoring.

Revenue Architecture diagnosis: The sales-to-CS handoff is likely broken. Customers are not being set up for success in the onboarding phase. Redesign the handoff protocol.

OKR-based diagnosis: Set an OKR for "increase activation rate to 60% this quarter" and cascade key results to the product team.

SaaS Science diagnosis: Growth Ceiling = $12,000 ÷ 0.04 = $300,000 MRR. The company is at 60% of its ceiling. The Hourglass audit shows activation (38%) is a red stage, which is the root cause of the 4% churn. The retention scenario — fixing activation, targeting 2% churn — would raise the ceiling to $600,000 MRR at roughly 40–50% the cost of doubling acquisition. Fix activation first, then retention, then model the acquisition scenario once the churn is below 2%.

These are not equivalent diagnoses. AARRR, PLG, and Revenue Architecture identify activation as a symptom. SaaS Science identifies it as the cause of a churn problem that is mechanically capping revenue at $300K MRR. The intervention is different because the model is different.

Framework 1: Pirate Metrics (AARRR) — Dave McClure

What it is

AARRR — Acquisition, Activation, Retention, Revenue, Referral — was created by Dave McClure at 500 Startups in 2007. It is a five-stage funnel that organizes product analytics and marketing metrics by customer lifecycle stage. It introduced "Activation" as a distinct measurement category — a genuine contribution to SaaS thinking that predates most product analytics tooling.

Strengths

Stage-by-stage clarity: AARRR gives teams a shared vocabulary for discussing conversion at each stage. Before AARRR, most teams conflated acquisition and activation, or treated revenue as a single event rather than a process.

Universal applicability: Every SaaS business can map its metrics onto the AARRR framework. It is framework-agnostic: you can apply it to PLG, sales-assisted, or hybrid models.

Simplicity: Five stages, five metrics. Easy to explain to a board, easy to cascade to department heads.

Weaknesses

Acquisition-first bias by construction: The framework is ordered A-A-R-R-R. The first "A" is Acquisition. This ordering — while alphabetically convenient — implies that acquisition is the first priority. In B2B SaaS post-PMF, the bottleneck is almost always activation or retention, not acquisition. The framework's ordering creates a systematic bias toward the top of the funnel.

No predictive ceiling: AARRR is a descriptive framework — it tells you where conversion is happening, not what your revenue maximum is. There is no formula in AARRR that produces a ceiling calculation. You can know that activation is at 38% and churn is at 4%, but AARRR does not tell you what those numbers together mean for your maximum revenue.

No causal weighting: AARRR treats each stage as equally important. In SaaS, activation is the pivot stage — poor activation causes poor retention, which causes poor referral. AARRR does not model this causality; it treats each stage as a separate metric to optimize.

Designed for consumer internet, 2007: AARRR was built for early-stage consumer web startups where acquisition was genuinely the binding constraint (virality, user growth) and where churn was less financially consequential (free user models). Applied to B2B SaaS, it consistently points founders in the wrong direction.

Expansion is missing: The Revenue "R" in AARRR is about converting free users to paid — not about expansion revenue from existing customers. In B2B SaaS where NRR > 100% is a key lever, AARRR provides no explicit model.

Best used for

Pre-PMF consumer apps where user acquisition and activation are the primary unknowns. As a vocabulary layer for team communication about stage-specific metrics.

Framework 2: Product-Led Growth (PLG) — Wes Bush / OpenView

What it is

Product-Led Growth, popularized by Wes Bush's book and OpenView Partners' research, argues that the product itself should be the primary driver of acquisition, conversion, and expansion. In a PLG model, users discover and adopt the product without significant sales involvement; the freemium or free trial becomes the core acquisition mechanism; viral sharing and usage-based expansion are the growth engines.

Strengths

Lower CAC at scale: When it works, PLG dramatically reduces customer acquisition cost. Products like Slack, Figma, and Notion grow primarily through organic sharing rather than paid acquisition — the marginal cost of each new user trends toward zero.

Shorter time-to-value: PLG forces product teams to design for self-serve setup and immediate value — which are the same capabilities that drive high activation rates. A well-executed PLG product tends to have better activation than an equivalent sales-assisted product.

Natural expansion vector: PLG creates viral expansion within accounts. One user adopts the product, invites colleagues, the account expands. This is the structural driver of NRR > 130% for the best PLG businesses.

Weaknesses

Requires genuine product virality: PLG only works if the product has network effects or collaborative utility — features that are better when used with others. Most B2B SaaS does not have inherent virality. An analytics platform, a project management tool for a single department, or a compliance SaaS may have no natural sharing vector. Attempting to engineer PLG in a non-viral product wastes significant engineering time.

Ignores Growth Ceiling math: PLG frameworks do not include a ceiling calculation. You can be executing a perfect PLG motion and still have a 4% monthly churn rate that caps your revenue at $300K MRR. PLG identifies growth motions; it does not diagnose growth constraints.

Does not work for complex B2B sales: Products with 3–6 month enterprise sales cycles, multiple stakeholder sign-offs, custom contracting, or significant implementation requirements cannot be PLG-native. The self-serve model requires that the product can be evaluated and adopted without human involvement — which is not true for most mid-market B2B SaaS.

Product-qualified lead scoring is complex: PLG requires defining exactly which product behaviors predict conversion. This is harder than it looks and requires significant instrumentation and data science capacity that most $10K–$500K MRR companies do not have.

Best used for

Products with inherent network effects, collaborative features, or viral sharing mechanisms. Consumer-adjacent SaaS. Products where the core value can be experienced without setup (calculators, templates, communication tools). Not appropriate as a primary strategy for single-user utility products or high-touch B2B SaaS.

Framework 3: Revenue Architecture — Jacco van der Kooij

What it is

Revenue Architecture (Winning by Design) applies systems engineering and physics principles to the revenue process. It focuses on designing repeatable revenue processes with explicit stage definitions, conversion benchmarks, and handoff protocols. It introduces concepts like "customer lifetime revenue," "ARR yield," and the "bowtie model" — a visual that extends the acquisition funnel to show retention and expansion as symmetric to the acquisition side.

Strengths

Sales process rigor: Revenue Architecture is the most rigorous framework for designing and measuring a multi-stage sales process. Stage definitions, exit criteria, conversion benchmarks, and handoff protocols are explicit and measurable. For sales-assisted SaaS, this rigor produces consistently better conversion rates.

Bowtie model: The bowtie (which mirrors the Hourglass shape) correctly recognizes that post-sale stages are symmetric to pre-sale stages. This framing aligns well with the SaaS Hourglass and pushes CS teams to think in conversion terms, not just relationship terms.

Customer lifetime revenue focus: Revenue Architecture introduces "ARR yield" — the ratio of total customer revenue to total cost of acquiring and serving that customer. This is a useful complement to LTV/CAC analysis in the unit economics framework.

Weaknesses

Sales-process focus misses product: Revenue Architecture is primarily a framework for designing the sales and CS motion. It does not model product activation, product-usage retention, or the causal chain between product experience and churn. A company can implement perfect Revenue Architecture and still have a 4% churn rate driven by a broken product onboarding experience.

No predictive ceiling: Like AARRR, Revenue Architecture does not produce a ceiling calculation. The bowtie can tell you that your post-sale retention is 80% at 12 months, but it does not tell you what your maximum revenue is given your acquisition and churn parameters.

Complex implementation: Revenue Architecture introduces significant vocabulary and process sophistication that can be disorienting for teams below $500K MRR. The methodology is optimized for companies with dedicated sales, CS, and RevOps functions — which most bootstrapped B2B SaaS at $10K–$300K MRR do not have.

Expansion model is high-touch: Revenue Architecture's expansion model assumes deliberate, human-driven upsell motions. It does not model usage-based or product-led expansion, which are increasingly common.

Best used for

Companies with dedicated sales teams executing multi-stage, multi-stakeholder sales processes. Mid-market and enterprise B2B SaaS where handoff design between sales stages has measurable conversion impact. Revenue Architecture is complementary to, not competitive with, SaaS Science — use Revenue Architecture for the sales process design and SaaS Science for the ceiling and diagnostic analysis.

Framework 4: OKRs for SaaS — John Doerr / Google Adaptation

What it is

Objectives and Key Results (OKRs) is a goal-setting framework originating at Intel (Andy Grove) and popularized by John Doerr. Applied to SaaS growth, OKRs translate growth strategy into quarterly objectives (directional goals) and key results (measurable outcomes). Many SaaS companies use OKRs as their primary "growth framework," setting objectives like "improve retention" with key results like "reduce monthly churn to 2%."

Strengths

Goal alignment: OKRs create alignment across teams around shared outcomes. They are particularly effective at ensuring that product, marketing, sales, and CS are working toward the same quarterly priorities.

Cascadable: OKRs can be set at the company level and cascaded to department, team, and individual levels — creating a traceable chain from company strategy to individual output.

Time-bounded: Quarterly OKRs create urgency and regular review cadences that prevent strategic drift.

Weaknesses

OKRs are not a diagnostic tool: OKRs tell you what to optimize; they do not tell you what is actually wrong with your business. Setting an OKR for "reduce churn to 2%" does not identify whether churn is caused by poor activation, poor product quality, wrong-fit customers, or pricing issues. OKRs without a diagnostic framework optimize the wrong thing with high confidence.

Can optimize the wrong metric: A team with an OKR to "increase trial-to-activation rate" might hit the target by redefining activation more leniently — technically achieving the key result while the underlying problem worsens. OKRs require that the metric being optimized is genuinely causal, which requires a diagnostic framework to establish.

No ceiling calculation: OKRs have no concept of a mathematical growth constraint. A company can hit every OKR for four consecutive quarters and still be approaching its Growth Ceiling — because OKRs do not model the churn-ceiling dynamic.

Goal-setting is not strategy: The most common misuse of OKRs in SaaS is using them as a substitute for strategic analysis. "We will grow MRR by 20%" is an OKR, not a strategy. The strategy is: "We believe our binding constraint is activation (38%), which is causing 4% churn, which caps our ceiling at $300K MRR. We will invest in onboarding to raise activation to 60% and reduce churn to 2%, raising the ceiling to $600K MRR."

Best used for

Team alignment, prioritization, and execution cadence — after a diagnostic framework has identified the correct priorities. OKRs are a communication and accountability tool, not a growth diagnostic tool. Pre-PMF teams benefit from OKRs to maintain focus. Post-PMF teams need OKRs plus a diagnostic framework (the Hourglass) to ensure they are aligning around the right outcomes.

Framework 5: SaaS Science — Deterministic Equilibrium Model

What it is

The SaaS Science approach — as implemented in SaasDash.ai's Growth Ceiling framework and inspired by Dan Martell's SaaS Academy methodology — is built around a mathematical equilibrium model. The core insight is that every SaaS business has a theoretical maximum revenue determined by the ratio of new MRR to churn rate. This ceiling is not a future projection — it is a present fact, calculable today from current operating parameters.

The framework has three interconnected tools:

1. The Growth Ceiling formula — produces the ceiling calculation and lever analysis
2. The Hourglass audit — diagnoses which stage is causing the binding constraint
3. Unit economics validation — confirms whether the ceiling is financially sustainable to pursue

What is different

Deterministic, not probabilistic: The Growth Ceiling formula produces a single number — not a range, not a distribution. Ceiling = New MRR ÷ Churn Rate. At $15K new MRR and 3% churn, the ceiling is exactly $500K MRR. This is a present fact about the business, not a forecast. This determinism is what makes it auditable and defensible to a board.

Lever-specific, not assumption-range: Unlike financial projections that vary all assumptions simultaneously, the Growth Ceiling model isolates each lever. The scenario modeling methodology shows what happens when exactly one variable changes. This produces actionable, comparable investment options rather than sensitivity ranges.

Causal, not correlative: The Hourglass framework establishes a causal hierarchy: activation failure causes retention failure, retention failure causes referral failure. The framework forces diagnosis in causal order — you cannot score retention before scoring activation. This prevents the most common mistake in SaaS: treating symptoms (churn) rather than causes (poor activation).

Full-stack: SaaS Science covers the complete diagnostic surface — acquisition (ceiling numerator), retention (ceiling denominator), expansion (ceiling multiplier), and unit economics validation. AARRR covers five stages without a ceiling. PLG covers one growth motion. Revenue Architecture covers the sales process. SaaS Science covers the entire business.

Defensible math: Because the formula is closed-form and the inputs are auditable (MRR, new MRR, churn rate), the Growth Ceiling calculation can be presented to investors, boards, and advisors with full transparency. The ceiling is not an opinion — it is the output of a formula that any stakeholder can verify.

Weaknesses

Requires accurate data: The Growth Ceiling formula is only as good as its inputs. Companies with poor MRR tracking, inconsistent churn definitions, or unreliable activation measurement will get inaccurate ceiling calculations. The framework demands data discipline that some early-stage companies lack.

Less applicable pre-PMF: The formula assumes that churn rate and new MRR are stable, steady-state parameters. Pre-PMF, churn is highly variable as the product evolves and the ICP sharpens. The ceiling calculation is less meaningful when underlying parameters are changing month-to-month. See the Growth Ceiling vs PMF analysis for the boundary conditions.

Does not address PLG motions explicitly: SaaS Science is most naturally applied to sales-assisted B2B SaaS. For pure PLG businesses where activation and expansion are product-driven, the framework applies but requires adaptation — in particular, the new MRR numerator needs to include viral/organic acquisition that does not map to traditional "new customer" definitions.

Best used for

Bootstrapped or lightly-funded B2B SaaS between $10K and $500K MRR that have achieved PMF and are now in a growth phase. Founders who need to make specific investment decisions (acquisition vs. retention vs. expansion) and need defensible math to support those decisions. Companies preparing for fundraising who need to demonstrate growth constraint awareness.

Framework Comparison Table

When to Use Which Framework

Pre-PMF ($0–$10K MRR): OKRs for alignment and focus. AARRR for stage vocabulary. Do not apply the Growth Ceiling formula — your churn rate is a product signal, not a steady-state parameter. The ceiling calculation requires stable parameters that pre-PMF companies do not have.

Early post-PMF ($10K–$50K MRR): Introduce the Growth Ceiling calculation to establish the baseline ceiling. Run your first Hourglass audit to identify the primary bottleneck. Begin unit economics tracking. AARRR vocabulary is useful for team communication; do not let it drive investment priorities.

Growth phase ($50K–$300K MRR): Full SaaS Science methodology. Quarterly scenario modeling (acquisition, retention, expansion). Monthly Hourglass stage monitoring. Unit economics validation before scaling acquisition spend. OKRs for team execution, anchored to the specific scenario being executed.

Scale phase ($300K–$500K MRR and above): Revenue Architecture for sales process design and CS motion. SaaS Science for ceiling and retention diagnostics. PLG for acquisition diversification if the product has viral potential. OKRs for cross-functional alignment at increasing organizational complexity.

PLG-native products at any stage: AARRR plus PLG framework for product analytics and growth loop design. SaaS Science for retention analysis — even PLG businesses have churn, and the ceiling formula applies. The Hourglass audit applies but the "activation" stage is measured through product-activation signals, not onboarding completion.

The Selection Test: Four Questions Before Choosing a Framework

Before committing to a framework, answer these four questions:

1. Do I know my Growth Ceiling? If you have not calculated New MRR ÷ Churn Rate, run that calculation before choosing any framework. The ceiling tells you whether your binding constraint is acquisition (ceiling is far away) or retention (ceiling is close). This single data point narrows the framework selection dramatically. Use the Growth Ceiling Calculator to get your number.

2. Is my churn rate stable? If your monthly churn is varying by more than 1–2 percentage points month-to-month, you are likely pre-PMF or in a product quality crisis. In this state, the ceiling calculation is unreliable. Focus on product quality and ICP definition before applying any growth framework.

3. Do I have a sales team or a self-serve product? Sales-assisted B2B SaaS should combine SaaS Science (ceiling and diagnostic) with Revenue Architecture (sales process design). Self-serve or PLG products should combine SaaS Science (ceiling and retention) with PLG principles (acquisition loop design). The frameworks are complementary along this axis.

4. What decision am I trying to make?

• "Which lever should I invest in?" → SaaS Science scenario modeling
• "Which stage is broken?" → Hourglass audit
• "Is my sales process efficient?" → Revenue Architecture
• "Can my product grow virally?" → PLG assessment
• "How do I align my team?" → OKRs

No single framework answers all four questions. The SaaS Science stack — Growth Ceiling + Hourglass + unit economics — answers questions 1, 2, and 3. Revenue Architecture answers question 3 in greater depth. OKRs answer question 4.

The Integration Architecture

For most B2B SaaS between $50K and $500K MRR, the recommended framework integration is:

Diagnostic layer: SaaS Science (Growth Ceiling formula + Hourglass audit). This runs quarterly and produces the investment priorities.

Validation layer: Unit economics (LTV/CAC analysis, CAC payback period, NRR tracking). This validates that the ceiling being targeted is financially sustainable.

Execution layer: OKRs for team alignment, anchored to the specific scenario being executed (retention scenario → OKR for churn reduction; acquisition scenario → OKR for new MRR growth).

Process layer (if applicable): Revenue Architecture for sales process design when the company has a sales team executing a multi-stage process.

Vocabulary layer: AARRR for communicating stage-specific metrics to stakeholders unfamiliar with the Hourglass framework.

The frameworks do not compete — they operate at different levels of abstraction. SaaS Science provides the strategic diagnosis. OKRs translate strategy into execution. AARRR provides communication vocabulary. Revenue Architecture designs the sales/CS process that executes the strategy.

Red Flags in Framework Selection

Choosing a framework because it is popular, not because it matches your stage. PLG is the dominant framework in VC and media circles in 2025. That does not make it appropriate for a 50-customer, $100K MRR B2B SaaS with a 90-day sales cycle.

Using AARRR to prioritize acquisition when the bottleneck is retention. The framework's ordering creates a persistent bias. If you are running an AARRR review and your acquisition metrics look weak, resist the automatic conclusion that acquisition needs more investment. Run the Growth Ceiling calculation first — if your ceiling is close, the binding constraint is churn, not acquisition.

Applying OKRs without a diagnostic framework. "Improve activation" is an OKR that can be executed efficiently or inefficiently. Without a prior Hourglass audit showing which aspect of activation is broken, the OKR team will optimize for the easiest-to-move metric rather than the most causal one.

Switching frameworks when the current one is not producing results. Framework switching without changing underlying data collection and analysis is like changing the weather app when it is raining. Before switching frameworks, determine whether the problem is framework selection or data quality.

Treating Growth Ceiling scenarios as financial projections. The ceiling is an asymptotic maximum, not a 12-month target. Presenting a $1M MRR ceiling to a board as a "$1M MRR in 12 months" projection misrepresents the math and creates unrealistic expectations.

Conclusion

The same metrics produce different diagnoses under different frameworks because the frameworks model different things. AARRR describes stages without modeling causality or ceiling. PLG describes a specific growth motion without applying universally. Revenue Architecture designs processes without producing a ceiling calculation. OKRs align teams without diagnosing what to align them around.

SaaS Science — the Growth Ceiling formula plus the Hourglass diagnostic — is different because it is explicitly predictive, causal, and lever-specific. The ceiling is a present fact. The Hourglass finds the cause. The scenario model quantifies what each fix is worth. Every number in the system is auditable and expressible in dollars.

This does not mean SaaS Science replaces every other framework. It means it should be the primary diagnostic framework for post-PMF B2B SaaS — with OKRs, Revenue Architecture, and AARRR vocabulary operating as complementary layers.

If you have not run your Growth Ceiling calculation, start there. The Growth Ceiling Calculator requires three numbers you already have: current MRR, new MRR per month, and monthly churn rate. The output — your ceiling and a comparison of what each lever is worth — is the foundation that makes every other framework decision more defensible.

Cross-reference with the Hourglass framework for the diagnostic layer, the unit economics guide for the financial validation layer, and the Growth Ceiling vs PMF analysis to confirm you are past the boundary condition where the ceiling formula is applicable.