I'mBoardDocs
Board OntologyFinance

Customer Support & Delivery

Direct cost of supporting and serving customers that is part of cost-of-revenue (front-line support, delivery operations tied to the product). Distinct from the Customer Success OpEx section, which covers retention/expansion-oriented account management. — Finance 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: finance.customer_support_delivery Type: Currency Domain: Finance

Definition

Direct cost of supporting and serving customers that is part of cost-of-revenue (front-line support, delivery operations tied to the product). Distinct from the Customer Success OpEx section, which covers retention/expansion-oriented account management.

Formula

Direct cost of serving/supporting customers included in cost of revenue.

Why it matters

Captures the service cost embedded in gross margin, separate from go-to-market CS.

How to interpret

If this scales linearly with customers, it caps gross margin; automation should bend the curve over time.

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

  • Front-line support and delivery operations that are part of serving the product, classified into cost of revenue (support reps, delivery ops tied to the product).

Exclusion rules

  • Retention/expansion-oriented Customer Success account management — that is finance.cs_payroll (OpEx, finance.total_cs).
  • Sales and go-to-market functions.

Required inputs

  • Support/delivery headcount cost classified to COGS.
  • A time-allocation basis for individuals who split between COGS support and OpEx success.

Edge cases

  • A person who both supports (COGS) and drives expansion (OpEx CS) must be allocated by time across the two lines.
  • Automation should bend the per-customer support cost curve over time.

Validation checks

  • If this scales linearly with customer count it caps gross margin.
  • Distinct from finance.cs_payroll — the same person cannot sit fully in both without an allocation.

Common miscomputations

  • Double-counting the same person in customer_support_delivery (COGS) and cs_payroll (OpEx).
  • Classifying all customer-facing staff as COGS (overstates COGS) or all as OpEx (overstates gross margin).
  • finance.total_cogs

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 stagePriority
Series ARecommended
Series BRecommended
Series C+Recommended
PublicRecommended

Suggested for stages: Series A, Series B, Series C+, Public.

Default owning functions

  • Finance

Machine-readable

On this page