Insights

105 Bidders for a $1 Million Project and the Winner Didn't Buy It

Extraordinary competition. A normal price. And useful lessons about price-to-win on smaller, outcome-based contracts.

· 3 min read

When 105 companies submitted proposals to modernize the CDC's Vaccine Adverse Event Reporting System (VAERS), it was reasonable to expect an unusually aggressive winning price. In very crowded competitions, technical proposals can become difficult to distinguish, while enough bidders cluster at the low end of the price range that the award can ultimately land at a level that is difficult to execute successfully.

It looks like something different happened here.

The award to SPN Solutions was approximately $992,000 (OrangeSlices AI). An independent market analysis using Rutherford Soddy's HXG1 platform estimated the competitive price at approximately $966,000, within 2.6% of the actual award.

Even with 105 bidders, the market price for this work was not an outlier. It was normal.

The prototype changed the competitive dynamics

The RFP required bidders to provide a link to a functioning prototype as part of their response. Given that requirement, it's remarkable that 105 companies still bid it. Some of them were almost certainly vibe coded or used existing demo platforms, but even a quickly built prototype forced bidders to demonstrate a concrete approach rather than simply describe one on paper.

That requirement may also help explain why extraordinary competition did not produce an extraordinarily low award price. Bidders who believed a strong prototype could differentiate them had less reason to compete on price alone. And on the other end of the spectrum, the prototype gave CDC a practical way to screen out unrealistically low-priced offers from teams that could not demonstrate that they were capable of delivering.

Solicitations like this are part of an emerging trend toward harder technical evaluations. Prototypes, live coding challenges, technical demonstrations and similar exercises give customers a way to test whether a team can actually perform the work, rather than relying entirely on resumes, staffing plans and written technical narratives.

In this case, the prototype put a real test of technical capability between the lowest price and the award decision. In a field of 105 bidders, that distinction mattered.

Competition doesn't equal commoditization

This was not a commodity purchase. CDC was buying a modern, secure, Section 508 compliant application for a sensitive public health program. The requirement included configurable form logic, bilingual functionality, system integration and a working prototype. When the Government is buying a custom-built outcome like that, the bar is a lot higher for demonstrating capability.

Project-based procurements aren't priced the same way as large, labor-driven services contracts. On a large services contract, staffing levels and labor categories are often prescribed. If they aren't, there is usually an incumbent delivery model to benchmark against. Either way, PTW is driven by staffing, compensation, indirects and fee. On a smaller project contract like this one, there is a defined end product, no minimum staffing level and multiple valid ways to deliver.

That changes the PTW sequence. You're not starting from an old staffing model and trying to cut off some percentage of cost. Instead, you work backwards from an outcome, and then build a technically credible solution that can perform at a reasonable price.

Key takeaways for capture and proposal teams

  • More bidders don't automatically mean lower prices. With the right evaluation, a deep competitive field can reveal, not distort, the true market price.
  • Small project bids require a different PTW mindset. Start with an independent view of the market, then build a technically credible solution that can win inside that price.
  • Competition doesn't equal commoditization. Even with 105 bidders, technical differentiation mattered, and the prototype made it real.
  • There isn't one correct staffing model. Reasonable teams can arrive at very different estimates. An independent market benchmark helps you understand the likely price range, regardless of the team structure you choose.

Acknowledgment

Thank you to Capture 411 for providing the RFP used in this analysis. Capture 411 turns historical RFPs into capture intelligence. Capture 411's historical RFP library grows daily as industry contributes documents, giving contractors access to the solicitations, PWSs, evaluation criteria and other procurement intelligence they need to understand what agencies bought before the next competition begins. www.capture411.com

See algorithmic pricing analytics in action.

Contact HXG1