The RFP response that gets you shortlisted.
US enterprise RFPs are read for forty-five seconds before the reviewer decides which pile to put you in. The pile is chosen on three artifacts, and offshore agencies routinely lose the pile on the first artifact. Here is how the winning response is actually structured.
A procurement analyst at a US Fortune 1000 opens twenty-two RFP responses in a Monday afternoon block. She spends forty-five seconds on each, sorts them into three piles — yes, maybe, no — and hands the yes pile to the technical reviewer on Tuesday morning. The maybe pile gets a second look only if the yes pile shrinks below three. The no pile is deleted.
Offshore agencies routinely land in the no pile on the executive summary alone. Not because the underlying work is weaker, but because the response was written as if the reviewer was going to read all forty pages. She was not. She read the executive summary, the pricing table, and the references section. In that order. And the executive summary is where offshore firms lose most often.
The executive summary that survives forty-five seconds
The winning summary is one page, three paragraphs, and answers exactly three questions in exactly this order. What is the specific outcome we are proposing to deliver, measured in the buyer's own success metric. What is the specific team and operating model we are proposing to run against it. What is the specific commercial shape of the engagement, at a level of detail the reviewer can put into a spreadsheet without going back to us for clarifications.
The three-paragraph summary is not decorative. Each paragraph maps to a question the procurement analyst has to answer in her sort. Paragraph one answers "is this the right kind of vendor." Paragraph two answers "can they actually do this." Paragraph three answers "does the money work." If any of the three paragraphs fails to answer its question inside its own paragraph, the response goes into the maybe pile at best.
What the pricing table has to look like
The pricing table is read second, and it is read for a specific thing: predictability. The reviewer is not shopping for the lowest price on the sheet. She is shopping for the price she can defend to her CFO as a reasonable, structured number that will not surprise her in month four.
That means role-based rates rather than blended. It means a target seniority mix stated on the table itself. It means a written change-order rate, so the CFO knows what happens when scope moves. And it means a total-cost estimate for the engagement's most-likely shape, not just an hourly menu. A pricing table that forces the reviewer to do math loses to a pricing table that hands her the number she was going to compute.
The references section that clears the risk review
The references section is read third, and it is read for one thing: whether the reviewer can call three people at three companies she has heard of, this week, and hear a coherent story. Not glowing testimonials. A coherent story.
Three references is the minimum. Each reference has a name, a title, a company the reviewer's boss will recognize, a direct line, and a two-sentence description of the engagement. Do not withhold contact information. "Available upon request" reads as "we do not want you to actually call them," and that is the single most damaging phrase in the entire response.
One of the three references should be a client where something went wrong and was fixed. The reviewer specifically wants that reference, because the procurement memo she writes needs a sentence about how the vendor behaves under pressure. If she cannot get that sentence from your references, she gets it from your competitor's, and your competitor wins.
What to leave out of the response
Everything the reviewer is not going to read on the first pass. The company history. The awards. The generic capability slide with sixteen logos. The methodology page that reads the same as every other agency's methodology page. All of it goes in an appendix labeled clearly, so the reviewer can find it in the yes pile round if she needs to, but none of it goes in the main body.
The most common failure mode is a response written as a marketing brochure with an RFP grafted onto the back. The reviewer's job is not to be marketed at. Her job is to sort. The response that helps her sort wins the sort. The response that tries to sell her something loses.
The signal a US buyer reads in the response's format
The buyer reads two format signals that offshore agencies frequently get wrong. First, is this response written in the buyer's business English or in a machine-translated register that suggests the actual delivery documents will read the same way. That signal is unfair but real. Have a US-native reader edit the response before it goes out.
Second, does the response reference the RFP's actual requirements in the RFP's numbering scheme, or does it ignore the numbering and answer in its own structure. Every RFP has a numbering scheme. The response has to match it. A response that reorders the questions reads as one that did not read them carefully, and that read survives into the memo.
- 01Forty-five seconds per response, three-pile sort. The executive summary decides the pile more often than the technical content.
- 02Three-paragraph executive summary: outcome in the buyer's metric, team and operating model, commercial shape at spreadsheet-ready detail.
- 03Role-based pricing with a target seniority mix and a written change-order rate. Hand the reviewer the number she was going to compute.
- 04Three references with direct contact information. "Available upon request" is the single most damaging phrase in the response.
- 05Match the RFP's numbering scheme exactly. Have a US-native reader edit the response before it goes out.
Get vetted. Get listed. Get the paper that survives the memo.
Twelve-minute intake, three-day turnaround. A passing scorecard is the shortest path from a good deck to a serious shortlist.