New Customers Added
Count of net-new logo customers signed during the period (a customer is a discrete buying entity — typically an account, not a seat). Paired with sales.new_business gives Average Selling Price (ASP) — a primary input to ICP / segment-fit conversations. Early-stage boards read the logo count as a sanity check on top-of-funnel and PMF before ARR-density grows enough to matter. Common pitfall: counting expansion deals or new contracts from existing customers as "new" inflates the acquisition signal — the count must match the same "first-time customer" criterion as New Business ARR. — 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.new_customers_added
Type: Number
Domain: Sales
Definition
Count of net-new logo customers signed during the period (a customer is a discrete buying entity — typically an account, not a seat). Paired with sales.new_business gives Average Selling Price (ASP) — a primary input to ICP / segment-fit conversations. Early-stage boards read the logo count as a sanity check on top-of-funnel and PMF before ARR-density grows enough to matter. Common pitfall: counting expansion deals or new contracts from existing customers as "new" inflates the acquisition signal — the count must match the same "first-time customer" criterion as New Business ARR.
Formula
New Customers Added = Count of distinct customer entities whose first-ever active contract started during the period. Must apply the same logo-counting unit (account / parent-org / billing entity) consistently across periods so the trend is comparable.Why it matters
Logo count is the most direct read on acquisition-motion volume before contract-value mix dominates the ARR view. Early-stage boards read it before ARR; growth-stage boards pair it with ASP to spot segment drift (e.g. up-market mix-shift where logo count falls while ARR rises).
How to interpret
Read alongside New Business ARR to derive ASP (= New Business ARR / New Customers Added). A rising ASP with falling logo count signals up-market drift (often intentional). Stable ASP with falling logo count signals a top-of-funnel problem. Falling ASP with stable logo count usually means discounting pressure — investigate competitive dynamics.
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
- Count of distinct customer entities whose first-ever active contract started during the period.
- Use a consistent logo unit (typically parent account / billing entity) across periods.
Exclusion rules
- Expansion deals to existing customers — even if a new product or new line of business is added.
- Renewals or reactivations of previously-churned customers — those are separately tracked.
- Pilots / free trials — until the first paid contract starts.
- Sub-accounts under an existing parent (when parent-level is the unit) — should not double-count.
Required inputs
- CRM customer table with stable customer-since field.
- Definition of "logo unit" (parent account vs sub-account vs billing entity) — pin one and apply consistently.
Data-source priority
- CRM with explicit customer-since field per logo unit.
- Billing system with first-billed-date as a fallback.
Edge cases
- Customer signs in period N but goes live in period N+1: pick a convention (signing-date vs go-live-date) and apply consistently with
sales.new_business. Mismatched conventions break ASP calculations. - Reactivated former customers: pin a policy ("count as new" or "count as recovery") and apply consistently. Most boards prefer separate reporting.
- Parent-child shifts: if the logo unit changes mid-year (e.g. multi-subsidiary deal becomes a single parent contract), don't treat the consolidation as a logo gain or loss.
Validation checks
- Count is a positive integer.
- New Customers Added × ACV ≈ New Business ARR within ~1% rounding — material divergence means the two metrics use different logo definitions.
- Trend should be smooth at steady state; large step-functions usually indicate a CRM data-cleanup or logo-unit change, not a real-world event.
Common miscomputations
- Counting expansion deals or sub-account adds as "new customers" — inflates the acquisition signal.
- Logo-unit inconsistency across periods (parent in Q1, billing-entity in Q2) — produces phantom growth or shrinkage.
- Using signing-date here but go-live-date for New Business ARR — ASP becomes nonsense.
- Counting trial conversions twice (once when trial started, once when paid contract began).
- Including customers in the count whose contract never went live (lost-to-implementation churn happens before live-ARR but after counting).
Related KPIs
sales.new_businesssales.avg_contract_valuesales.cacsales.pipeline_deal_countsales.closed_won_countsales.win_rate
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 | Recommended |
| Series C+ | Recommended |
| Public | Recommended |
Suggested for stages: Pre-Seed, Seed, Series A, Series B, Series C+, Public.
Default owning functions
- Sales
Machine-readable
- This KPI as JSON:
/api/ontology/sales/new_customers_added.json - All Sales KPIs:
/api/ontology/sales.json - Full catalog:
/api/ontology/index.json
New CAC Ratio
S&M expense attributable to new-customer acquisition divided by the new-customer CARR generated in the period. Per SMSB, the cleanest read on the new-logo acquisition engine's efficiency — strips out the expansion motion which has materially different unit economics. Common pitfall: failing to split AE comp time correctly between new and expansion activities — when the same AE owns both motions, an allocation rule (often the % of OTE tied to new-vs-expansion quota) is required and must be applied consistently quarter-over-quarter. — Sales KPI anchored to SaaS Metrics Standards Board.
New Opportunities Added
Total dollar value of new opportunities entering the pipeline during the period — the top-of-funnel inflow line in the pipeline flow. The single best read on the marketing-and-SDR engine's output. Common pitfall: counting inflated, un-qualified opportunities (e.g. every demo request) overstates the engine's output; restrict to opportunities that pass a defined qualification stage (typically SQL or higher) before counting. Boards expect this number to track forward quota — a quarter's top-of-funnel should be ~1× the same quarter's quota for a normal sales-cycle business. — Sales KPI, I'mBoard-authored (editorial tier).