Create reusable templates

Start with one template per deal type, not per customer. Most small businesses need two or three: a standard project or subscription, a larger or custom engagement, and a renewal or add-on. More than five templates usually means you are copying instead of standardising.

The content of a proposal, such as scope, options and acceptance, is covered in How to build proposal templates. Here we focus on making it reusable in the tool.

Open your best recent proposal and highlight every line in two colours. Fixed text stays identical in every proposal: company background, how you work, terms, legal wording. Variable text changes with the deal: the customer's name and situation, the problem in their words, the scope and the price.

Aim for about two thirds fixed. Too little fixed content and you save no time. Too much and the proposal reads like a brochure.

Merge fields pull data from your CRM into the document. At minimum, set up:

• Contact first and last name.
• Company name.
• Deal name and value.
• Deal owner's name and email.
• Proposal date and expiry date.

Tools such as PandaDoc, Proposify, Qwilr and Better Proposals connect to CRMs such as HubSpot. Check what your plan supports before you design around it. If your CRM holds a field that the team keeps filling in by hand, such as the customer's main goal, map that one too.

Put pricing in a table that the tool calculates, not in text. Add each standard item as a line with a fixed price, and mark extras as optional so the customer can tick them. Include quantity and discount fields. A calculated table removes arithmetic errors and keeps totals consistent between the proposal and the invoice.

Save sections you reuse as blocks: case studies by industry, team bios, a security statement, a standard timeline. A rep then assembles a proposal by choosing blocks instead of copying text from an old file. Name blocks clearly, such as "Case study, logistics" or "Timeline, 6 weeks", and give each one an owner who keeps it current.

Decide who can send what. A common rule: any discount above ten percent, or any change to the standard terms, needs a manager's approval before sending. Set this up in the tool so it is automatic rather than a Slack message someone forgets. If your tool does not support approvals, keep a rule in writing and ask for a review before sending.

Attach the e-signature step to the template, using the built-in signing in your proposal tool or a separate one such as DocuSign. Details are in Set up e-signatures and contracts. Turn on notifications for opens and signatures, and set a reminder to the owner when a proposal has not been opened after three days.

Create a fake deal in your CRM with your own email address. Generate a proposal from each template, send it, open it on a phone, sign it and check that every merge field filled in. Fix anything that shows a blank, a wrong name or a broken layout. Do this before the team uses the template, and again after every change.

Give each template a version number and a review date. Review them each quarter: update prices, case studies and terms. One person owns the library. When a rep asks for a custom change, decide whether it belongs in the template or stays one-off.

• Copying an old proposal instead of using the template, which leaves the previous client's details in.
• Building twelve templates before using one.
• Putting prices in free text.
• Skipping the dummy test.
• Having no owner, so the library goes out of date.

A standard proposal goes out within an hour of the qualifying call. Reps no longer ask for the latest version. You see no wrong names or leftover figures in sent proposals. You can see in How to track proposal performance that more proposals are opened and signed.