This is one of many analyses on competitions as featured in our “Deadly Sins” series. We periodically pick up and analyze protests to offer observations on competitions to learn from these decisions as a case study in competition.
Our latest analysis breaks down the U.S. Space Force research and experimental development competition that was protested and that the GAO protest decision was published on July 21, 2026.
TL;DR: ITSC won a best-value tradeoff with a merely “acceptable” technical quotation because its competitor (the incumbent), IESE, priced a technically superior proposal roughly 73 percent (more than $61 million) higher. IESE swept every non-price rating and still lost, because in a best-value tradeoff “good enough” at the right price beats “exceptional” at the wrong one. ITSC made some calculated risks to challenge the incumbent and they paid off while the incumbent was anchored in a myriad of incumbent traps.
Summary of the Competition and Protest
IESE Solutions, protested the award of a contract award of its recompete contract to ITSC Secure Solutions. The work was for research and experimental development services for the U.S. Space Force, spanning system design, engineering and integration, IT, and around-the-clock operational support.
The RFQ used three factors: staffing approach (the most important, and itself split into a staffing matrix subfactor and a professional employee compensation subfactor), prior experience, and price. The non-price factors combined were “significantly more important” than price. The protest centered on three allegations:
- The agency unreasonably evaluated ITSC’s staffing matrix and its professional employee compensation plan
- The solicitation was too unclear for vendors to compete “on a common basis”
- The resulting best-value decision was therefore flawed.
The GAO denied every ground.
The Overall Evaluation
Here is the entire story in one table:
| Factor / Subfactor | IESE (Protester) | ITSC (Awardee) |
| Staffing Matrix (most important) | Exceptional | Acceptable |
| Professional Employee Compensation | Low Risk | Medium Risk |
| Prior Experience | Relevant | Somewhat Relevant |
| Price | $145,203,290 | $83,726,266 |
Read that again. IESE was rated higher vs. ITSC on all three non-cost measures. Exceptional vs. Acceptable on the most important subfactor, Low Risk vs. Medium Risk on compensation, Relevant vs. Somewhat Relevant on prior experience. The agency even called IESE’s quotation “technically superior.” But wait a minute…look at that price gap. Technically superior (and wildly so) IESE offered a $61.4 million premium. Did you hear that? That’s the first nail being hammered into the coffin.
There is a quiet detail in a footnote that illustrates the bigger backdrop of the competition. The third, unsuccessful vendor priced the work at about $80.4 million. The winner, and ITSC, came in at $83.7 million. Two of the three vendors clustered near $80–$84 million. IESE stood alone at $145 million. There was a pretty big gap on pricing. The plot thickens.
Staffing Matrix: Requirement vs. Recommendation
The staffing matrix subfactor is where the protest lived and died. IESE argued that ITSC should have been rated unacceptable because ITSC mapped the solicitation’s labor categories to broad GSA Schedule positions that did not, on their face, reference engineers, operations specialists, or space, satellite, or sensor expertise and because ITSC proposed labor categories with, by IESE’s count, less than half the years of experience the RFQ called for. In IESE’s telling, the agency did a “mere compliance check” instead of a real evaluation.
Wording matters and here we go.
With respect to whether the agency reasonably evaluated the GSA MAS labor categories experience requirements, we first note that the staffing matrix provided in the solicitation was a recommendation, and not a requirement … the RFQ stated that vendors could deviate from this staffing matrix as long as they provided a written narrative explaining any deviations. Accordingly, the RFQ did not require vendors to meet the experience levels stated in the staffing matrix.
Another nail enters the coffin. The staffing matrix was a recommendation.
ITSC read it that way, deviated down on experience where it made business sense, wrote the required narrative, and accepted the evaluation risks. And the agency did not gloss over those risks. The evaluators documented that for 12 of 19 positions, including all seven key personnel roles, ITSC mapped to GSA MAS labor categories allowing far less experience than the government recommended. As such, evaluators flagged the risk of backfilling with bare-minimum staff and noted schedule risk. It then balanced that against places where ITSC exceeded the requirement with enhanced key-personnel descriptions, a program manager with eight years against a five-year recommendation and assessed an aggregate “moderate risk,” which mapped to Acceptable.
ITSC made some very calculated gambles to beat the incumbent.
FedSavvy’s Take: A documented risk does not necessarily lead to unacceptable rating. Evaluators are allowed to see a flaw, write it down, weigh it, and still assign a passing rating. Incumbents often like to overthink what the RFP actually says and assume they know where the “wink wink nudge nudge” factors exist. The challenger responded to the RFP by really pushing the boundaries of the RFP.
The LCAT Trap
Another aspect of the protest that we have seen before and was again a calculated risk from ITSC was using labor categories (LCATs) that could be argued as non-compliant. In fact, IESE did argue this with some LCATs used by ITSC that had minimum requirements that fell below requirements stated in the solicitation. This was likely used by ITSC to allow it to have lower labor rates and thus compete better on price.
The trap here was just because the GSA MAS LCAT fell below stated RFP requirements did not mean ITSC could not or would not provide candidates who exceeded its own GSA MAS LCAT requirements and solicitation requirements. Instead, it gave ITSC room to maneuver on labor rates while still keeping the door open to provide compliant candidates.
FedSavvy’s Take: This was assigned a risk in terms of more government oversight, but it did not result in a loss.
Professional Employee Compensation: The Realism Trap
IESE’s second ground argued that ITSC’s compensation plan should have been rated High Risk rather than Medium, because ITSC’s salaries were unrealistically low — below incumbent and market rates — and could not attract or retain the workforce. IESE wanted the agency to benchmark against the incumbent’s compensation as the “most relevant data available.”
The agency instead benchmarked salaries against Bureau of Labor Statistics wage data and fringe against a DOD civilian fringe rate. It found ITSC’s own salaries “moderately below” the industry average and its two subcontractors 17.2 percent below — a real, acknowledged “team-wide salary deficit.” But it also found that ITSC and one subcontractor employed most of the workforce and offered strong fringe packages above the 29 percent benchmark, plus recruitment, retention, and profit-sharing incentives — enough, in the agency’s judgment, to pull the plan from high to medium risk while warranting monitoring. Note that this gets into TOTAL compensation as a part of the overall evaluation.
Did you hear that? Yep. Another nail just got hammered into the coffin.
FedSavvy’s Take: If you plan to win a compensation-realism argument, first check what the solicitation uses as the basis of realism. Someone bidding rates lower than what the incumbent pays is NOT a realism issue. Whatever yardstick the government states is the basis of realism is what is realistic.
The Final Boss Fight: Best Value Tradeoff
Here we have a classic case of a somewhat risky, acceptable and low price proposal vs. a very strong and highly rated technical proposal with low risk and a very high price.
It’s like this situation is perfect for a best value tradeoff.
The RFQ weighted non-price “significantly more” than price, which is exactly the language IESE would want. That’s a good thing, right? Not when you’re trying to win with a $61.4 million premium or 73 percent higher than an acceptable offer.
Hammer. Nail. Coffin. Ouch.
FedSavvy’s Take: Non-price being “significantly more important” than price does not mean price stops mattering. It means the agency has to decide how much of a pricing premium it wants to consider (if any). Could a pricing premium from IESE still won? We think so. 73 percent more? Nope.
Where did the incumbent go wrong?
This was not a weak proposal. By every non-cost rating IESE had a much better proposal. The problem is that IESE competed as though the objective were the highest technical score and going well above and beyond with a wildly high price. IESE built their solution as the incumbent and ITSC broke out the slingshot to win cheaply.
The most revealing moment in the whole decision is IESE’s own argument. IESE told GAO that, had the agency “clarified” its requirements, it would have offered a “significantly less skilled and experienced workforce at a much lower price.” The government is not your mother and they are under no obligation to coach you.
The FedSavvy takeaway
- “Technically superior” is a description of your proposal, not a prediction of the award. In a best-value tradeoff it is the price-to-value ratio that enables wins, not the rating column.
- Read every solicitation for what is required versus what is recommended. ITSC won this competition in how it read one word “recommended”and priced to it.
- Acceptable, with documented and monitored risk, is a winning hand when you own the price line. ITSC absorbed three risk write-ups and a medium compensation rating and never blinked.
- “Unstated criteria” and “no common basis” arguments are near-automatic losers. Divergent quotations read to GAO as different business strategies the solicitation allowed, not as agency error.
- Did the capture team study evaluation trends to know when a price premium is worth pursuing — and when it is dead on arrival? With the right analysis, that line is knowable before bid.
- Premium pricing with good value can win such as in this example, but 73 percent pricing premiums aren’t going to cut it.
How can you avoid losses using competitive intelligence to guide you?
We mine protest decisions among other sources of intelligence to help clients win and not leave money on the table. FedAgency Insight is a report we can deliver to help you analyze evaluation decisions so you can shape your solution and price it to win. Ask us about this and more competitive intelligence solutions to win your unfair share of contracts. Contact us today!
Frequently Asked Questions
Why did GAO deny IESE’s protest?
GAO found the agency’s evaluation reasonable and consistent with the solicitation. The recommended staffing matrix was a recommendation, not a requirement, so ITSC was free to deviate; the agency documented the resulting risks and still reasonably rated ITSC “acceptable”; and a $61.4 million price premium was more than enough to justify awarding to the lower-priced, technically acceptable quotation.
How can the technically superior offeror lose?
Best value is a tradeoff, not a technical beauty contest. When the price gap is large enough, an agency can reasonably decide that a merely acceptable proposal is the better value. Here IESE was rated higher on every non-price measure and still lost because its price was roughly 73 percent higher.
What is the difference between a “recommended” staffing matrix and a required one?
A recommended staffing matrix is a government suggestion of the labor mix and experience levels it expects; vendors may deviate, typically with a written narrative explaining why. A required matrix sets a floor a vendor must meet. Treating a recommendation as a requirement can force you into a higher-priced solution than the competition — exactly what happened to IESE.
Was the agency required to compare ITSC’s salaries to the incumbent’s?
No. Although the compensation subfactor resembled FAR 52.222-46 — which contemplates comparing to the incumbent workforce — that clause was not incorporated into the solicitation. The agency was free to benchmark against BLS wage data and a DOD fringe rate instead.
Can a vendor use a GSA Schedule labor category with fewer years of experience than the solicitation lists?
Yes, within reason. GAO has held that a GSA MAS labor category whose minimum experience is below the solicitation’s can still be within scope, because the years of experience are a minimum — nothing stops a vendor from providing more experienced personnel. The scope question is whether the function is covered by the schedule contract, reasonably interpreted.
What is the practical lesson for GovCon bidders?
Compete for the award, not for the rating sheet. Identify what the solicitation actually requires versus recommends, decide deliberately whether any technical premium is worth its price to this specific customer, and never let your solution drift so far above the minimums that you become the price outlier in your own competition.
