I’ve written somewhere north of 200 proposals since starting PipelineRoad. The first 50 or so were terrible. Long, generic, packed with agency jargon, and structured around what we could do rather than what the client needed. Our close rate on those early proposals was around 15%. One in six or seven. Painful.
Today we close roughly 40 to 45 percent. Still not a coin flip, but nearly triple where we started. The difference is not that we got better at selling. It’s that we got better at writing.
A proposal is a document, and documents can be engineered. Here’s what we’ve learned about engineering them well.
The First Mistake: Starting With Yourself
The single most common proposal mistake is opening with a section about your agency. Your history, your team, your values, your methodology. Three pages of self-congratulation before the client sees a single word about their problem.
Nobody reads this. I know because clients have told me. They skip straight to the section about what you’ll do for them and how much it costs. Everything before that is decoration.
Our proposals open with the client’s situation. Not a generic “challenges in your industry” overview — a specific, detailed account of what we heard them say during the discovery process. Their exact words, wherever possible. “You mentioned that your sales team is getting leads that aren’t qualified. You said your website doesn’t reflect how the product has evolved. You described a gap between what your content says and what your buyers actually care about.”
This does two things. First, it proves we listened. In a world where most agencies show up with a templated deck, demonstrating that you actually heard what the prospect said is a genuine differentiator. Second, it frames the entire document around their needs, not our capabilities. The proposal becomes a story about them — and people pay attention to stories about themselves.
The Structure That Works
After the situation section, our proposals follow a consistent structure.
Diagnosis. This is where we translate what we heard into a strategic assessment. Not a list of problems — a coherent narrative about why things are the way they are and what needs to change. The diagnosis is the most important section of the proposal because it’s where trust is built. If a prospect reads our diagnosis and thinks, “Yes, that’s exactly right,” the rest of the document is a formality.
Recommended approach. This is the strategy section. What we propose to do, in what order, and why. We’re specific here — not “we’ll create a content strategy” but “we’ll build a topic cluster around your three core use cases, targeting keywords with high buyer intent and low competition, publishing four pieces per month for the first quarter.”
Specificity signals competence. Vagueness signals that you’re figuring it out as you go.
Scope and deliverables. This is the operational section. What exactly will we deliver, on what timeline, with what dependencies from the client? We break this down by month for the first quarter and by objective for subsequent quarters. The client should be able to read this section and know precisely what they’re getting.
Investment. Not “pricing.” Investment. This isn’t just semantics — it frames the number in the context of what they’re getting, not what they’re spending. We present one recommended option, not three tiered packages. The three-tier model (“Basic, Professional, Enterprise”) signals that you haven’t done the diagnostic work to know what the client actually needs. If you’ve done the discovery properly, you should have one recommendation. Make it.
The Mistakes That Kill Proposals
Beyond the structural issues, there are specific errors that I see consistently — in our own early work and in competitor proposals that clients have shared with us.
Too long. If your proposal is more than eight pages, it’s too long. Proposals are decision documents, not strategy documents. The prospect needs enough information to say yes or no. They don’t need a dissertation on content marketing trends.
Too generic. If you could swap the client’s name for another client’s name and the proposal would still work, it’s too generic. Every section should contain details that could only apply to this specific prospect. If it doesn’t, you haven’t done enough discovery.
No timeline. Prospects want to know when things will happen. A proposal without a clear timeline feels theoretical. We include a 90-day roadmap in every proposal — not because we can predict the future with precision, but because it demonstrates that we’ve thought about sequencing and dependencies.
Burying the price. Some agencies put pricing on the last page, hoping the prospect will be so enamored by the strategy that the number won’t matter. This is wishful thinking. Put the investment section where it’s easy to find. If the prospect has to hunt for the price, they’ll be annoyed, not persuaded.
The Follow-Up
The proposal itself is half the equation. The follow-up is the other half.
We never send a proposal and wait. We send it, give the prospect 48 hours to read it, then schedule a call to walk through it together. The walk-through is not a presentation — it’s a conversation. We go section by section, ask for reactions, address concerns in real time, and clarify anything that’s ambiguous.
Most objections surface in this conversation, not in email. A prospect who would ghost your proposal will often tell you their concerns face to face. “The timeline feels aggressive.” “I need to get buy-in from my CTO.” “The price is higher than we budgeted.” These are all workable objections, but only if you hear them.
The walk-through also gives you something invaluable: the chance to close. Not in a pushy, sales-tactic way. In a human way. “Does this feel right? Is there anything you’d change? What would it take for you to move forward?”
Sometimes the answer is yes. Sometimes it’s not yet. Sometimes it’s no. All of those are useful. What’s not useful is sending a PDF into the void and hoping for the best.
The Underlying Principle
The principle beneath all of this is simple: a proposal is not a sales document. It’s a trust document. Its job is not to persuade — it’s to demonstrate that you understand the prospect’s situation deeply enough to solve it.
If the proposal reads like it could have been written by anyone, it will lose to the proposal that couldn’t have been. Specificity, structure, and evidence of listening — that’s the formula. Everything else is noise.