How to write a sales proposal clients can sign online

What to put in a sales proposal, how to show pricing clearly, and how online signing speeds up the yes. A practical guide for small sales teams.

A proposal is where a good conversation turns into a decision, and it’s also where a lot of sales stall. The client liked the call, asked for a quote, then went quiet. Often the proposal arrived late, looked like a wall of text, buried the price, or needed printing, signing and scanning before anyone could say yes.

Here’s how we’d build one that gets answered, from what goes in it to how it’s signed and chased.

What a proposal is for

It does three jobs. It shows you listened, reflecting the client’s situation in their words. It makes the offer clear: what they get, what it costs and what happens next. And it makes saying yes easy. A proposal that does all three tends to get signed, and one that only lists prices tends to get compared with a cheaper one.

What goes in it

The detail depends on what you sell, but most good ones run in the same order.

Start with a short cover that says who it’s for and from, the date and a title that says what it’s about: “Proposal for fleet fuel card services” beats “Quotation 4471”. Then a summary of what you heard, two or three short paragraphs on the client’s situation, what they’re trying to achieve and what’s in the way. It’s the most valuable part, because it shows you understood and frames everything after it, and it comes straight from your call notes, which is why recording calls properly pays off here.

Next, what you’ll do, in plain language and focused on what the client gets, not on how clever you are. Put heavy detail in an appendix. Then the price, covered below. After that, what happens once they say yes, with rough timings, which cuts the anxiety that’s behind many delays. Then terms: payment terms, how long the offer’s valid and anything else they have to agree to. Keep these separate from the persuasive part, and have them written or checked by someone qualified, since we can’t give legal advice and what you need depends on what you sell. Finish with one obvious way to accept.

Showing the price

Price is the part read most carefully, so make it hard to misread. Itemise what matters, so the client sees what makes up the total, and show the total prominently so nobody adds it up. Be explicit about what’s included and what isn’t, because surprises later damage trust. Offer two or three options at most, since ten overwhelm people. Say whether VAT is included, which is a surprisingly common source of confusion. Separate recurring costs from one-off ones. And if you take a deposit, say how much and when.

If your pricing depends on a calculation, such as a saving or a volume-based figure, work it out with the client and include the result. In Henkan CRM, custom calculators let reps work out a quote, a saving or a price comparison during the conversation. The result is saved to the lead and can go straight into a proposal.

Make it easy to read

Few clients read every word, so design for skimmers: short sections with clear headings so the price takes seconds to find, plain language, your branding applied consistently, tables for pricing and short lists for steps. Length should fit the deal. A small job needs two pages, not twenty. And it should work on a phone, since a lot of clients read on the move.

That last point is a good reason to send proposals as web pages and not attachments. A web page adapts to any screen. A PDF on a phone is a chore.

Why sign online

The old route is an attachment that’s printed, signed, scanned and emailed back, and each step is a chance to stall. Signing online removes most of them. The client agrees where they read it, decisions come faster because there’s less friction, you’ve a clear record of when it was opened and accepted, and nobody’s working from an out-of-date version.

In Henkan CRM, proposals and e-signature works this way. You build a proposal from sections, add pricing and any calculator results, and send it as a web page. The client reads it on their own device, then accepts and signs by typing their name. You get a signed PDF with a certificate of acceptance, and every step, from sent to viewed to accepted, is recorded on the lead. Whether a typed-name signature is enough depends on the country and the type of agreement, so take advice for your own situation.

If you take a deposit or full payment up front, put it in the acceptance, because fewer steps means fewer drop-offs. A Henkan CRM proposal can ask for a deposit or full payment as part of accepting, and you can send a Stripe or Revolut payment link from a won deal. When the customer pays, the link is marked paid automatically and a note is added to the lead.

Send it fast, then follow up

Speed matters. A proposal sent the same day as the call, while the conversation’s fresh, does better than one sent next week, so keep templates ready and only personalise the details. Henkan CRM starts you from a template with the sections and branding in place, and admins keep the master versions, which also keeps quality consistent whoever sends them. Set an expiry too. A proposal with no end date has no urgency, and admins can choose a default of 14, 30, 60 or 90 days, or none.

Then follow up, and don’t assume silence means no. The usual causes are that it’s sitting in an inbox, the decision needs someone else or there’s one unanswered question. A day after sending, check it arrived and offer to talk it through. A few days later, ask if there are questions. After a week, ask whether timing is the issue. If it’s still quiet, send a final polite note saying you’ll close the file for now. Knowing whether the client has opened it helps enormously: if the status says Viewed you can say “I saw you’d had a look”, and if it doesn’t, the answer may be that they never got it. Follow-up emails and sequences goes deeper, and how to set up a sales pipeline shows where proposals sit among your stages.

Common ways it goes wrong

Starting with yourself instead of the client’s problem. Burying the price. Writing too much, since length isn’t persuasion. Sending late, when momentum has faded. Leaving the next step unclear, so people don’t know how to say yes. Skipping follow-up, when many deals are won on the second or third message. And keeping proposals scattered around inboxes, when keeping them on the lead lets you see where each stands. If you’re choosing a CRM partly for this, CRM for small sales teams covers what else to look for.

Should you send a proposal before a call? Usually not. Have the conversation first, so the proposal reflects it. Should you discount in it? That’s a business decision, but if you do, show the original price, the discount and the total clearly.

To see a proposal built, sent and signed in Henkan CRM, book a demo.

See Henkan CRM set up around how you sell.

Book a demo and we will show you the product with your own sales process in mind.

Book a demo
  1. 01 Book a demo Tell us a little about your business.
  2. 02 See it around how you sell We show you the product with your sales process in mind.
  3. 03 We set it up for you Our team configures your account, from fields and stages to automations.