How to Create a One Pager

What is a one pager?

A one pager is a single-page document that combines short text, visuals, and design to explain one product, service, project, or idea fast. Zapier defines it as a single-page document used to boil detailed information down so stakeholders can review it quickly and make decisions, and Johns Hopkins frames it as a concise summary of a problem, why it matters, and the action you want next (Zapier, Apr 17 2026; Johns Hopkins Lerner Center, accessed Jun 25 2026).

That means the job of a one pager is not to say everything. Its job is to answer the 3 questions Johns Hopkins highlights: what is the problem, why does it matter to this reader, and what action should happen next. If your draft cannot answer those 3 questions in one scan, it is still a rough note, not a finished one pager (Johns Hopkins Lerner Center, accessed Jun 25 2026).

When people actually use one pagers

• Company intro: a fast overview for a prospect, partner, or investor.
• Product summary: pricing, use case, proof, and a clear next step.
• Project brief: objective, timeline, owner, status, and decision needed.
• Policy or advocacy brief: issue, evidence, recommendation, and ask.
• Internal alignment sheet: goal, metrics, owners, and deadline.

What should a one pager include?

The most practical structure I found is a 6-part layout from ISTE: recommendation or message, introduction, background, analysis, visual, and conclusion. That matches the 3-part logic from Johns Hopkins: problem, relevance, recommendation. Put together, those sources give you a clean template that works for business, project, product, or policy one pagers without turning the page into a wall of text (ISTE toolkit, accessed Jun 25 2026; Johns Hopkins Lerner Center, accessed Jun 25 2026).

Copy this 6-part one-pager template

Paperflite's 2026 guide matches this structure closely. Its search snippet says a one-pager should include a clear headline, problem statement, solution overview, visual proof such as stats or testimonials, differentiation, and a CTA. That is a near-perfect business version of the ISTE model, so you do not need to invent your own structure from scratch (Paperflite search result, Mar 4 2026; accessed Jun 25 2026).

What to cut

• Long paragraphs. ISTE explicitly recommends bullets instead of lengthy paragraphs.
• Full history lessons. Keep only the background needed to understand the decision.
• Every argument and counterargument. ISTE says not to include lengthy analysis of all research.
• Multiple asks. If you have 2 different asks, make 2 one pagers.
• Decorative visuals with no job. Every chart, icon, or image should support the message.

How do you create a one pager step by step?

The fastest build path is 7 steps: define the audience, write the one-line outcome, collect proof, choose a 6-part structure, draft in bullets, add one visual, and cut until it fits on one page. This workflow is based on the recommendation-first approach in ISTE, the problem-relevance-action logic from Johns Hopkins, and the strong visual hierarchy seen in Zapier's 2026 examples (ISTE, Johns Hopkins, Zapier; accessed Jun 25 2026).

Use this exact workflow

• Step 1: Pick one reader. Write the audience at the top of your draft: buyer, manager, investor, policymaker, client, or team lead.
• Step 2: Write one outcome sentence. Example: Approve a 30-day pilot. Book a demo. Fund the next phase. Vote yes. Without this line, your page will drift.
• Step 3: Gather 3 proof points. Use 1 to 3 numbers, short examples, or customer quotes. More than 3 usually turns into clutter.
• Step 4: Fill the 6 blocks: headline, problem, solution, proof, visual, CTA.
• Step 5: Convert paragraphs into bullets. ISTE specifically recommends bullets over long paragraphs.
• Step 6: Add one visual that replaces text, such as a 3-step process strip, comparison box, or mini chart.
• Step 7: Edit for fit. Delete anything that does not support the outcome sentence.

Here is a simple business example. Reader: a sales manager. Outcome: approve a new one-page product leave-behind. Proof: 3 customer use cases, 2 testimonial quotes, and 1 pricing summary. Visual: a 3-column comparison. CTA: book a 20-minute review. That is enough to make a complete draft without writing a long memo.

A fill-in prompt you can use before you design

• Audience: who will read this first?
• Decision: what do I want them to do after 1 minute?
• Problem: what pain, gap, or opportunity matters to them?
• Solution: what am I proposing?
• Proof: which 3 facts or examples make this believable?
• CTA: what exact next step should appear at the bottom?

How long should a one pager be?

Exactly one page. That sounds obvious, but many drafts fail because they are really 2-page notes squeezed into one screen. A practical target is 6 content blocks and 3 proof points. That gives you enough substance to be credible and enough restraint to stay readable. Johns Hopkins and ISTE both push brevity, and ISTE specifically says to keep the document brief and avoid lengthy analysis (Johns Hopkins and ISTE, accessed Jun 25 2026).

How to make a one pager fit

• Limit yourself to 1 headline, 1 problem statement, 1 solution, 1 proof cluster, 1 visual, and 1 CTA.
• Use 2 to 4 bullets per section instead of dense paragraphs.
• Keep proof to 3 items. If you have 8 stats, pick the best 3 and move the rest to a backup doc.
• Use one main visual, not a gallery.
• If you need more than 1 decision or more than 1 audience, split it into 2 one pagers.

Zapier's April 2026 roundup is useful here because the strongest examples are not text-heavy. Threekit is highlighted for strong visual hierarchy and minimal copy. CAT is highlighted for callout boxes and illustrations that manage text density. Tegria is called out for a clear 4-step process and credibility statistics. The pattern is consistent: better one pagers show structure, not just text (Zapier, Apr 17 2026).

What does a good one pager look like?

A good one pager looks like a decision tool, not a brochure. It has a clear top section, a visible proof area, and an obvious next step. Zapier's 2026 examples give useful patterns: Threekit uses minimal copy and strong hierarchy, SAP uses customer success stories and colorful stats, and Tegria uses a 4-step process plus credibility numbers. Those are not decoration choices; they are clarity choices (Zapier, Apr 17 2026).

Three layouts that work

If you are stuck, choose one of the 11 types Zapier lists and match your page to the job: company, startup, pitch presentation, strategic plan, product, report, investor update, employee orientation, B2B, marketing, or consulting. Choosing the type first saves time because it tells you what proof belongs on the page and what can be cut (Zapier, Apr 17 2026).

A quick visual checklist

• Can I understand the page from the headline and subhead alone?
• Do the 3 most important facts stand out without reading every line?
• Is there one clear visual instead of several competing graphics?
• Can the reader see the CTA in one glance?
• Would this still make sense if I had only 60 seconds to scan it?

What are the most common one-pager mistakes?

Most weak one pagers fail in predictable ways: they try to say too much, bury the ask, or swap proof for generic claims. ISTE warns against lengthy analysis and recommends bullets over long paragraphs, while Johns Hopkins keeps the structure tightly focused on problem, relevance, and recommendation. The lesson is simple: if the page is hard to scan, the message is hard to trust (ISTE and Johns Hopkins, accessed Jun 25 2026).

Fix these 5 mistakes before you share the page

A practical editing pass is to read the page once and mark only four things: headline, proof, visual, CTA. If one of those is missing or weak, the draft is not ready. This test works because the best 2026 examples in Zapier's roundup all make those elements visible without forcing the reader to decode dense copy (Zapier, Apr 17 2026).

Frequently asked questions