Department-Level Headcount
Outcome: the size of your target function at each account, a minimum-viable-team threshold, and a ratio that tells you how the company is built.
- Surface
- App and MCP server
- Level
- Intermediate
- Uses
headcount_by_department- Credits
- ~1 per company
- Prerequisite
- Lesson 03's surviving accounts
Total headcount is the wrong number
A 400-person company might have 60 engineers or six. A 200-person company might have a 40-person sales org or two founders doing all the selling.
If you sell to a function, the size of that function is the qualifier — and total headcount is at best a weak proxy for it.
Reference: headcount_by_department.
Minimum viable team size
Most B2B products have a team size below which the problem does not exist yet.
Find yours from your own customers
Look at the department size of your best accounts at the time they bought. There is usually a clear floor.
Below the floor, the problem is manual and tolerable
Two people coordinating do not need coordination software. Five do.
Just above the floor is the best segment
The pain is new, no incumbent tool exists, and nobody is defending a previous decision.
Well above the floor means an incumbent
Solvable, but it is a displacement sale rather than a greenfield one.
The “just above the floor” band is usually the highest-converting segment in a hiring-signal play, and it is exactly what this course finds: a company hiring into a function that has just crossed the size where the problem becomes real.
Ratios tell you how a company operates
Department headcount as a share of the total reveals what kind of business it is.
| Ratio | Reading |
|---|---|
| Engineering high, sales low | Product-led. Sell to engineering; self-serve motion. |
| Sales high, engineering low | Sales-led. Longer cycles, committee decisions. |
| Ops or support high | Service-heavy, or a manual process — often an opportunity |
| Marketing high relative to sales | Demand-gen led; marketing may be the buyer |
This is one of the more useful qualifiers available cheaply, and almost nobody uses it. A product-led company and a sales-led company of the same size are entirely different sales.
Combine with the hiring signal
Department headcount plus openings gives you the intensity metric from lesson 03, and a clearer read:
| Department size | Openings in it | Reading |
|---|---|---|
| Below your floor | Any | Too early — watch, do not work |
| Just above floor | 2+ | Best target — crossing the threshold now |
| Well above floor | 2+ | Scaling an established team; incumbent likely |
| Well above floor | 0 | Established and static — needs a different trigger |
Coverage caveats
Department data is derived from professional-network profiles, so:
- It undercounts in markets and industries with lower network presence.
- It misses contractors, agencies and outsourced functions entirely.
- It lags — recent hires take time to appear.
Treat it as a band and a ratio, not an exact count. A company reported with 18 in engineering has somewhere around 18, and that is enough to decide.
Do this now
Run department headcount on surviving accounts
Find your minimum viable team size
From your own closed-won accounts, pre-purchase.
Build the department ratio column
Function headcount ÷ total headcount.
Classify company type
Product-led, sales-led, service-heavy.
Build the size-versus-openings reading
Four cells, as a classification.
Gate on the floor
Below minimum viable size, move to a watch list rather than the active queue.
Check the survivors
Read 20. Do the department sizes match what you would expect?
Check your work
- Department headcount is populated for surviving accounts
- Your minimum viable team size comes from your own customer data
- The ratio column classifies company type
- Accounts below the floor are watched, not deleted
- You spot-checked 20 department sizes for plausibility
Where this breaks
Hard-filtering on an exact department headcount removes real accounts on the strength of an estimate that undercounts by construction. A company with a reported engineering headcount of 8 may genuinely have 15, plus contractors. Filter on bands and keep the near-misses on a watch list — they cost nothing to hold and they cross the threshold on their own.
Further automation
Track department headcount over time rather than as a snapshot. A function that grew 40% in two quarters is a stronger signal than one that is simply large — and it is the signal that fires before the tooling decision rather than after it.
Next lesson
05 — From hiring company to buying committee, where the expensive work finally starts.
Reference for this lesson: headcount_by_department, Company total employees, Headcount growth, TAM Sourcing.