---
title: "One-Pager Writing"
description: "One-pagers are the highest-impact document format in business: a single page that earns a meeting, secures a budget, aligns a partner, or briefs an exec in under three minutes."
---

# One-Pager Writing

## Overview

One-pagers are the highest-impact document format in business: a single page that earns a meeting, secures a budget, aligns a partner, or briefs an exec in under three minutes.

## Core Concepts

### 1. The no-second-page discipline

A one-pager fits on one page. The moment you flow to page 2, the document is now a half-finished two-pager. Everything else in this skill exists to enforce this rule.

Practical effects:
- Cut by 30-50% from your first draft. Always.
- Drop full sentences for fragments where fragments work.
- Move evidence to an appendix link, not a footer.
- If three things won't fit, you have three things — not one.

### 2. Above-the-fold visual hierarchy

The reader scans before they read. What lives above the fold:

1. **Headline** — the one-line value prop, written in the reader's language.
2. **Subhead or value-prop sentence** — what changes for the reader if they say yes.
3. **The "if you only read one line" sentence** — bolded, set off visually.
4. **A visual anchor** — chart, screenshot, diagram, photo, or large pull-quote.

### 3. The "if you only read one line" pattern

Every one-pager has one sentence the reader must take away. Find it. Bold it. Place it above the fold. Repeat it in different words at the end.

```
Bad:  "Our new initiative aims to improve customer engagement
       through innovative cross-functional collaboration."

Good: "Cutting onboarding from 12 days to 3 will unlock $2.4M in
       Year 1 retention. We need $180K and 2 engineers for 6 weeks."
```

### 4. Headline + value-prop pattern

```
Headline:    Atlas Migration Acceleration Program
Value prop:  Cut customer migration time from 90 days to 30,
             at no incremental cost to your team.
```

### 5. The Amazon 1-pager and the PR/FAQ lineage

The Amazon 1-pager / PR-style opener:
1. **Heading**: the product or initiative name.
2. **Subheading**: who it's for, in their language.
3. **Summary paragraph (3-4 sentences)**: what it does, who benefits, why now.
4. **Problem paragraph**: the customer's status quo.
5. **Solution paragraph**: how this changes the status quo.
6. **Quote (optional)**: an executive or customer making the value claim concrete.
7. **Call to action**: what the reader does next.

Two non-negotiables: written as full sentences; written as if the product already launched.

### 6. Bullets vs paragraphs

**Use paragraphs when:** The reader needs to see how ideas connect; describing a customer's strategic status quo; Amazon 1-pager opener.

**Use bullets when:** Listing 3-7 parallel items; scannable facts; the reader is an exec who triages.

Heuristic: paragraphs for the upper half (the narrative), bullets for the lower half (the facts and the ask).

### 7. Section budget for a single page

A single page gives you roughly 550-650 words of usable real estate:
- **Headline + value prop**: 20-30 words
- **Above-the-fold callout**: 15-25 words
- **Body — problem / context**: 80-120 words
- **Body — solution / approach**: 100-150 words
- **Body — outcomes / proof**: 80-120 words
- **The ask**: 30-50 words

### 9. The five canonical species

- **Account brief** — for an internal audience to brief before a customer meeting.
- **Project pitch** — to get funding or headcount.
- **Product one-pager** — for stakeholders evaluating a product.
- **Sales-enablement one-pager** — for sellers to use in front of buyers.
- **Amazon 1-pager / PR-FAQ opener** — for internal alignment on a new product.

### 10. The ask, the owner, the next step

Every one-pager ends with:
1. **The ask** — what specific thing do you need from the reader. A verb with an object.
2. **The owner** — who runs this, with name, role, contact.
3. **The next step** — when, where, what format.

These three sentences are the entire reason the one-pager exists. Never cut these.

## Templates

### Template: Account brief

```
[ACCOUNT NAME]  |  Brief for [Reader Role]
ARR: $X.XM  •  Renewal: [date]  •  Owner: [name]

ONE-LINE STATUS  >>>  [Account] is at [color/state] heading into [event].
The single most important thing is [X].

CONTEXT
[80-120 words on relationship history.]

TOP 3 RISKS                        TOP 3 OPPORTUNITIES
1. [risk]                          1. [opp]
2. [risk]                          2. [opp]

THE ASK
What we need from [reader]: [one-sentence verb-object ask].

NEXT STEP
[Meeting / decision / intro], owned by [name], by [date].
```

## Anti-Patterns

- **The 1.5-pager** — runs onto a second page by half a paragraph.
- **The mystery headline** — "Project Phoenix: A New Approach." No value visible.
- **The ask buried at line 47** — the ask should be visible above the fold.
- **The "alignment" ask** — "We're seeking alignment on..." No verb, no object.
- **The missing owner line** — the page is anonymous.
- **The four-CTA ending** — list more than two CTAs and readers pick zero.

## References

- [Working Backwards — Amazon's Six-Page Memo culture](https://amazonchronicles.substack.com/p/working-backwards-dave-limp-on-amazons)
- [How to Write a Product One-Pager — ProductPlan](https://www.productplan.com/learn/product-one-pager)