The AE's Guide to RFPs: What to Decide Before Your SE Opens the Document

The expensive RFP is not the one you lose. It is the one you were never going to win, staffed with the engineer you needed on the deal you could have.

1. Is there a person, or only a document?

The single strongest negative signal in an RFP is no access to the people who wrote it: one clarification window, answers published to every bidder, no calls. That is a document designed to be answered rather than a decision being made in the open.

If you cannot get a conversation, you are competing on paper against someone who has had nine months of conversations. That is not always a reason to walk, but it should change what you spend.

2. Whose language is this written in?

Requirements phrased in one vendor's terminology — their feature names, their way of splitting a capability into sub-requirements nobody else splits — mean that vendor helped shape the document. That is ordinary procurement practice rather than misconduct, and it is readable in an hour. Six tells, and what to do about them.

3. What is the mandatory-gap count?

Not the gap count — the count of gaps against mandatory requirements. One unmet mandatory line usually ends it regardless of how the rest scores, and the number is knowable in the first days if requirements are actually scored rather than skimmed.

This is the number to bring to a bid review. “We are strong on most of it” is not a position; “three mandatory gaps, two of which we could argue” is. It is also what makes the bid/no-bid conversation a five-minute decision rather than a standing debate.

4. What does winning this actually get us?

Worth asking plainly, because the answer is sometimes “a reference logo in a segment we are trying to enter” and sometimes “revenue we have already forecast”, and those justify very different levels of investment. A deal worth bidding at a fraction of the usual effort is a real category, and it is rarely named out loud — so it gets staffed as if it were the other kind.

If you decline, decline well

A no-bid is a competitive move rather than a surrender. Send it in writing, to the person who owns the business outcome rather than to the procurement mailbox, and say which requirements read as pre-shaped and what would need to change for a serious bid.

Two things follow. The relationship survives for the re-compete, which is the bid that is actually winnable. And occasionally the process changes, because someone senior did not know the requirements had been drawn that tightly and does not want a single-vendor outcome on their governance record.

The arithmetic nobody runs

Every RFP you answer consumes technical capacity that is finite and shared. The concurrency limit is real and it is lower than most pipelines assume — six evaluations in the same fortnight is a different week from six across a quarter, even at equal deal count.

So the question is never just whether this RFP is winnable. It is which deal loses its engineer if you say yes.