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. Not a skim of the totals, a line-by-line read of what was actually being priced, checked against the program's baselined requirements. The question for every line was simple. What requirement does this trace to, and is it already covered somewhere else?
What the review found
Two patterns emerged. The first was redundant scope: work priced into the proposal that the program was already getting through existing efforts. The second was requirement mismatches: line items that did not trace cleanly to anything in the baselined requirement set. Neither pattern was misconduct. This is what naturally happens when a large proposal is assembled quickly against a complex program. But paid for twice is paid for twice, and unpriced-against-requirements 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 an untraceable line item, documented and defensible. I worked through our contracts team, who own the contract action itself, and the conversation with the vendor changed character. It stopped being a negotiation about a number and became a review of evidence. The result was a renegotiated scope, stronger terms, and a funded contract at roughly $9M, with the final award executed through our contracts office.
The outcome
About $3M in cost avoidance, and a program that kept moving on a contract the sponsor could actually fund. No descoping the mission, no protracted escalation, no damaged vendor relationship. The vendor delivered against a cleaner scope, and the sponsor funded work that traced to requirements.
What I took from it
- Traceability is negotiating leverage. You can only cut what you can trace. The baselined requirement set turned an argument about money into a review of evidence.
- Cost discipline is a governance practice, not a finance event. The review worked because the program had the artifacts to check the proposal against. That discipline exists before you need it or not at all.
- Influence without authority runs on specifics. The contracts team held the pen. My review gave everyone at the table the same defensible baseline, and that was enough.