Proposals guide
12 Proposal Mistakes That Slow Down Decisions
A polished proposal can still fail if it makes the customer work to understand the decision. Use this list as a pre-send review and as a diagnostic when proposals receive many questions, revisions, or no response.
Short answer
The most damaging proposal mistakes are weak discovery, generic copy, vague scope, hidden exclusions, too many choices, confusing price, unsupported proof, buried next steps, inconsistent numbers, poor mobile usability, silent revisions, and unplanned follow-up.
Key takeaways
- Most proposal problems begin before writing, during weak discovery.
- Clarity about boundaries builds more trust than vague comprehensiveness.
- One obvious decision path beats a decorative final page.
- Version and delivery controls are part of proposal quality.
Step-by-step process
- 1
Run a content check
Verify the customer, outcome, scope, quantities, assumptions, exclusions, price, and timeline against discovery.
- 2
Run a decision check
Confirm options are meaningful, risk is addressed, proof is relevant, and the next action is obvious.
- 3
Run a consistency check
Compare totals, taxes, deposits, dates, terms, names, and attachments across every section.
- 4
Run a usability check
Review the proposal on a phone, test links and signature actions, and confirm readable headings and line wrapping.
- 5
Run a record check
Confirm delivery is real, the sent version is retained, and revisions will not overwrite history.
Mistakes 1–4: relevance and scope
1. Starting with company history instead of the customer's outcome. 2. Reusing generic discovery language. 3. Describing activity instead of deliverables. 4. Hiding assumptions and exclusions until the terms page.
Mistakes 5–8: choice, price, and proof
5. Offering too many nearly identical options. 6. Showing a lump sum with no recognizable scope. 7. Exposing an internal cost sheet instead of customer value. 8. Using broad claims or testimonials that do not reduce the buyer's actual risk.
Mistakes 9–12: decision and operations
9. Inconsistent totals, dates, or customer names. 10. A next step buried in a paragraph. 11. A document that breaks on mobile. 12. Silent edits, fake sent statuses, or missing revision history after delivery.
Action checklist
- Customer-specific opening
- Measurable scope
- Visible assumptions
- Meaningful options
- Recognizable pricing
- Relevant proof
- Consistent totals
- Single next step
- Phone tested
- Delivery confirmed
- Revision history protected
Frequently asked questions
Why are customers not responding to my proposals?
Possible causes include poor qualification, unclear value or scope, unresolved risk, confusing price, missing stakeholders, bad timing, delivery failure, or an undefined next step. Diagnose before sending more reminders.
Can a proposal be too detailed?
Yes. Detail becomes harmful when it obscures the decision. Keep essential commercial information in the main flow and move technical support material into labeled sections or appendices.
Should I reuse proposal copy?
Reuse accurate structure and approved explanations, but customize the customer problem, scope, assumptions, options, price, proof, and next step.