AI IDIQ Task Order Strategy Playbook
Your firm holds a position on a $400M GSA Multiple Award Schedule vehicle with 11 other contractors. The government has issued 3 task orders in the first year, and your firm has won 0 of the 3. Win rates for incumbents on similar MAS vehicles average 28–34%. Your BD team needs a task order strategy before the next competition.
When to use this playbook
- Use this playbook when the decision looks like the situation above: Your firm holds a position on a $400M GSA Multiple Award Schedule vehicle with 11 other contractors.
- It is a fit when you have source files in hand and need a structured, reviewable analysis — not a generic chat answer about "IDIQ Task Order Strategy".
- Do not use it as a substitute for licensed, legal, clinical, or authorized official judgment in the domain.
What you'll need
- The 3 task order solicitations you lost (available from SAM.gov)
- Award data for all 3 task orders (awardee, price, NAICS)
- Your 3 submitted task order proposals
- MAS vehicle terms and ordering procedures
- Competitor MAS pricelist data (public)
Attachments: Documents (Documents)
The Prompt
You are a federal BD strategist developing a task order win strategy for a GSA MAS vehicle. I am attaching: Work only from the attached source files. If a conclusion is not supported, say so. Produce: 1. Diagnose why you lost each of the 3 task orders: was it price, technical approach, past performance, or evaluation approach misread? 2. Compare your labor rates against the awardees' public pricelist rates for the key labor categories in each task order—quantify any pricing gap. 3. Identify the pattern in the task orders being issued: are they favoring certain NAICS codes, small business categories, or specific technical capabilities you don't emphasize? 4. Recommend 3 specific changes to your MAS strategy: pricing adjustments, capability additions, or relationship-building with the ordering agency. 5. Tell me which of the upcoming anticipated task orders (from agency procurement forecasts) represent the best win probability and why. Call out where independent models are likely to disagree, and list follow-up documents a reviewer should request.
What to expect
- Loss analysis for each task order with root cause
- Pricing gap quantification vs. awardees
- Task order pattern analysis
- 3 strategic recommendations with expected win rate impact
- Upcoming task order opportunity scoring
Review before you act
- Validate this output against source files before relying on it: Diagnose why you lost each of the 3 task orders: was it price, technical approach, past performance, or evaluation approach misread?.
- Validate this output against source files before relying on it: Compare your labor rates against the awardees' public pricelist rates for the key labor categories in each task order—quantify any pricing gap.
- Validate this output against source files before relying on it: Identify the pattern in the task orders being issued: are they favoring certain NAICS codes, small business categories, or specific technical capabilities you don't emphasize?.
- Validate this output against source files before relying on it: Recommend 3 specific changes to your MAS strategy: pricing adjustments, capability additions, or relationship-building with the ordering agency.
- 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 IDIQ Task Order Strategy, 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 loss analysis for each task order with root cause; pricing gap quantification vs. awardees; task order pattern analysis; 3 strategic recommendations with expected win rate impact. 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.

