Is the goal clear enough to choose the work to propose?
The goal is sufficiently defined when you can explain the change the customer wants and why the proposed work could contribute to it. If you only have a broad request, context is missing. Confirm the priority and current situation before choosing deliverables that might address a different need from the one that exists.
A request to “improve our digital presence” can conceal concerns about awareness, enquiries, sales or organisation. Immediately preparing a package of website, ads and content makes the document longer without clarifying which need takes priority. The proposal ends up reflecting what the provider knows how to sell rather than what the customer needs.
Ask a question that helps make a decision: what would have to change for the customer to find this work useful? Then ask for an example of the current situation. You do not need every operational detail, but you should be able to explain the relationship between the need and the recommended intervention.
This preparation complements what you should know about a customer before accepting a project. Here the criterion is more specific: is there enough information to write a proposal the customer recognises as a response to your conversation, without filling the essentials with assumptions?
To prepare your next step, explore The B2B sales process.
Which gaps make the scope unreliable?
A gap is decisive when its answer could change the effort, responsibilities or inclusions. Identify dependencies such as access, existing systems, materials and third-party participation. If you cannot estimate the impact of that uncertainty, clarify it before presenting a delivery commitment with conditions that appear definitive to the person receiving your proposal.
Imagine a hypothetical integration between a website form and a CRM. The idea seems simple, but you do not yet know who controls the form, which data should enter or how the team handles duplicate contacts. Each answer could change the work required and how delivery should be verified.
Writing “integration included” does not resolve those questions. It may simply move them to a point after the project has started. A useful proposal explains the intended process, exclusions and conditions the customer must provide, using language that both sides can understand and apply to the work.
Not every uncertainty requires delaying everything. You can define an initial diagnostic phase with its own deliverable and clear limits. Avoid presenting complete implementation as settled when you still need that investigation to know what you will build and how much work it involves.
Do you know how the decision will be made?
Before sending, understand who will assess the proposal, who participates in the decision and which criteria will be used. The person you spoke to may need to discuss it internally. Prepare information that can circulate clearly and agree how questions will be resolved, without assuming a positive conversation amounts to authorisation to proceed.
Asking about the decision process does not mean requiring the entire management team at an initial meeting. It means understanding the document's route. If the recipient needs to explain the project to someone else, the objective, scope and conditions must remain understandable without you in the room.
It also matters what is being compared. A proposal to deliver work includes different responsibilities from one offering advice alone. If the customer is comparing alternatives, clarify those differences without disparaging competitors or assuming every offer solves the same problem in the same way.
The proposal stage belongs to the work of turning leads into customers in a service business. The document should help a decision, and that usefulness depends on knowing the decision-maker's questions. More pages about your company cannot compensate for failing to answer the main concern.
Have the necessary resources been secured?
Confirm the availability of the people, materials and information on which delivery depends. Check whether the desired schedule fits those conditions too. A proposal can have a clear objective and still be premature if execution depends on an essential resource whose availability date remains unknown to everyone involved in the project.
If the work requires content approval, identify who approves it and how much availability they have. If it depends on a supplier, clarify what that supplier must provide. An enthusiastic contact may not control those conditions, even when they want to start as soon as possible.
Do not turn a desired date into a promised date without understanding dependencies. You can indicate an estimated duration from the point when conditions are met. Explain what triggers the start and how delayed information affects the sequence, without hiding those conditions in a note that is difficult to find.
One alternative is to organise the project's first month around priorities. Some tasks can progress while others await their requirements, provided that separation makes sense and is agreed. Dividing the work should clarify execution rather than disguise the fact that the main part remains blocked.
What can you send while information is missing?
You can send a summary of your current understanding, the open questions and a preliminary indication of the work that might be possible. If you include estimated prices or timings, identify their assumptions. The recipient should understand they are receiving guidance to continue the conversation, rather than a final proposal ready for approval.
That summary can begin with what is already aligned: need, priority and people involved. Then present the questions preventing you from finalising scope and identify who can answer each one. A specific request is easier to resolve than a general statement that you need more information.
When the approximate investment matters in deciding whether to continue, you can share a substantiated range. You need not require lengthy investigation to reveal an already obvious budget mismatch. The range should explain what it covers and what could still change the estimate once the remaining information arrives.
Define the next contact or a condition for resuming too. If the information does not arrive, the opportunity can be explicitly placed on hold. This prevents sales from treating silence as rejection and the delivery team from reserving capacity for work that is not yet ready to be contracted.
How do you recognise that the proposal is ready?
A proposal is ready when you can connect need, delivery, price, responsibilities and next steps without concealing decisive gaps. The customer should understand what they are assessing and what remains conditional. Review the document from that perspective instead of using its length or visual presentation as a sign that it is ready.
Read the summary as though you had not attended the meeting. Is it clear why the work was proposed, what it includes and how it will be monitored? Do relevant conditions appear beside the decisions they affect? Someone reading only the document should find the essentials without having to guess the context.
A guided presentation may help explain value and answer questions. That does not make sending a written proposal wrong in every case. Choose a format that suits the customer and retain a clear version for reference, particularly when other people are involved in the decision.
Finally, agree when and how you will speak again while respecting the customer's process. Sending fewer proposals without the right conditions may free time to prepare real opportunities more carefully, but the goal is not to maximise a close rate by hiding difficult cases. It is to make commitments both sides understand and can execute.