I'mBoardDocs
Board OntologySales

CARR

Contracted Annual Recurring Revenue — recognized MRR × 12 plus the annualized value of contracts that are signed but not yet live (i.e. implementation, ramp, deferred-start). Per the SMSB standard, CARR sits between ARR (live only) and pipeline (unsigned) on the revenue-certainty spectrum: contractually committed but not yet delivered. Boards reading CARR > ARR gap can quantify the in-flight implementation backlog and the leading indicator of next-period ARR. Common pitfall: counting verbal commitments or LOIs as CARR — only signed contracts qualify under the SMSB definition. — Sales KPI anchored to SaaS Metrics Standards Board.

Rogue ID: sales.carr Type: Currency Domain: Sales

Definition

Contracted Annual Recurring Revenue — recognized MRR × 12 plus the annualized value of contracts that are signed but not yet live (i.e. implementation, ramp, deferred-start). Per the SMSB standard, CARR sits between ARR (live only) and pipeline (unsigned) on the revenue-certainty spectrum: contractually committed but not yet delivered. Boards reading CARR > ARR gap can quantify the in-flight implementation backlog and the leading indicator of next-period ARR. Common pitfall: counting verbal commitments or LOIs as CARR — only signed contracts qualify under the SMSB definition.

Formula

CARR = ARR (live, recognized contracts annualized) + Annualized value of signed contracts not yet in production. Per SMSB §CARR: requires a signed contract; excludes verbal commitments, letters of intent, and pipeline. The (CARR − ARR) gap = in-flight ARR awaiting go-live.

Why it matters

A leading indicator that ARR alone misses — if CARR is growing faster than ARR, an implementation backlog is building and ARR will accelerate as those contracts go live. Boards use the CARR-to-ARR ratio to interrogate the implementation engine.

How to interpret

A CARR / ARR ratio of 1.00 means everything signed is already live (no implementation backlog); 1.10–1.20 is typical for enterprise SaaS with multi-month implementation timelines; > 1.30 may signal either an implementation bottleneck (operational risk) or a deliberate backlog-build before a known activation event (intentional). Always cross-reference with the implementation team's capacity plan.

  • sales.arr
  • sales.new_business
  • sales.blended_cac_ratio
  • sales.new_cac_ratio
  • sales.bookings_backlog_total

Source

SaaS Metrics Standards Board · section: CARR — published 2023-01-01.

Why does this cite SaaS Metrics Standards Board? Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.

Metric definitions reference standards published by the SaaS Metrics Standards Board (saasmetricsboard.com). imboard is not affiliated with, endorsed by, or a member of SMSB.

Stage relevance

Company stagePriority
Pre-SeedRecommended
SeedCore
Series ACore
Series BCore
Series C+Core
PublicCore

Suggested for stages: Pre-Seed, Seed, Series A, Series B, Series C+, Public.

Default owning functions

  • Finance
  • Sales

Machine-readable

On this page