Most lost deals don't come with a reason. The buyer goes quiet, then sends a short note saying they went another way. Sometimes the price was the problem. Often, in our experience, the proposal made saying yes harder than it needed to be. These are the sales proposal mistakes we see most on big deals, and what we'd do instead.
Writing about yourself first
Pages of company history, a mission statement, an org chart. The buyer has already looked you up. Open with their situation and move your credentials next to the parts of the plan they back up.
Sending the same proposal to everyone
Swapping the logo and the client name doesn't make a proposal custom. Buyers notice the paragraph that was clearly written for someone else, and the wrong client name that slipped through on page 14 (it happens). Each big deal deserves its own proposal, built from the notes of that buyer's calls.
Writing for the champion only
The person you've been talking to already likes you. The people who decide may never meet you. A proposal that only works for the champion leaves them explaining it from memory. Write a section for the CFO, one for whoever owns the risk and one for the person who has to live with the rollout. We go further on this in writing a proposal for a buying committee.
Hiding the price
Burying the number on the last page sends the reader looking for it, and it reads as nervous. Put the price where they expect it, next to what it buys.
Too many options
Three clear options can help a buyer choose. Six options with a dozen line items each turns your proposal into homework. If you offer choices, make the differences obvious and say which one you'd pick for them.
Jargon and acronyms
Your team knows what your acronyms mean. Finance doesn't. Write so someone outside the project can follow along. If a term needs a definition, it probably needs replacing.
No clear next step
A lot of proposals end on "we look forward to working with you." Then nothing. End with what happens after yes. Who signs, by when, and what starts the following week.
A PDF that's hard to read on a phone
Executives read on their phones between meetings. A dense, multi-column PDF at phone size is a chore. Our read is that a live web version of the proposal, with the PDF kept for the file, gives every reader a version that works where they are. More on that in the old way of building proposals.
Padding it to look thorough
Long doesn't read as serious. Proposify, which sells proposal software, found in its 2026 report that winning proposals averaged 11 pages and losing ones averaged 13. It's one data set from a company with a stake in the topic, so treat it as a hint. Our read is that it points the same way as everything else on this list. Cut whatever doesn't help the buyer decide.
Sending it and waiting
The proposal is one step in the deal. Agree on a review call before you send it, and plan follow-ups that give your champion something useful. We wrote more on how to follow up on a proposal.
Generic proof
"Trusted by industry leaders" and a strip of logos tell the buyer you've worked with other companies. They say nothing about whether you can handle this buyer's problem. Pick the one or two past clients whose situation looks most like this buyer's, and put them next to the part of the plan they prove. See where case studies in a proposal do the most work.
Leaving the risks unsaid
Every buyer has a worry they haven't said out loud. Skipping it won't make it go away. Name the risks that apply to this deal, like a tight timeline or a complicated handoff, and say how you'll handle each one. A seller who names the risk first looks like someone who's done this before.
Why sales proposal mistakes are hard to spot
Most of these sales proposal mistakes are hard to see from the inside. The team writing the proposal was on every call. They know the buyer's problem, the context behind each line and what the price includes. Reading the draft, they fill in every gap without noticing.
The buyer's CFO wasn't on those calls. Neither was legal, or the executive who signs. They read only what's on the page. That's why a proposal that feels clear to the seller can read as vague, long or confusing to the people deciding. The fix is to read it as someone who missed every meeting, or better, to hand it to someone who did miss them. It's also why we build each proposal from the discovery notes outward. The notes keep the buyer's own words and priorities in front of us the whole time.
Questions we hear about proposal mistakes
What's the most common sales proposal mistake?
In our experience, it's writing the proposal around the seller. Company history up front, features ahead of outcomes and a structure that follows how the seller thinks about the product. Almost every other mistake on this list grows out of that one.
Can a great proposal save a deal that's going badly?
Rarely on its own. A proposal can't fix a bad fit or a price that's way off. What it can do is keep a good deal from slipping away because the people who decide couldn't follow the case.
How do you catch these mistakes before sending?
Give the proposal to someone who wasn't on any of the calls and ask them three things. What's the buyer's problem, what are we proposing and what does it cost? If they can't answer all three in a couple of minutes, it isn't ready.
The short version
Most of these mistakes come from the same habit, building the proposal around the seller. Build it around the buyer instead, and most of this list fixes itself.
If your next big deal deserves more than the template, see the work or start a proposal.
