Qualify and route: the bid/no-bid decision
The most valuable decision in the whole process happens before any writing: whether to bid at all. A response costs real hours across sales, creative, pricing, and leadership. Spend them on the RFPs you can win, and say no cleanly to the rest.
The bid/no-bid rubric
Score the RFP on four questions. A weak answer on any one is a reason to pause; weak answers on two is usually a no-bid.
| Question | Bid signal | No-bid signal |
|---|---|---|
| Fit | The ask maps to what you actually do well | You would be stretching into an offer you cannot deliver confidently |
| Winnability | You have a real angle, a relationship, or proof in this space | No relationship, no differentiator, cold against entrenched competitors |
| Is it real | Open process, genuine evaluation, multiple vendors in contention | Signs an incumbent is pre-chosen and the RFP exists to justify them |
| Worth the cost | Deal size and strategic value justify the effort | High-effort custom response for a small or low-probability deal |
Disqualifiers
Some signals are strong enough to decline on their own:
- The requirements describe a specific competitor's product in detail (the spec was written for them).
- The timeline is too short to produce a response you would be proud of, with no flexibility.
- Mandatory terms you cannot meet (compliance, exclusivity, pricing floor).
- No access to the buyer for questions, and the brief has gaps you cannot responsibly guess at.
A clean, prompt no-bid is a professional answer, and it preserves the relationship for a better-fit RFP later. It beats a rushed, half-hearted response that signals you do not understand the ask.
Routing once you commit
The moment the decision is bid, assign ownership so nothing falls between people. Keep it to a few clear roles, however your team is structured:
- Owner of the response - drives the whole thing to the deadline, holds the timeline, and is accountable for submission.
- Identifier / qualifier - the person who read the RFP first, understands what is being asked, and briefs the rest of the team so no one re-reads from scratch.
- Contributors - whoever supplies pricing, creative, technical answers, security or legal review.
- Approver - the human who signs off on the final proposal before it is submitted.
Write these down on the RFP's working record on day one. The single most common coordination failure is an unassigned long-pole item (custom pricing, a security questionnaire) that no one realises they own until the deadline is close.
Capturing the decision
Record the bid/no-bid call and the reason, even for a no. A logged no-bid is not wasted: it is the pattern that tells you, over a quarter, which RFP sources are worth your time and which routinely send unwinnable requests.