The short answer
When a Vice President of Engineering demands the immediate release of unearned headcount requisitions, they are aggressively challenging the financial governance of the company. Corporate hiring plans are rarely fully funded at the beginning of the year. Headcount is typically gated behind specific, measurable business milestones, ensuring that the company only assumes permanent payroll liabilities after it has secured the revenue to pay for them. The Engineering VP is attempting to bypass these gates based on partial credit.
As a Financial Planning and Analysis Manager, you are the designated gatekeeper of corporate working capital. You cannot allow executive impatience to dictate cash flow. Releasing five expensive developer requisitions before the milestone is fully completed is a massive violation of fiscal discipline. You cannot pay partial salaries with partial revenue.
You must reject the demand instantly and hold the line on the established metrics. You must remind the Vice President that financial gates are absolute. You will not open up permanent, compounding operational expenses based on an eighty-percent completion rate. By enforcing the one-hundred-percent verification rule, you protect the company's cash runway and force the engineering department to focus entirely on finishing their current commitments before expanding their empire.
Why this question is a trap
The trap relies on the relentless operational pressure of the engineering roadmap. The Engineering VP is using their authority to blur the lines between "almost done" and "financially viable." They are framing the eighty-percent completion mark as a massive victory that deserves an immediate reward. They are betting that you will be intimidated by their senior title and want to look like a supportive business partner who enables product velocity.
If you cave and open up the requisitions early, you severely damage the company's cash position. You immediately burden the balance sheet with recruiting costs, onboarding expenses, and massive salary liabilities. When the final twenty percent of the Q2 milestone inevitably stalls due to unforeseen technical debt, the company will be paying for the new developers without having the projected revenue to support them. You will trigger an avoidable cash crunch that will force the CFO to implement painful, company-wide budget cuts next quarter.
Furthermore, giving partial credit destroys the entire concept of gated funding. If the engineering department learns that eighty percent is good enough to get their budget unlocked, they will never fully complete a milestone again. They will constantly abandon the difficult final stages of product delivery to start building new features with their new headcount. You must act as the rigid financial wall that forces them to cross the finish line.
What most people say
Most frontline finance managers react with a desire to compromise, trying to balance financial rules with the executive's anger. They say something like, "Eighty percent is really great progress, but finance rules say we have to wait for the whole thing. I can maybe open up two of the requisitions for you today so you can start interviewing, and we will hold the other three until the milestone is completely done."
This response is an absolute failure of working capital governance. By compromising and unlocking two requisitions, you completely invalidate the headcount authorization gate. You prove that the rules are fake and entirely negotiable. You have still authorized unauthorized spending, just slightly less of it. The Engineering VP will take the two roles, start interviewing, and then bully you again next week for the remaining three. You have surrendered your leverage and proven you cannot defend the budget under pressure.
What to say instead
"I will not open up the developer requisitions on partial completion. Releasing permanent payroll liabilities before the revenue triggers are fully secured burns our cash runway and violates our headcount authorization gate. We require one hundred percent verified milestone delivery and the corresponding product sign-off. Once your team completes the final twenty percent, I will immediately authorize all five requisitions."
This script is a fortress of fiscal discipline. You begin with an absolute, unyielding refusal. Stating "I will not open up the developer requisitions on partial completion" establishes total control over the financial process. You do not apologize for the rules. You state them as immovable facts of the business.
You immediately justify the refusal with pure financial mechanics. By explicitly naming "permanent payroll liabilities" and "cash runway," you translate their hiring demand into a massive corporate risk. You force the Engineering VP to look at the financial danger of their request. By citing the "headcount authorization gate," you prove that you are enforcing an executive committee standard, not just inventing personal roadblocks.
Finally, you outline the exact path to victory. You demand "one hundred percent verified milestone delivery." You leave zero room for ambiguity or partial credit. You promise that once they actually finish the job, you will immediately authorize the funding. You align their desire for new headcount directly with the company's need for completed products. You use their ambition as leverage to force project completion.
The phrase to anchor on
Violates our headcount authorization gate.
How to deliver it
Deliver this response with the calm, immovable authority of a vault door. Your tone must project complete confidence in the company's financial operating model. You are not arguing with the VP; you are simply reading the metrics and enforcing the outcome. Do not let any frustration or annoyance leak into your voice.
Maintain direct eye contact with the Vice President. When you say the phrase regarding permanent payroll liabilities, speak slowly and deliberately. You want the financial severity of the concept to land heavily in the conversation. When you deliver the final sentence promising the authorization upon completion, keep your tone professional and firm. You are offering a clear transaction: finish the work, get the funding.
Mistakes that cost you the room
The most fatal mistake is allowing the Engineering VP to debate the definition of "done." If they claim that the final twenty percent is just minor bug fixing and doesn't really matter, you must cut them off. The milestone definition was locked at the beginning of the quarter. You are an FP&A manager, not a software tester. You only open up funds when the product team officially signs off on the completed delivery. Do not negotiate the metrics mid-flight.
Another critical error is complaining that the finance department does not have enough money. If you say, "We just don't have the cash right now to let you hire," you look weak and the company looks fragile. The issue is not whether the company is broke; the issue is that the engineering team has not earned the authorization. Frame the refusal entirely around their failure to hit the gate, not the treasury's balance.
Finally, do not promise to ask the CFO for an exception. If you offer to take their case to leadership, you abdicate your own role as the gatekeeper. You become a mere messenger. You must own the refusal yourself. If the VP wants to escalate to the CFO, let them do it on their own time. Your answer is no.
Practice plan
First, review the exact, documented definitions of every major operational milestone tied to your department's headcount gates. You must know exactly what constitutes one hundred percent completion so you cannot be tricked by technical jargon.
Second, practice delivering the opening refusal out loud. Saying "I will not open up the developer requisitions" to a Vice President is intimidating. Rehearse the line until it sounds completely natural, devoid of any nervous hesitation or upward inflection.
Finally, run the drill in the Talk Rightly studio. Focus entirely on your physical stillness. When an aggressive executive demands resources, the natural physical response is to shrink or fidget. You must train yourself to sit perfectly still, projecting the massive, unshakeable stability of the corporate balance sheet.