Asking Finance for More Headcount

Scene: Dana, an engineering manager, meets Wei, the finance director, to argue for one more developer. Wei approves every headcount request in the company, so he has heard "we're too busy" a hundred times. Dana: Thanks for the time, Wei. I want to make the case for one additional engineer. I know headcount is tight, so I've come with numbers rather than just a feeling that we're stretched.

Wei: Good, because a feeling won't get approved. Give me the numbers. What does this hire cost, and what does the company get back?

Dana: A senior engineer is about 160K a year, fully loaded — salary, benefits, equipment. Here's the return: right now, my team ships features two weeks late on average because we're the bottleneck for three other teams. Those delays pushed two enterprise deals into next quarter, worth 500K. One more engineer clears the queue.

Wei: So you're framing 160K of cost against 500K of delayed revenue. That's the right way to talk to me. But delayed is not the same as lost — those deals may still close. What's the real return on investment if I say yes?

Dana: Fair point. Conservatively, faster delivery pulls forward about 300K in revenue this year and prevents roughly 200K in overtime and contractor costs. So a 160K investment returns close to 500K in year one — the hire pays for itself in about four months.

Wei: The payback period is what sells me, not the headline number. Here's my concern: I can't add a full permanent role to this year's budget. Can we do it another way?

Dana: I anticipated that. Option B: hire a six-month contractor now to clear the backlog, then convert the role to permanent in next year's budget once the revenue lands. That halves this year's cost and lets the numbers prove themselves first. Shall I write it up that way?

Wei: Yes — do that. You brought a cost, a return, a payback period, and a fallback when I pushed back. That's not a request; that's a business case. Get it to me in writing and I'll approve the contractor this week.