Was That RFP Wired? The Tells, the Data, and the Honest Counterargument

Almost every team that loses a public bid arrives at the same question, usually within a day of the award notice: was that RFP written for somebody else? It deserves a straight answer rather than a reassurance, and the straight answer has two halves.

Sometimes, yes. Often enough that the suspicion is reasonable rather than paranoid, and far less often than the losing bidder assumes in those first forty-eight hours. Both are true at once, and the gap between them is where most teams waste their energy.

Here is the more useful framing. A wired RFP is one whose requirements were shaped in advance around a chosen vendor, so the outcome is effectively settled before the document goes public. A benchmarked RFP is one whose requirements simply describe what the agency already buys and already receives, usually from an incumbent. "Wired" and "benchmarked" produce nearly identical documents. A specification shaped by months of quiet conversation with one vendor and a specification shaped by an agency that has run the same service with the same incumbent for eight years both read like a portrait of that incumbent. The first is a rigged process. The second is a buyer describing what it knows. You cannot reliably tell them apart from the outside, after the fact, from the document itself. What you can do is read the structural signals honestly, decide whether to spend the pursuit budget, and fix the actual problem, which is that you arrived after the requirement was already written.

Across 12,926 businesses surveyed by the European Commission in Flash Eurobarometer 557 (2025), 58% said that specifications tailored to particular companies are a widespread practice in their country's public procurement, 51% said the same of bidders being involved in designing those specifications, and 53% of conflicts of interest in the evaluation of bids. Among companies that had not bid on a public tender in three years, 17% cited criteria that seemed tailor-made and 12% said the deal seemed to be done before the call for tender. Separately, Kang and Miller (2022) found that 44% of the US federal procurement budget in fiscal year 2015 went to contracts that drew only a single bid. The suspicion is widespread and the competition is thin. Neither fact proves any individual RFP was rigged.

How common are wired RFPs?

Start with what is actually measured, because the numbers that circulate in this conversation usually are not.

The strongest survey evidence comes from the European Commission. Flash Eurobarometer 557 interviewed 12,926 businesses across the 27 EU member states in 2025. Tailor-made specifications for particular companies ranked first among suspected practices, with 58% calling it widespread; involvement of bidders in designing specifications reached 51%, and conflicts of interest in evaluation 53%. Among firms that had participated in a public tender in the previous three years, 25% believed corruption had cost them a win.

Two caveats matter, and skipping them is how this statistic gets abused. First, this is European data, describing a different procurement regime than the one most readers work in. We use it because there is no alternative: no US-wide survey asks vendors whether specifications get tailored to particular companies, and the Eurobarometer series is the largest official measurement of the phenomenon anywhere. The US evidence that does exist, the single-bid share of federal procurement dollars and Portland's published single-proposal rate, points in the same direction, so we treat the EU findings as directional evidence and label them that way rather than passing them off as a US number. Second, and more importantly, the survey measures perception, not incidence: the question asks how widespread respondents think a practice is. Belief is not nothing, since it shapes who bids and who stops bidding, but it is not a count of rigged solicitations.

The perception is also stable: the 2023 wave put tailor-made specifications at 61%, with IT and telecom highest at 67%. This is not a spike. It is the ambient temperature of public buying.

You will also encounter the practitioner figure that 40% to 80% of a procurement decision is made before proposals are submitted. It comes from capture-management training, usually attributed to Shipley-style methodology, and as far as we can determine it has never been measured against a public dataset. Treat it as folklore encoding something real (early influence matters enormously) rather than as a statistic.

What does the US procurement data actually show?

The American picture comes at the problem from a different angle: not who believes the process is rigged, but how many firms show up. In "Winning by Default: Why Is There So Little Competition in Government Procurement?", Karam Kang and Robert A. Miller report that 44% of the federal procurement budget in fiscal year 2015 was paid to contracts drawing only a single bid. Note what that measures. It is a share of dollars, not of contracts. Large awards are disproportionately represented, and the figure says nothing about how many solicitations were single-bid.

