Every Proposal Tells the Story of the Discovery Call That Came Before It
Every proposal tells me how the discovery call went.
While yes, I dive into the root causes on discovery, and problems and impacts, if this one thing is missing - it's telling as to why deals are stalling, buyers are ghosting and your team is chasing and throwing out discounts to win.
A few weeks ago, a Sales leader reached out because three opportunities had gone completely quiet after proposals were sent. The demos had gone well. The buyers were engaged. They asked for pricing. Then...nothing.
He wanted to know what happened as they weren't closing any deals. After some back and forth, one deep dive gave me my answer.
The Proposal Was Telling the Wrong Story
The proposal. It described the platform, outlined the implementation approach, highlighted the capabilities, and included pricing.
It never once talked about the buyer's business.
There wasn't a quantified business problem. There wasn't a root cause. There wasn't an explanation of what those problems were costing the organization. There wasn't a compelling reason for the buyer to change now instead of six months from now.
The proposal answered, "What do you sell?". It never answered, "Why should we buy?"
When that's the story your proposal tells, buyers do exactly what you've trained them to do.
They compare capabilities. They compare implementation timelines. They compare pricing. Then they ask for discounts.
And they are not trying to beat your team up on price, it's just that they have nothing else to evaluate.
Proposals Don't Create a Business Case
One of the biggest misconceptions in sales is that the proposal is where value gets created.
It isn't. The proposal (or whatever you call it internally,) is simply the final output of everything that happened during discovery.
If discovery was centered on features, your proposal will be centered on features.
If discovery focused on technical requirements, your proposal will focus on technical requirements.
If discovery never uncovered the buyer's business problems, quantified their impacts, identified the root causes, or measured the cost of doing nothing, your proposal can't suddenly invent those things after the demo.
By the time you're writing the proposal, it's already too late. Because your team skipped the meaty part.
Recommendations Are Built Long Before They're Written
The best sales organizations don't wait until someone asks for pricing to start building a business case because all of that is built DURING discovery. Question by question, response by response - all pulled together to tell a story.
Every section of a recommendation should come directly from something the buyer has already confirmed. The executive summary should describe the buyer's current state. The business problems should be theirs, not yours. The impacts should be quantified using their numbers. The recommendations should map directly back to the root causes they admitted were preventing change.
By the time the document is written, there shouldn't be much left to think about.
You're simply documenting the case for change the buyer helped build. That one document gets compared competitors while another gets compared against the cost of doing nothing.
And no, the recommendation isn't the end all be all, but I can tell you from the last 3.5 years, fine tuning our internal A Sales Growth Company 's recommendation, has lead to higher win rates.
Your Proposal Shouldn't Be About You
Ask yourself, is your ream's proposal something marketing created? A product brochures with a price attached. Is it full of capabilities, implementation plans, company history, customer logos, and pricing tables.
While all of that is important, it's just about where it goes - in what order.
Your buyer doesn't approve projects because your implementation methodology is better than someone else's. They approve projects because the cost of staying the same has become greater than the cost of changing.
But it's up to your team to highlight that early. And if it isn't obvious by the time the buyer reached the pricing, the proposal hasn't done its job.
We Decided to Publish Ours
Our team wins just over 50% of the opportunities we pursue. Mine personally is 52% YTD. That's right. My win rate. Sure - it may fluctuate through year end - but I'm getting really good at discovery and building the case so that if the buyer chooses to not change, I can live with myself that I didn't get outsold!
And it's not the look and feel. It's what's inside.
And this is why I am recommending you spend 20 minutes and snag ours:
We send recommendations built from the buyer's own business. Every section traces back to something they told us during discovery. Nothing is generic because nothing is invented after the fact.
That's why we decided to publish The Modern Sales Proposal. Instead of giving you another template, we broke down the recommendation we actually send buyers, section by section, and explained the discovery required to write each one. You'll see exactly why most proposals get compared on price while recommendations get compared to the cost of doing nothing.
But here's the rub. Almost every team I talk to off the bat can't get to the real problem they are solving. So if you haven't done that exercise and had it signed off on by our team and you say are a Gap Selling org - YOU ARE AT RISK of your team leading a root cause level discovery and your metrics not changing.
Saving time, they want to have, they don't have, saving money, siloed data - those are not business problems C Suite buys on.
If your team has deals that go quiet after you send a proposal - I'd suggest you start by asking whether the discovery produced enough evidence to write a recommendation in the first place.
What's inside:
Snag it here. If it helps your team build stronger business cases and win a few more deals, then it was worth publishing.

