Cost support inside a live bid cycle
The situation
The client builds space electronics: radiation-tolerant processing and communications hardware for national security space missions. They were working two things at once. A proposal on a Space Development Agency program, and a hardware subcontract flowing down from a large defense prime.
Those two look like different jobs and they are the same job pointed in opposite directions. On the proposal, the company is the one whose numbers get analyzed. On the subcontract, the company is priced by a prime whose contracts organization does cost analysis for a living and whose flowdowns arrive already written.
The engagement was scoped to the plans and costs supporting both and was capped to the bid window itself, which is the shape this work usually takes: concentrated at the estimate and the review gates, quiet in between.
Where cost volumes come apart
Almost never on arithmetic. A cost volume comes apart because the estimate cannot be traced: hours appear against a work breakdown element with no stated method behind them, a material figure carries no quote and no history, a subcontract line has no analysis showing the price was tested. Every one of those is an evaluator’s question and each question costs schedule at the point in the bid where there is none left.
The second failure is inconsistency between volumes. The technical volume describes an approach the cost volume did not price, or the plan commits to staffing the estimate does not carry. Evaluators read the volumes against each other, and a mismatch between what you said you would do and what you priced to do reads as either an error or an attempt, and both are expensive.
The third is treating the subcontract side as a smaller version of the prime side. A subcontract proposal to a prime gets analyzed under the prime’s own purchasing system obligations, which means the prime has to document that your price was tested before they can flow it into their own proposal. A supplier who understands what the prime is required to produce writes a submission that helps the prime produce it, and gets asked fewer questions for the rest of the program.
What we did
1. Built the cost basis so it could be traced. Estimates structured against the work breakdown, each element carrying a stated method and the evidence behind it, so that a reviewer can follow any number back to its source without asking. The test we apply is whether a reader who was not in the room can reconstruct the estimate from the document. If not, it is not finished.
2. Worked the plan and the cost together. The scope covered plans as well as costs, and the two were built against each other rather than in sequence, which is how the mismatch between volumes gets caught before submission rather than in the evaluator’s question set.
3. Priced the subcontract for the prime’s analysis, not just for the supplier’s margin. A submission structured so the prime’s contracts organization could test it and document that it tested it. Assumptions stated, exclusions stated, and the price separable so that a change in requirement produces a priced change rather than a negotiation.
4. Worked to the client’s standard, in the client’s terms. The agreement set performance in accordance with professional aerospace workmanship standards, and the work ran on the client’s own paper rather than on ours. Those terms are worth stating because they describe how the practice engages generally: inside the client’s standards, inside the client’s process, and against the client’s definition of done.
If this is the position you are in
A bid lands, the technical team is already committed, and the cost volume is due in six weeks. Hiring is not a solution on that timeline and pulling a program controls analyst off a running contract has a cost that shows up somewhere else. What is actually needed is somebody who can build the estimate, write it so it survives review, and leave when the volume is submitted.
That is what a capped, dated engagement is for. It is scoped to the bid window, it ends when the bid does, and the work product stays with the client as the basis for the next one.
What Sivad delivered
- —Two cost positions, one bid window. We built the plans and the cost position supporting a major program proposal and a critical hardware subcontract at the same time, which is exactly the double load that stretches a small technical organization past its limits in a live bid cycle.
- —Discipline where the standards are unforgiving. Sivad’s consultants brought bid-and-proposal pricing discipline to a part of the defense market where the margin for error is small, the review standards are unforgiving, and a number without a traceable basis does not survive first contact with the evaluator.
- —Delivered the way we tell clients to deliver. The work was performed to aerospace workmanship standards inside a tightly capped engagement and finished when the bids were, which is exactly the discipline the work itself teaches, applied to our own paper.
- —An estimate the client kept. The cost basis was written so that a reviewer who was not in the room could reconstruct it from the document alone, and that same property is what let the client carry the estimate forward into the next pursuit instead of rebuilding it, inside an engagement that was capped, dated, and finished when the bids were.
If you are inside a bid window and short on cost capacity
A first conversation is scoped as a working session, so bring the solicitation or the prime’s request, the due date, and what you have drafted so far, and we will tell you what is missing and whether the remaining time is enough.