Their contract-level analysis is narrower but sharper. Among IT and telecommunications contracts from fiscal years 2004 to 2015, solicitations using a negotiated proposal or quote (the closest federal analogue to a competitive RFP) drew a median of two bids, and 45% drew exactly one. Even under full and open competition, the median was two.

This is not a federal artifact. The City of Portland, Oregon publishes a live procurement scorecard tracking the same measure, and its most recent value is 30% of competitive solicitations receiving only one proposal. The city cites Kang and Miller directly for context and frames its own 30% as the better result.

Regulators have noticed. In April 2026 the FCC adopted Order 26-30, which will require, from funding year 2028, that E-Rate service providers submit bids through a portal run by the Universal Service Administrative Company and that applicants upload their evaluation criteria, scoring worksheets, evaluator names and roles, award correspondence, and contracts. The order restates the standard that has governed the program for years: competitive bidding must be fair and open, uncompromised by improper conduct on either side, with every bidder given the same information. A regulator does not build a document repository for a problem it believes is rare.

Put the two literatures together and the picture is uncomfortable but honest. Vendors widely believe specifications get shaped. Competition is measurably thin. And here is the part most people skip: Kang and Miller conclude that corruption and administrative hurdles "appear to play very limited roles" in explaining it. Their model attributes the thinness mostly to buyers extracting informational rents and to sellers being fairly similar once project attributes are controlled for. The paper most often cited as proof the game is rigged concludes something closer to the opposite.

What are the tells?

If the data cannot settle an individual case, structural reading can sharpen the guess. Three tells come up constantly, and all three are worth taking seriously.

A short window on a long scope. A fourteen-day response window attached to a fifty-page technical scope means someone had a draft ready. Writing that scope took weeks; the timeline assumes the reader already understands it. This tell is checkable against a baseline: across 33,096 public RFPs in Settle's corpus posted between August 2024 and July 2026, the median question deadline falls just 12 days after posting. Arrive two weeks late and you have already lost the right to ask questions. That matters doubly, because those questions are how you would have found out.

Brand-name lock with no "or equal" language. A specification naming a manufacturer, model, or platform without allowing equivalents has, in effect, already named the winner or the winner's reseller. Standardization and interoperability are legitimate reasons, and a good solicitation states them in writing. When it does not, the omission is the signal.

Requirements only one firm can satisfy. Five years of documented experience on a platform the agency has only ever run with one vendor. A certification held by three companies nationally. A local office requirement where exactly one bidder has an office. Individually these can be defensible. Stacked, they describe a single company, and the stacking is what to notice.

Practitioners trade these patterns constantly. The r/GovernmentContracting threads are a reasonable field guide, and the follow-up discussion is where the argument gets interesting.

Is it actually wired, or just benchmarked?

Here is the counterargument, and it deserves more weight than losing bidders usually give it.

A contracting officer's rebuttal in that second thread runs roughly like this: when a requirement looks written around the incumbent, that is usually because the incumbent is the benchmark, not the anointed winner. The agency knows what it currently gets, at what service level, at what price, and the next solicitation describes that. The document is a portrait of the status quo, not a promise to a friend. Requiring what you already receive is not favoritism; it is the least imaginative way to write a specification, which is a different failure entirely.

That same officer's practical advice is worth more than any tell on the list: the evaluation method tells you far more about your odds than the requirements do. Lowest price technically acceptable is a fundamentally different game from best-value tradeoff. Under LPTA, a superior technical approach earns you nothing past the threshold, and if you cannot win on price you cannot win. Under best-value tradeoff, the scoring weights show exactly where the buyer will accept a premium. Read the evaluation section first. It is where the actual decision rules live.

