You answered every question. You hit every requirement. Your pricing was sharp.
And you still lost.
You may not want to hear this, but it probably wasn't the writing. It probably wasn't even the price.
It's that you sent a package, not a proposal.
What a package looks like
A package takes the requirements, answers the questions and makes the company submitting it the hero of the story.
Our history. Our team. Our awards. Our products. Our process.
It checks every box. It's often beautifully formatted. And it reads almost exactly like the three other packages sitting next to it on the evaluator's desk.
When everything looks the same, buyers fall back on the one thing that's easy to compare: price.
What a proposal does differently
A proposal answers the same questions. But it's built around the buyer, not the company submitting it.
It understands the scoring and what the RFP is asking for. It also understands the people behind the decision: what they need to get right, what they're worried about, and what would make them look good for choosing you.
The difference shows up in small places:
→ The executive summary talks about their goals before it mentions your company.
→ Answers follow their structure and use their words, so evaluators never have to hunt.
→ Their biggest risk is named and addressed, not left for them to wonder about.
→ Proof is chosen because it matches their situation, not because it's your favourite case study.
One buyer described a proposal I worked on as "an easy yes." That's the goal. Not the longest response or the prettiest one. The easiest one to say yes to.
Where that insight actually comes from
Here's the part most teams miss: the insight that turns a package into a proposal doesn't come from the RFP document.
It comes from your sales team. They've had the conversations. They know who's frustrated with the current vendor, who has to sign off, and what keeps coming up in meetings.
If you're writing before you've talked to sales, you're already writing a package.
Try this on your next bid
Before anyone writes a word, sit down with sales for 30 minutes and answer four questions:
What does this buyer value most, in their words?
What are they afraid of getting wrong?
What objection is likely to come up about us?
What would make the decision-maker look good for choosing us?
Then read your executive summary and ask one more: could we send this to any other buyer?
If the answer is yes, it's a package. Rewrite it until the answer is no.
The bottom line
You won't win every bid. But when your team has put you in a position to win, your proposal shouldn't be the reason you lose.
Write for the buyer, and you'll stop being compared on price alone.
Not sure where your bids are slipping? The Bid Self-Check is 10 questions and 5 minutes. Email me and I'll send it your way.
I write about how buyers decide and how to win more bids. If this was useful, share it with whoever owns your next RFP.
— Jen
