You're not bidding. You're donating.
Most response teams don't have a bandwidth problem. They have a qualification problem wearing a bandwidth costume.
Five forty on a Thursday. The RFP hit the shared inbox around four — a couple of hundred questions, a portal login, a due date mid-week. The calendar invite goes out before anyone has read past the cover page. The title is some version of RFP — do we have bandwidth?
Six people join. Somebody shares the requirements doc and scrolls. Somebody counts the sections out loud. Then the meeting does what that meeting always does. It becomes a capacity conversation. Who has hours. What slips. Whether the solutions lead can give up Tuesday and Wednesday.
You’ve been in that meeting. I’ve run it, sat in it, and cleaned up after it — in B2B SaaS and life sciences since 2011, running Deal Desk and Sales Operations since 2018, across more than a thousand proposals.
And in most versions of it, nobody asks the first question. Should we be answering this at all?
Start with the arithmetic
The numbers make the case better than the argument does.
Source: Loopio, 2026
Put those together.
Now the question that actually matters: how many of those ninety were knowable at intake?
I have run retrospective reviews of lost RFPs at three different organisations — pulling a year of losses and reading them back against what was known on the day the RFP arrived. My estimate from that work is at least a quarter. That is my read, not a research finding, and I would rather state the basis than dress it up: three retrospectives, across three companies, over a career in this work.
A quarter of ninety is more than twenty serious responses a year that a governed decision would have declined.
Those are not losses. They are volunteer work.
The bandwidth problem is wearing a costume
Here’s the reframe: a bandwidth problem is usually a qualification problem wearing a bandwidth costume.
The symptom is real. The team is genuinely underwater. Nobody is exaggerating the workload. The diagnosis is where it goes sideways — underwater gets read as not enough people, so the ask becomes headcount. A writer. A contractor. A platform with a bigger library.
More capacity gets you more responses. It does not get you better-chosen ones. Add a person to a team that says yes to everything and you have bought more losses, delivered faster, at higher cost.
AI has sharpened this rather than softening it. 79% of proposal teams now use AI and 69% own dedicated response software (Loopio, 2026) — and average win rates still sit near 45%. When the cost of producing an answer falls, the volume of answering rises, and so does the number of pursuits nobody stopped to justify. Cheap answers make a qualification problem bigger.
Why the bill never arrives
Every organisation I have worked in could tell you what a lost deal cost in revenue. Almost none could tell you what a bad pursuit cost, because that cost never takes the shape of a number.
There is no line item for the four days a solutions architect spent on a requirements matrix for a buyer who was never going to switch. None for the security lead pulled off the roadmap to answer forty questions you have answered forty times. None for the winnable deal down the hall that got the leftovers, closed a quarter late, and was coded “long sales cycle.”
The loss reviews don’t help either. Losses get coded price, timing, incumbent, no decision. I have never seen a field for we should never have bid. So the pattern stays unmeasured, which means it stays unmanaged.
And the deepest part of the trap: bad pursuits show up as effort. Effort looks like commitment. Teams get praised for the all-nighter on the response that never had a path. Nobody gets praised for the response they didn’t write.
Seven questions, in two groups
A real pursuit decision is not a gut read on whether the logo would look good on the site. It weighs seven things, honestly, out loud, in front of people who can disagree.
Can we win it?
Fit
Not could we serve them, but do we win here. Name the last three deals you won that look like this one. If you can’t, you’re not qualified. You’re hopeful.
Access
A named champion who will act, a route to whoever signs, and permission to ask questions before the deadline. If your only contact is the address on the cover page, that isn’t an obstacle to work around. That’s an answer.
Timing
Is something on their side forcing a decision, owned by someone measured on the outcome? Or are you the third quote that makes an incumbent’s renewal look competitive?
Incumbency
If someone is already inside, can you name the specific failure the buyer will say out loud, unprompted? “We’re better” is a hope with a slide deck.
Do we want it?
Cost to compete
What a serious response costs in senior hours, and whose hours they are. Every yes here is a no somewhere else, and the somewhere else is often a deal you’d have won.
Complexity
What delivering this actually takes.
Growth potential
Is this a ceiling or a floor?
Most published frameworks stop at the first group. The second group is where an operator’s gate separates from a template, so it’s worth being concrete about both.
Complexity, concretely
The clearest example is the over-complex bid from the largest, most process-heavy buyers — in my world, top-tier pharma.
They are extremely stringent on requirements and on procedure. They mandate their own systems for intake and processing. And the scope they put out frequently demands resourcing that a smaller or mid-market vendor simply cannot field, whatever the proposal says.
These are also the most desirable logos in the category, which is exactly why so many vendors respond. Realistically, very few of the organisations submitting for that kind of project have a genuine path to winning it — and the ones who don’t have spent senior weeks finding that out.
Complexity is not “this will be hard.” It’s a question about whether the delivery you would be signing up for is one you can actually staff. A deal that wins and then costs double to deliver is a loss with a longer settlement period.
Growth potential, concretely
The variables here are strategic rather than mechanical, and they’re worth naming because almost no bid/no-bid process weighs them at all.
In my experience it usually comes down to a synergy of two things: leadership on both sides genuinely wanting to work together, and a real operational gap or complementarity where each side stands to gain from the other. When those two line up, a smaller initial deal can be worth considerably more than a larger one that terminates.
The hard part is that identifying those variables is the easy half. The other half is patience — those relationships often take a longer arc than a standard cycle, and weathering that stretch is more than some leaders will persevere through. Which is itself worth knowing at intake, because a growth bet nobody will fund past two quarters is not a growth bet.
What a governed go/no-go actually is
I built a Deal Desk from scratch that governed a pipeline north of $25M. The highest-leverage thing in it was never the approval matrix. It was the gate at the front — the moment somebody with a name decided whether a deal got the team’s hours at all.
Four elements.
One owner
A named person who can say no and have it hold. Not a committee — committees don’t say no, they say let’s see what we can do, which is yes wearing a lab coat.
One moment
Before kickoff. Before the outline. Before anyone “just starts pulling answers to get a head start.” Once response work begins, momentum has made the decision and no meeting reverses it.
Consistent criteria
The same seven questions every time, so the answer isn’t a function of who opened the email or how the quarter is tracking. A deal you’d decline in April shouldn’t get a yes in September because the number is short.
On the record
One page. What you believed about each of the seven, at intake, in writing. Six months later you can read what you believed and check it against what happened. That’s how a team gets better at choosing rather than just faster at answering — and it is the only way you ever find out what your own version of that quarter-of-ninety number really is.
An hour of meeting and one page of writing. It buys back weeks.
Now the fair objection: what if we no-bid something we’d have won? You will. Count it honestly. But weigh the two errors properly. A regretted no-bid is one deal, and it’s reversible — you can call the buyer, ask what would have to be true, and re-enter if the answer is real. A policy of yes-to-everything isn’t one deal. It’s every quarter, permanently, with your best people paying for it.
The pickiest team wins
The teams that respond best are not the fastest. They’re the pickiest.
Speed is what you get after you’ve stopped spending senior hours on deals that were never yours — it isn’t the thing you buy your way to first.
The work of winning a deal should accumulate. Every strong answer, every business case, every hard-won position should be worth more the next time it’s needed. It cannot accumulate if you spend it on pursuits nobody chose on purpose.
Could you produce, today, a written reason you chose to pursue your last five deals?
Rob Roberts is the founder of Widenine Solutions. In B2B SaaS and life sciences since 2011, running Deal Desk and Sales Operations since 2018 — including a Deal Desk built from scratch governing a $25M+ pipeline, and a 2,000+ vetted Q&A library behind 5,000+ responses built and audited.