Kilby as CEO Coach. Driving Profitable Growth.
CEO’s Question:
We’re projecting 40% revenue growth next year. My CFO is building a hiring plan that adds 25 people to support it. How should I think about whether that’s the right number?
Kilby’s Response:
This is the right question to ask before the plan gets baked in. Here’s the framework I’d use:
Start with revenue per employee — it’s the single most diagnostic metric.
T.J. Rodgers ran Cypress Semiconductor on this number religiously. The logic is clean: if you grow revenue 40% but grow headcount faster, you’re getting less efficient, not more. The income statement won’t show the damage immediately, but the organizational drag compounds fast.
Run the math:
- Current revenue per employee — what is it today?
- Pro forma revenue per employee — if you add 25 heads and hit your 40% revenue target, does the ratio go up, stay flat, or decline?
- What happens if you miss the revenue target but still hire the 25? This is the scenario your CFO should stress-test. Hiring is a step function with sticky costs. Revenue is not.
If the ratio declines meaningfully, you’re building a bigger company, not a better one.
Second, decompose the 25 into value-creation vs. overhead.
Not all headcount is equal. Ask your CFO to tag each role:
- Revenue-generating or revenue-enabling — sales, customer success, product/engineering shipping features that drive growth
- Infrastructure/overhead — finance, HR, ops, compliance
A 40% revenue growth plan should be heavily weighted toward the first category. If more than a third of the 25 are overhead, push back hard.
Third — and this matters more now than even a year ago — model the AI substitution layer.
Before approving any role, ask: Can an AI agent do 60%+ of this job’s core workflow within 12 months? Token spend on agents is an operating expense that scales linearly and can be dialed down. Headcount is a step function that’s painful to reverse. For a company at your stage, every unnecessary hire you avoid is runway and optionality preserved.
Roles most likely to be compressible with AI right now: data entry/ops, first-pass research and analysis, reporting, content generation, basic customer support, QA, and parts of finance/accounting workflows. Your CFO’s plan should explicitly account for which of the 25 could be replaced or deferred by tooling investment.
Fourth, sequence the hiring against revenue milestones, not calendar quarters.
Don’t approve 25 heads on January 1. Approve them in tranches tied to revenue or pipeline triggers. Example: first 10 on day one, next 8 when ARR crosses $X, final 7 when pipeline coverage hits Y. This is how you protect the downside scenario without slowing the upside.
The sharp version of the question to bring back to your CFO:
“If we added 15 people instead of 25 and spent the delta on AI tooling and automation, would we still hit the 40% target? And if we added 25 and only grew 25%, what does the P&L look like?”
That forces the real tradeoff into the open. The answer to whether 25 is the right number lives in the gap between those two scenarios.
Learn more: https://agentkilby.com/