Expansion Opportunities
Identified upsell, cross-sell, and seat-expansion opportunities inside the existing customer base, with deal size and timing where known. This is the qualitative narrative behind the expansion component of NRR — what the CS / Sales team sees in the pipeline that has not yet converted. The board reads this as forward-looking signal on whether NRR will trend up or down next quarter. Common pitfall: confusing "opportunities" (real conversations with named accounts) with "addressable upside" (theoretical TAM uplift) — keep this field anchored in actual pipeline. — Customers 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: customers.expansion_opportunities
Type: Text
Domain: Customers
Definition
Identified upsell, cross-sell, and seat-expansion opportunities inside the existing customer base, with deal size and timing where known. This is the qualitative narrative behind the expansion component of NRR — what the CS / Sales team sees in the pipeline that has not yet converted. The board reads this as forward-looking signal on whether NRR will trend up or down next quarter. Common pitfall: confusing "opportunities" (real conversations with named accounts) with "addressable upside" (theoretical TAM uplift) — keep this field anchored in actual pipeline.
Formula
Qualitative — no calculation. Narrative list of named-account expansion opportunities (seat count, module add-on, tier upgrade, cross-sell) with estimated deal size and target close period when available.Why it matters
Forward-looking signal on NRR trajectory. A thin expansion pipeline is the leading indicator of NRR compression — boards catch it here before it shows up in the metric next quarter.
How to interpret
Anti-pattern: vague "we see room to expand in mid-market" framing without named accounts or sizing. Strong content lists ≥3 named opportunities with deal size estimates and target timing, plus a short note on the blocking gate (procurement, integration, exec sponsor) for each. If the pipeline is genuinely thin, write that explicitly — the board needs to know.
Related KPIs
customers.net_revenue_retentioncustomers.retention_insightscustomers.key_initiativessales.arr
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 |
|---|---|
| Series A | Recommended |
| Series B | Recommended |
| Series C+ | Recommended |
| Public | Recommended |
Suggested for stages: Series A, Series B, Series C+, Public.
Default owning functions
- Sales
Machine-readable
- This KPI as JSON:
/api/ontology/customers/expansion_opportunities.json - All Customers KPIs:
/api/ontology/customers.json - Full catalog:
/api/ontology/index.json
Customers Churned
Count of customer logos that ended their subscription/contract during the period. Includes voluntary cancellations and non-renewals. Some companies separately track downgrade-to-zero as churn — be explicit about whether downgrades that drop ARR to $0 count as churn (typical: yes) vs. material contraction that keeps ARR > 0 (typical: tracked under contraction, not churn). The board reads this as the raw count behind `logo_churn_rate`; the percentage tells you the rate, the absolute count tells you the volume of CS pain. Common pitfall: counting customers that re-activate (sometimes called "boomerang" or resurrection) — settle the rule (typical: count each cancellation event, do not net resurrection). — Customers KPI, I'mBoard-authored (editorial tier).
Gross Revenue Retention (GRR)
Recurring revenue retained from the cohort of customers present at the start of the period, excluding expansion — so the metric captures only churn and contraction. Per the SaaS Metrics Standards Board (SMSB) GRR standard. GRR is bounded at 100% (cannot exceed it) and reads as the "no-defense-against-churn" floor on retention. The board reads GRR alongside NRR (`customers.net_revenue_retention`) — the gap between them is the expansion contribution. Common pitfall: treating GRR and NRR as substitutes — they answer fundamentally different questions, and a healthy NRR with sliding GRR signals churn masked by upsell. — Customers KPI anchored to SaaS Metrics Standards Board.