How to ask for headcount
One role, one start month, the risk in his terms: an opening line for the headcount ask, the three offers that aren't a hire, and where you stop.
Most headcount asks don’t get refused. They get sympathised with. You describe the load, the VP nods, says he hears you, and offers a contractor, an intern, or a conversation in Q1. You leave with everything except a hire.
This guide is the shape of the ask that produces a requisition: what to decide before you walk in, the first sentence, the three things a VP says instead of yes, and the point where you stop.
Why this one is hard
Tom Vandenberg has frozen requisitions twice this year. He opens every budget conversation with “we’re doing more with less,” and he’ll tell you before you’ve sat down that he’s said no to three headcount pitches this month. Assume he isn’t bluffing. He has a portfolio of teams and every one of them is tired.
Your team runs the on-call rota with four people. Healthy teams here run six. One resignation and the rota doesn’t get thinner; it collapses. That’s a real risk, and exactly the kind that gets lost when it’s described as “we’re stretched.” Tired is a feeling. A rota that fails on one departure is a number, and numbers are what survive finance.
Before you walk in
Decide four things, and write them down.
One role, one month. A requisition for a specific role with a start month. Not “more support,” not “a couple of people over the year.” Tom can say yes to one thing. Give him one thing.
The risk in his terms. Your team’s exhaustion is your problem. The service going dark for a weekend because the last person on the rota is on leave is his problem, in front of his board. Say the second one.
The cost of no. Not a threat; a forecast. What you will stop doing, or what will break, if the answer is no. Have the actual roadmap item ready, because he’ll ask what you’d cut, and “nothing, we’ll manage” is a no you’ve just written for him.
Your walk-away point. A requisition, or a dated no with what would change it. A contractor, an intern, or “let’s revisit in Q1” with nothing attached are all below that line. They are not hires, and the rota knows the difference.
Your opening line
Lead with the ask. He’s told you it’s a headcount pitch; don’t pretend otherwise.
One requisition, a senior engineer, February start. We run on-call with four and the floor here is six. If one person resigns, the rota fails, and the service that goes dark is the one you own in front of the board. That’s the ask. I’d like to walk you through what happens if it’s no.
You’ve said the number of roles, the month, and the risk in his language, in four sentences. Everything after this is detail he can test.
The version to avoid sounds humble and is dead on arrival:
I know we’re doing more with less, and I know you’ve had a lot of these, but the team’s really stretched and I wondered whether there was any chance of some extra support at some point…
You’ve agreed with his opening, apologised for the ask, and asked for nothing specific. He can sympathise with that for twenty minutes without spending a penny.
The three pushbacks you’ll hear
“I hear you. What about a contractor for six months?”
Sympathy with a substitute attached. It’s the thing he can give without a fight with finance, and it’s not a hire. A contractor doesn’t go on the rota, and if they do, they leave in six months and you’re back to four.
A contractor helps the backlog and doesn’t change the rota. The risk is the rota. The ask is still one req, February.
Take the offer seriously, say precisely why it doesn’t address the risk, and come back to the one thing.
“Four people can run a rota. What would you cut to fund it?”
He’s challenging your maths and your priorities at once. The second half is the real question: he wants to know whether you’ve thought about this as a trade or only as a wish.
Four can run it with nobody on leave and nobody sick. We’ve had both twice this quarter. If I have to fund it from inside, the reporting rebuild moves to Q2. I’d rather not, and I will if that’s the price.
You’ve answered the maths with incidents, not adjectives, and named the cut. Now it’s a trade he can take upstairs.
“Strong leads run lean.”
The reframe: the rota risk becomes a question about you. It’s a test of whether you’ll get defensive, and the right answer is not to.
Strong leads also say when the risk has moved from the team to the org. This one has. I’d rather tell you now, in numbers, than in an incident review.
Calm, specific, and back to the risk. You’ve declined to argue about leadership and kept the subject where it belongs.
Where you stop
If you have a requisition, or a dated no with named conditions, you’re done. If Tom says “one req, February, and I want the burn-risk memo under my name by Friday,” say yes and write the memo. Under his name is how it survives finance.
If he’s still circling, say this once:
If it’s a no, I’d like it to be a no for this quarter with a date, so I can plan the cut rather than hope.
If the answer is “everyone’s rota is on fire, come back when yours is actually the worst,” stop. Arguing about whose team is most on fire is a competition you can’t win in his office. Leave the numbers with him and go.
What a good version of this conversation surfaces is the thing he hasn’t said. He may be holding a requisition back for an emergency. A case made in his terms, with the failure scenario written down, is what lets him say that your team is the emergency. That admission is the hire.
Afterwards
Send the memo the same day, whether he asked for it or not: rota numbers, the failure scenario, what it costs the org, the one role, the start month, and the roadmap item you’d cut to fund it. Keep it to a page. If he said to put it under his name, do that.
Then the habit: track rota load every month, with incidents and leave. The next ask comes with a trendline instead of a story.