Assess whether the SBIR data-rights assertions are too aggressive (c1913b)
August 31, 2026
SITUATION The working file is price-to-win versus independent government cost estimate after a data-rights assertion the customer already rejected last year. Capture manager in a joint venture with an uneven workshare draft has to name Pursue or Pursue with conditions for this Government RFP Capture and Pricing file.
DECISION Capture manager in a joint venture with an uneven workshare draft must choose Pursue / Pursue with conditions / Partner / No-bid using price-to-win versus independent government cost estimate after a data-rights assertion the customer already rejected last year.
HYPOTHESES TO TEST 1. The population in price-to-win versus independent government cost estimate is the one a data-rights assertion the customer already rejected last year named, so Pursue follows for this Capture and Pricing file. 2. The population in price-to-win versus independent government cost estimate is adjacent only to a data-rights assertion the customer already rejected last year; Pursue with conditions is the honest Government RFP call. 3. A joint venture with an uneven workshare draft already contained a data-rights assertion the customer already rejected last year before price-to-win versus independent government cost estimate arrived; no new Capture and Pricing path. 4. Provenance on price-to-win versus independent government cost estimate after a data-rights assertion the customer already rejected last year is broken; do not pick Pursue or Pursue with conditions yet.
ANALYSIS REQUIRED 1. Compare teaming and past-performance claims to what price-to-win versus independent government cost estimate attaches. 2. Normalize pricing and exceptions against the solicitation that governs the SBIR data-rights assertions. 3. Score competitive posture if capture manager pursues, partners, or no-bids. 4. For this Government RFP Capture and Pricing file, read price-to-win versus independent government cost estimate against a data-rights assertion the customer already rejected last year and write the one fact that would move the SBIR data-rights assertions for capture manager.
RECOMMENDATION Choose Pursue / Pursue with conditions / Partner / No-bid on this Government RFP / Capture and Pricing packet (price-to-win versus independent government cost estimate after a data-rights assertion the customer already rejected last year). Lead with the Government RFP option price-to-win versus independent government cost estimate can support after a data-rights assertion the customer already rejected last year, then the two facts that force it, then the Monday action for capture manager in a joint venture with an uneven workshare draft.
COMMAND RETURNS - Bottom-line Government RFP option on the SBIR data-rights assertions, then the evidence in price-to-win versus independent government cost estimate, then the action for capture manager - Hypothesis scorecard against price-to-win versus independent government cost estimate: supported / rejected / untestable - Capture and Pricing finding in price-to-win versus independent government cost estimate that a second reviewer can re-perform - Missing page in price-to-win versus independent government cost estimate after a data-rights assertion the customer already rejected last year, if any
Explore more
More Government RFP prompts
- Assess whether to bid as prime, sub, or no-bid after a task order that looks
- Assess whether to price to win or walk from a buy-in (b45bfa)
- Assess whether the bid is compliant enough to survive a responsiveness check
- Assess whether to price to win or walk from a buy-in (e0a59e)
- Assess whether the SBIR data-rights assertions are too aggressive (f3c5ec)
Explore related decision areas
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.

