Top Product ARR Concentration
Percentage of total ARR contributed by the single largest product line. Diversification-risk indicator at the product level (parallel to customer-concentration risk at the GTM level). Common pitfall: concentration risk is dismissed when the dominant product is performing well — but a one-product company is a one-feature-decision-away from existential risk. Boards should track this number alongside the portfolio narrative; sustained 70%+ concentration in a maturing company should pair with a documented diversification thesis or an explicit decision to remain a single-product company. Frames analogous to customer-concentration discussions in venture diligence (NfX / Bessemer founder essays cover the customer-side; the product-side analogue follows the same logic). — Product 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: product.top_product_arr_concentration
Type: Percentage (%)
Domain: Product
Definition
Percentage of total ARR contributed by the single largest product line. Diversification-risk indicator at the product level (parallel to customer-concentration risk at the GTM level). Common pitfall: concentration risk is dismissed when the dominant product is performing well — but a one-product company is a one-feature-decision-away from existential risk. Boards should track this number alongside the portfolio narrative; sustained 70%+ concentration in a maturing company should pair with a documented diversification thesis or an explicit decision to remain a single-product company. Frames analogous to customer-concentration discussions in venture diligence (NfX / Bessemer founder essays cover the customer-side; the product-side analogue follows the same logic).
Formula
top_product_arr_concentration_pct = (arr_from_largest_product / total_arr) × 100. Define "product" explicitly — a SKU, a billable module, or a packaging unit — and hold the definition stable. Surface both the percentage and the named top product.Why it matters
Quantifies single-point-of-failure risk in the product portfolio. The board reads this alongside portfolio_strategy to assess whether the company has a real second product or is effectively still single-SKU. Drives both strategic (build / buy / partner for diversification) and financial (valuation framing) conversations.
How to interpret
Industry folk-wisdom, not citation-grade: concentration of 60–80% in the flagship product is common at early-growth multi-product SaaS; sustained 90%+ should be paired with an explicit single-product-strategy thesis or a documented diversification plan. The trend matters most — concentration falling from 95% to 70% over 4–6 quarters signals successful diversification; rising concentration during a multi-product strategy is a flag the secondary products are underperforming.
Related KPIs
product.portfolio_strategyproduct.offensive_roadmap_pctsales.arrcustomers.gross_revenue_retention
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
- Product
- Finance
Machine-readable
- This KPI as JSON:
/api/ontology/product/top_product_arr_concentration.json - All Product KPIs:
/api/ontology/product.json - Full catalog:
/api/ontology/index.json
Time to Capacity Limit
Months of system capacity remaining at the current growth rate before the platform requires major (not incremental) infrastructure investment — typically driven by the binding bottleneck (database, message bus, single-tenant compute ceiling, regional capacity, or compliance-driven re-architecture). Surfaces the "scale runway" alongside the financial runway. Common pitfall: a single number hides which bottleneck binds. Boards should require the bottleneck to be named ("database shard hot-spot binds at ~150K accounts at current growth, ~4 months out"), not just the headline months — a named bottleneck makes the investment decision concrete. — Product KPI, I'mBoard-authored (editorial tier).
Total Engineers
Headcount of engineers (software, infrastructure, security, data, ML) in the R&D organization, typically including full-time employees plus contractors at a defined FTE-equivalence factor. The "capacity input" side of all R&D ratios. Common pitfall: definition drift. Some companies include only software engineers, others include product managers and designers, others include all of R&D plus QA, plus support engineers. Boards should anchor the definition once and hold it stable — otherwise quarter-over-quarter comparisons are noise. Pair with `rd_monthly_spend` to derive fully-loaded cost-per-engineer. — Product KPI, I'mBoard-authored (editorial tier).