Should you use ghosting techniques against competitors in RFP responses?
Yes, you can use ghosting techniques in RFP responses, but only when done subtly and ethically. Ghosting means highlighting a competitor's weaknesses without naming them, framing evaluation criteria so your strengths look essential and rivals' gaps look risky. Done clumsily, it backfires and makes you look unprofessional. Done well, it shapes how evaluators score the field.
What Ghosting Actually Means in Proposals
Ghosting (sometimes called "competitive ghosting" or "casting shadows") is a capture strategy where you subtly raise doubts about competitors without ever mentioning them by name. The goal is to make evaluators question whether other vendors can deliver something you've positioned as critical.
A classic example: if you know a rival relies on offshore subcontractors, you might write, "Our delivery team is fully U.S.-based and badged on-site, eliminating the handoff delays and security gaps that plague distributed offshore models." You never named the competitor. You just made their model sound like a liability.
Most teams get this wrong by being too aggressive. Naming competitors directly, or making claims you can't back up, reads as desperate and can violate procurement rules.
When Ghosting Works
Ghosting is effective when you have:
- Accurate competitive intelligence. You actually know a rival's approach, pricing model, or staffing weakness.
- A genuine discriminator. You can deliver something the competitor can't, and it matters to the buyer.
- A way to tie it to evaluation criteria. The weakness you're ghosting should map to something the RFP scores.
The technique pairs well with strong win themes and discriminators in your executive summary, where you set the frame before evaluators read detailed sections.
Common ghosting angles
| Competitor weakness | Ghosting language (no names) |
|---|---|
| Offshore delivery | "On-shore team with no time-zone handoffs" |
| Proprietary lock-in | "Open standards, no vendor lock-in, full data portability" |
| Small bench / single point of failure | "Redundant staffing with cross-trained backups for every role" |
| Slow legacy platform | "Cloud-native architecture deployed in weeks, not quarters" |
| New to the market | "15 years delivering this exact scope in your sector" |
When Ghosting Backfires
The practice carries real downside risk. Avoid it when:
- Your intel is shaky. If you ghost a weakness the competitor doesn't actually have, an informed evaluator notices and you lose credibility.
- The RFP prohibits comparative claims. Many government and enterprise procurements explicitly ban disparaging other bidders. Read the instructions to offerors.
- You name names. Direct attacks almost always hurt you. Evaluators sympathize with the underdog and see you as unprofessional.
- It overshadows your own value. If your proposal is more about tearing down rivals than proving your fit, you've lost the plot.
The U.S. federal procurement community discusses these tactics openly in capture-management circles, and resources like the APMP body of knowledge treat ghosting as a legitimate but carefully bounded strategy.
How to Ghost Ethically and Effectively
1. Make it positive-first
Lead with your strength, then let the contrast do the work. "Our 24/7 on-shore support desk resolves 92% of tickets on first contact" implies others can't, without saying so.
2. Tie it to risk the buyer feels
Evaluators care about delivery risk, cost overruns, and security. Frame competitor gaps as risks to their outcomes, not as flaws in their business.
3. Use evaluation criteria as your map
If the RFP weights "implementation speed" at 30%, ghost slow competitors there. Aligning ghosting with scored criteria multiplies its impact. Clean, scannable structure helps; follow proposal writing conventions that improve readability for evaluators so your discriminators don't get buried.
4. Keep claims defensible
Every implied contrast should survive a fact-check. If you claim "no hidden integration fees," your pricing must actually show that.
Should You Even Be in This Bid?
Ghosting only matters if you have a real shot. If you're ghosting heavily because you can't compete on merit, that's a signal. Run a disciplined go/no-go process before deciding to bid on an RFP instead of writing a defensive proposal you'll likely lose.
Ghosting Across Bid Types
The technique fits formal RFPs better than transactional requests. Understanding the difference between an RFP and an RFQ in procurement helps here: an RFQ is price-driven with little room for narrative, so ghosting has nowhere to live. RFPs reward differentiation, which is exactly where shaping the evaluation pays off.
Key Takeaways
- Yes, ghosting is a legitimate tactic when used subtly and backed by real competitive intelligence.
- Never name competitors or make claims you can't defend.
- Anchor ghosting to scored evaluation criteria so the contrast affects your score.
- Lead with your strength; let the implied contrast do the heavy lifting.
- Check procurement rules first, since many RFPs prohibit comparative or disparaging language.
- If you're ghosting to mask a weak bid, reconsider bidding at all.
Used with discipline, ghosting shapes how evaluators read the entire field in your favor. Used carelessly, it hands the win to the competitor you were trying to undercut.