A Proposal Readiness Checklist Before You Send the Offer

Understand the situation before responding

Write down the problem in the buyer words, the consequence they recognise and what they want to change. Check who owns the issue, who approves spend and whether budget has been discussed. You do not need perfect information, but you do need to know which assumptions matter. A prospect asking for a document may want an estimate or market comparison rather than be ready for a purchase decision.

An example message to adapt

Before I prepare the full proposal, can we confirm the outcome you need, who will review the options and what timing is realistic? I also want to be clear about the scope and the information your team can provide. That will help me send something relevant rather than a document built around guesses.

Illustrative teaching example. Replace the prompts with buyer-confirmed facts; this is not a client conversation, claimed result or message to send automatically.

Prepare a useful next action

Use a brief checklist: confirmed problem, intended outcome, scope boundaries, client dependencies, budget status, decision roles and next review step. Mark unknown items explicitly. Where an unknown materially affects feasibility or price, resolve it before offering a firm commitment or provide a clearly labelled estimate. Agree what happens after the proposal arrives, including whether a review conversation would be useful. Do not demand unnecessary confidential information as a qualification ritual.

Record the decision and its limits

Choose between sending a scoped proposal, providing an indicative estimate, offering a defined discovery step or pausing. Explain the reason to the buyer. If they will not discuss any requirements, decide how much speculative work you are prepared to do. A shorter, honest offer can be more useful than a polished document that assumes authority, timing and budget. Review the checklist again if the project changes.