Cost Realism: Surviving the Government Price Analysis

The Moment That Kills the Award

Cost realism is not the same as price reasonableness. Reasonableness asks whether you are charging too much. Realism asks whether your price is high enough to actually perform the work. Both can disqualify you, but realism failures are more common among small businesses that sharpen their pencils too aggressively to win.

What the FAR Actually Requires

FAR 15.404-1(d)(1) states that cost realism analysis shall be performed on cost-reimbursement contracts to determine whether the estimated proposed cost elements are realistic for the work to be performed. The agency must assess whether costs reflect a clear understanding of the requirements and are consistent with the unique methods of performance described in the technical proposal.

That last clause matters operationally. If your technical volume describes a senior systems engineer leading integration, but your cost volume prices that labor at a GS-11 equivalent, the CO has a documented inconsistency. The technical and cost volumes must tell the same story. When they do not, the agency can substitute its own cost estimate for yours when computing the evaluated price, a process called a Most Probable Cost (MPC) adjustment. You can win the technical evaluation and still lose on MPC if your cost volume is not defensible.

Labor Rates: The Most Scrutinized Line Item

If your proposed rate for a mid-level cybersecurity analyst is below the SCA WD floor for the applicable locality, that is not aggressive pricing, it is a compliance defect. The CO will flag it, and you will not be able to perform at that rate without violating the McNamara-O'Hara Service Contract Act. Build your labor matrix from the WD up, then layer in fringe, overhead, G&A, and profit to arrive at a fully loaded rate. Document each step.

For professional services not covered by SCA, anchor your rates to a published source. BLS OEWS data is free, publicly available, and defensible. GSA's Calc tool (calc.gsa.gov) lets you benchmark against awarded Schedule rates by labor category, education, and experience. If your rate falls outside the reasonable range for the market, explain why in your cost narrative. A rate that looks low because you are proposing remote work in a lower cost-of-living area is defensible if you say so explicitly.

Subcontractor and Consultant Pricing

FAR 15.404-3 requires prime contractors to conduct cost or price analysis of subcontractor proposals and to include that analysis in the prime's cost submission. On many small business proposals, this step is skipped or reduced to a one-line assertion that the sub's price is fair and reasonable. That is not enough.

For each subcontractor or consultant above the simplified acquisition threshold, you need either a price analysis (comparing to market rates, catalog prices, or prior awards) or a cost analysis if the sub's work is not commercially available. Attach the sub's cost breakdown, your analysis memo, and any relevant quotes or rate cards. If the CO asks for it during discussions or a DCAA pre-award audit requests it, you need to produce it quickly. Not having it is a source selection risk.

ODCs, Travel, and the Round-Number Problem

Equipment and materials should reference vendor quotes or published catalog prices. Software licenses should cite the vendor's current price list. If you are proposing cloud infrastructure, pull a cost estimate from the provider's pricing calculator and attach it. Round numbers without backup are a red flag in any cost realism review.

The Cost Narrative: Your First Line of Defense

Every cost volume should include a narrative that walks the evaluator through your pricing rationale. This is not boilerplate. It is your opportunity to preempt the CO's questions and demonstrate that your price reflects a genuine understanding of the work.

Structure the narrative to mirror the cost volume: one section per major cost element. For each element, state the basis of estimate (BOE), the data source, and any assumptions. If you are assuming government-furnished equipment (GFE) will be available on day one, say so, because if that assumption is wrong, your cost will be wrong, and the CO needs to know your price is contingent on it.

A strong BOE also protects you in post-award. If the government later claims you underestimated a cost element and tries to use that as leverage in a modification negotiation, your documented BOE is evidence of what both parties understood at award.

Proposal Consistency: Technical and Cost Must Align

The single most common cost realism finding is a mismatch between the technical approach and the cost volume. If your technical volume promises weekly status reports, a dedicated project manager, and a 24-hour helpdesk, those commitments have cost implications. If none of them appear as discrete line items or are absorbed into a suspiciously low overhead rate, the evaluator will notice.

Before final submission, run a deliberate cross-check: pull every staffing commitment, deliverable, and performance standard from the technical volume and verify that each one has a corresponding cost element. This is not a one-person job on a complex proposal. Assign a compliance reviewer whose only task is to reconcile the two volumes.

Short Takeaway

Cost realism is not a negotiating tactic. It is a compliance requirement with direct consequences for award. Build your labor rates from documented market sources, analyze every subcontractor's price, break out ODCs to the line-item level, and write a cost narrative that explains your logic before the CO has to ask. The proposal that survives price analysis is the one where every number has a source and every commitment in the technical volume has a dollar attached to it.