The Anatomy of an RFP
From the buyer's side, an RFP is rarely just a shopping list. It is procurement governance: a way to distribute risk across a committee, create an audit trail for the decision, and, in the public sector, satisfy a legal obligation to run a fair process. Understanding that purpose is what lets you read the document for what it really is. The requirements carry authorship fingerprints, and learning to read them tells you, before you write a word, which of the three species you are dealing with.
The Genuine Evaluation
A real, open competition. The criteria describe outcomes rather than one vendor's feature names, stakeholders will talk to you, and the timeline leaves room for a real evaluation. This is the RFP worth winning, and the one where the work you did before it was published decides the result.
The Wired Deal
A favorite has already been chosen, and the process exists to justify a decision that is effectively made. You are there to make the comparison look competitive. Responding fully is how a quarter quietly disappears into a result that was never available to you.
The Fishing Expedition
No budget, no compelling event, no real intent to buy soon. The document exists to harvest price points, feature lists, and ideas, sometimes to build a business case the buyer has not yet won internally, sometimes to pressure an incumbent on renewal. Your detailed answers become free market research. The honest move is usually to decline, or to convert the genuine curiosity into a real conversation before committing the team.
The Qualification Gate: Five Questions
Before a single answer is written, the RFP has to pass a gate. Five questions predict the outcome with uncomfortable accuracy. Answer them honestly and most doomed responses never get started, which is the entire point: the time you save on the un-winnable ones is the time that wins the real ones. The examples are phrasings an SE or AE can actually use with the buyer or internally.
Did We Know This Was Coming?
Relationship and discovery before the document existed is the single strongest predictor of winning. A good answer: you have been in the account for months, you helped them think about the problem, and the RFP confirms a direction you already shaped. A bad answer: it arrived cold, from a buyer you have never spoken to.
Can We Talk to a Human?
The access test. A buyer running a genuine evaluation wants the strongest possible field and will allow clarification. A buyer who refuses every conversation and routes everything through a no-contact portal is telling you the decision is already made. A good answer: they will take a call. A bad answer: all questions in writing, no exceptions, no meetings.
Whose Words Are These?
The fingerprint test. Requirements carry the vocabulary of whoever wrote them. If the criteria use a rival's exact feature names, branded terms, or oddly specific thresholds that match one product's datasheet, the spec was shaped before you arrived. A good answer: outcome-framed requirements written in the buyer's own language. A bad answer: a competitor's marketing copy with the logo removed.
Is This a Buying Timeline?
Test the dates against reality. A real purchase has a budget cycle behind it and a described decision process after the submission. A fishing expedition has neither. A good answer: a funded initiative with an evaluation period, a decision date, and named approval steps. A bad answer: an aggressive deadline, no budget mentioned, and silence on what happens after you submit.
What Does Winning Cost?
The no-bid math. Weigh the response effort, in SME hours and SE time, against the weighted expected value: deal size multiplied by an honest probability of winning. A long shot on a large deal can be worth it; a long shot on a small one almost never is. Crucially, someone has to be allowed to make the no-bid call. If every RFP is an automatic yes, you do not have a gate, you have a queue. A good answer: a clear-eyed estimate and a named owner empowered to decline. A bad answer: "we respond to everything."
Shaping the Requirements
The RFP is won or lost before it is published. Once the requirements freeze, your influence drops to near zero, so the real work is upstream: helping the buyer define what good looks like while the criteria are still soft. The best RFP strategy is to make the document a formality that confirms a decision your earlier work already earned.
Get in before the document freezes
Influence happens during discovery, not during the response. When you are in the account early, helping a buyer think through their problem, you are also helping them decide which criteria actually matter. Vendors who arrive only when the RFP lands are responding to a specification that someone else, often a competitor, already shaped.
Arm the champion with outcome criteria
Give your champion evaluation criteria framed as business outcomes, not feature checkboxes. "Reduce contract turnaround to under two days" is a criterion you can win and a competitor cannot easily copy; "supports bulk export" is a checkbox anyone ticks. A champion who carries outcome-framed criteria into the requirements-gathering meeting is shaping the RFP on your behalf, in their own words.
Stay on the right side of the line
There is a clear ethical line. Helping a buyer write better, outcome-focused criteria is good selling. Rigging a spec so only your product can qualify is not, and it tends to backfire when a procurement team notices. In the public sector the line is firmer still: once an RFP is published, attempts to influence it privately are usually against the rules, and crossing that line can disqualify you. Shape early, shape openly, and stop when the process formally begins.
Make the RFP confirm a decision
The goal of all this upstream work is simple: by the time the RFP is published, the buyer should already believe you are the right answer, and the document should read like it was written with your strengths in mind because those strengths are what they decided mattered. The response then confirms a conclusion rather than fighting for one. That is the difference between a 20 percent win rate on cold RFPs and a much higher one on RFPs you helped create.
Responding to Win
Once the gate says yes, the craft of the response is what separates a win from an honorable mention. Evaluators are tired, skimming, and scoring against a rubric. Everything below is about making it easy for them to score you high and hard for them to miss why you are different.
Triage before anyone writes a word
Build a compliance matrix first: every requirement, its weight, who owns the answer, and whether you fully meet it, partially meet it, or do not. This turns a wall of text into a plan, surfaces the dealbreakers early while you can still act on them, and stops the team from pouring hours into low-weight questions while the scored ones go thin.
Architect every answer: answer, differentiate, prove
Lead with the direct answer to the question asked, in the first sentence. Then, and only then, add the differentiation and the proof. Evaluators are scoring whether you answered, so make that unmissable before you reach for the story. Essay-first answers, where the differentiator is buried in paragraph three, lose points the evaluator never even read.
Be honest about partial fits
A clearly framed "partial, and here is the workaround" beats a confident "yes" that collapses in the demo or the proof of concept. Overstating capability wins the paper round and loses the deal at the moment of highest cost, after you have everyone's attention. Mark futures as futures. Evaluators have been burned before and reward the vendor who is straight with them.
Build the executive summary on win themes
The executive summary is often the only section every decision-maker actually reads. Do not waste it on company boilerplate and founding dates. Build it on two or three win themes tied to the outcomes the buyer told you mattered, in their language, so the person who controls the budget sees their own priorities reflected back before they read a single requirement answer.
Treat the answer library as an asset
A good answer library has owners and review dates, not a graveyard of paragraphs copied from the last response and slowly going stale. Pasting an 18-month-old answer about a feature that has since changed is how a response quietly lies. Maintain it like product documentation, and every RFP makes the next one faster instead of riskier.
Coordinate SMEs, and use the clarification window
Protect the team by giving each subject-matter expert a scoped ask and a real deadline, not the whole document and a vague plea. And treat the clarification-question window strategically: a well-placed question can surface a buried requirement, signal your expertise to the evaluators, or gently expose where a rival-shaped spec does not actually serve the buyer.
The No-Bid Play
Saying no is a skill, and a clean no-bid is often the most professional move on the table. It protects the team's time, preserves the relationship for a better-timed deal, and, done well, earns more respect than a doomed response ever could. The buyers worth working with remember the vendor who was honest about fit.
- A genuine thank-you for the invitation, and a gracious, specific reason: timing, focus, or fit, never a complaint about the process.
- An honest, non-defensive line on why you are not the right answer for this particular requirement set.
- A door left open: the relationship matters more than this one document.
- Where the interest is real, an offer of something more useful: a scoped workshop, a reference, or a conversation.
- Nothing that burns a bridge or makes the buyer regret having asked.
When the interest is genuine but the RFP itself is not winnable, do not simply decline: counter-offer a different process. A scoped workshop, a focused evaluation, or a working session can sidestep a rigged document and put you back on ground where your work actually counts. The decline is not the end of the conversation, it is a redirect to a better one.
Log every no-bid with its reason, and revisit the outcome later. If the deals you walked away from went to the pre-selected favorite anyway, your gate is well calibrated. If they went to a competitor you could have beaten, your gate is too cautious and needs loosening. Either way the no-bid is data, not a loss, and the vendor who declines gracefully is the one who gets the call when the next, better-timed RFP comes around.
RFP Anti-Patterns
Most RFP failures repeat the same five mistakes. Each has a recognisable shape, a reason it keeps happening, and a direct fix. Several of them are really just the qualification gate getting skipped.
The Checkbox Sprint
Responding to every RFP that arrives, on the logic that "you can't win if you don't play."
The Word-Count War
Believing the longest, densest answer wins, and padding every response until it strains the page limit.
The Hero Author
One SE writes the entire response from scratch, every time, through the weekend.
The Roadmap Promise
Marking future or planned capabilities as if they exist today, because a "yes" scores higher than a "partial."
The Submit-and-Pray
Sending the document by the deadline and going silent, treating submission as the finish line rather than the halfway mark.
Score Your RFP Process
Rate your team's RFP process, drawing on the last few you responded to, on a 1–5 scale. 1 = this didn't happen. 5 = this is consistently how you work. Be honest, the score only helps if it's accurate.
What Shaped This Playbook
The frameworks here are original, but they didn't emerge in a vacuum. These four books shaped how I think about qualification, differentiation, and the discipline of proposal craft, all available in the SE Resources books section.
The reference text for the SE role end-to-end. Its treatment of qualifying opportunities and managing formal evaluations is the practical grounding for the qualification gate and the discipline of saying no to the wrong RFP.
The research on reframing and commercial teaching is what turns a compliant response into a differentiated one. Its lesson, that the strongest sellers reshape how a buyer sees their own problem, is exactly the work of shaping requirements before the document freezes.
A study of why deals end in no decision. It sharpens the qualification gate and the no-bid call: many RFPs are not a competition you lose, they are a purchase that was never going to happen, and recognising that early is what protects the team's time.
White's insistence on being brilliant at the basics is what the answer library and the compliance matrix are really about. The unglamorous discipline of preparation, not last-minute heroics, is what wins the RFPs worth winning.
Found this playbook useful? Share it with your team.
Share on LinkedIn