AI Price-to-Win Analysis Playbook
Your firm is competing on a 5-year IDIQ for cybersecurity services at DHS. The estimated contract value is $45M. FPDS shows the incumbent won at $38.2M 5 years ago, and two competitors have been awarded similar vehicles at DHS in the past 18 months. Your current cost model comes in at $43.7M.
When to use this playbook
- Use this playbook when the decision looks like the situation above: Your firm is competing on a 5-year IDIQ for cybersecurity services at DHS.
- It is a fit when you have source files in hand and need a structured, reviewable analysis — not a generic chat answer about "Price-to-Win Analysis".
- Do not use it as a substitute for licensed, legal, clinical, or authorized official judgment in the domain.
What you'll need
- FPDS awards data for the incumbent contract and 2 competitor awards
- Your firm's current cost model (labor categories, hours, rates, ODCs)
- Market survey of comparable labor rates (GSA MAS, OMB rate guidance)
- DHS acquisition history and small business utilization rates
- Solicitation LPTA or best value determination from Section M
Attachments: Documents (Documents)
The Prompt
You are a price-to-win analyst building a competitive pricing strategy for a DHS cybersecurity IDIQ. I am attaching: Work only from the attached source files. If a conclusion is not supported, say so. Produce: 1. Estimate the likely competitive price range based on FPDS data, adjusted for inflation and scope changes from the incumbent contract. 2. Identify the specific labor categories where your current rates are above the competitive range and quantify the gap. 3. Assess whether this is an LPTA or best value acquisition and how that changes the price sensitivity for our bid decision. 4. Model three pricing scenarios: most competitive (at incumbent adjusted), mid-range (current model with targeted reductions), and premium (full rate with technical differentiation). 5. Tell me the price-to-win target and which labor categories I should negotiate with subcontractors to close the gap. Call out where independent models are likely to disagree, and list follow-up documents a reviewer should request.
What to expect
- Competitive price range estimate with methodology
- Labor category rate gap analysis
- LPTA vs. best value bid strategy assessment
- Three pricing scenario models
- Price-to-win target and subcontractor negotiation priorities
Review before you act
- Validate this output against source files before relying on it: Estimate the likely competitive price range based on FPDS data, adjusted for inflation and scope changes from the incumbent contract.
- Validate this output against source files before relying on it: Identify the specific labor categories where your current rates are above the competitive range and quantify the gap.
- Validate this output against source files before relying on it: Assess whether this is an LPTA or best value acquisition and how that changes the price sensitivity for our bid decision.
- Validate this output against source files before relying on it: Model three pricing scenarios: most competitive (at incumbent adjusted), mid-range (current model with targeted reductions), and premium (full rate with technical differentiation).
- Confirm every cited figure, date, counterparty, or requirement against the attached originals — models compress and can drop a qualifier.
- Treat disagreement between models as a review item, especially on classification, materiality, and recommended next action.
- Do not authorize an operational, clinical, legal, credit, or enforcement action solely because the models agree.
Why compare models on this
For Price-to-Win Analysis, running the same attachments across independent models is useful because the hard part is classification and completeness, not fluency. The workflow is already designed to surface competitive price range estimate with methodology; labor category rate gap analysis; lpta vs. best value bid strategy assessment; three pricing scenario models. Those are comparison artifacts — they only exist if more than one model runs. Models split on whether a requirement is mandatory, how to score a differentiator, and protest likelihood. Those splits should be resolved before color-team review, not after submission.
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

