Sending a proposal is an action. Agreeing to evaluate it is progress.

Imagine a proposal that is finished, formatted and sent. The opportunity moves forward in the seller’s system. Nothing in the buyer’s week has changed.

A LinkedIn post by sales adviser Aaron Evans questions the habit of treating a sent proposal as evidence of a qualified opportunity. It is an argument about sales practice, not a measured explanation for every stalled deal.

Ask the buyer what they need to decide after reading the document. A price range may let them rule out an unaffordable project. A scoping note may let two colleagues agree on the work. Write for that decision before choosing the template.

Three documents for three different conversations

Imagine a fictional founder asking a software-services firm what a project might cost. They have not settled the requirements and need to decide whether further investigation is worthwhile.

A bounded estimate with clear assumptions can help. A formal proposal pretending the scope is settled cannot create that certainty. Withholding all pricing until a long discovery process may also make a simple early decision unnecessarily difficult.

Now imagine the founder has identified the problem but the team disagrees about what work belongs in the first phase. A short scoping note may be more useful than a polished commercial document. It can show the options, exclusions and questions that need agreement.

Finally, suppose the buyer has agreed what they want evaluated and who will review it. A proposal can describe the work, responsibilities, commercial terms and decision process in enough detail to support that review.

These are illustrative situations, not mandatory stages. A simple purchase may need very little documentation. A complex process may require a formal response before the seller can speak with every stakeholder. Fit the document to the actual buying process.

Ask what will happen after it arrives

Before writing, ask the buyer how they plan to use the document. Who will read it? What decision should it support? Which uncertainties must it address? Is there a review date or a dependency?

You do not need to turn those questions into an interrogation. A short exchange can reveal whether you are preparing a budgeting aid, a comparison, an approval request or a response to a formal procurement requirement.

Record what the buyer says. “Send something over” may mean they want information. It does not necessarily mean they have agreed to evaluate a purchase.

If they do not know the next step, help make it clearer without pretending it has been agreed. The champion business-case guide can help when the missing step is an internal explanation of the decision.

Write the assumptions where the reader needs them

A proposal should distinguish the agreed problem from the seller’s suggested approach. Put material scope assumptions beside the relevant work and price, rather than hiding them in a distant qualification.

State what the buyer needs to provide and which decisions remain with them. If access, data or specialist review is required, explain how that affects the proposed sequence. Do not promise a delivery date that depends on an unconfirmed start condition.

Keep capability statements accurate. A proposed investigation should not be described as proof that a solution will work. A possible future feature should not appear among available functionality.

The buyer should be able to identify both the offer and the conditions under which it makes sense.

Record evidence of progress separately

Sending the proposal is an event worth recording. Buyer activity is a separate record: a review arranged, a question returned, a stakeholder introduced or an explicit decision made.

Do not replace one with the other merely to make the opportunity look further along. At the same time, do not invent a rigid universal rule that every proposal requires the same approvals. Your stage definitions should reflect your actual sales process and distinguish seller actions from buyer commitments.

If the document receives no response, return to the agreed purpose and next step. The pricing follow-up guide offers a way to investigate the gap without assuming that price caused it.

RevQ describes drafting proposals and follow-ups from conversation context. The useful test is whether the draft answers the buyer’s current question and preserves what remains unagreed.

Before sending, read the opening page as someone who missed the sales call. Can you tell what is being offered, what remains uncertain and what decision the document asks you to make? Fix whichever answer is hardest to find.

About this article: AI-assisted writing and editing, informed by the linked public discussion. Illustrative examples are labelled; they are not customer case studies. Read our editorial approach.

Updated October 3, 2026