{
  "rogueId": "sales.carr",
  "slug": "carr",
  "domain": "sales",
  "defaultLabel": "CARR",
  "description": "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.",
  "fieldType": "currency",
  "unit": null,
  "maturity": "general",
  "suggestedForStages": [
    "preSeed",
    "seed",
    "seriesA",
    "seriesB",
    "seriesC",
    "public"
  ],
  "defaultOwningFunctions": [
    "Finance",
    "Sales"
  ],
  "stageRelevance": {
    "preSeed": "recommended",
    "seed": "core",
    "seriesA": "core",
    "seriesB": "core",
    "seriesC": "core",
    "public": "core"
  },
  "definitionSource": {
    "tier": "published",
    "sourceName": "SaaS Metrics Standards Board",
    "sourceUrl": "https://www.saasmetricsboard.com/contracted-annual-recurring-revenue",
    "sectionRef": "CARR",
    "publicationDate": "2023-01-01",
    "attributionNotice": "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."
  },
  "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.",
  "whyItMatters": "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.",
  "interpretationGuidance": "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.",
  "relatedKpiIds": [
    "sales.arr",
    "sales.new_business",
    "sales.blended_cac_ratio",
    "sales.new_cac_ratio",
    "sales.bookings_backlog_total"
  ]
}