Pipeline Composition
Container handle for the manual pipeline-composition summary the bespoke Composition subform edits — four user-entered scalars (total open deals, average deal size, median deal size, largest deal) plus optional `dealsByType` / `dealsByStage` count+value breakdown maps. The median vs. average gap reveals pipeline skew: a median well below the average means a few mega-deals dominate. Common pitfall: carrying the summary forward each quarter instead of re-deriving it from the current open pipeline — roll-forward resets these to zero precisely so a human re-enters the period’s real numbers. — 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.pipeline_composition
Type: Text
Domain: Sales
Definition
Container handle for the manual pipeline-composition summary the bespoke Composition subform edits — four user-entered scalars (total open deals, average deal size, median deal size, largest deal) plus optional dealsByType / dealsByStage count+value breakdown maps. The median vs. average gap reveals pipeline skew: a median well below the average means a few mega-deals dominate. Common pitfall: carrying the summary forward each quarter instead of re-deriving it from the current open pipeline — roll-forward resets these to zero precisely so a human re-enters the period’s real numbers.
Formula
Container — { totalDeals, averageDealSize, medianDealSize, largestDeal, dealsByType?, dealsByStage? }. The four scalars are manual summary stats (not computed); the optional dealsByType/dealsByStage maps carry per-category { count, totalValue }. medianDealSize < averageDealSize signals right-skewed deal-size concentration.Why it matters
Summarizes the shape of the open pipeline in one place — deal count and size distribution — so a board can read concentration risk (a handful of large deals carrying the forecast) at a glance, alongside the reconciling pipeline flow.
How to interpret
Read medianDealSize against averageDealSize: a large gap (e.g. median $82k vs. average $95k) means the pipeline leans on a few large deals — pair with sales.pipeline_flow and the notable-opportunities list to see whether those large deals are progressing. A largestDeal that dwarfs the median is single-deal risk worth naming in the narrative.
Related KPIs
sales.pipeline_deal_countsales.average_deal_sizesales.median_deal_sizesales.pipeline_flowsales.pipeline_key_deals
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/sales/pipeline_composition.json - All Sales KPIs:
/api/ontology/sales.json - Full catalog:
/api/ontology/index.json
Pipeline Assumptions
Narrative documenting the key assumptions underlying the pipeline forecast — conversion rates by stage, expected sales-cycle length, segment-mix expectations, and any deal-specific dependencies (e.g. "we assume Acme renews their POC by end of month and signs the upgrade in Q3"). Common pitfall: leaving assumptions implicit makes the forecast non-falsifiable — if you don't list the assumptions, you can't identify which one broke when the forecast misses. Renders side-by-side with sales.pipeline_risk_factors in the TwoColumnTextarea widget (sales.pipeline_context_notes container). — Sales KPI, I'mBoard-authored (editorial tier).
Pipeline Context Notes
Container handle for the side-by-side contextual notes — pairs sales.pipeline_assumptions (left slot) with sales.pipeline_risk_factors (right slot) in the TwoColumnTextarea widget. Visually positions the "what we're assuming" narrative directly next to the "what could break those assumptions" narrative, forcing the team to write them in concert (rather than as two independent surfaces that drift apart over quarters). Common pitfall: writing assumptions without their corresponding risks (or vice versa) means the forecast is incomplete — every assumption should pair to a risk factor that captures the failure mode. — Sales KPI, I'mBoard-authored (editorial tier).