Then the cautionary tale, from the same discussion. A thirteen-year incumbent's contract came up for recompete and drew only two bids, because everyone else read the history and assumed it was wired. The incumbent, apparently reading the same signals, phoned in a sloppy proposal. It lost to a technically superior bid that was also 12% cheaper.

That is the real cost of the cynicism. Assuming "wired" is how you lose winnable deals. Thin competition is evidence the field clears out, and a cleared field belongs to whoever is still standing in it. Both readings of the single-bid data are legitimate. Only one of them wins contracts.

What can you do about it?

Almost nothing, once the solicitation posts. That is the honest answer, and everything useful follows from accepting it.

The moment an RFP goes public, most jurisdictions impose a cone of silence: contact is restricted to the designated procurement officer, and stray outreach to the program office or an elected official can disqualify you. The relationship window closes, legally, at exactly the moment you learn the opportunity exists. Protests are slow, expensive, and rarely change an award. The question period is your only real instrument, and it lasts a median of twelve days.

So the countermove has to happen earlier. Three things we have learned from conversations with SLED sellers and public-sector buyers:

Aim for a seat at the table, not authorship of the spec. A government sales lead in a heavily commoditized category described the realistic goal of early engagement plainly: not writing the requirement, which is neither achievable nor advisable, but being present enough that the requirement does not quietly exclude you. Nobody hands you the pen. The win is that the drafter knows your category exists and does not write a clause that rules you out by accident.

Brief the program office, not procurement. A chief procurement officer at a large city put it directly: the program manager drives what gets bought. Procurement runs the process and enforces the rules, but the need originates in the operating department. Reach the program office early, explain the category, and let them route you. Approaching procurement first is polite and largely inert.

Watch the sole-source threshold. Growing an account past a dollar threshold can inadvertently trigger the open competition you were trying to avoid, converting a renewal into an RFP. Occasionally that is a good trade, but it should be a decision rather than a surprise.

None of this requires believing the system is corrupt. It requires accepting that requirements are written by people who have already talked to somebody, and deciding to be somebody they talked to.

That is a discipline problem before it is a tooling problem. The teams that solve it have a system for noticing what precedes a solicitation (a budget line approved, a contract nearing expiration, a board agenda item, a new department head with a mandate) and routing each one to the person who can act while the specification is still shapeable. Settle builds that system with public-sector sales teams, inside the workflows they already run, so the signal reaches the right owner instead of a shared inbox. If that is the gap, pre-RFP signals covers what to watch for, and the 2026 report on public RFP timing covers how little runway the posted window gives you.

Frequently asked questions

Is it illegal for a vendor to help write an RFP? It depends on the jurisdiction and the nature of the help. Responding to a formal request for information or a published market-research inquiry is a sanctioned part of procurement and is often actively encouraged. Ghost-writing a specification that then appears verbatim in the solicitation is a different matter, and can create an organizational conflict of interest that disqualifies the vendor, taints the award, or both. Programs draw the line explicitly: the FCC's E-Rate rules require that competitive bidding be fair and open, uncompromised by improper conduct on either side, with all bidders given the same information.

How can I tell if an RFP is wired before I spend money on the response? You cannot know, but you can improve the guess cheaply. Read the evaluation method first, because LPTA and best-value tradeoff imply completely different odds. Check the response window against the size of the scope. Look for brand-name requirements without "or equal" language, and for experience requirements only one firm could plausibly meet. Then submit real questions before the question deadline, which our data shows is a median of 12 days after posting. How the answers come back (substantive and public, or terse and deflecting) is often more informative than the original document.

If competition is that thin, should I bid more or bid less? More, but on fewer opportunities. A median of two bids on negotiated federal IT solicitations and a 30% single-proposal rate in a major city point the same direction: the field is thinner than it looks from outside, and much of that thinness is other vendors talking themselves out of bids. Qualify hard, pursue the ones where you can point to specific evidence of fit, and do not let a plausible-looking incumbent advantage substitute for that analysis. The thirteen-year incumbent lost because two firms refused to assume the outcome.