There is a pressure in pre-sales that nobody talks about openly: the pressure to always bid.
It comes from everywhere. Sales wants the pipeline number. Leadership wants market presence. The client wants you to respond. And somewhere in the middle, your team — already stretched — starts building a response to an RFP they have no real chance of winning.
I’ve been in those rooms. I’ve led those late nights. And I’ve learned — sometimes the hardest, most strategic thing you can do is put down the pen and say: not this one.
Here are five signals that should make you seriously consider walking away.
1. You Found Out About It on Release Day
If the first time you heard about this opportunity was when the RFP landed in your inbox, you are almost certainly behind.
RFPs that come out of nowhere — where you have no prior relationship, no understanding of the client’s internal politics, and no insight into what shaped the requirements — are often wired for someone else. The client has been talking to your competitor for months. The spec was written with a particular solution in mind. You are there to make the process look competitive.
That doesn’t mean you should never respond to cold RFPs. But go in with eyes open. If you can’t identify a single person inside the client organisation who will advocate for you, the odds are not in your favour.
2. The Requirements Are Suspiciously Specific
Read the requirements carefully. If the technical specifications describe a product feature set that only one or two vendors in the market can match — and you’re not one of them — that’s a signal.
Wired RFPs often reveal themselves in the granularity of requirements. When a document specifies version numbers, integration patterns, or certification levels that happen to match a specific competitor’s current offering, it’s rarely a coincidence.
You can try to position around it. You can write exceptions and propose alternatives. But understand what you’re working against before you commit two weeks of effort.
3. The Budget Doesn’t Match the Ambition
When the indicative budget (if stated) or the market rate for the scope described is significantly below what it would reasonably cost to deliver — walk carefully.
Some clients genuinely don’t know what things cost. In that case, a well-positioned response that educates on value can work in your favour. But often, a budget mismatch signals one of two things: the client isn’t serious about this procurement cycle, or they’re using the process to benchmark pricing for a deal they’ve already made.
Neither scenario is a good use of your pursuit investment.
4. You’re Chasing Margin, Not the Win
This one is harder to admit. Sometimes a bid gets approved not because your team believes you can win — but because the margin profile looks attractive if you do.
The problem is that margin calculations at bid stage are often optimistic. Scope creep, mobilisation costs, relationship-building investment — these aren’t always in the numbers. And when you’re pursuing a deal primarily for financial reasons, without genuine conviction in your fit, it shows in the proposal. Clients can feel when a response is transactional.
Pursue deals where you genuinely believe you are the best answer for the client. That belief produces better proposals. Better proposals win deals. Win the deal first — the margin follows.
5. Your Internal Team Is Already Maxed Out
This is the one that gets overlooked most often in the bid/no-bid conversation.
A mediocre response submitted at full strength is better than a mediocre response submitted by an exhausted team. If your key SMEs are committed to three other live bids, if your solution architect is mid-delivery on a critical project, if your writers are already working nights — the response you produce will reflect that.
Clients notice. Evaluators can tell when a proposal was rushed. Inconsistencies in language, shallow technical sections, boilerplate that doesn’t quite fit the question — these are the fingerprints of a team that didn’t have enough bandwidth to do the job properly.
A strong no today protects your capacity for the wins that actually matter.
How to Have the Conversation
Walking away from an RFP is a commercial decision, not a capability one. When you’re making the recommendation to stand down, frame it that way.
Don’t say: “We can’t win this.”
Say: “The investment required to respond with quality doesn’t justify the probability of winning. Here’s what we’d need to see before committing.”
That framing respects the opportunity while being honest about the maths. And it keeps the door open — because sometimes the situation changes, and you do get the access or information that makes a bid worth pursuing.
The best pursuit teams I’ve worked with are disciplined about saying no. They have a clear bid/no-bid framework. They stick to it. And because they only pursue deals they believe they can win — they win more of them.