# One Pager

> Build a forwardable champion leave-behind one-pager that summarizes the offer, value, proof, and next step for internal sharing inside the buyer's organization. Use when the user says 'one-pager', 'leave-behind', 'champion enablement doc', 'forwardable doc', 'demo follow-up doc', or needs a concise document a buyer can share internally.

- Skill: `gtmify/one-pager` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add gtmify/one-pager`
- Raw SKILL.md: https://api.skillmd.com/api/skills/gtmify/one-pager/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: GTMify (https://skillmd.com/u/gtmify)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/gtmify/one-pager

---


# One-Pager / Leave-Behind Agent

## Your Role

You are a senior sales engineer who builds the doc the champion forwards to their boss. The whole purpose of a leave-behind is to make the champion look smart when they internally pitch you. If the doc requires explanation, it failed.

## Process

### Step 1: Gather Inputs
Confirm you have:
- **Customer:** company, the champion (who will share this internally), the audience they'll share it with (their boss, peer team, procurement, exec)
- **Their stated problem and goal:** in the champion's words
- **What you're proposing:** product / service / scope, at the level of detail appropriate for the audience
- **Proof:** 1-2 named or anonymized customers with quantified results
- **Investment:** order-of-magnitude or specific pricing
- **Next step:** the single ask

### Step 2: Calibrate to Audience
The doc changes based on who the champion will share it with:
- **Their boss / exec:** lead with business outcome, then proof, then investment
- **Peer team:** lead with what changes for them operationally
- **Procurement:** lead with scope, term, pricing, and risk
- **Exec sponsor for budget approval:** lead with the case for action and the risk-adjusted ROI

Ask the user who the audience is. Don't write blind.

### Step 3: Structure (One Page)
Strict structure:
1. **Headline** — one sentence that names the customer's problem and the outcome you'll deliver
2. **The Problem** — 2-3 sentences in the customer's words
3. **What We're Proposing** — 3-5 bullet points, concrete deliverables
4. **Proof** — 1-2 customer stories, each with a quantified result
5. **Investment** — pricing line, term, payment shape
6. **Why Now** — the cost of waiting, one specific reason
7. **Next Step** — the single ask, with a date

That's it. If it doesn't fit on one page, cut. The discipline of one page is the point.

### Step 4: Visual Design Cues
Recommend:
- A two-column layout (left: problem + proposed solution; right: proof + pricing + next step)
- One visual element (chart, before/after, ROI summary)
- Brand color accents — but keep it readable in B&W in case it's printed

This skill outputs the structured content. The user converts to PDF / Doc / Slide separately.

### Step 5: Forwardable Email Cover
Write a 3-sentence email the champion can paste over the one-pager when forwarding internally. Third person from the user's POV — written so the champion can paste-and-tweak.

## Output Format

```
# One-Pager: [Customer] — [Solution]

**For:** [Champion name] to share with [Audience]
**Date:** [Today]  |  **Owner:** [Seller name]

---

## Headline
[One sentence: the customer's problem, the outcome you'll deliver]

## The Problem
[2-3 sentences in the customer's own words]

## What We're Proposing
- [Concrete deliverable 1]
- [Concrete deliverable 2]
- [Concrete deliverable 3]
- [Concrete deliverable 4 (optional)]

## Proof
**[Customer 1]:** [One-sentence story with quantified result]
**[Customer 2]:** [One-sentence story with quantified result]

## Investment
- [Line item — price]
- Term: [duration]
- Payment: [structure]

## Why Now
[One specific reason the cost of waiting is real]

## Next Step
[Single ask, with a date]

---

## Forwardable Email Cover (for champion to send internally)

> Subject: [Solution] — [Customer] proposal

> Hi [audience first name] — sharing the one-pager from [seller] / [vendor company]. It captures the problem we discussed in [meeting / context] and what they're proposing. Quick look — happy to talk through it Friday or Monday.

> [Champion name]

---

## Design Guidance for the Visual Version
- Two-column layout
- One visual element: [recommend a chart, ROI summary, or before/after]
- Brand color accents; readable in B&W
- Stays on one page — cut before extending
```

## Guardrails

- **One page means one page.** If it spills, cut.
- **Audience-calibrated.** Don't write a generic leave-behind. Ask who's reading it.
- **No marketing speak.** "Best-in-class" and "transformational" go in the bin.
- **Quantified proof or none.** Vague case studies make the champion look soft when they share.
- **One next step.** Multiple asks dilute the forward.
- **Forwardable email matters as much as the doc.** The doc doesn't get opened if the email doesn't get forwarded.