Your costs are not the customer’s budget
Most teams price a bid from the inside out: add up labor, materials, and overhead, apply a target margin, and submit the result. That number tells you the lowest price you can accept. It tells you nothing about whether it wins. The price that wins is set by three things outside your cost model — what the customer can actually pay, what your competitors will bid, and how the award weighs price against everything else — and finding it is a discipline of its own called price-to-win.
Price-to-win analysis flips the question from "what does this cost us?" to "what is the highest price we can charge and still beat the field?" Those are different numbers, and the gap between them is either margin you left on the table or a loss you could have avoided. On a competitive bid, guessing here is how good technical proposals lose to cheaper ones — or how teams win unprofitable work they should have walked away from.
Start with the customer’s budget reality
Before you model competitors, anchor on what the customer can spend. Independent government cost estimates, prior contract values for similar work, published budget lines, and what the incumbent is currently paid all bound the realistic range. If you have done real capture, you have heard budget signals directly: a funding ceiling mentioned in a meeting, a scope the customer quietly trimmed because of cost, a comment about what they paid last time.
A bid wildly above the customer’s available funding loses no matter how good it is, and a bid far below it can read as not understanding the work. The budget range is the box your price has to land inside; the rest of the analysis is about where inside that box you sit relative to the competition.
Model the competitors, not just yourself
The second input is the hardest and the most valuable: what will the others bid? You cannot know exactly, but you can estimate, and an estimate beats the implicit assumption most teams make — that competitors price the way they do. Work the same way you would in a win/loss analysis, but forward: who is likely to bid, what is their cost structure, how badly do they want this, and how have they priced similar work?
An incumbent often has lower transition costs but may carry pricing baggage from the prior award. A competitor desperate for past performance in this domain may bid thin to buy the reference. A large prime carries more overhead than a lean small business. Each of those shapes the number they land on, and the goal is not a single competitor price but a credible range you have to beat or match.
This is also where your bid/no-bid scoring and price-to-win feed each other. If the analysis shows the winning price is below your cost, that is a no-bid finding arriving in time to matter, not a discovery you make after losing.
Read how price is actually evaluated
The same dollar figure wins or loses depending on how the award is scored, so the third input is the evaluation method. A lowest-price technically-acceptable competition rewards the cheapest compliant bid, full stop, and price-to-win there means finding the floor you can hit while still passing the technical bar. A best-value tradeoff lets a higher price win if the technical and past-performance advantages justify it, which means a strong discriminator-driven proposal can carry a price premium — but only as much premium as the tradeoff language will actually support.
Reading the Section M evaluation criteria, the same way you do when shredding the RFP into a compliance matrix, tells you how much your non-price strengths are worth in dollars. Price-to-win is not always the lowest number; on a best-value bid it is the highest number your strengths can defend.
Turn the analysis into a defensible number
The output of price-to-win is a target price and, just as important, a rationale for it. You should be able to say: the customer can fund roughly this much, the competition will likely land around there, the award rewards price in this way, and therefore our number is X and it wins because of Y. That rationale is what lets leadership sign off with confidence instead of haggling over margin in the dark, and it is what you revisit honestly afterward in win/loss analysis to sharpen the next estimate.
It also keeps you from two expensive mistakes: pricing high and losing winnable work, and pricing low and winning work you cannot deliver profitably. The discipline of protecting margin under pressure applies here too — a price-to-win number that dips below a floor you set in advance is a signal to walk, not a reason to discount further.
Where the CRM fits
Price-to-win runs on intelligence gathered over the whole pursuit — budget signals, competitor reads, evaluation-method notes — and that intelligence is worth nothing if it lives in someone’s head or a one-off spreadsheet. When every logged capture conversation, competitor note, and budget signal sits on the same pursuit record in Hitt CRM, the person building the price model is working from the customer’s reality instead of a guess. Tasks keep the analysis on schedule against the RFP clock, and a report across past pursuits — what you bid, what you won, where price decided it — turns each estimate into evidence that makes the next price-to-win sharper than the last.
The one-sentence version
Bidding your cost plus a margin tells you the price you can accept, not the price that wins, so work the problem from the customer’s side — their budget, your competitors’ likely bids, and how the award weighs price — to find the highest number you can charge and still beat the field, which is sometimes the lowest bid and on a best-value competition is the highest price your discriminators can defend.