How to Write an RFP Response That Wins

Renee's team spent 11 days on a pump station proposal: 46 pages, a site survey, and a price they were proud of. The buyer rejected it before anyone scored it, because the signed acknowledgement for Addendum 2 wasn't in the package. (Renee is fictional, but the failure is common.)

You already know a good RFP response takes real work. What's less obvious is that most of what wins it is decided before anyone writes a paragraph: whether to bid, what the buyer will score, and what you learned on site.

This guide takes those in order, with the sections to include, a go/no-go scorecard, the writing steps, and an RFP response template you can copy. It's written for manufacturers, sales engineers, and reps, not software vendors. If your best facts come from plant walks, try ParrotNotes free so they're on the record when the document lands.

Not sure it's an RFP at all? Run the triage test in our RFQ vs RFP guide first. A fixed spec with a price form needs a quote instead, and our RFQ template has the format.

What goes in an RFP response

An RFP response is a written offer that shows a buyer how you'd solve their problem, what it costs, and why they should believe you. Most responses have the eight sections below. The buyer's own format always comes first: if the RFP names its sections, use its names and its order.

U.S. federal RFPs make this easy to find. Instructions for the response sit in Section L and evaluation factors in Section M (FAR 15.204-5). Commercial and state RFPs use their own headings, but the same two questions are in there somewhere.

A capability statement doesn't replace any of this. It introduces your company before a job exists, though it's a useful source for the past performance section.

Should you respond? A go/no-go test

A full RFP response is expensive. Loopio, which sells RFP software, reports that teams spend 33 hours per RFP and nine people contribute, and that 75% of teams use a go/no-go process. Those are a vendor's survey averages, as read in November 2026, and an engineered bid can take far longer.

So decide first. Give it 30 minutes, with one named person making the call.

Five hard stops

One "no" here ends the bid, unless you can fix it before the deadline.

1. Mandatory requirements: do you hold every required certification, registration, bond, and insurance level?
2. The spec: can you meet it without an exception the buyer has ruled out?
3. The date: can your plant deliver by the required date, at current lead times?
4. The terms: can you live with the contract terms, or does the RFP allow exceptions?
5. The people: are the engineer and pricing lead free before the due date?

Six scored factors

Score each from 1 (weak) to 3 (strong), then add them up.

14 to 18: bid. 10 to 13: bid only if the owner can name what would move a low score. Under 10: decline. These cut-offs are our suggested starting point, not research, so adjust them after your first ten decisions.

Check the break-even

Then compare what the bid costs with what winning pays. Say a response takes 120 hours at a loaded rate of $75: that's $9,000. If the job's expected margin is $60,000, you need better than a 15% chance of winning to come out ahead ($9,000 ÷ $60,000). These numbers are only an illustration, so plug in your own.

Compare that with your real win rate on similar bids, not someone else's. Loopio's own page gives two averages, 39% this year and 45% across 2019 to 2026, and neither tells you about bids like yours. Our free win rate calculator gives you your own number.

Picture Omar, a fictional manufacturers' rep, holding an RFP whose flow-rate table matches one competitor's catalog line for line. He'd never met the buyer. He scored it 8, sent a polite two-line decline, and his principal spent those 120 hours on a bid they'd helped shape.

How to write an RFP response, step by step

1. Read how you'll be scored first

Skip to the evaluation section before anything else. In U.S. federal buying, factors and "their relative importance shall be stated clearly in the solicitation" (FAR 15.304). Proposals are then judged "solely on the factors and subfactors specified in the solicitation" (FAR 15.305). Whatever doesn't touch a factor earns nothing.

2. Build a compliance matrix

List every "shall" and "must" before anyone drafts. Add every addendum, because that's where Renee's bid died. Here's a fictional example from a pump station RFP:

An evaluator should find every answer without hunting. Nothing goes out while a row says "Open."

3. Ask your questions early

Send them to the named contact before the deadline. Many RFPs bar contact with anyone else, so don't call your friend in maintenance. Answers often go to every bidder, so don't hand a competitor your angle.

4. Budget pages by points

Teams tend to write most about what they know best. Give space by points instead. Hawaii's State Procurement Office publishes a sample split of 1,000 points. Here's what it would mean for a 40-page limit, with the cost volume on its own form:

Company history isn't on that list, so cut it to a paragraph. The same split works for hours.

5. Answer each requirement the same way

Use four beats: state that you meet it, say how, show proof, and say what it means for them.

• Weak: "We are an industry leader with decades of experience in high-efficiency pumping solutions."
• Strong: "We meet the 1,200 gpm duty point at 85 ft head with Model X. The attached curve shows the duty point at 78% efficiency. You'll witness the test at our plant before shipment, so the number is proven before the pump reaches your site."

