A Price to Win effort succeeds when it follows a disciplined path from early uncertainty to executive decision. The process does not begin with a model and it does not end with a number. It begins with a clear understanding of the opportunity, develops an initial market hypothesis, tests that hypothesis through research, converts the evidence into price scenarios, and then helps leaders decide how to compete.
5.1 Overview of the Full PTW Workflow
PTW workflow: the sequence of activities that turns an opportunity-specific market hypothesis into a recommended price position and set of bid decisions. The workflow should be visible to capture, solution, pricing, finance, and executives from the beginning of the pursuit. If the PTW process is hidden inside one function, it will either arrive too late or fail to influence the choices that determine competitiveness.
The workflow has four phases. Phase 1: opportunity framing and hypothesis development. Phase 2: market, customer, and competitor research. Phase 3: competitive price modeling and scenario development. Phase 4: executive alignment, iteration, and bid decision support. These phases are not rigid handoffs. They overlap and repeat as new facts emerge. A solicitation amendment may force the team back into research. A teaming change may require a new internal price comparison. A competitor’s unexpected move may require updated scenarios.
The first principle is to start before the company has perfect information. Many teams delay PTW because they do not yet have the final solicitation, final scope, final competitor list, or final solution. That is exactly why the work should begin. Early PTW is hypothesis-driven. It asks what the company currently believes about the customer, market, competitors, budget, evaluation criteria, and likely winning price. Those beliefs are then tested. Waiting for certainty defeats the purpose because many important solutions and teaming decisions will already have been made.
The second principle is to separate facts, assumptions, and judgments. A fact might be the prior contract award value, the stated evaluation method, or a published labor rate. An assumption might be that the incumbent will reduce fees to defend the account. A judgment might be that the customer will not pay more than a modest premium for transition risk reduction. PTW mixes all three, but it must label them clearly. The team should never allow a repeated assumption to harden into a fact simply because it appeared in multiple review decks.
The third principle is to make each phase decision-oriented. PTW should not produce research for its own sake. Every activity should support a decision: whether to bid, which competitors matter, what customer questions to pursue, how to shape the solution, what price range to target, what margin trade-off to accept, or whether to walk away. The output of PTW is not analysis. The output is better bid behavior.
- Frame: define the procurement, evaluation method, customer value equation, initial competitor field, and first win-price hypothesis.
- Research: gather and normalize customer, competitor, award, budget, vehicle, and rate information that affects the likely winning price.
- Model: estimate competitor price bands, customer premium tolerance, award scenarios, and the company’s position against the market.
- Decide: reconcile PTW with internal pricing, identify required changes, brief executives, and support the final bid posture.
5.2 Phase 1: Opportunity Framing and Hypothesis Development
Phase 1 defines what the PTW effort is trying to solve. The most common mistake at this stage is jumping immediately into data collection without first framing the opportunity. The team begins searching for award values, rates, and competitor names, but it has not clarified the procurement structure, evaluation logic, scope boundaries, or strategic pricing question. The result is a pile of information rather than a focused market hypothesis.
Opportunity framing: the structured understanding of the procurement context before detailed analysis begins. The PTW team should examine the customer, mission, contract type, period of performance, expected value, procurement vehicle, set-aside status, pricing structure, evaluation criteria, incumbent status, and likely schedule. This framing determines what kind of PTW analysis is needed. A recompete for a labor-intensive services contract requires different analysis than a new technology integration effort, a commodity task order, or a cost-reimbursement development program.
The team should identify the central price question. In some pursuits, the question is whether the incumbent can be beaten below the current run rate. In others, it is whether the customer will pay a premium for a lower-risk technical approach. In a task order, the question may be how low the field will go on labor rates. In a strategic new account pursuit, the question may be whether the company is willing to accept lower margin to enter the customer. A clear price question prevents the PTW effort from becoming too broad.
Phase 1 should also produce the first win-price hypothesis. This is not the final answer. It is a reasoned starting point that says, for example, “The likely winning price will need to be 8 to 12 percent below the incumbent run rate unless the customer gives significant weight to transition risk,” or “The customer is likely to accept a moderate premium if the bidder can demonstrate staffing certainty and mission continuity.” The hypothesis should include both the expected price range and the logic behind it.
The initial hypothesis should be built from available information, not speculation alone. Sources may include the current contract value, prior award notices, known agency behavior, capture intelligence, budget documents, incumbent performance, prior debriefs, and comparable procurements. Every hypothesis should be accompanied by assumptions to test.
Phase 1 is also the right time to identify early disqualifiers. If the company’s likely cost position appears structurally above the market, leadership should know immediately. If a competitor has a decisive vehicle, customer, or cost advantage, the team should understand the implications. If the evaluation method is likely to compress technical differentiation, the solution team should be warned before designing an expensive offer.
The deliverable from Phase 1 should be concise: a framing memo or short readout that states the opportunity, the initial PTW hypothesis, the top assumptions, and the research plan. The goal is not to impress the organization with volume. The goal is to align the team on what must be learned next.
5.3 Phase 2: Market, Customer, and Competitor Research
Phase 2 tests the initial hypothesis. This is where the PTW team moves from plausible beliefs to evidence. The research effort should be targeted because pursuit teams rarely have unlimited time. The purpose is to gather the information that changes the likely winning price, competitor bands, customer premium tolerance, or bid strategy.
Market research: the collection and interpretation of comparable award, vehicle, rate, budget, and procurement data that reveals price norms for similar work. The team should identify relevant contracts and task orders, normalize them for scope and period of performance, and determine whether they provide valid benchmarks. A prior award is not automatically comparable because it involves the same agency or vehicle. The team must assess mission similarity, labor mix, geography, security requirements, transition complexity, contract type, performance risk, and timing.
Customer research: the analysis of how the buying organization behaves when selecting among price and value alternatives. This includes award history, debrief themes, protest decisions, budget constraints, public statements, acquisition strategy, and capture intelligence gathered through appropriate channels. The team should ask whether the customer has historically paid premiums, favored incumbents, emphasized affordability, scrutinized cost realism, or used price as the practical discriminator after determining technical acceptability.
Competitor research: the assessment of who is likely to bid and how each bidder is likely to price. The team should distinguish between possible competitors and serious competitors. A firm may be eligible to bid but unlikely to invest. Another may lack the strongest technical position but have a cost structure that makes it dangerous. For each serious competitor, the PTW team should estimate motivation, customer access, vehicle position, past performance fit, teaming options, probable staffing approach, indirect rate posture, and likely fee behavior.
The research should be conducted through triangulation. No single source is usually sufficient. A historical award value may show what the government paid, but not how the scope changed. A labor rate may show a ceiling rate, but not the discounted rate used in a task order. A debrief may reveal evaluation logic, but only for a specific procurement. A capture source may provide insight, but the team must separate firsthand evidence from opinion.
Phase 2 should also include a research gap log. Pursuit teams often lose track of what they do not know. A gap log records unknowns that materially affect the PTW range: the incumbent’s current staffing level, the customer’s budget ceiling, a likely competitor’s teaming decision, whether transition cost will be evaluated, or whether the agency will score technical strengths meaningfully. Each gap should have an owner, due date, and fallback assumption if the answer cannot be obtained.
Ethics must be explicit in Phase 2. PTW research should rely on lawful, appropriate sources: public records, published awards, legitimate customer engagement, prior debriefs, company experience, vehicle data, budget materials, and market knowledge. The team must not seek protected source selection information, proprietary competitor pricing, or nonpublic bid details. A strong PTW process is rigorous because it can be defended.
The output of Phase 2 should be an evidence pack, not a data dump. It should show the most relevant comparables, the customer pricing profile, the refined competitor list, early competitor price indicators, and the key assumptions that survived or changed. A well-run Phase 2 usually modifies the Phase 1 hypothesis. If it does not, the team should ask whether it truly tested the hypothesis or merely collected confirming evidence.
5.4 Phase 3: Competitive Price Modeling and Scenario Development
Phase 3 converts research into a market-based price view. This is where PTW becomes explicitly quantitative, but the quantitative work should remain tied to judgment. The model is not valuable because it looks sophisticated. It is valuable because it clarifies the likely winning range, shows how competitors may cluster, explains which assumptions matter most, and helps the company decide how to position its offer.
Competitive price model: a structured estimate of the price bands likely to be submitted by serious competitors and the award range likely to result from the customer’s evaluation. The model should begin with the solicitation’s evaluated price structure. If the government evaluates base years, option years, labor categories, escalation, travel, other direct costs, transition, or optional tasks, the model must reflect that structure. A PTW model that estimates an unevaluated price is not useful, no matter how carefully it is built.
The model should then build competitor-specific price bands. Each band should be based on a theory of how that competitor will bid. The incumbent may have current staff, transition advantages, and customer knowledge, but also legacy cost and margin expectations. A challenger may have lower indirect rates, a leaner staffing approach, and a willingness to accept lower fees, but also transition risk. A strategic entrant may price aggressively to enter the account. A technically strong premium bidder may stay above the low-price field but hope for a best-value trade-off. These competitor theories should be explicit.
Normalization is essential. Historical prices must be adjusted for scope, time, volume, labor mix, inflation, contract type, and performance period. Rate comparisons must account for labor categories, seniority, location, clearance, and whether rates are ceiling, bid, or actual billed rates. Incumbent run-rate comparisons must account for contract changes, surge, vacancies, pass-throughs, and option-year escalation. Without normalization, the model can create a false sense of precision from mismatched data.
The PTW team should develop scenarios rather than one answer. A typical model includes a most-likely scenario, aggressive-price scenario, premium-tolerant scenario, and sometimes an incumbent-defense or challenger-disruption scenario. Each scenario should describe the customer behavior and competitor behavior that would produce it. An aggressive-price scenario may assume technical parity and one low-cost bidder with a lean staffing model. A premium-tolerant scenario may assume the customer assigns meaningful value to transition certainty and mission risk reduction.
Sensitivity analysis should identify the assumptions that move the range. Common drivers include labor mix, staffing level, indirect rate assumptions, subcontractor workshare, fee aggressiveness, transition pricing, escalation, budget ceiling, and technical premium tolerance. The team should not bury these drivers in the model. Executives need to see them because they define the management choices available to the company.
The model should produce five practical outputs. Likely winning range: the price band where award probability is strongest. Competitor bands: estimated price ranges for meaningful bidders. Scenario outcomes: how the winning range changes under different customer and competitor behaviors. Company comparison: the company’s internal price, margin, and evaluated position against the PTW range. Action levers: the solution, teaming, pricing, or margin choices that could move the company into a better position.
5.5 Phase 4: Executive Alignment, Iteration, and Bid Decision Support
Phase 4 turns the PTW analysis into action. This phase is where many companies lose value. They complete the research, build the model, and produce the range, but then fail to force the hard decisions. The PTW team presents a market price below the internal price. Capture agrees the bid must be competitive. Finance objects to margin erosion. Solution argues that the technical approach cannot be reduced. Executives ask for another iteration. Unless the process is managed tightly, the team cycles until the deadline removes meaningful options.
Executive alignment: the process of bringing decision makers to a shared view of the market range, company economics, win probability, and required trade-offs. Alignment does not mean everyone likes the answer. It means leadership understands the evidence and makes an explicit choice. The choice may be to price within the PTW range, justify a premium, redesign the solution, reduce fee, change teaming, invest strategically, or no-bid.
The first step is reconciliation with internal pricing. The PTW range should be compared against the company’s cost-based price and margin targets. If the two are close, the team can focus on proposal messaging and risk management. If there is a material gap, the team must diagnose it. A gap may result from an overbuilt solution, high indirect rates, expensive subcontractors, conservative staffing, unrealistic margin expectations, or an overly aggressive PTW assumption. The reconciliation should identify the root cause before prescribing action.
Iteration should be structured. The PTW team should not simply tell pricing to lower the number, and pricing should not simply defend the cost build. The team should evaluate specific levers. Can the labor pyramid be adjusted? Can senior roles be reserved for key tasks while routine work moves to lower levels? Can delivery locations change? Can automation reduce hours? Can subcontractor workshare be rebalanced? Can fee vary by contract line item? Can transition be priced differently? Can the technical narrative justify a premium?
Executives should receive a concise decision package. The package should include the recommended bid price or price range, the PTW analysis behind it, the internal price comparison, likely competitor positions, customer premium tolerance, margin impact, major execution risks, and the decision required. Executives need enough evidence to challenge the recommendation, but the central question should be clear: “Given this market view and these economics, how do we choose to compete?”
Phase 4 should also support bid/no-bid discipline. PTW sometimes reveals that the right answer is not to bid. That conclusion can be difficult, especially after significant capture investment. But a disciplined no-bid may be superior if the company cannot reach the likely winning range without unacceptable delivery or financial risk. PTW should make that conclusion visible early, and executives should reward teams for identifying unwinnable pursuits rather than punishing them for not chasing revenue.
At final proposal submission, the PTW record should document the decision. The company should know where it bid relative to the likely winning range, why it chose that position, what assumptions it accepted, and what risks it took. This record is valuable after the award, whether the company wins or loses. A win can validate or refine the model. A loss can reveal whether the issue was price, technical evaluation, competitor behavior, or incorrect assumptions.
The end-to-end PTW process is both analytical and managerial. It gathers evidence, builds models, and estimates ranges, but its real purpose is to shape choices. A contractor that follows the process will not win every bid. No methodology can produce that. But it will compete with clearer eyes. It will understand the market before the final week. It will see the tension among price, value, margin, and risk. It will make deliberate decisions rather than accidental ones. That is the practical value of PTW: it turns pricing from a late-stage number into an end-to-end strategy discipline.
