Proposal templates

A template is a proposal skeleton: the sections you use every time, in the right order, with the wording that does not change already written and placeholders where it does.

Creating one

Create a template from the template list and build it in the same editor you use for proposals — same sections, same blocks, same settings. A template has its own name and description; the description is what your colleagues see when picking one, so “Retainer, monthly, for existing clients” beats “Template 3”.

Templates can be marked active or inactive. Inactive ones stay in the list for reference but drop out of the picker, which is how you retire last year’s pricing without deleting the history.

Using one

When creating a proposal, pick a template and its sections are copied into the new proposal. From that point the two are independent: editing the proposal never touches the template, and improving the template never rewrites a proposal already sent.

The picker separates your templates from more templates — a catalogue Pural suggests based on the industry you chose during onboarding.

Building one with AI

A connected assistant can build a template for you: run /pural:draft_proposal_template and it asks which sections this kind of offer always needs, which of your blocks or which pages of your own website should feed them, what the price table has to be able to express, and how acceptance should work. Everything client-specific becomes a placeholder.

It can create and edit templates but never delete one — proposals have been built from it, so that stays with you.

Templates or blocks?

Both live in the library, and the difference is scope:

• A template is a whole proposal — use it as a starting point.
• A reusable block is one or more sections — insert it into a proposal you are already writing.

Your standard “about us” belongs in a block. Your standard retainer offer belongs in a template. Putting “about us” in every template means updating it in every template.