Proposals and one-pagers
Why a template that is 90 percent filled produces proposals that are 90 percent generic, and why this is the only content type where going stale becomes a contractual problem.
The operational shape
- Trigger
- A deal shape recurring often enough to be worth templating
- Reads
- Value propositions and the offer structure, from decisions. Cleared proof and numbers.
- Cadence
- Template maintained; instances per deal
- Gate
- Approve before publish for the template; instances follow the sales boundary
The failure is easy to spot once named: a template that is 90 percent filled produces proposals that are 90 percent generic. Every deal-specific section that ships pre-written is a section somebody will leave as-is under time pressure, and the buyer reads a document assembled for somebody else.
A good template makes the reusable parts genuinely reusable and leaves the specific parts obviously, uncomfortably blank.
The operational shape
Trigger. A deal shape recurring often enough to template. Templating a shape that has happened twice produces a template for a pattern that does not exist yet.
Reads. Value propositions and the offer structure from decisions. Cleared proof and numbers.
Cadence. The template is maintained; instances are per deal.
Gate. Approve before publish for the template. Instances follow the sales boundary — content owns the reusable asset, sales instantiates and sends.
What good looks like
The blanks are conspicuous. A placeholder that reads like finished prose gets shipped as finished prose. One that visibly demands the deal's specifics gets filled, because leaving it is worse than filling it.
Every claim inside traces to the value proposition bank. A proposal is where messaging quietly forks — a rep rewrites a claim for one deal, it works, and now two versions exist. Claims come from the bank or they do not go in.
The one-pager is written for the person who is not in the room. Its reader is an economic buyer or a colleague being briefed second-hand, and it has to survive being read without context. That makes it harder than the proposal and it usually gets a fraction of the effort.
Terms and numbers come from one place. Pricing, term length, and anything contractual are mirrored from wherever they are owned, never retyped. Retyping is how two proposals go out the same week with different numbers.
When it goes stale
This is the only capability here where staleness becomes a contractual problem rather than a credibility one.
Three triggers. Pricing or terms changed and the template did not, so a proposal goes out offering something the company no longer offers — and a signed one is binding regardless of the mistake. The offer structure changed, so the template describes packaging that has been retired. A claim inside was superseded in the value proposition bank and never propagated, which is the silent version.
The structural fix is that nothing contractual lives in the template as text. It is mirrored, so a change at the source invalidates the copy rather than being quietly outlived by it.
What it feeds
- Sales decks — the same argument, arranged for a conversation rather than a document
- Meeting prep — the proposal is usually what the meeting is about
- Learnings — which sections get rewritten every time, which is the template telling you it is wrong
Frequently asked
- Who fills in a proposal template?
- The sales side, per deal. ContentOS owns the reusable asset; sales instantiates and sends it. That split is decided, and it is what keeps one source of truth for the claims inside.
- How much of a proposal should be pre-written?
- The parts that are the same in every deal, and no more. A template that pre-fills the deal-specific sections produces proposals that read as generic, because they are.
- What is the difference between a proposal and a one-pager?
- A one-pager is for someone who has to explain the purchase to somebody else. A proposal is for the person making it. The one-pager is usually the harder document and gets the least attention.