Start with the customer's situation, in their words

Open with a short summary of what you heard: the problem, what it costs them in time or money as they described it, and what a good outcome would look like. Use the customer's own phrases where you can.

This does two things. It proves you listened, and it gives the decision maker a paragraph they can reuse when presenting internally. If your summary is wrong, you also find out early, which is better than finding out after a rejection.

State the scope plainly

Describe what you will do, what you will deliver and what is not included. Vague scope is the main cause of disputes later, and it also makes your price harder to compare fairly with other offers.

Use plain words instead of internal jargon. If you must use a technical term, explain it once.

  • What will be delivered, in a short list
  • What you need from the customer, such as access, data or approvals
  • What is out of scope, with a note on how extra requests are handled
  • Who on your side will be responsible

Present the price with context

Show how the price is built if that helps the customer understand it, and offer options where genuinely useful. A simple choice between a basic and a fuller version can help a customer feel in control, and it gives you a way to discuss budget without discounting.

Put payment terms, validity of the offer and tax treatment in one clear place. Check any contractual or tax wording with your own adviser, as this article is general guidance only.

Show proof that is relevant and honest

Use evidence that matches this customer's concern: a similar situation you have handled, a sample of your work, or a clear description of your process. Only include claims you can back up, and only name customers who have agreed to be named.

If you do not yet have strong references, a well-explained working method and a small pilot option can build confidence better than inflated claims.

End with a next step and a date

The last page should make the decision easy: what the customer needs to do to proceed, by when, and what happens after they say yes. For example: 'To start in the first week of next month, we need approval by the 20th. On approval we will schedule a kickoff call within three working days.'

Offer to walk through the proposal on a call. Many proposals are never read closely, and a fifteen-minute walkthrough often surfaces objections that would otherwise stay silent.

Keep it short and make it easy to forward

Most proposals are read quickly, often on a phone, and passed to someone else. A short opening page that states the problem, the recommendation, the price and the next step lets a reader grasp the offer in a minute. Details can follow in later pages for those who want them.

Use clear headings and short paragraphs, and save the file in a format that opens anywhere. After sending, note the date you will follow up and keep to it. Then record what the customer said in the deal notes, so that each proposal you write benefits from what you learned from the last one.

A proposal that gets a decision is short, built around the customer's problem, clear about scope and honest about proof. Write it so a person who missed every meeting could still understand it and forward it. If your team's proposals take too long to produce or rarely get a clear answer, a review of your template and process with a sales consultant can be a good place to begin.