Company Size Targeting
Company size targeting segments and prioritizes prospects by firmographic scale, usually employee count or annual revenue, to align offers and sales effort with each tier.
Key takeaways
- Size bands mark thresholds where buying behaviour changes, not evenly spaced numeric ranges.
- Headcount data lags reality and private company revenue is usually estimated, not reported.
- Map every band to a sales motion before writing band-specific creative or pricing.
- A quiz can ask size early and branch its later questions on the answer.
- Headcount misprices trading firms, franchise groups and other seat-light, high-value accounts.
In depth
Company size targeting sorts accounts into bands using a numeric attribute, usually headcount, annual revenue or seat count inside the product, and then attaches a different treatment to each band. The bands are arbitrary lines drawn on a continuous variable, so the real work is finding the thresholds where buying behaviour changes: where a security review appears, where procurement enters, where a company card stops being enough. Once the bands exist, ads, pricing pages, quiz branches and sales queues all key off that same field.
Two things decide how well the bands work. The first is where the lines sit. Too few bands and enterprise complexity leaks into a self-serve flow; too many and no single band carries enough volume to learn from. The second is data quality, since headcount from a public profile lags reality and revenue is rarely disclosed by private firms. Wide bands are robust and imprecise, narrow bands personalise better but demand reliable data and enough traffic per band to justify separate creative.
Teams normally map each band to a sales motion before touching any creative: self-serve with no human contact, an inside-sales call, or a named account team. Pricing pages then show different anchors and the follow-up cadence changes length. Inside a scorecard funnel, size is a natural early question because it can be asked plainly, and the answer can branch the remaining questions, sending large respondents toward governance and integration topics and small ones toward speed and budget before routing to the matching queue.
Headcount is a poor proxy wherever value scales with something other than people. A thirty-person trading firm can outspend a three-thousand-person retailer, and a franchise group may report a tiny corporate headcount while running hundreds of sites. Revenue bands mislead in low-margin industries where turnover is large and budget is not. Size also says nothing about timing: a large account with no open budget cycle is worth less this quarter than a small one with a funded project already underway.
Example in practice
How to measure it
Report conversion rate, average deal size and sales cycle length separately for every band, then check whether the bands genuinely differ. If two adjacent bands produce the same three numbers, they are one band and the extra creative is wasted work. Watch the share of leads arriving with no size data at all, because those silently fall into a default treatment that nobody designed on purpose.
Acquisition cost alone always flatters the smallest band, so pair it with expected revenue: divide a band's acquisition cost by its average first-year contract value to get a payback ratio comparable across bands. Also count mis-routings, meaning deals reassigned from one band's queue to another. That count measures how often the size field was wrong, which no conversion report will reveal on its own.
Common mistakes
The first mistake is copying the small, mid-market and enterprise labels from someone else's deck without checking where your own deals change shape. Plot closed deals against headcount and find the point where cycle length jumps or a security questionnaire first appears. That is the real boundary, and it rarely lands on a round number. Bands inherited from a competitor route traffic into a motion your product and team do not actually support.
The second is showing the band label to the buyer. A page headed for small businesses invites the reader to argue with the label instead of the offer, and mid-market buyers almost never identify with that term. Change what the page proves instead: the number of seats in the example, the depth of the integration story, whether procurement is mentioned at all. Speak about their situation rather than the tier you filed them under.
Frequently asked questions
How is company size usually measured for targeting?
The two most common measures are employee headcount and annual revenue, sometimes supplemented by funding stage or location count. Teams group these into bands like SMB, mid-market, and enterprise.
Why adapt the sales motion to company size?
Small companies want fast, self-serve value while large ones require procurement, security reviews, and dedicated support. Matching the motion to the band avoids overwhelming small buyers and under-serving large ones.
Can a quiz branch by company size?
Yes. A scorecard can ask a sizing question early and branch into tier-specific questions and offers, then route leads to the right sales track. This keeps each segment relevant and improves qualification.
Where should we draw the line between mid-market and enterprise?
Draw it where your own deals change behaviour, not at a round number. Look for the headcount at which procurement or a security review first appears, cycle length steps up, or a single signer is replaced by a committee. That point is product-specific: a payroll tool may see it near two hundred employees and a design tool not until several thousand.
Should we band on employee count or on revenue?
Employee count is more widely available and more stable, so it is the usual default. Revenue predicts better when your pricing scales with money rather than people, as in payments or logistics. Many teams band on headcount and use revenue only as a tiebreaker for accounts sitting near a boundary or looking unusual for their apparent size.
How do we collect size data without a long form?
Ask one banded question instead of an exact number: under ten, ten to fifty, and so on. Ranges feel far less intrusive than an exact headcount and are all a routing rule needs. You can also enrich from the email domain after capture, keeping the self-reported answer as the winner whenever the two sources disagree.
Can a single funnel serve every company size?
One entry point can, but the path after it should not stay identical. Keep a single ad and landing page if budget demands it, then branch at the first qualifying question so a ten-person company never meets a security appendix and an enterprise respondent is never left with a self-serve trial button as the only next step.
Does company size targeting matter for a self-serve product?
Yes, mainly for expansion rather than acquisition. Small accounts convert without a human but rarely grow, while larger companies that sign up self-serve are exactly the ones worth intercepting before they hit a limit. Using the size band as a trigger for sales-assisted outreach captures that value without adding friction to the main signup flow.
How small is too small to target?
Too small is the point where expected first-year revenue no longer covers acquisition and support cost, which you calculate rather than guess. A floor usually exists because tiny accounts consume roughly the same onboarding effort as larger ones. If that floor sits above your cheapest plan, the plan is subsidising churn and either price or targeting has to move.