Two of the most misunderstood tools in federal proposal pricing — and why using only one (or neither) is costing you contracts.
Federal pricing decisions made without intelligence are guesses — and guesses are expensive in the government contracting world. Too high and you lose to a lower bidder. Too low and you either win an unprofitable contract or trigger a price realism concern that tanks your technical evaluation. The two tools designed to solve this problem are Price to Win (PTW) analysis and Should-Cost modeling. Most contractors use neither. The ones with the highest win rates use both.
This article explains what each approach does, when to use it, how they work together, and what happens when you walk into a competitive evaluation without either.
Price to Win (PTW) analysis answers one question: What price do I need to offer to beat my likely competitors? It is externally focused — built on research into what competitors are likely to offer, what the government expects to pay, and how price will be weighted in the source selection.
PTW analysis draws on publicly available data (FPDS, USASpending.gov, GSA pricing databases), industry research, incumbent contract history, and competitive intelligence gathered during the capture phase. The output is a target price range — typically expressed with a recommended offer point and confidence intervals — that gives your pricing team a defensible, data-grounded mandate rather than a gut-feel estimate.
Should-Cost modeling answers a different question: What should this work actually cost if performed efficiently? It is internally focused — a bottom-up build of costs from first principles, independent of what anyone else is likely to charge.
Should-Cost modeling starts with the statement of work and builds upward: labor hours by task by category, labor rates by category, indirect rates, materials, ODCs, profit. The goal is to establish a defensible cost floor — the minimum price at which you can perform the work and remain profitable — and to identify specific efficiency opportunities that might reduce cost without compromising technical quality.
PTW analysis is most valuable on competitive, high-value procurements where price carries meaningful weight in the source selection — particularly best-value tradeoff competitions, LPTA procurements with a defined technical threshold, and opportunities where you have credible intelligence on likely competitors. As a general rule, any opportunity above $5M in total value warrants at least a basic PTW analysis.
You're competing against 2–4 known competitors on a best-value IDIQ task order. Your PTW analyst researches incumbent pricing history on FPDS, estimates competitor indirect rates from public disclosures, and delivers a target range of $4.2M–$4.6M — giving your pricing team a mandate that's grounded in competitive reality, not internal cost-building alone.
Should-Cost is most valuable when you need to demonstrate price reasonableness and cost realism to the government — particularly on cost-reimbursable contracts, R&D acquisitions, or any procurement where the agency explicitly requests should-cost analysis. It's also essential as a tool for identifying cost efficiencies that improve your competitiveness without creating performance risk.
You're bidding a cost-plus R&D contract where the agency will perform a cost realism assessment. Your Should-Cost model demonstrates that your labor hours are reasonable for the scope and your indirect rates are consistent with your disclosed accounting practices — protecting you from a realism downward adjustment that would reduce your evaluated cost.
The most powerful use of these tools is in combination. Should-Cost sets your price floor — the minimum you can bid and still perform the work profitably. PTW sets your competitive ceiling — the maximum you can bid and still win. Your optimal offer lives somewhere between those two bounds, and the distance between them represents your pricing strategy opportunity.
In practice, the combination works like this:
This integrated approach gives evaluators confidence in your pricing, differentiates you from competitors who are either too high or suspiciously low, and protects your profitability if you win.
Contractors who skip these analyses typically do one of three things: they use a historical cost model from a previous contract (which may be years out of date), they add a fixed percentage to their cost build (which has no relationship to competitive reality), or they ask a BD person to estimate what they think the government will pay (which is an informed guess at best).
The result is predictable: win rates suffer. Either you're consistently outbid because you're pricing above the competitive range, or you're winning contracts you'll lose money on because your cost build was optimistic and your PTW estimate non-existent. Federal contracting has too thin margins and too long performance periods for pricing to be casual.
FedBiz Solutions' Price to Win analysis services cover both dimensions — competitive intelligence research for PTW and should-cost modeling for cost realism — delivered early enough in the proposal process to actually shape your pricing strategy, not just document it after the fact.
FedBiz Solutions' price-to-win analysts give you a competitive price target grounded in real data — early enough to shape your entire offer, not just your cost volume.
Get a Free PTW ConsultationQuick answers to common questions about federal pricing strategy.