Why do we keep losing RFPs we should be winning?

The scene I'm in this week

Earlier this week I got a forwarded email from the CEO of a $28M cybersecurity company. Subject line: "RFP debrief." His team had just come in second on a deal they'd spent eleven weeks answering. Two hundred and six requirement rows. A demo for a committee of nine. A pricing exercise with three scenarios. Second place.

He wanted me to look at the response, convinced the writing had let them down. The response was fine. Better than fine... thorough, accurate, professionally produced. His team had answered every row honestly and scored well on most of them. And they still lost to a competitor he swears is two years behind him on the actual technology.

Then I read the RFP itself, and there it was, in row 47. A requirement for a specific architecture approach, phrased in a very particular way. I pasted the phrase into a search bar. Word for word, it was the headline on the winning competitor's product page.

That RFP arrived pre-answered. The buyer didn't sit down one morning and independently invent 206 rows of requirements. Somebody taught them what to want. The document was the receipt for six months of teaching, and my client's first contact with the deal was the receipt.

The loss happened before the document existed. Week eleven just delivered the news.

Naming what's actually broken: the Borrowed Scorecard

Here's the pattern I want you to see. An RFP is a scorecard, and every scorecard has an author. When you didn't help write it, somebody else did... usually the incumbent, or the competitor who's been in the account for months, or a consultant who built the requirements list by reading vendor websites. Whoever wrote the scorecard wins the game, because they wrote the rows they win.

I call this the Borrowed Scorecard. You're playing an away game on a field somebody else drew, grading yourself against criteria built from somebody else's story, and doing it enthusiastically because the deal is big and the document looks official.

And here's the uncomfortable half of the diagnosis. Solution-Centric Marketing set you up for this. When your homepage is a feature list and your deck is a feature list, you've taught the market to see you as a vendor of features, and features are exactly what an RFP knows how to compare. You trained buyers to procure you like a commodity, then felt blindsided when the procurement document treated you like one. I wrote about the deeper version of this dynamic in Why do competitors with weaker products win more deals than us?. This is just truth.

Why this is worse now than ever

RFP responses used to be expensive to produce. That expense was a filter. A buyer issuing an RFP five years ago got four serious responses and could actually read them.

AI took the cost of a polished response to zero. Now every vendor within shouting distance of the category fires back eighty flawless pages, and every response sounds equally confident and equally beige. The procurement team can't genuinely read twelve of those, so they do the obvious thing: they feed the stack to an AI and score the summaries. Your carefully crafted differentiation, the kind that lives in adjectives and paragraph fourteen, dies in the summarization pass.

“Executives and decision-makers are drowning in AI-generated noise, developing a subconscious filter for generic outreach.”

... LinkedIn B2B research via Incremys, 2026

It gets one layer worse. The evaluators use AI on their side of the table too... somebody on that committee typed your category into ChatGPT before the scoring meeting. If the machine describes you the way your response does, as one option among twelve with a similar feature set, you got flattened twice. Brand is the new backlink... in AI search, a clear and consistent brand narrative is what gets a company cited, the way backlinks once drove search rankings. The narrative reaches into the scoring meeting whether you're in the room or not. If buyers can't hold onto what makes you different, neither can the machine briefing them, which is the same disease I diagnosed in Why don't buyers remember what makes us different?.

The diagnostic: run this on the RFP sitting on your desk

Three tests. Run them today, before your team sinks another eleven weeks into a scorecard you can't win.

1. 1The Authorship Test. Read the requirements and highlight every phrase you could trace to a specific competitor's website or datasheet. Actually paste the odd-sounding ones into a search bar. If the spec reads like somebody else's marketing, it is somebody else's marketing, and you're being invited as column fodder to make their procurement look competitive.
2. 2The Cold-Drop Count. Pull your last ten RFPs and split them into two piles: deals where you'd shaped the conversation before the document dropped, and deals that arrived cold in the inbox. Calculate your win rate for each pile separately. Every team I've run this with finds the same thing... the cold pile is where win rates go to die, and it's usually the bigger pile.
3. 3The Missing-Row Test. Open your last response. Did you add anything to the scorecard? A named cost the RFP never asks about, a risk the requirements ignore, a criterion only you can win? If your response only fills in the rows you were given, you accepted somebody else's story of the problem, and the best you can come in is a polite second.

