Sales proposal after a meeting: structure and example

A proposal picks up a specific conversation

After a meeting, clients often receive a general company presentation. It lists plenty of capabilities, but it can be hard to tell which task was discussed and what is included in the price. A useful proposal gives the recipient something they can use to make a decision and share with colleagues.

The transcript helps recover the terms discussed, but it does not produce a cost estimate. Verify prices, timelines, staff availability and scope against the team's current sources. If there is not enough information, name the assumptions or suggest a short clarification phase instead of hiding the gap with a precise figure.

Build the proposal around the client's decision

1. Verify the original task

   Write down the desired change, starting situation and success criterion. Check who raised the need and who decides. Some ideas in the conversation may have been examples or wishes for later. Include only the work actually in scope.

2. Describe the work and deliverables

   Show what the client will receive and which activities are included. Set limits for each deliverable. If you offer several options, compare them on the same criteria so the differences are clear without another call.

3. Link the terms to the scope

   Put cost, timing and dependencies next to the relevant option. Specify what information or actions you need from the client. Explain expected benefits through the agreed use case and avoid unverified claims about effectiveness.

4. Define the next step

   State what the client needs to check or choose. List open questions separately and suggest a way to resolve them. Before sending, verify that the terms are current and follow the team's usual approval process.

Proposal for a small knowledge base

This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.

The proposal should describe a limited deliverable: approved materials for ten situations. Transferring all the company's knowledge and launching a platform should not be included as if they were already discussed.

The terms can specify that timing depends on expert availability and draft review. This example leaves the price open because it must be calculated from confirmed scope. If interviews reveal more situations, discuss them separately.

Working structure for a proposal

For a small task, the template can fit into a few paragraphs. What matters is that the choice is clear.

Recipient and meeting reference:
Client's task:
Proposed deliverable:
Work and materials to deliver:
What is excluded:
Options and differences:
Cost and basis for the estimate:
Timing and dependencies:
What the client needs to provide:
Assumptions and open questions:
Next step and contact:

Review the document before sending

• The client recognizes their task in the first section.
• The cost is tied to a clear scope.
• Dependencies and exclusions are clear without a follow-up call.
• The recipient understands what decision is needed.