Revenue per head: what it is and how AI moves it
By Jordan Neville · November 3, 2026
The short answer
Revenue per head is annual revenue divided by full-time headcount. It's the simplest test of whether your tools and AI are making each person more productive, and a GTM engine moves it by taking research, drafting, logging and reporting off people's plates so the same team can handle far more pipeline.
How to calculate it
Divide annual revenue (or your current run rate) by full-time headcount.
For example, a company with $6 million in revenue and 24 full-time people has revenue per head of $250,000.
Pick one definition and keep it. Decide up front whether long-term contractors count, and never count agents. Track it quarterly, because monthly numbers move too much with hiring timing.
Try it on your own numbers with the revenue per head calculator.
Why it matters now
For years, the default way to grow revenue was to add people: more reps, more marketers, more operations staff. AI changes that trade. When research, first drafts, follow-ups, logging and reporting are handled by agents, each person can cover far more accounts and conversations.
Revenue per head is the number that shows whether that's actually happening. If you've bought AI tools and the number hasn't moved, the tools are adding work, not removing it.
Why $1M per head
The GTM Engine is built toward $1M in revenue per head: a few people, each backed by agents, doing the work of a much bigger team. It's a direction to build toward and a way to judge decisions, not a promise. The useful question is whether each change moves you closer.
Where AI moves it in go-to-market
- Research: account briefs in minutes instead of an hour per account.
- First drafts: emails, posts, call prep and follow-ups written from your knowledge base, in your voice.
- Signal to action: buying signals noticed and acted on within a day, instead of being missed.
- Logging and reporting: the CRM updated and the weekly report written without anyone typing it.
- Content and AI search: the questions buyers ask AI assistants answered on your site, so you get found without adding headcount.
What doesn't move it
- Buying AI tools that don't connect to each other or to your CRM
- Automating before there's a knowledge base, so the agents write generic messages nobody approves
- Replacing people's judgment instead of their busywork, which shows up as lower reply rates and damaged trust
How to start
- Calculate your number today and agree the headcount definition.
- List where your team's time goes in a typical week, and mark what an agent could draft or do.
- Build the knowledge base first, then connect the tools, then turn on a few plays.
- Review the number every quarter.
Or take the GTM Engine Scorecard to see which parts of your go-to-market would move it most.
Questions
Is revenue per head the same as revenue per employee?+
Yes. Both mean annual revenue divided by the number of people. We use full-time headcount and agree up front whether contractors count.
Should we cut headcount to raise it?+
That raises the number without building anything. The goal is to grow revenue faster than headcount by making each person more productive, not to shrink the team.
How fast can a GTM engine move it?+
It depends on your starting point and sales cycle. The engine changes how much each person can handle within weeks of going live; revenue follows on the timeline of your sales cycle.
See where your go-to-market stands
The GTM Engine Scorecard takes three minutes and shows your three biggest gaps.
Get your GTM Engine score