Customer Acquisition Headcount

What it measures

A point-in-time count of full-time-equivalent (FTE) employees whose primary job is acquiring new customers, normally read at month-end or quarter-end. It is the sum of Sales Headcount and Marketing Headcount: quota-carrying and quota-supporting sellers (Account Executives, Sales Development Representatives, Sales Engineers, sales leadership) plus the full marketing department (demand generation, product marketing, content, brand, marketing operations, analytics, and the CMO). It excludes customer success, support, onboarding, product, and R&D — those are cost-of-delivery and retention functions, not acquisition. Contractors and agencies are excluded; their cost lives in Total Sales and Marketing Expenses. Split roles count at their FTE share, so a person who spends 50% of their time on acquisition counts as 0.5.

Why it matters

CAC Headcount is the denominator beneath every go-to-market productivity number — new ARR per GTM head, pipeline per head, the sales-efficiency ratio — and a proxy for how much capacity you are pointing at growth. A healthy business adds new revenue faster than it adds acquisition bodies; that gap is operating leverage. GTM leadership uses the count to plan hiring, size capacity against the bookings target, and translate pipeline into a staffing forecast. Finance and the board use it to judge unit economics and organizational maturity, and to test whether past hiring actually paid off — a spike can mean demand-backed expansion (good) or a team that needs more people to move the same revenue (a productivity problem). The count alone does not tell you which; you read it against the revenue it produced.

How to read it

Read CAC Headcount as 'selling-and-marketing capacity in bodies,' and always read it against the revenue it generates — never as a standalone snapshot. The most useful framing is CAC Headcount per \$1M of New ARR (or new customers) trended over time: a declining ratio means you are acquiring more with the same or fewer people, the signature of compounding GTM efficiency; a flat or rising ratio means you are buying growth with headcount rather than leverage. Use the trend to time hiring — if output per head is improving you can stretch the existing team; if it is flat or worsening, new heads need a clear pipeline or market-expansion justification before they are approved. Remember the count is a lagging input: a rep or marketer hired today contributes pipeline a quarter or two later, so pair it with new bookings, pipeline generated, and CAC before drawing conclusions.

What good looks like

Watch-outs

• Double-counting shared roles. A product marketer who is 50% acquisition and 50% retention is 0.5 of a CAC head, not 1.0, and must not be counted in full on both the sales and marketing sides. Define each person's FTE share once and apply it consistently, or per-head efficiency math breaks.
• Folding in non-acquisition functions. Customer success, support, onboarding, finance/ops, product, and engineering do not belong in CAC Headcount — including them inflates the count, understates New ARR per head, and muddies the link to CAC. The metric must isolate the bodies directly tied to winning new customers.
• Ignoring ramp and hiring lag. Five reps hired in January book roughly zero that month and may close little through March; a hiring spike depresses New ARR per head for two to four quarters until the cohort ramps — expected, not a crisis. Track the ramp curve alongside the count and compare realized ramp to plan.
• Reading the count in isolation. Flat CAC Headcount does not mean flat efficiency — if pipeline doubled on the same team, you got more efficient. Always pair the count with New ARR, new customers, or pipeline generated to compute true GTM productivity.
• Counting contractors and agencies as headcount. Outsourced demand gen, freelance sellers, and fractional agencies are external spend that belongs in Total Sales and Marketing Expenses, not FTE headcount — mixing them in inflates the count and distorts every per-head ratio.

Worked example