Written to Lose: The Quiet Arithmetic of RFP Pursuits That Were Over Before They Began

A mid-sized enterprise software firm outside Dallas recently conducted an internal audit of its proposal activity. The findings were sobering: over eighteen months, the sales organization devoted an estimated 4,200 hours to responding to requests for proposals. Total revenue attributable to those efforts? Three contracts, none of which covered the fully loaded cost of pursuing them.

This scenario repeats across American enterprises of every size, from healthcare vendors in the Midwest to federal contractors in the Beltway. The proposal grind has become a fixed ritual — one that consumes talent, distorts pipeline forecasts, and quietly erodes margins — while the actual win rates behind it remain stubbornly, embarrassingly low.

The Hidden Ledger Behind Every Submission

Most organizations measure RFP activity by output: proposals submitted, pipeline value logged, opportunities "covered." Almost none measure the true unit economics of a pursuit. When those costs are tallied — subject-matter expert time pulled from delivery work, executive hours spent on review calls, graphic design, legal review, and the opportunity cost of deals left unworked — a single enterprise-grade response can easily represent $15,000 to $40,000 in real expense.

Multiply that across dozens of annual pursuits and the arithmetic turns ugly. A team responding to 60 RFPs per year at a 7 percent win rate is, in effect, running a division whose primary product is rejection. The question is not whether the team works hard. It is whether the work is pointed at winnable terrain.

Reading the Signals of a Predetermined Process

Experienced procurement professionals will tell you, off the record, that a substantial share of RFPs are issued for reasons that have nothing to do with selecting a new vendor. Sometimes a competitive bid is legally required even though an incumbent is the presumptive winner. Sometimes an RFP exists to generate market intelligence — pricing data, feature benchmarks, solution architecture — that will be handed to a favored supplier. Sometimes it is issued to satisfy a stakeholder who needs the appearance of diligence.

The signals are usually visible to anyone willing to look:

• Specification fingerprints. When the requirements language mirrors a competitor's product documentation, or when the technical specifications match the incumbent's capabilities with suspicious precision, the document was likely written by or for someone specific.
• Timeline compression. A two-week response window on a complex enterprise scope suggests the evaluation committee already knows what it wants and is simply fulfilling a procedural obligation.
• The disappearing sponsor. If your outreach to the issuing organization yields no substantive answers — no discovery call, no access to the actual users, no clarity on evaluation criteria — you are not being evaluated. You are being collected.
• Asymmetric incumbency. When the incumbent helped draft the scope, holds multi-year relationships with every evaluator, and the budget was set around their pricing, you are decorating a decision already made.
• Budget opacity. Organizations serious about buying share what they can spend. Organizations running a paper exercise tend to be vague, evasive, or silent on the subject.

None of these signals alone is disqualifying. Two or three in combination, however, should trigger a hard conversation about whether to respond at all.

Building a Pursuit Discipline That Actually Disciplines

The fix is structural, not motivational. Enterprises that consistently outperform in competitive procurement share a common trait: they treat the bid/no-bid decision with the same rigor as a capital allocation decision, because that is precisely what it is.

A workable framework starts with a scoring gate. Before any hours are committed, the pursuit is scored against a small set of weighted criteria: Does an existing relationship exist with the buyer? Did we shape or see the requirements before publication? Is our differentiation material to the stated evaluation criteria? Can we articulate why the buyer would risk changing from the status quo? Pursuits falling below a threshold are declined — in writing, with the rationale documented so patterns emerge over time.

Second, enterprises should institute a capture-ratio review each quarter. If the win rate on qualified pursuits is materially higher than on unqualified ones — and it always is — the data itself becomes the internal argument for saying no more often. Sales leaders who can show that declining twenty marginal pursuits freed capacity for ten well-shaped ones, yielding more revenue at lower cost, will find the cultural resistance to walking away dissolves quickly.

Third, redirect the surplus capacity deliberately. The hours recovered from declined pursuits should flow toward pre-RFP engagement: building relationships with procurement teams before solicitations drop, participating in industry working groups where requirements are discussed, and investing in the account development that shapes future requirements rather than reacting to them. Deals are won in the eighteen months before an RFP is published far more often than in the three weeks after.

The Cultural Hurdle: Why Teams Keep Chasing

If the logic is so clear, why do capable organizations keep responding to unwinnable solicitations? The answers are human. Quota pressure makes any pipeline look better than an empty one. Salespeople fear that declining a pursuit will be read as a lack of effort. And somewhere in most corporate cultures lives the legend of the long-shot bid that shocked everyone and won — a story that gets retold at every kickoff, while the hundreds of quiet losses that funded it go unmentioned.

Leadership must address this directly. Walking away from a bad pursuit should be framed and rewarded as a strategic act, not a failure of effort. The metric that matters is not proposals submitted; it is revenue per hour of pursuit investment. When that number is visible at the leadership level, behavior follows.

Recalibrating the Effort

The RFP will remain a fixture of American enterprise commerce, and rightly so — structured procurement serves a legitimate purpose, and some solicitations are genuinely open competitions worth winning. The problem is not the instrument; it is the undisciplined way organizations respond to it.

Enterprises that audit their pursuit economics, read the signals of a fixed process honestly, and reallocate proposal capacity toward shaping future opportunities will find something counterintuitive: they win more by responding less. In a market where talent is scarce and margins are scrutinized, that reallocation may be among the highest-return operational decisions a sales leadership team makes this year.