Proposal copy that wins: what moved our close rate 22%

Proposals don't get much love in marketing. They're long, on a deadline and usually live somewhere between sales, legal and operations. Nobody puts them in a portfolio.

They should. At XPO, I owned the strategy and development of our responses to requests for proposals and requests for information, known as RFPs and RFIs. The work we did there raised close rates by up to 22%. That's revenue, and it came from writing.

Stop answering the question you wish they'd asked

The fastest way to lose an RFP is to paste in your standard boilerplate. Prospects can tell. They write a specific question because they have a specific worry, and a generic answer tells them you weren't listening.

Before I wrote anything, I read the whole RFP, looking for the real problem underneath it. What went wrong with their last vendor? What does this industry lose sleep over? The answers rarely sat in any single question. They showed up in the pattern.

A prospect that asks five different questions about on-time delivery is telling you something. So is one that asks about reporting in three separate sections. Once you see the pattern, you can lead every answer with the thing they care about most.

Build a library, then refuse to use it lazily

We moved our content into Loopio and SharePoint, which cut a lot of busywork and improved team efficiency by about 20%. A good answer library is a gift. It's also a trap.

The library gave us a strong starting point. It didn't give us the answer. We still tailored every response to the prospect's industry, language and stated priorities. The tailoring is the part that wins.

Keeping the library healthy took discipline too. Answers aged fast. Stats changed, services expanded and old phrasing crept back in. We reviewed the most-used answers on a schedule, so the starting point stayed accurate instead of quietly drifting out of date.

“A generic answer tells them you weren't listening.”

Write for the scorer

Someone has to score your response, often against a rubric, alongside four others and at the end of a long day. Make their job easy:

• Answer the question in the first sentence, then support it.
• Mirror their language so they can find what they're scoring.
• Put proof right next to the claim, not in an appendix.
• Cut anything that doesn't help them check a box or feel more confident.

Formatting matters more than most writers think. Clear headings that match the RFP's numbering, short paragraphs and a summary at the top of long answers all help a tired reader find what they need. If they have to hunt, you lose points you earned.

Specific beats impressive

"Industry-leading solutions" scores nothing. A number, a named process or a short example from a similar customer is what moves a scorer from "meets" to "exceeds."

That's why I paid close attention to proof. Every claim in a strong response has something behind it, whether that's a metric, a client in the same industry or a step-by-step description of how the work will happen. Adjectives are cheap. Evidence is what makes a scorer believe you.

Keep a steady drumbeat of expertise

Proposals don't start when the RFP lands. At XPO, I wrote a monthly State of the Industry report for prospects and clients. It gave our sales team a reason to stay in touch between deals, and it showed prospects we understood their market before they ever asked us to bid.

When the RFP did arrive, we weren't strangers. That made the proposal easier to write and easier to believe.

Arm the sales team

Proposals don't end at submission. At XPO, I built sales enablement and training programs for an 18- to 20-person sales force, so the story they told in the room matched the one on the page. When those two don't match, prospects notice.

That meant short briefs on each major response, talking points for finalist presentations and a clear record of what we promised. Sales walked into every meeting knowing exactly what the prospect had read.

Treat losses as research

Every lost bid has something to teach you, but only if you ask. When we lost, we requested a debrief whenever the prospect allowed it. What scored well? Where did we fall short? Who won, and why?

Those answers fed straight back into the library and our approach. Sometimes the lesson was about price or service, which was outside our control. Often, it was about clarity, proof or how directly we answered the real question. Those were the lessons we could act on right away.

The short version

Treat proposals like the high-stakes copy they are. Find the real worry, tailor everything and back every claim with proof. Write for the person holding the rubric, stay in touch between deals and make sure sales can say it out loud.