Situation First

pitch

The One-Pager That Actually Gets Read

Published · 7 min read

A one-pager is not a short deck. It’s a different artifact entirely. A deck is designed for a room — it assumes someone is narrating it. A one-pager is designed for a desk — it assumes someone is reading it alone, with no context and limited attention, and needs to arrive at a clear picture of what’s being asked without any help.

Most one-pagers fail because they try to be both: the density of a document with the design conventions of a presentation. The result is something nobody reads closely enough to understand and nobody presents clearly enough to persuade.

Who it’s for

Anyone who needs to communicate a proposal, idea, or opportunity in written form to someone who will read it asynchronously — a busy executive, a prospective investor, a potential client, or a senior internal stakeholder who asked for something in writing before a decision meeting.

What a one-pager needs to do in 90 seconds

The average executive reads a one-pager in under two minutes. In that time, they’re evaluating: Is this relevant to me? Does this person understand the situation? Is there a clear ask? Those three questions, in that order.

A one-pager that answers all three clearly and quickly gets a reply. A one-pager that requires them to read all the way through before they understand what’s being asked gets archived.

The structure

Header: three lines maximum

Your name or company name, the date, and the title of the document — which should be the decision or opportunity in plain language, not a project code or marketing phrase. “Proposal: switch to [Vendor] for identity management — decision needed by May 1” is a useful title. “Identity Infrastructure Modernization Initiative” is not.

Opening paragraph: the situation and the ask

The first paragraph of a one-pager should contain two things and only two things: what’s true right now (one or two sentences), and what you’re asking for (one sentence). Not background. Not history. The situation and the ask.

“Our identity provider contract renews in July at a 40% price increase. I’m recommending we migrate to [Vendor] and need a go/no-go decision by May 1 to hit the transition window.”

That’s a complete opening paragraph. The reader knows the situation, the recommendation, and the timeline in four seconds.

The case: three to five bullets, each earning its place

Bullets are appropriate here — not because one-pagers should be bullet-heavy, but because they force compression. Each bullet should carry one piece of evidence or one argument. Not both.

Use this test for each bullet: does it answer one of these questions? Why now? Why this option? Why trust this? If it doesn’t answer one of those, remove it.

Avoid bullets that start with “We believe…” or “Our goal is…” — both are claims about your internal state that the reader cannot evaluate. Bullets should be about the situation, the evidence, or the tradeoffs — things that exist independently of your preferences.

The options and recommendation: what you looked at and what you chose

Even in a one-pager, showing that you considered alternatives before arriving at a recommendation matters. It tells the reader that the recommendation isn’t just the first idea you had.

This doesn’t require a table. One sentence per option considered: “We evaluated three vendors: [A] was eliminated due to SOC2 certification gaps; [B] was competitive but required a full API replacement; [C] meets compliance requirements and uses our existing SSO infrastructure.”

Then one sentence on your recommendation and the most important reason: “We recommend [C] because the migration scope is bounded to two engineer-weeks and eliminates the July cost increase.”

The ask: explicit, timed, and binary if possible

End with what you need and when: “I’m looking for a go/no-go decision by [date] so we can begin the migration planning. If you have concerns that would change the recommendation, I’d like to address them before [date].”

The “binary if possible” note is important: a decision is easier to make when the options are framed as go/no-go rather than “let me know your thoughts.” If there are multiple decision points, make the most important one explicit and put the others in an appendix.

What to leave out

Your company description. If the reader doesn’t know who you are, the one-pager is going to the wrong person.

Background longer than two sentences. Background is what you needed to write the document, not what they need to read it. If you find yourself writing more than two sentences of context, you haven’t found the situation yet.

The methodology behind the recommendation. One-pagers are not research papers. The methodology belongs in an appendix or a separate document. Reference it: “The full cost model is attached — the one-pager reflects the base case.”

Anything that requires a footnote to interpret. If you need a footnote, the sentence isn’t working. Either fix the sentence or remove it.

Format choices that matter

Typography: Readable serif font at 10–12pt for body text. Don’t try to compress by going to 9pt — it reads as desperation. If you need 9pt to fit on one page, you have too much content.

White space: One-pagers with dense margins and no whitespace are cognitively exhausting. Generous margins and line spacing are not wasteful — they’re part of the communication design.

Length: One page means one page. If you’re running onto a second page, you’re writing a two-page document. That’s fine — just don’t call it a one-pager and don’t expect one-pager reading behavior from it.

Version and date: Include both. Decision documents without dates cause confusion when they resurface. “v2 · April 24, 2026” is three tokens of information that save significant confusion.

Worked example structure

Situation First · April 24, 2026 Proposal: migrate identity provider before July contract renewal

Our identity provider contract renews in July at a 40% cost increase ($48k → $67k annually). I recommend migrating to [Vendor] before renewal and need a go/no-go by May 1 to stay within the transition window.

Why this option:

  • SOC2 Type II certified — resolves the compliance gap flagged in January’s security review
  • Uses our existing Okta SSO infrastructure — no new credentials or employee re-enrollment
  • Migration scoped at 2 engineer-weeks based on review of our integration surface
  • Contract locks in current pricing for 24 months; estimated 3-year saving: $58k

Alternatives considered: [A] eliminated due to SOC2 gap; [B] competitive but required full API replacement (estimated 6–8 weeks); [C] recommended for reasons above.

Ask: Go/no-go by May 1. If concerns would change the recommendation, please flag before April 28 so we can address them before the decision point.

Full cost model and vendor comparison matrix attached.

Practice prompt

Take something you’re currently trying to communicate in writing — a proposal, a recommendation, an update that needs a decision. Write it as a one-pager using this structure. Then remove anything that doesn’t answer “Is this relevant to me?”, “Does this person understand the situation?”, or “Is there a clear ask?” Read what remains. If you’re uncomfortable with how brief it is, that discomfort is the point. Trust the reader to ask questions.

← All pitch guides · Guide builder · Resources & checklists