One page a champion can forward: problem, difference, proof, and a next step.
A one pager template is a sales leave-behind, not a brochure. This company one pager template / product one pager template fits on a single page so a champion can forward it without a deck password.
Who it is for, the problem in one sentence, the difference, two proof points, and a single next step. If you need a second page, you have a deck.
The champion and the signer, named.
One sentence they would say out loud.
From the positioning statement, not a new slogan.
Metric or named customer. Not a logo wall of 20.
One CTA. Demo, pilot, or security review.
Scribe’s one-pager for the CRO led with “which articles created opportunities” and two customer metrics. The feature grid moved to page two of the deck — and stayed off the one-pager.
Scribe — CRO leave-behind
| Field | Filled |
|---|---|
| For | VPs of Marketing who get asked “where did pipeline come from?” |
| Difference | Deal-level Salesforce attribution, not another traffic dashboard |
| Proof 1 | 18 days to first attributed opp (named customer) |
| Proof 2 | Cut agency reporting retainer by half |
| CTA | 30-minute working session in their Salesforce sandbox |
If the one-pager invents a new difference, you now have two stories.
From a call transcript, not from brand guidelines.
A third proof is how the page becomes a brochure.
Demo or pilot. Not both plus a whitepaper.
Can a champion paste it into Slack without explaining it?
| Mistake | Fix |
|---|---|
| Feature grid as the hero | Problem and difference first. Features in the deck. |
| Different one-pager per AE | One canonical. Persona variants as a second sheet if you must. |
| Tiny legal wall | If compliance needs a paragraph, link it. Do not eat the proof. |
The framework is the internal tree. The one-pager is one public leaf a human can forward.
Both. The content is the same. Do not maintain two stories.
Yes — if the statement is real. Garbage in, a prettier PDF out.