Skip to content
Arpeet Ravalji
← Frameworks & Ideas
// How to Build ARR Metrics from the Ground Up

Build ARR you can prove, from the ground up.

A decision tree, not a template. Start with your business model, follow the branches through source data, a data-quality assessment, methodology trade-offs, and movement buckets, then monitor and diagnose. Pick your model and the tree adapts to the questions that actually apply to you.

Your model:
  1. Stage 01

    What is your business model?

    Everything downstream branches from here, how ARR even exists is different for each.

  2. Stage 02

    What is your source data?

    Name the system of record for every field that touches revenue, before you trust any of it.

    Billing
    Zuora, NetSuite, Stripe, Chargebee, Maxio, SFDC CPQ…
    CRM
    Accounts, opportunities, close dates, product.
    Contracts
    Term, ACV, start/renewal dates, order forms.
    Usage logs
    Metered events for consumption.

    One field, one system of record. Where billing and CRM disagree, decide which wins, and write it down.

  3. Stage 03

    Run a full Data Quality Assessment

    You can't build ARR on data you haven't tested. The DQA is the high-level lens for everything that follows.

    Entity integrity
    Customer mapping (parent/child), primary keys, no critical nulls.
    Referential integrity
    No orphan line items; every charge ties to a contract & account.
    Domain integrity
    Dates, amounts, currency and term values are in valid ranges & formats.
    Business-rule integrity
    Term × amount reconciles; no overlapping or negative contracts.
    Completeness & coverage
    Every revenue-affecting event is captured, not in someone's inbox.
    Continuity
    History is intact across billing migrations, re-platforms, and re-IDs.
    ↩ Process issues surface here

    A failing check is rarely just data, it's a broken process. Mid-month upgrades not captured, manual overrides, missing renewal dates. Fix the upstream process, then re-run the DQA before you build. This loop is the whole game.

  4. Stage 04

    Choose your ARR construction methodology

    Every decision here is a trade-off. Make each one once, document it, and enforce it. Your model dims the ones that don't apply.

    ARR basis
    CommittedRecognizedInvoiced
    Trade-off · Committed is forward-looking but includes not-yet-live. Recognized ties to GAAP but lags reality.
    Annualization
    MRR × 12ACV ÷ term
    Trade-off · Run-rate reacts fast but is noisy; contract-value is stable but hides mid-term change.
    Multi-year & rampSubscription / Hybrid
    Full value at signingStep up at each tier
    Trade-off · Signing-value flatters early ARR; step-recognition matches cash but complicates the bridge.
    Unit modeling (usage → ARR)Usage / Hybrid
    Trailing 3-mo run-rateLast month × 12Committed minimum
    Trade-off · This is the hardest call for consumption. Run-rate captures reality; committed-minimum is defensible but understates.
    Product migration
    Treat swap as migrationChurn + new
    Trade-off · Migration keeps the bridge net-neutral; churn+new inflates both gross churn and new ARR.
    Non-recurring exclusions
    Exclude servicesExclude one-time
    Trade-off · Purists exclude everything non-recurring; the risk is stranding revenue nobody reconciles.
    Currency / FX
    Spot rateBudget rate
    Trade-off · Spot is accurate but adds FX noise to the bridge; budget rate isolates real growth.
    Activation rule
    Go-liveContract start
    Trade-off · Go-live is conservative and matches value delivery; contract-start counts committed-but-dark ARR.
  5. Stage 05

    Define your movement buckets

    Every dollar of change between periods lands in exactly one bucket. This taxonomy is your ARR bridge.

    New
    First ARR from a new logo.
    Expansion
    Upsell, cross-sell, price uplift.
    Reactivation
    A churned logo returns.
    Migration
    Product/SKU swap, net-neutral, not churn+new.
    Contraction
    Downgrades, seat cuts, usage decline.
    Churn
    Full cancellation of a logo.

    Then fix your retention base, start-of-period vs. available-to-renew (UFR). GRR and NRR mean nothing until this is locked.

  6. Stage 06

    Build the bridge, then monitor it

    ARR is a rate, not a quarterly artifact. Reconcile continuously and watch it like uptime.

    ARR bridge + retention views
    Beginning → movements → ending, by segment & product.
    Continuous reconciliation
    Tie ARR to subscription revenue, billings, deferred, every period.
    Anomaly & drift alerts
    Flag >20% single-customer swings and methodology drift in real time.
  7. Stage 07

    Troubleshoot & diagnose, MECE

    Now the metrics earn their keep. When a number moves, decompose it mutually-exclusive, collectively-exhaustive.

    Example: “Net ARR came in below plan, why?”
    Acquisition
    New ARR ↓
    • Fewer new logos
    • Lower new-logo ACV
    • Longer sales cycle / slipped deals
    Expansion
    Expansion ARR ↓
    • Upsell motion stalling
    • Cross-sell whitespace untapped
    • Price actions not landing
    Contraction
    Contraction ↑
    • Seat / license reductions
    • Usage decline (consumption)
    • Downgrades to lower tier
    Churn
    Gross churn ↑
    • Logo losses in a segment
    • Onboarding / value gaps
    • Concentration in at-risk cohort
    Measurement
    Data / timing
    • Methodology drift
    • Recognition timing vs booking
    • Reconciliation gap, not real

    Five branches, no overlap, nothing left out. Rule each in or out with the data, and the miss has exactly one home.

  8. Stage 08

    Turn diagnosis into strategy, and execute

    A clean diagnosis points at exactly one lever. Pull it, measure, and feed the result back into monitoring.

    Prioritize the lever
    The MECE branch that moved most is where the strategy goes first.
    Set the target metric
    Name the metric that must move, and by how much.
    Close the loop
    Execution feeds Stage 06 monitoring, the system learns.

You don't calculate ARR once. You build the system that produces it.

This is the build order. The Quality of Revenue Metrics are what you produce, the Integrity Pyramid is the maturity model, and the Readiness Ladder scores where you stand.