GTM Spotlight: Support

What KBCM Measures

This section is short because the data is. The certified series contains exactly three kinds of Support signal.

1. Where Support cost is booked, an allocation question asked in five survey years:

2. Support as an AI automation target:

3. One demographic trace: in the 2020 survey, “Customer Support & Success” appears as the primary buyer for 5% of respondents’ products (2019 data, 2020 Survey, p. 22): Support as someone else’s customer, not as a measured function.

That is the complete inventory. No ticket volume. No time-to-resolution. No escalation rate. No CSAT. No cost-per-contact. No headcount. No coverage ratio.

The 2024 survey does define the boundary: Customer Support is “service + product assistance,” distinct from Customer Success’s “renewals + upsells” (definitions, 2024 Survey, p. 37). The definition confirms the survey knows the function exists as a distinct discipline. It simply measures nothing the discipline does.

Set the two adjacent functions side by side and the survey’s model of the post-sale organization becomes explicit:

The one trend the allocation data does carry deserves framing: the survey’s operative question about Support has always been which margin line it damages. The COGS share moved from 56% (2018) to the low-to-high 80s (2020–2023): by the efficiency era, Support was overwhelmingly treated as a cost of delivering the product, directly compressing the gross margin the survey tracks so carefully (75% → 78%, 2022–2024, 2025 Survey, p. 38). A function classified almost entirely as COGS, in an era of margin discipline, is the function cost-cutting reaches first. Inference

What KBCM Concludes

There is no KBCM or Sapphire commentary on Support anywhere in the certified series: no quote to reproduce, which is itself the finding.

The survey’s only forward-looking statement involving Support is implicit in the 2025 AI data (see AI Investment and Exposure Data): 55% of respondents rank “Customer Service and Support” among the largest AI opportunity areas: third overall, behind only New Products/Services (82%) and Back Office/Data Automation (56%), and far ahead of workforce reduction (15%, the lowest-ranked area; 2025 Survey, p. 25). The same survey’s AI-hype page records, qualitatively, that respondents view customer support agents as among the more properly-to-over-hyped AI categories (qualitative finding, 2025 Survey, p. 25; band-level values not reproduced).

Read together with the allocation history, the survey’s implied position is coherent and troubling: Support is a COGS burden, and AI’s promise for it is cost removal.

What We Conclude

The industry is preparing to automate a function it has never measured

The 55% AI-opportunity ranking is a plan to transform Support’s cost structure, recorded in a dataset containing not one baseline metric for Support’s performance. No resolution-time benchmark, no quality measure, no signal-value measure. Whatever AI does to Support, this survey series will be structurally unable to detect what was gained or lost, except as a movement in gross margin. The efficiency case will be measurable; the damage, if any, will not be.

Support generates retention signal the survey records only as cost

Consider what the survey’s own headline problems would look like from inside a support queue.

• The churn floor (14–15% on the current edition, unimproved in every measured year; see The Churn Tax): churning accounts ticket differently before they leave, volume spikes, unresolved escalations, then silence.
• The downsell wave (32% of gross retention loss overall in 2024, and 37–39% at the smallest and largest companies; 2025 Survey, p. 19): shrinking accounts stop opening tickets for unused modules first.
• The product capability gaps the Product spotlight documents as invisible: every one of them arrives in Support first, tagged with a feature name and an error message, months before it becomes a churn statistic.

Support holds the leading indicators for the exact lagging metrics this survey has spent seven years documenting, and contributes zero fields to the dataset.

The signal loop the companion analysis calls for runs through this unmeasured function

The companion analysis’s Product sections propose Support ticket root-cause data as a required roadmap input: a product-gap heat map delivered to Product on a regular cadence. That machinery cannot be benchmarked, and its absence cannot even be noticed, in a survey where Support’s only quantified property is its expense classification.

The 2018-to-2020 allocation shift shows the classification is a choice, not a fact

In 2018, a third of Support cost sat in S&M; by 2020, 84% sat in COGS. The function did not change; the industry’s accounting posture did. Where Support cost lives determines which executive owns cutting it, and the migration into COGS put Support’s budget under the gross-margin lens at precisely the moment the efficiency era began.

The Blindspot

The survey’s data model has no category for operational signal, only for cost. Support is the function this omission erases most completely, and the erasure distorts the series’ conclusions in three ways:

1. The churn floor looks unexplainable because its explanatory data was never collected. The companion analysis concludes churn is a “structural constant” that no macro condition or strategy has broken. But the dataset contains no early-warning layer: nothing between “customer exists” and “customer churned.” A floor observed without its precursors will always look structural. Whether it actually is cannot be established from a dataset that never measured the place where churn announces itself first.
2. Support’s retention contribution is unpriceable, so it defaults to zero. Resolution speed and escalation handling plausibly move renewal outcomes, but with no Support metrics adjacent to the retention metrics, the correlation cannot be computed. In benchmark-driven budget decisions, a contribution that cannot be computed is treated as absent. The COGS classification then finishes the logic: cut it and margin improves, with no visible retention cost, the same illusion the companion analysis documents for the R&D cut (margins improved, retention did not), replayed one function over.
3. The product-gap signal chain is severed at its origin. The Product spotlight establishes that the survey cannot see product-caused churn because it never asks why customers leave. The answer to “why” exists, in structured form, in every respondent’s ticketing system, categorized by feature, timestamped, trended. The survey’s blindness to Product’s churn contribution and its blindness to Support are the same blindness: the evidence lives in Support’s data, and Support’s data was never invited in.

The distortion, compounded: a function classified as pure cost, holding the company’s richest retention telemetry, ranked third as an AI automation target, with no baseline against which automation’s effects will ever be judged. And it sits on the function most exposed to the next round of cost-cutting. Inference

What a Complete Picture Would Require

The through-line: nothing proposed here asks the survey to flatter Support. It asks the survey to measure what the operating model already relies on, the function that detects retention risk first. The benchmark series measures every financial consequence of retention and none of it.

Related Spotlights

• Product: the destination of Support’s most valuable signal: product-gap-tagged tickets are the churn-reason data the Product spotlight shows the survey never collected
• Customer Success: the adjacent post-sale function, classified as S&M where Support is classified as COGS, and the operator of the plays Support’s early warnings should trigger
• Sales: over-sold deals surface in Support’s queue as adoption friction long before they surface as downsell
• Marketing: cohort-level Support telemetry is the earliest available audit of acquisition quality by channel

All certified values from the KBCM/Sapphire survey series. Analytical interpretations are the work of SuccessCOACHING and are not attributable to KBCM, KeyBanc Capital Markets, or Sapphire Ventures.