Every GovCon BD lead knows the feeling. You spend three weeks pulling together a $30K proposal, the award goes to the same vendor who had the contract before, and you realize somewhere around page 47 that this thing was never really open.
You weren't losing a fair fight. You were filling out paperwork.
The problem isn't that wired solicitations exist — incumbents have real advantages and agencies like continuity. The problem is that most contractors can't identify them early enough to walk away.
What "Wired" Actually Means
A wired RFP isn't necessarily illegal. It's a solicitation where the evaluation criteria, SOW language, past performance requirements, or technical specifications were crafted — intentionally or not — to favor a specific offeror.
The incumbent already knows what the agency wants. They may have helped write the PWS. Their past performance is a perfect match because they're the ones who performed the work. Their incumbent knowledge isn't a leg up — it's a structural wall.
You can write a perfect proposal and still lose by 12 points on "understanding of requirements."
The 7 Signals We Track
These signals are additive. One flag is a yellow light. Three or more on the same procurement is a red light.
1. Short solicitation windows
A 14-day response window on a complex IT services solicitation doesn't leave room for a thorough proposal — unless you already know what you're writing. Incumbents don't need 30 days. You do.
What to look for: Response windows under 21 days for IDIQ task orders, under 30 days for full-and-open competitions with complex technical requirements.
2. Hyper-specific past performance requirements
"Offeror must demonstrate experience with [very specific system] version 4.2 or later deployed in a [very specific agency environment]." That's not a requirement — it's a description of the incumbent's resume.
Real competition has performance standards, not performance descriptions.
3. SOW language that mirrors incumbent capability
Pull the incumbent's capability statement and compare it to the PWS. If the language is suspiciously close — same terminology, same phasing approach, same acronyms — someone briefed the agency on what they could deliver, and the agency wrote it down.
4. Single-agency past performance at unusually high thresholds
A NAICS 541511 (Custom Computer Programming) solicitation requiring 3 contracts each worth $5M+ with the same agency isn't unusual on its own. But if only the incumbent can hit that exact threshold at that exact agency, it's a filter, not a standard.
5. Evaluation criteria weighted toward "understanding"
Technical approach is easy to evaluate fairly. "Understanding of the agency's mission and current environment" is not. High weighting on understanding factors benefits the contractor who's been inside the building.
6. Pre-solicitation activity with the incumbent
Check USASpending. If the incumbent received a bridge contract, a J&A sole-source, or a series of T&M orders in the 6 months before this RFP dropped, the agency is telling you something: they already know who they want to work with next.
7. No industry day, or an industry day without questions
Agencies that want real competition hold industry days and answer questions substantively. Agencies going through the motions hold perfunctory events and say "see the solicitation" to every question.
Always pull the Q&A log from SAM.gov. If there are no questions, or if every question got a non-answer, that's a signal.
What To Do When You See the Flags
One or two flags: Proceed with caution. Consider a lighter-touch proposal approach. Don't commit your A-team.
Three or four flags: Have an honest bid/no-bid meeting. Model the probability. If your win rate on this vehicle with this customer is under 20%, you need a strong reason to continue.
Five or more flags: Walk away. Write a loss analysis in your CRM so you don't make the same call next cycle. Flag the incumbent for relationship-building if this is a customer you want long-term.
Why We Built RFP Recon
We kept watching smart contractors chase the wrong solicitations. Not because they were naive — because the signals were buried in SAM.gov PDFs, USASpending data, and FPDS reports that no one has time to correlate manually.
RFP Recon pulls those signals together before you commit to a bid decision. Incumbent identification, award history, bridge contract patterns, Q&A analysis — in a format that takes 10 minutes to review, not 10 hours.
We started using bid intelligence tools last year. The first procurement we passed on based on the analysis would have cost us $40K in B&P and taken 6 weeks of our BD team's time. That's 6 weeks we put into a solicitation we actually won.
— A GovCon VP of Business Development
If you're evaluating 10 solicitations a month and bidding 6 of them, you should be bidding 3 and winning more of them.
That's the math we're trying to fix.