What I see across 200+ B2B companies

PitchKitchen builds Magnetic Messaging Frameworks for founder-led B2B companies in the $5M-$75M range, which means I've now watched a couple hundred sales teams handle RFPs, and the pattern barely varies. Nine in ten losing responses read like the fifth-best datasheet in the stack, every one of them accurate and impossible to tell apart from the next. The team behind each one believed volume was the strategy: answer more RFPs, win more deals. The math runs the other way. The teams that win more are answering fewer, because they qualify on authorship... shape it or skip it.

Buyers have built filters against sameness, and the filters keep getting sharper. At B2BMX 2026, DemandView CEO Chris Rack shared that 45% of buyers are less likely to consider a vendor when the outreach feels synthetic. That instinct doesn't switch off when the document is a formal RFP response. A committee reading twelve AI-polished submissions can smell the sameness, and a scorecard resolves sameness the only way it knows how: price.

The winners do something that looks reckless from the outside. They challenge the scorecard: the response opens by renaming the problem, page one adds the missing row, and every so often the answer is a polite decline plus a one-page letter about what the requirements miss. Buyers remember the vendor who argued with the test. It reads like conviction, because it is. The same posture wins against size, which I covered in How do we position against a much bigger competitor?.

A real example

A cybersecurity company in the low twenties of millions, PE-backed, selling into mid-market financial services. When we started, RFPs made up a quarter of their pipeline and their cold-RFP win rate sat around one in eight. The sales team was proud of their response machine... templates, a content library, a full-time proposal manager. The best-oiled machine in the building was producing polished second places.

We rebuilt the story first. The Magnetic Messaging Framework (MMF) gave them a named villain (the audit-season fire drill every compliance team had accepted as normal), an old-way / new-way contrast, and one criterion they win outright: time-to-evidence during a regulator request. Then the RFP playbook changed. Cold RFPs got the Authorship Test, and the ones that failed it got a decline letter with the company's point of view attached. The ones they answered opened with the missing row, in the CFO's language, on page one.

Two quarters later they were answering half as many RFPs and winning one in three. Same product and the same proposal manager. The only new thing in the building was the author.

What this means for you

Here's the move. Your leverage sits upstream of the document, in the months of conversations and content that teach a market what to want. The scorecard is downstream of the story. When you own the story, the next RFP arrives with your language already in the rows. When somebody else owns it, you're bidding to be their column fodder. Does that make sense?

1. 1Run the Authorship Test on whatever RFP is open on your desk right now. If it fails, have the honest internal conversation about whether eleven weeks of response work is worth it, and what a decline-with-a-point-of-view letter would say instead.
2. 2Write your missing row. One criterion only you win, stated in business language the CFO recognizes, with the cost of ignoring it attached. Put it on page one of every response, before the compliance matrix starts.
3. 3Start the authorship work. Document the story you'd want every scorecard written from: who it's for, the villain you're fighting, the old-way / new-way contrast, the promised-land outcome. Publish it everywhere your buyers and their AI engines look, so the next requirements doc gets drafted with your words in it.

That documented story is the work I do all day. I'm Greg Rosner, founder of PitchKitchen and author of Story Craft for Disruptors, and the MMF is the strategic narrative system I built across more than 300 founder engagements: category design, villain framing, an old-way / new-way contrast, and a promised-land outcome, written down so every rep, every proposal, and every AI engine tells the same story. PitchKitchen fixes broken marketing messages and underperforming websites for CEOs whose sales are stalling because their message isn't doing the work. Why it matters here: the framework is how you become the author. Companies with a documented, consistently told story get their language into requirement docs before the RFP exists. Companies without one keep renting other people's scorecards. An RFP you didn't help shape is a scorecard somebody else wrote, and filling it out neatly just certifies you as the second-best fit for their story.