This appendix consolidates the working tools needed to run a disciplined Price to Win effort. The templates are designed for live government contracting pursuits, where teams must make decisions with incomplete information, compressed timelines, and competing functional priorities. They are not meant to create administrative burden. They are meant to make the PTW process visible, repeatable, and decision-oriented.
Each tool can be scaled to the size and importance of the pursuit. A major recompete may require full versions of every template, supported by detailed backup analysis. A small task order may require abbreviated versions completed in a working session. The principle is the same in both cases: document the market view, identify assumptions, compare PTW with internal pricing, and force timely decisions.
A. Price to Win Project Charter
Purpose: the PTW project charter defines the objective, scope, roles, timeline, data sources, and decision path for the PTW effort. It should be completed during qualification or early capture, before the team begins detailed research. A strong charter prevents confusion about what PTW will deliver and what decision it is intended to support.
Opportunity name: | [Program, task order, vehicle, solicitation, or recompete name.] |
Customer and buying office: | [Agency, bureau, command, program office, contracting office, and known decision influencers.] |
Contract profile: | [Contract type, anticipated value, vehicle, set-aside status, period of performance, and expected award date.] |
PTW objective: | [Bid/no-bid, target price, premium strategy, recompete defense, challenger strategy, or margin exception support.] |
Scope of analysis: | [Total evaluated price, labor rates, base plus options, transition, subcontractors, competitor bands, customer premium tolerance.] |
Out of scope: | [Compliant cost-volume build, final fee approval, subcontractor negotiations, or final bid-price ownership.] |
Core team: | [PTW lead, capture lead, pricing lead, solution lead, finance lead, contracts lead, compliance contact, executive sponsor.] |
Primary outputs: | [PTW range, competitor price map, agency pricing behavior view, scenarios, assumptions register, reconciliation sheet, executive readout.] |
Governance cadence: | [Qualification, capture strategy, solution alignment, solicitation refresh, reconciliation, final bid approval.] |
Decision owner: | [Named executive accountable for the final bid-price decision.] |
The charter should be reviewed with all major functions. If the opportunity changes materially, the charter should be updated rather than left as a static kickoff document.
B. Opportunity Framing Checklist
Purpose: this checklist helps the team understand the procurement before building the PTW model. It should be used in the first PTW working session to identify what the procurement appears to reward, what the customer can afford, and what market assumptions require testing.
- Procurement identity: What is the customer, vehicle, anticipated value, contract type, set-aside status, and schedule?
- Mission context: What mission outcome is the customer buying, and what is the consequence of failure?
- Scope clarity: Which work elements are clear, ambiguous, optional, or likely to drive cost?
- Incumbent position: Who is the incumbent, what is the current run rate, and how satisfied is the customer?
- Evaluation method: Is the procurement LPTA, best value, trade-off, cost realism, or practically price-driven?
- Pricing structure: What exactly will be evaluated: total price, labor rates, base plus options, sample tasks, transition, travel, or ODCs?
- Budget pressure: What affordability signals, funding constraints, or savings expectations are visible?
- Customer pain points: Is the customer trying to solve cost, performance, staffing, transition, innovation, quality, or risk?
- Likely competitors: Which bidders could materially affect the winning price?
- Initial PTW hypothesis: What is the provisional winning range, confidence level, and top assumptions?
The checklist should result in a short framing memo. The memo should state the procurement’s pricing logic, the initial win-price hypothesis, the most important unknowns, and the immediate capture or solution decisions required.
C. Agency Pricing Behavior Profile
Purpose: the agency pricing behavior profile captures how a customer has historically treated price, value, risk, incumbency, and affordability. It should be maintained at the buying-office or program-office level whenever possible, because large agencies often contain very different acquisition cultures.
Customer / buying office: | [Agency, bureau, command, program office, contracting activity, and key stakeholders.] |
Relevant procurement categories: | [IT services, engineering, cybersecurity, professional services, logistics, software, operations, facilities, or other categories.] |
Typical evaluation posture: | [LPTA, best value, trade-off, cost realism, technically acceptable with price pressure, or mixed behavior.] |
Observed price sensitivity: | [High, medium, low, or situation-specific. Include evidence from prior awards and debriefs.] |
Premium tolerance: | [What premiums has the customer accepted, under what conditions, and for which evaluated strengths?] |
Incumbent behavior: | [Does the customer tend to retain incumbents, replace them, or require savings to justify retention?] |
Budget and affordability signals: | [Flat funding, savings language, budget ceiling, expiring funds, program growth, or consolidation pressure.] |
Cost realism posture: | [Does the customer challenge low staffing, low compensation, unrealistic labor mix, or aggressive assumptions?] |
Debrief and protest lessons: | [Recurring themes from prior debriefs, award rationales, corrective actions, or protest decisions.] |
PTW implications: | [How this profile should affect the likely winning range, premium strategy, solution design, and bid/no-bid decision.] |
Each conclusion in the profile should cite evidence. Avoid unsupported labels such as “price sensitive” or “best-value customer” unless the underlying award behavior supports them.
D. Competitor Threat Matrix
Purpose: the competitor threat matrix helps the PTW team identify which competitors are most likely to affect the winning price. It should focus on serious bidders, not every company that is technically eligible to bid.
Threat level: a combined view of the competitor’s technical credibility, customer fit, pricing flexibility, and likelihood of influencing the award.
Competitor / likely team | Bid probability | Threat level | PTW implication |
[Incumbent prime / incumbent team] | [High / Medium / Low] | [High / Medium / Low] | [Sets the baseline for current run rate, continuity value, and transition-risk premium.] |
[Major prime challenger] | [High / Medium / Low] | [High / Medium / Low] | [May pressure the incumbent and define the credible best-value alternative.] |
[Low-cost challenger] | [High / Medium / Low] | [High / Medium / Low] | [May set the price floor if technically acceptable and trusted by the customer.] |
[Niche specialist or strategic entrant] | [High / Medium / Low] | [High / Medium / Low] | [May strengthen another bidder’s team or create a disruptive pricing scenario.] |
The matrix should be supported by brief notes on evidence and assumptions, such as prior awards, vehicle access, customer relationships, teaming signals, observed hiring, debrief lessons, or rate behavior. If a rating is based mainly on judgment rather than evidence, the team should say so explicitly.
E. Historical Award Analysis Worksheet Outline
Purpose: this worksheet converts prior awards into usable PTW benchmarks. It prevents the team from relying on raw award values that may not be comparable to the current opportunity.
Historical award name: | [Program, contract, task order, or solicitation name.] |
Customer / buying office: | [Agency, program office, contracting activity.] |
Awardee and role: | [Prime awardee, known teammates, incumbent or challenger status.] |
Award date and source: | [Public record, debrief, internal pursuit file, protest decision, or other source.] |
Contract type and vehicle: | [Fixed-price, cost-reimbursement, T&M, hybrid, IDIQ, BPA, schedule, or other.] |
Period of performance: | [Base period, option periods, transition period, total duration.] |
Reported value: | [Award value, ceiling value, obligated value, evaluated price, or run rate. Specify which.] |
Scope summary: | [Major work elements, sites, users, systems, labor categories, workload, or deliverables.] |
Comparability assessment: | [High, medium, or low. Explain why.] |
Normalization adjustments: | [Scope, duration, volume, labor mix, geography, inflation, escalation, contract type, or risk.] |
Normalized benchmark: | [Adjusted total price, annualized value, unit price, or relevant benchmark range.] |
PTW implication: | [What this award suggests about winning price, price compression, premium tolerance, or competitor behavior.] |
Do not average historical awards mechanically. Weight the most comparable awards more heavily, and make outliers explicit.
F. Competitor Pricing Data Collection Checklist
Purpose: this checklist structures the collection of legitimate competitor pricing intelligence. Use it for each serious competitor that could influence the winning price. The objective is to estimate likely bid range and pricing flexibility, not to obtain protected competitor information.
- Competitor identity: Who is the likely prime, and what team members may be involved?
- Bid probability: What evidence suggests the competitor will submit a serious proposal?
- Strategic motivation: Is the competitor defending, entering, expanding, protecting a vehicle, or buying into an account?
- Relevant award history: What comparable work has the competitor won?
- Historical price posture: Has the competitor behaved as low-price challenger, premium bidder, incumbent defender, or opportunistic bidder?
- Vehicle and rate data: What public or accessible rates exist, and are they ceiling rates, bid rates, or billing indicators?
- Likely labor mix: Will the competitor use senior-heavy staffing, lean pyramid, incumbent staff capture, delivery centers, automation, or subcontractors?
- Indirect-rate posture: What evidence suggests high, medium, or low burdened cost relative to the field?
- Subcontractor economics: Which teammates may raise or lower price through workshare, pass-throughs, or niche rates?
- Fee behavior: Is the competitor likely to preserve margin, discount moderately, or price aggressively?
- Customer credibility: Will the customer view a low price from this competitor as credible or risky?
- Likely price band: What conservative, likely, and aggressive ranges should be modeled?
Each answer should be labeled as known, inferred, or assumed. Unsupported assumptions should be carried into the PTW model as sensitivities, not facts.
G. PTW Model Output Template
Purpose: the PTW model output template presents the market-based price view in a format suitable for capture and executive review. It should summarize the likely winning range, competitor bands, confidence level, scenarios, sensitivities, and recommended action.
Opportunity: | [Customer, program, vehicle, contract type, pursuit stage, and expected award date.] |
Evaluated price construct: | [Total evaluated price, base plus options, labor-rate evaluation, sample task, transition, travel, or other evaluated elements.] |
Recommended PTW range: | [Low credible winning price, most likely winning price, upper winning price.] |
Confidence level: | [High, medium, or low, with one sentence explaining evidence quality.] |
Primary rationale: | [One paragraph explaining the customer, competitor, historical, and evaluation evidence supporting the range.] |
Competitor bands: | [Estimated price ranges for incumbent, large prime challenger, low-cost challenger, niche specialist, or strategic entrant.] |
Most likely scenario: | [Expected customer behavior, competitor behavior, and likely award logic.] |
Aggressive-price scenario: | [Conditions under which the winning range moves lower.] |
Premium-tolerant scenario: | [Conditions under which the customer may pay above the low-price field.] |
Key sensitivities: | [Competitor participation, customer premium tolerance, incumbent fee reduction, labor mix, escalation, cost realism, or subcontractor rates.] |
Recommended action: | [Lower price, improve solution, defend premium, change teaming, seek margin exception, or no-bid.] |
The output should be concise enough to brief in one executive meeting, with detailed backup available for challenge.
H. PTW vs. Internal Pricing Reconciliation Sheet Outline
Purpose: this sheet compares the market-based PTW range with the company’s internal cost-based price. It identifies the gap, diagnoses the cause, and presents available actions.
PTW range: | [Low credible, most likely, and upper winning price, with confidence level.] |
Internal price: | [Current cost-based evaluated price and target margin.] |
Delta to PTW: | [Dollar and percentage gap versus the most likely PTW point and range endpoints.] |
Component bridge: | [Labor, labor mix, indirects, subcontractors, ODCs, travel, transition, escalation, risk reserve, fee.] |
Gap diagnosis: | [Cost problem, solution problem, margin problem, win-probability problem, PTW assumption issue, or combination.] |
Available levers: | [Staffing, labor pyramid, management structure, delivery model, workshare, subcontractor concessions, fee, escalation, or scope interpretation.] |
Recommended change package: | [Specific changes, price impact, margin impact, evaluation impact, and delivery risk.] |
Resulting bid posture: | [Below range, within range, upper range, premium position, or outside range.] |
Executive decision required: | [Approve target price, margin exception, investment, solution redesign, teaming change, or no-bid.] |
The reconciliation sheet should be used before the final price review, while the team can still change the solution rather than only reduce the fee.
I. Executive Readout Template
Purpose: the executive readout converts PTW analysis into a leadership decision. It should focus on the recommendation, the evidence behind it, and the trade-offs among price, probability of win, margin, risk, and strategic value.
Opportunity and gate: | [Customer, program, pursuit stage, contract type, estimated value, and review gate.] |
Decision required: | [Bid, no-bid, invest, partner, re-scope, approve target price, defend premium, or approve margin exception.] |
PTW conclusion: | [Likely winning range, most likely price point, confidence level, and rationale.] |
Company price position: | [Internal price, proposed bid price, position versus PTW range, and evaluated price construct.] |
Competitor view: | [Likely competitors, expected bid ranges, price-floor setter, incumbent posture, and most dangerous challenger.] |
Customer behavior: | [Price sensitivity, premium tolerance, affordability signals, evaluation method, and historical behavior.] |
Win-probability implications: | [Directional win probability under proposed price and alternatives.] |
Margin and economics: | [Target margin, current margin, margin at recommended price, investment required, and guardrail exceptions.] |
Risk profile: | [Delivery risk, evaluation risk, business risk, contractual risk, and mitigation actions.] |
Recommended action: | [Specific price posture, solution changes, teaming actions, investment decisions, or no-bid recommendation.] |
Decision record: | [Approved decision, decision owner, date, conditions, and risks accepted.] |
The readout should begin with the requested decision, not the analytical history. Executives need enough evidence to challenge the recommendation and enough clarity to act.
J. PTW Compliance Checklist
Purpose: the PTW compliance checklist ensures that competitor research, customer insight, external advisor work, and pricing intelligence remain within legal and ethical boundaries. It should be completed at the start of the effort, refreshed after solicitation release, and reviewed before final executive approval.
- Compliance owner: Has a legal or compliance contact been assigned to the PTW effort?
- Source rules: Has the team defined approved, restricted, and prohibited information sources?
- Procurement integrity: Has the team avoided source selection information and protected competitor bid or proposal information?
- Competitor communications: Have all contacts with competitors, teammates, and subcontractors been limited to legitimate business purposes?
- Antitrust guardrails: Has the team avoided discussions of future prices, bid intentions, market allocation, bid suppression, or customer allocation?
- Teaming review: Have joint ventures, exclusivity provisions, and competitor-teammate arrangements been reviewed where needed?
- OCI screen: Has the team checked for organizational conflicts of interest involving the company, teammates, or advisors?
- Former personnel review: Have former government or competitor employees been screened for restrictions?
- Customer communication: Have all questions and meetings followed solicitation instructions and authorized channels?
- Data classification: Has major PTW information been classified as public, internal, third-party, restricted, or under legal review?
- Assumption register: Does the PTW model distinguish facts, inferences, judgments, and unsupported assumptions?
- Questionable information protocol: Does the team know how to handle suspicious, proprietary, misdirected, or protected information?
- External advisor controls: Do advisor agreements include confidentiality, conflict, information-use, and work-product controls?
- Record retention: Are source records, assumptions, reviews, and decisions retained according to company policy?
The compliance review should produce one of three outcomes: Cleared: the PTW effort may proceed as planned; Cleared with restrictions: the team may proceed but must exclude or limit specified information; or Not cleared: the team must pause use of affected information pending legal or compliance review.
Used together, these tools create a complete PTW operating system. The charter defines the work. The opportunity checklist frames the procurement. The agency profile explains the customer. The competitor tools define the field. The historical worksheet grounds the analysis. The PTW model presents the market view. The reconciliation sheet compares that view with internal economics. The executive readout forces the decision. The compliance checklist protects the integrity of the process. Consistent use of these tools turns Price to Win from a pursuit-specific exercise into a repeatable management discipline.
