I'mBoard API Docs

Count of active paying customer logos at the end of the period. "Active" means the customer has a live paid subscription or contract on the reporting date — not trial, not cancelled, not zero-revenue. The board reads this alongside ARR to triangulate whether growth is logo-driven (more customers at similar ACV) or expansion-driven (existing customers paying more). Common pitfall: definitions of "customer" drift over time as the company sells to subsidiaries, parent accounts, or self-serve users — settle the counting unit (parent vs. account vs. seat) and document it in `customer_definition_note` so cross-period comparisons stay honest. — 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.total_customers Type: Number Domain: Customers

Definition

Count of active paying customer logos at the end of the period. "Active" means the customer has a live paid subscription or contract on the reporting date — not trial, not cancelled, not zero-revenue. The board reads this alongside ARR to triangulate whether growth is logo-driven (more customers at similar ACV) or expansion-driven (existing customers paying more). Common pitfall: definitions of "customer" drift over time as the company sells to subsidiaries, parent accounts, or self-serve users — settle the counting unit (parent vs. account vs. seat) and document it in customer_definition_note so cross-period comparisons stay honest.

Formula

Count of customer logos with an active paid subscription/contract on the reporting date. Excludes trials, paused accounts, and $0 contracts. Counting unit (parent vs. account vs. seat) must be documented and held constant period-over-period.

Why it matters

The denominator beneath every retention, churn, and concentration metric — and the simplest read on whether the company is winning new logos at the headline level. Boards use it to disambiguate logo-led vs. ARR-led growth.

How to interpret

Net change = new logos − churned logos; pair with customers_churned and ARR delta. Stage-typical absolute counts vary so widely (B2B enterprise vs. SMB SaaS) that an absolute count is industry folk-wisdom, not citation-grade — compare instead to the company's own trailing 4-quarter trend. A definitional change to "customer" must be flagged on the chart, not absorbed silently.

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 one unit per customer logo that holds a LIVE paid subscription or contract on the reporting date — a period-end, point-in-time snapshot.
"Active" means revenue > $0 and the subscription has gone live on the reporting date — a real paying relationship, not a promise.
Pin the counting unit (parent organization vs. billing account vs. seat) and hold it constant period-over-period; document it in customer_definition_note.

Exclusion rules

Trials, free / freemium accounts, and unconverted pilots — no live paid contract.
Cancelled / churned logos whose contract is not live on the reporting date.
$0 contracts (fully-discounted, design-partner, or paused-to-zero accounts) — they are not paying customers.
Signed-but-not-yet-live logos — count a logo only once its contract goes live, consistent with customers.new_customers_added.

Required inputs

Subscription / contract ledger with per-logo live-and-paid status as of the reporting date.
The pinned counting-unit definition (parent vs. account vs. seat).
The reporting-date (period-close) boundary.

Data-source priority

Billing / subscription system with live-paid status keyed by a stable account ID.
CRM customer table as a fallback — verify against billing, since CRM can lag activation and retain dead logos.

Edge cases

Parent / subsidiary deals: count by the pinned logo unit; do not count each subsidiary when the parent is the unit.
Account merger (two starting logos consolidate into one): the survivor is one logo and the count drops by one — that is NOT churn; disclose the consolidation.
Paused / suspended account held open at $0 on the reporting date: exclude from the active count (consistent with the $0-contract exclusion) and flag separately.
A logo holding several contracts or products counts once.

Validation checks

prior_quarter_total_customers + new_customers_added − customers_churned = total_customers. If the logo bridge does not reconcile, a definitional change or restatement happened — surface it rather than absorbing it.
The count is a non-negative integer.
A change to the "customer" definition must be flagged on the chart, never silently absorbed into the count.

Common miscomputations

Counting trials, free users, or $0 design-partner accounts as customers — inflates the denominator beneath every retention / churn / concentration metric (this is the count-tree root).
Counting signed-but-not-yet-live logos here while excluding them in new_customers_added (or vice versa) — breaks the logo bridge.
Logo-unit drift (parent one period, billing-account the next) — manufactures phantom logo growth or shrinkage.
Double-counting a multi-product or multi-contract logo as several customers.
Silently restating the count after a "customer" redefinition instead of footnoting the change.

customers.customers_churned
customers.logo_retention_rate
customers.logo_churn_rate
customers.top_customer_concentration
sales.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.