You read an RFP and something feels off. The requirements are oddly specific. The timeline is impossibly short. The evaluation factors seem written for one particular company. You may be looking at a wired RFP — a solicitation that has been shaped, deliberately or carelessly, so that only one bidder can realistically win it. Wired RFPs are one of the most frustrating parts of federal contracting for small businesses, because they turn a fair competition into a formality. This guide explains what a wired RFP is, the eight red flags that give it away, and what you can actually do about it — because sometimes the right move is still to bid, and sometimes it is to walk away and use the opportunity as intelligence for the next round.
What Is a Wired RFP?
A wired RFP is a solicitation whose requirements, timeline, or evaluation criteria have been written in a way that favours one specific vendor — usually the incumbent contractor. The wiring is not always deliberate corruption. Often it happens innocently: the government team writes the requirements based on how the current contractor does the work, because that is the only way they have seen it done. The result is the same either way. The statement of work describes the incumbent’s exact processes, the staffing plan mirrors the incumbent’s team, and the evaluation factors reward the incumbent’s unique experience. A newcomer can still bid, but they are bidding against a specification that was built from their competitor’s playbook. Before spending proposal hours, learn to recognise the pattern. If you are new to reading solicitations, our guide on how to read an RFP will help you find the sections where wiring usually hides.
8 Red Flags of a Wired RFP
1. Overly Specific Requirements
The statement of work demands a very specific tool, process, or methodology that has nothing to do with the actual outcome. For example, the RFP requires “five years of experience with the XYZ-4000 ticketing platform, version 7.2” when any modern ticketing platform would do the job. Or it specifies a proprietary workflow that only one vendor uses. Genuine requirements describe outcomes — what must be delivered and to what standard. Wired requirements describe a particular vendor’s way of working, dressed up as a requirement. When you see specificity that does not connect to the mission, be suspicious.
2. An Impossible Timeline
The RFP gives bidders ten days to respond to a complex services requirement, or demands that the winning contractor start work five days after award with a fully cleared, fully badged team. A timeline that only the incumbent could meet is a classic sign of wiring. The incumbent already has staff in place, security clearances, and facility access; everyone else would need weeks to mobilise. Short timelines are not always wired — some requirements genuinely are urgent — but a compressed schedule combined with other red flags on this list is a strong signal.
3. Brand-Name Specifications
The RFP names a specific brand, product, or software and says “or equal” — but then describes the “equal” in terms that only the named brand can meet. Federal rules generally require brand-name justifications, and a contracting officer is supposed to document why only that brand will work. In practice, brand-name specs that survive into a competitive solicitation often point to a customer who has already decided what they want and is going through the motions of a competition. If the named brand is the incumbent’s product, that is a near-certain sign of a wired RFP.
4. The Incumbent’s Exact Staffing
The RFP requires a team structure that mirrors the incumbent’s organisation chart: the same number of people, the same labour categories, the same certifications, even the same reporting lines. Requirements should be based on the work, not on how one company happens to be organised. When the staffing table reads like a copy of the incumbent’s proposal, the solicitation was probably built from that proposal. Check the incumbent’s footprint first using our guide to finding incumbent contractors, so you know whose structure you are looking at.
5. Evaluation Factors That Match One Firm
Evaluation factors are supposed to measure what matters for the mission. In a wired RFP, they measure what one firm happens to have. Watch for factors like “demonstrated experience supporting Agency X’s specific legacy system” where that experience can only belong to the incumbent, or a heavy weight on a past-performance reference from the very same agency. Also watch for oddly weighted factors: technical approach counts for almost nothing while a niche certification the incumbent holds counts for a lot. Read the evaluation section carefully — it tells you who the government is really looking for.
6. No Industry Day and No Real Engagement
Healthy competitions usually include an industry day, a draft RFP, or at least a Q&A period where the government engages with prospective bidders. A wired RFP often skips all of that. There is no industry day, no draft, and the solicitation appears with little warning. The government team has no incentive to talk to new vendors because they already know who will win. The absence of engagement is not proof on its own — small, simple buys often skip industry days — but for a large services contract, silence is a warning sign.
7. Evasive or Empty Q&A Answers
When you submit questions, the answers come back vague, dismissive, or not at all. “See the RFP” is the classic non-answer. Or the government answers only the easy questions and ignores the ones that would expose the wiring — for example, questions about why a specific tool is required, or whether an equivalent approach would be accepted. A contracting team running a genuine competition wants good questions, because good questions produce better proposals. A team running a wired competition wants the questions to go away.
8. A Recompete with the Same Scope, Same Everything
The RFP is a recompete of an existing contract, and nothing has changed: same scope, same staffing, same deliverables, same performance standards. That is not automatically wiring — sometimes the requirement genuinely has not changed. But when a recompete is a carbon copy of the incumbent’s contract, with no lessons learned, no updated requirements, and no opening for a better approach, it usually means the customer is happy with the incumbent and wrote the solicitation to keep them. Combined with a short timeline and incumbent-matched evaluation factors, this is the clearest pattern of all.
What to Do When You Spot a Wired RFP
Option 1: Bid Anyway as a Challenger
Sometimes bidding is still worth it. If the wiring is soft — the result of habit rather than intent — a strong, well-priced proposal can win, especially if the incumbent has performance problems or the customer is under pressure to show real competition. Bid as a challenger: highlight your differences explicitly, show how your approach delivers the same outcomes better or cheaper, and use the proposal to educate the evaluators about alternatives they may not have considered. But go in with your eyes open, and run the numbers through your bid no-bid decision framework first. A challenger bid is a calculated risk, not a lottery ticket.
Option 2: Ask Questions — on the Record
Submit written questions through the official channel, and make them specific. Ask why a particular tool or certification is required, whether an equivalent would be accepted, and how the government will evaluate approaches that differ from the incumbent’s. Written questions create a record. If the government amends the RFP in response, the wiring may loosen. If the answers are evasive, you have documented evidence of the problem — and that evidence is useful for the next two options.
Option 3: Protest — Carefully
If the solicitation contains terms that are genuinely unduly restrictive — requirements that exclude capable competitors without a legitimate need — you can file a pre-award protest with the Government Accountability Office or the agency. This is a serious step with real costs and deadlines, and it should not be taken lightly. A protest is not a complaint; it is a legal argument that the solicitation violates competition rules. Get advice from a government contracts attorney before filing, and be aware that protesting can affect your relationship with that agency. But protests exist for a reason, and agencies do amend solicitations when a protest shows the terms are indefensible.
Option 4: Walk Away — and Use It as Intel
Often the smartest move is to walk away and treat the RFP as free intelligence. You now know the customer’s requirements, the incumbent’s approach, the evaluation factors, and the price range. File all of it. Track when the contract expires — that is your next window. Build the capability, the past performance, or the partnership that would have made you competitive, and start engaging with the customer now, years before the next recompete. Many small firms win a contract on the second cycle precisely because they used the first, wired RFP as a study guide instead of a proposal exercise. That is not losing; that is preparing.
Related Guides
Wired RFP: Walk Away or Bid Like a Challenger
A wired RFP is not a reason to stop reading solicitations — it is a reason to read them harder. Use the eight flags as a checklist on every opportunity you seriously consider, and run the bid/no-bid decision before you spend a single proposal hour. A wired RFP you recognise early costs you nothing; one you discover after the Gold Team review costs you a week. The discipline is the same either way: decide deliberately, and never let momentum choose for you.
Keep the tools close: a wired RFP is easier to judge against our bid/no-bid decision framework and the guide to reading an RFP, and FAR Part 15 sets the rules on questions, amendments and late proposals. A wired RFP is a signal, not a verdict — learn to read it, and every competition gets easier to judge.
2 Responses