Starting ARR
Opening ARR at the beginning of the period — the baseline against which the period's ARR waterfall (new + expansion − downgrades − churn) reconciles to ending ARR. Equal to the prior period's closing ARR by construction. The FlowSubform widget binds starting_arr as the `start` slot of the ARR-bridge flow, and the ending position is computed as start + Σ(deltas). Common pitfall: restating starting_arr mid-period to "fix" a prior-period reporting error breaks the period-over-period audit trail; corrections should land as a separate restatement note, not by editing the opening balance. — Sales KPI, I'mBoard-authored (editorial tier).
I'mBoard-authored (editorial tier)
No public third-party standard anchors this KPI yet, so I'mBoard authors and maintains the definition — transparently labeled as editorial tier. See the ontology methodology for the published vs editorial tier system and the back-attribution workstream.
Rogue ID: sales.starting_arr
Type: Currency
Domain: Sales
Definition
Opening ARR at the beginning of the period — the baseline against which the period's ARR waterfall (new + expansion − downgrades − churn) reconciles to ending ARR. Equal to the prior period's closing ARR by construction. The FlowSubform widget binds starting_arr as the start slot of the ARR-bridge flow, and the ending position is computed as start + Σ(deltas). Common pitfall: restating starting_arr mid-period to "fix" a prior-period reporting error breaks the period-over-period audit trail; corrections should land as a separate restatement note, not by editing the opening balance.
Formula
Starting ARR = ARR snapshot at period open = the prior period's closing ARR. Identity that must hold: starting_arr + new_business + expansion − downgrades − churn_arr = ending ARR (sales.arr at period close). Reconcile any gap as a "data quality" line and root-cause it before next period.Why it matters
The anchor of the ARR waterfall — without an explicit starting point, the period's net-new ARR cannot be audited. Boards expect the waterfall to reconcile to the penny, period over period.
How to interpret
If starting_arr ≠ prior-period ending ARR, there is either a restatement or a data issue — surface it explicitly. Beyond that the value itself is descriptive, not interpretive; the interpretive work happens on the delta lines.
Calculation policy
How an AI agent should compute this KPI from messy company data. Free-text rules consumed at reasoning time — not a deterministic DSL. The most common ways to get this wrong are listed under Common miscomputations.
Inclusion rules
- ARR snapshot at the exact open of the period.
- By identity, equals the prior period's closing ARR (
sales.arrat prior period close).
Exclusion rules
- Any in-period activity (new business, expansion, churn, downgrades) — Starting ARR is the opening balance only.
- Restatement corrections — never edit the opening balance to fix a prior error; land corrections as an explicit restatement line.
Required inputs
- Prior period's closing ARR.
Data-source priority
- Prior period's board-reported closing ARR (the audited / agreed number).
Edge cases
- First period a company tracks ARR: Starting ARR is whatever the historical ARR was at that open; if unknown, disclose as "first tracked period — opening balance estimated."
- Restatement of a prior period: Starting ARR for the current period uses the RESTATED prior close, with the restatement disclosed. Do not silently absorb it.
- Acquisition that closed exactly at period open: decide whether acquired ARR is in the opening balance or appears as an in-period inorganic line, and disclose.
Validation checks
- Starting ARR === prior period closing ARR. Any inequality is a restatement or a data error — never let it pass silently.
- Starting ARR + New Business + Expansion − Downgrades − Churn === Ending ARR. The waterfall must reconcile to the penny.
Common miscomputations
- Restating Starting ARR mid-stream to "fix" a prior reporting error — breaks the period-over-period audit trail; corrections belong in a restatement note.
- Using current-period ARR as the starting balance (off-by-one-period error) — the whole waterfall then fails to reconcile.
- Letting Starting ARR drift from prior closing ARR because the two are computed by different teams from different snapshots.
- Folding acquired ARR into Starting ARR without disclosure — masks how much of "growth" was inorganic.
Related KPIs
sales.arrsales.new_businesssales.expansionsales.churn_arrsales.downgrades
Source
I'mBoard editorial — authored and maintained by I'mBoard, first published 2026-04-01. No third-party standard is cited for this KPI; when one emerges, the definition is back-attributed and promoted to the published tier (a minor version bump). Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.
Stage relevance
| Company stage | Priority |
|---|---|
| Pre-Seed | Core |
| Seed | Core |
| Series A | Core |
| Series B | Core |
| Series C+ | Core |
| Public | Core |
Suggested for stages: Pre-Seed, Seed, Series A, Series B, Series C+, Public.
Default owning functions
- Finance
- Sales
Machine-readable
- This KPI as JSON:
/api/ontology/sales/starting_arr.json - All Sales KPIs:
/api/ontology/sales.json - Full catalog:
/api/ontology/index.json
Quarterly Forecast
The team's expected closed-won dollars for the current quarter — usually a sales-leader judgment call informed by weighted forecast but adjusted for deal-by-deal commit confidence. Distinct from weighted_forecast (which is mechanical, stage × probability). Boards read both: a quarterly_forecast materially below weighted_forecast means the team has explicit negative judgment on specific big deals; above it means they're calling deals stronger than the stage probabilities suggest. Common pitfall: anchoring the call to plan rather than reality — boards quickly learn to discount "we will hit plan" forecasts and reward calibrated commit-vs-actual track records. — Sales KPI, I'mBoard-authored (editorial tier).
Sales Strategic Context
Executive-summary narrative for the sales section of the board pack — the CRO/CEO's one-screen synthesis of overall sales performance, market dynamics, and the story behind the quarter's numbers. Categorical state derived from operational reporting — no calculation. Renders via ExecutiveCommentary widget as multi-section tabbed prose with per-section word counts. Common pitfall: writing it as a numbers-recap repeats what the KPI table already shows; the goal is the connective tissue — why the numbers moved, what changed in the market, what the next 90 days look like. Boards read this first when scanning the deck. — Sales KPI, I'mBoard-authored (editorial tier).