How to spot vague promises in a business proposal
Translate broad proposal promises into testable deliverables, assumptions and written clarifications before committing.
A proposal can sound convincing while leaving the important work undefined. Phrases such as “fast delivery”, “full support” and “better results” need a follow-up question: what will happen, by when, and how will we know? You do not need to distrust every broad phrase. You do need to turn material promises into decisions that both sides can manage.
Translate adjectives into deliverables
Underline claims that could affect your choice. For “fast delivery”, ask for milestones, your own input dates and the meaning of “complete”. For “ongoing support”, ask about hours, channels, response, exclusions and duration. For “improved performance”, ask which measure will change, what the starting position is and who controls the factors involved.
A proposal for a website redesign might promise “search-friendly pages”. That could refer to basic page titles, a content plan or ongoing search work. Ask the supplier to list actual tasks and the files or settings you will receive.
Find the assumptions hidden behind the price
Look for statements that begin “subject to”, “assuming” or “where possible”. They can be reasonable, but they change what the quote covers. Ask what happens if the assumption is wrong. Who pays for extra work? Is a revised schedule required? Do not count an optional feature as included because it appears elsewhere in the sales material.
Compare the final proposal with the brief. Mark each required outcome as addressed, excluded or unclear. A supplier who identifies an important gap may be helping you make the project more realistic. What matters is that the gap is visible before approval.
Ask for a written clarification
Send short, neutral questions. “What does your support package cover for a broken enquiry form?” is more useful than “Can you guarantee good support?” Request that material answers appear in the agreed scope or schedule. Keep version numbers and dates so a later revision does not quietly drop an important point.
You can make this process consistent with a like-for-like proposal comparison. The aim is to judge evidence and fit, not the supplier's confidence in a presentation.
Test one promise against a real decision
Choose the claim that most influences your decision and imagine the work did not meet your expectation. What evidence would show whether the promise was met? If neither side could answer, rewrite the promise. “Improved customer experience” might become a list of user tasks to test before and after launch, together with the work the supplier will perform. The supplier need not guarantee every business outcome, but it should be able to describe its contribution and how progress will be reviewed.
Frequently asked questions
Is vague language always a warning sign?
Not always. Early proposals may leave room for discovery. A material promise should become specific before you commit to a price or outcome.
What if the supplier says a result cannot be guaranteed?
Ask what work they will perform, which factors they control and how progress will be reported. Honest limits can be useful evidence.
Should I reject a proposal with many assumptions?
Not automatically. Check whether the assumptions are reasonable, visible and manageable. Unpriced consequences are the larger risk. Ask for the cost and timing effect if a key assumption proves wrong.
HELP US IMPROVE
Was this article useful?
Your feedback helps shape future coverage.