The $3M review
A $12M vendor proposal, a sponsor budget that could not fund it, and the line-by-line review that closed the gap without cutting the program.
A proposal the budget could not fund
Partway through a multi-year modernization program, the vendor's proposal for the work ahead came in at roughly $12M. The sponsor's budget could not fund it. That is a familiar moment on large programs, and there are two easy ways to handle it: escalate the gap and wait for someone else to resolve it, or accept the number and plan to descope later. Both keep the program stalled, and both quietly hand the outcome to somebody else.
Owning the review
I took a third path: I led the technical and cost review myself. I could, because my team had helped write the government specification that went into the RFP. The requirement did not arrive from nowhere. Government specification, then RFP, then contract, then the contractor's own requirements documents, which the government reviews and signs off for use. I was auditing the proposal against a spec I had a hand in writing. So it was not a skim of the totals. It was a line-by-line read of what was actually being priced, and the question for every line was simple. What does this trace to, and is it already covered somewhere else?
What the review found
Four things surfaced. First, scope inflated by a misreading of the requirements, which I could see because I knew what the requirements were meant to buy. Second, redundant scope: the same work billed across separate groups inside the contractor. Third, facility costs priced into the proposal that another contract was already paying for. Fourth, engineering hours far above benchmark, which I checked against work breakdown structure lines from programs I had run myself. None of it was misconduct. It is what happens when a large proposal is assembled quickly against a complex program. But paid for twice is paid for twice, and scope that traces to nothing is scope nobody agreed to.
Specifics, not sentiment
I do not hold contracting authority, and I did not need it. What I brought to the negotiation was specifics: each proposed cut tied to a named overlap or a line item that traced to nothing, documented and defensible. I worked through our contracts team, who own the contract action itself. I took the findings back to the contractor and sat down until we had agreement. It was not a rejection, it was a working session. The result was a renegotiated scope and a funded contract at roughly $9M, with the award executed through our contracts office.
The outcome
A $3M reduction from proposal to signed award, and a program that kept moving on a contract the sponsor could actually fund. No descoping the mission, no protracted escalation, no damaged relationship with the contractor. Here is the part I did not have to argue for: the contractor later came in under the agreed hours. My estimate was closer to reality than theirs, and I still left buffer for the genuine unknowns rather than cutting to the bone.
What I took from it
- Traceability is what you negotiate with. You can only cut what you can trace. Because my team helped write the spec, I knew what every line was supposed to buy, and that turned an argument about money into a review of evidence.
- Cost control is a governance job, not a finance event. The review worked because the program had the artifacts to check the proposal against. You build that before you need it, or you do not have it.
- Influence without authority runs on specifics. The contracts team held the pen. My review gave everyone at the table the same set of facts, and that was enough.