Our sales engineer guide has a read-back script for getting them right in the room.

6. Make the price match the plan

If the plan promises a technician on site for 12 weeks and the price assumes four, an evaluator will catch it. List your assumptions and exclusions plainly.

Write only what your plant can deliver. Under FAR 2.101, a response to a federal RFP is an offer that, "if accepted, would bind the offeror to perform the resultant contract." Commercial terms and local law decide the details elsewhere. This isn't legal advice, so have counsel read any exceptions.

7. Score your own draft, then send it early

Hand the draft and the evaluation section to someone who didn't write it, and have them score it as a buyer. Then send it well before the deadline. A federal proposal that arrives after the exact time is "late" and generally won't be considered (FAR 15.208).

RFP response template

Copy this RFP response outline into your document. Keep the buyer's section names where they differ, and delete the prompts as you fill them in.

COVER LETTER (one page) RFP number and title: [ ] Due date: [ ] Named contact: [ ] Our offer in one sentence: [ ] Addenda acknowledged: [numbers] Offer valid until: [date] Signed by someone who can bind the company: [name, title]

1. EXECUTIVE SUMMARY (one page) What you told us you need: [the problem, in their words and numbers] What we propose: [solution in two sentences] Why it fits your top scoring factors: [one line each, in their order] Total price: [only if the RFP allows price outside the cost volume]

2. COMPLIANCE MATRIX [Ref | Requirement | Must or should | Meets, partly, or exception | Our section]

3. TECHNICAL APPROACH (most of your pages if it's the top factor) Understanding of the site or application: [baseline numbers, from your visit] Proposed solution: [models, drawings, data sheets] Requirement by requirement: [meets it, how, proof, what it means for them] Alternates: [only if the RFP allows them, priced separately]

4. PROJECT PLAN AND TEAM Schedule: [milestones, lead times, and what starts each clock] Testing and acceptance: [factory test, site test, who witnesses] Installation, training, and handover: [ ] Named team: [role, name, one line of relevant experience] What we need from you: [site access, utilities, approvals]

5. PAST PERFORMANCE For each of [number] jobs: customer, contact (with permission), dates, value, what we delivered, and the result. Choose jobs most like this one.

6. SERVICE AND SUPPORT Warranty: [terms] Spares: [list, lead times] Response time: [ ]

7. PRICE AND TERMS (separate file if the RFP says so) [Use the buyer's price form exactly] Assumptions and exclusions: [ ] Freight and delivery terms: [ ] Payment terms: [ ] Validity: [ ]

8. FORMS AND EXCEPTIONS Required forms, signed: [list] Registrations and certificates: [list] Exceptions: [clause number | what we propose instead | why]

Before you send it, check three things: every matrix row has a section, every addendum is acknowledged, and file names and format match the instructions.

What happens after you submit

The buyer may ask clarifying questions, or invite the top bidders to discussions or oral presentations. In federal buying, discussions take place with offerors in the "competitive range" (FAR 15.306). Bring the engineer who wrote the technical section to any orals.

Win or lose, ask for a debrief. Federal bidders must request one in writing "within 3 days" after they're notified of the award, and it covers your flaws, the winner's price and technical rating, and why the award was made (FAR 15.506). Commercial buyers don't have to agree, but it's worth asking. Put what you hear into your next scorecard.

Win the RFP response before the RFP lands

The strongest line in a technical section usually comes from a site visit. Imagine Renee's next bid. Months before the RFP, she walked the pump station with the operators and heard that night callouts were what they hated most. Her debrief recorded the callout count and who said it. Her executive summary opened with that problem, in their words.

ParrotNotes keeps those conversations usable. Record your debrief in the car after a plant tour or site walk, and you get a transcript, an AI summary, and action items. When the RFP arrives months later, search the pump station's name and the operator's words are there.

ParrotNotes Pro adds custom insight templates, so a debrief can come back sorted into the fields your proposal needs. If you're recording a meeting rather than yourself, ask everyone first, and check site rules on phones. Download ParrotNotes free and talk through your next site visit before you start the car.

Bid less, and answer what's scored

A winning RFP response is rarely the longest one. It's the one that should have been bid, answers what's scored, and misses nothing.

• Run the hard stops and the scorecard before writing
• Build the compliance matrix first, addenda included
• Give pages and hours by points
• Ask for a debrief, win or lose

Start with the template, then add the site notes that make it specific. Get ParrotNotes free and capture them while you still remember who said what.