Sales Base Currency
The ISO-4217 currency code (e.g. `USD`) the sales/pipeline feed displays its money metrics in. The bespoke sales and pipeline feed cards read this to choose the currency symbol/format; absent it, they fall back to USD. This is a board-level reporting-currency constant rather than a measured metric. Common pitfall: leaving it unset on a non-USD board — the feed then silently renders USD symbols over non-USD figures. — 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.base_currency
Type: Text
Domain: Sales
Definition
The ISO-4217 currency code (e.g. USD) the sales/pipeline feed displays its money metrics in. The bespoke sales and pipeline feed cards read this to choose the currency symbol/format; absent it, they fall back to USD. This is a board-level reporting-currency constant rather than a measured metric. Common pitfall: leaving it unset on a non-USD board — the feed then silently renders USD symbols over non-USD figures.
Formula
A single ISO-4217 currency code. Not a calculation — it is the display/reporting currency the feed formats sales money figures in.Why it matters
Ensures the sales/pipeline feed renders money in the board's actual reporting currency instead of a silent USD default.
How to interpret
Should match the board's reporting currency. If FX conversion is applied upstream, this is the post-conversion display currency, not each deal's original currency.
Related KPIs
sales.arrsales.pipeline_value
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/base_currency.json - All Sales KPIs:
/api/ontology/sales.json - Full catalog:
/api/ontology/index.json
Average Sales Cycle (Days)
Average number of days from opportunity creation to closed-won status — measured only on won deals (lost deals are tracked separately). The motion-velocity metric — directly determines how much pipeline coverage is needed, how quickly investment in new reps pays back, and how feedback loops on packaging or pricing experiments compound. Common pitfall: blending segment cycles (SMB and Enterprise often differ 5–10×) into a single average hides material trend signals — segment-cut the metric where deal-volume permits. — Sales KPI, I'mBoard-authored (editorial tier).
Blended CAC Ratio
Total fully-loaded S&M spend in the period divided by the dollars of new CARR generated in the period (new-customer + expansion CARR combined). Per the SMSB standard, the headline efficiency ratio for the full sales-and-marketing motion — answers "how many cents do we spend on S&M to add one dollar of contracted ARR." Common pitfall: blending without separately reporting New CAC Ratio and Expansion CAC Ratio hides which side of the motion is driving efficiency — for a healthy SaaS company expansion CAC is usually 3–5× cheaper per dollar than new-logo CAC. — Sales KPI anchored to SaaS Metrics Standards Board.