Price-to-win gets treated like a trade secret. It is not. It is an estimate of the price a competitive offeror would need to bid to win a given contract, built from three things: what similar work has actually sold for, what the work actually costs to deliver, and what you know about who else is bidding. Big primes have whole teams that do this. You can do a rough version of it yourself with a laptop and public records.
What it actually is
Price-to-win is not your cost plus your target margin. That number tells you what you need to charge to make money. Price-to-win tells you what the government is likely to accept, given what it has paid for comparable work before. The two numbers can be close or far apart, and the gap between them is the actual decision you are making when you price a bid: chase the win at a thinner margin, or protect the margin and accept a lower chance of winning.
A price-to-win estimate is a range, not a figure. Anyone who hands you a single number is skipping the part where they show their work.
The three inputs
Historical award data. USAspending.gov publishes federal contract award data, including the awarded amount, the awarding agency, and the vendor, searchable by NAICS code, PSC code, and agency. If you can find five or ten awards for work similar to what you are bidding, you have a real price band, not a guess.
Cost realism. The government does not just want low. FAR Part 15 requires contracting officers to assess whether a proposed price is realistic for the work described, not just whether it is the lowest number on the page (FAR Subpart 15.4, Contract Pricing). A price with no plausible path to delivering the work gets flagged, even if it is lowest. Your own cost buildup, labor, materials, overhead, is the check against pricing yourself into a proposal you cannot actually perform.
Market and competitive intel. Who else is likely to bid. Is this a recompete where the incumbent has an obvious cost advantage. Is it a new requirement where nobody has pricing history yet. This is the softest of the three inputs and the one most bidders skip, but even a rough read of "is this a crowded lane or an empty one" changes how aggressive you should price.
Building a rough estimate yourself
Start with USAspending.gov and pull every award you can find under the relevant NAICS or PSC code, filtered to the same agency if possible, going back two to three years. Note the award amounts, the period of performance, and whether the awardee was a small business or not, since that changes the comparison. That gives you a band, not a point.
Layer your own cost buildup on top. If your realistic cost to deliver sits above the historical band, that is useful information on its own. It tells you either the requirement has changed enough that old awards are not a fair comparison, or you are not the right fit for this particular lane at this particular price.
This is exactly where a bid pipeline tool earns its keep instead of a spreadsheet. Ours pulls the same public award history and lines it up against the solicitation you are looking at, so you get a price band without building the query yourself from scratch. You can see how that works on the features page. It is a starting estimate, not a guarantee of what will actually win. Nothing built from public data can promise that, and nothing we sell claims to.
What it will not do for you
Price-to-win narrows the guess. It does not remove the judgment call. Two contractors looking at the same award history and the same cost buildup can still land on different bids, because the last mile is always a decision about how much margin you are willing to give up to win the work. No estimate, ours or a consultant's, makes that decision for you.
Related reading
- How to Write a Government Contract Proposal (Section-by-Section)
- Past Performance: How to Bid Competitively With None