An RFP has just landed. How do you decide whether to bid on it?

The decision is capital allocation, not enthusiasm

A serious RFP response is not free and it is not paid for in marketing budget. It is paid for in the calendar of the three or four people who can credibly design a solution, and those are the same people carrying delivery escalations and the two other pursuits already in flight. Once you frame it that way, the question stops being "could we do this work?" — the answer to that is almost always yes — and becomes "is this the best use of the scarcest thing we have this quarter?"

That framing is most of what an interviewer is listening for. Answering with capability and appetite describes a sales instinct; answering with an opportunity cost describes judgement, and judgement is what gets you trusted with the bid/no-bid call rather than just the technical sections.

The signals that predict a wired deal

Some RFPs are genuine competitions and some are procurement theatre run to satisfy a three-quote policy after the buying decision was already made. The tells are reasonably consistent.

Requirements written to a competitor's feature list. Not "must support role-based access control" but a requirement naming a specific screen, a specific term of art, or a workflow only one product implements that way. Three or four of those in one document is someone's datasheet with the logo removed. Often the incumbent's presales team helped write it, which is legitimate, and also means you are bidding to be the comparison.

No access to business stakeholders. All questions routed through procurement in writing, no discovery call, no chance to meet the people who will use the system. If nobody will spend forty minutes with you before you spend two hundred hours on them, that asymmetry is the answer.

A timeline that is not survivable. Four weeks to respond on a genuinely complex integration is tight but workable. Nine days over a holiday period, on a document that took them six months to write, usually means the deadline was set to suit someone who already has the answers.

Arriving cold. You are not in their vendor list, nobody in your organisation has a relationship there, and the document simply appeared. Cold RFPs are winnable, but the base rate is poor, and "we found it on a portal" is not the same opportunity as "the CIO's architect asked us to look at it".

A qualification pass you can run in an hour

Score honestly, before anyone gets attached to the deal.

Question	Bid signal	No-bid signal
Can we speak to a business owner before submission?	Yes, scheduled	Written questions only
Who wrote the requirements?	Consultant or client, product-neutral	Reads as a competitor's datasheet
Do we have a prior relationship?	Existing account or warm referral	Arrived via portal, no contact
Is the timeline consistent with the scope?	Yes, with a plan	Compressed with no explanation
Do we meet the mandatory criteria without a partner?	Yes	Requires a partner we have not worked with
Can we name a reason we would win?	Yes, in one sentence	"We are a good all-round fit"

The last row does more work than the rest combined. If nobody on the team can finish the sentence "they should pick us because…" without listing generic strengths, you do not have a win theme, and a response without a win theme is a compliance exercise that loses to whoever has one.

Price the response before you commit to it

Put a number on it in people and days: a solution architect for six days, a data engineer for three, a security lead for two, plus bid management and review cycles. Then weigh that against deal size and a realistic win probability. A pursuit costing thirty senior days at a twenty per cent chance of a modest deal is a bad trade even though every individual day feels justified as you spend it.

This is also the argument that actually persuades a sales leader who wants to bid on everything. "I don't think we'll win" is an opinion and loses the discussion. "This takes the same architect who is committed to the other bid closing next Thursday, and that one has a named sponsor" is a resource conflict, and resource conflicts get resolved rather than debated.

Win-theme construction when you do bid

If you bid, decide what you are selling before you answer a single question. A win theme is two or three claims that are true, that matter to this buyer's stated outcome, that a competitor cannot make as convincingly, and that you can evidence. "We have already migrated two clients off the exact ERP version you are running, and both are referenceable" is a win theme. "Deep domain expertise and a partnership approach" is not, because everyone submitting has written the same words.

Then the themes have to appear where they will be read: the executive summary and the top of each major section, in the client's language and against the criteria they published, not in an appendix the evaluator scoring you will never open.

Bidding conditionally

The middle path is underused and it is the answer that marks out seniority. A conditional bid means you respond and state plainly what the response is contingent on: a phased scope rather than a big bang, a paid discovery phase before a fixed price is meaningful, an assumption that the client provides test data by a named date, or an exclusion where a mandatory requirement needs a partner whose risk you would rather not carry.

The discipline is that the conditions must be real. Conditions you drop under pressure teach the client that your positions are negotiable and invite them to test the rest. Conditions you hold cost you some deals, win you better ones, and protect delivery from a commitment the bid team made and never had to live with.

Declining well

A no-bid is a communication task. Respond inside the deadline rather than going silent, thank them for the invitation, give one honest and specific reason — capacity in that window, a mandatory requirement you cannot meet without a partner, a commercial model that does not fit — and never imply the process was rigged. Then offer something genuine: a view on the requirement you found interesting, an introduction to a better-fitting partner, an ask to be considered for the adjacent workstream.

That last move is the point. Procurement teams remember the vendors who submitted something thin and wasted the evaluators' time, and the ones who declined cleanly and said why. The second group gets called before the next RFP is written, which is the only stage at which the requirements are still yours to influence.

The trap: treating no-bid as the safe answer

Interviewers set this question up so that the tells are obvious, and the weak response is to spot them, say "I would no-bid," and stop. That reads as risk-aversion, and it fails for the same reason bidding on everything fails: it is a rule applied instead of a judgement made.

The strong answer names what would change the decision. A wired-looking RFP is still worth a bid if you can get in front of the business owner and reframe the requirement, or if a narrow scope you can win beats the full scope you cannot. Equally, an RFP with no bad signals at all is still a no-bid if the two people who would have to write it are already committed elsewhere. What is being scored is whether the decision comes from evidence and cost or from a reflex, and both "always bid" and "never bid against an incumbent" are reflexes.

Bid/no-bid is a decision about where to spend your scarcest senior engineers, so justify it with opportunity cost and a nameable reason you would win — and when the answer is no, decline in writing, on time, with a reason that gets you invited before the next requirements document is written.