Guide · July 21, 2026 · 10 min read
How to Make a One-Pager (Structure, a Worked Example, and How to Actually Send It)
A one-pager is a small document that does a lot of work. Done right, it decides whether a prospect books a call, whether an investor opens your deck, whether a partner takes you seriously. Done wrong, it's a crowded mini-brochure that nobody finishes.
This is the document sense of "one-pager" — a single summary sheet you hand to someone. If you landed here looking to build a single-scroll website (Squarespace/Webflow one-page templates), that's a different thing and this isn't it. Everything below is about the sheet: sales sell sheets, startup investor one-pagers, company overviews, and the internal product one-pager.
What is a one-pager (and what is it for)?
A one-pager gives one audience exactly enough to make one decision — and nothing more. It's a filter and a door-opener, not the full story. Its job is to earn the next step: a reply, a meeting, a demo, a forward to the person who actually signs.
The mental model that fixes almost every one-pager: it's a trailer, not the movie. A trailer doesn't show you the whole film. It shows you just enough to make you want to watch. Your one-pager's success metric isn't "did they learn everything" — it's "did they take the next action." Once that clicks, every length and content decision gets easier, because you stop trying to say everything.
You'll see the same object under a dozen names — one-sheet, one-sheeter, sell sheet, sales sheet, leave-behind, fact sheet, product brief, executive summary. Same discipline, different label. What it's for depends on which kind you're making:
- Sales / product one-pager. Hand it to a prospect, or leave it behind after a meeting. It answers: what is it, who's it for, why it beats the alternative, and what to do next. Bottom-of-funnel — the reader mostly knows they have a problem.
- Startup / investor one-pager. The pre-deck. Investors triage with it; it decides whether they open the full deck. Also used for accelerator applications and warm intros.
- Company / business overview. For partnerships, RFP responses, and the classic "just send me something about your company."
- Product / PM one-pager. Internal alignment before anyone builds — problem, proposed solution, scope, success metric.
Pick the type before you write a word. The spine changes.
What goes on a one-pager? The structure that works
Here's one reliable spine, top to bottom. Assume the reader will scan the headline, the proof, and the CTA first, and may never read the middle — so make those three blocks work independently, and put the most important thing highest.
- Headline / value proposition. The biggest thing on the page. One line: what it is plus the outcome, not the mechanism. "Cut invoice processing from 3 days to 3 minutes" beats "AI-powered AP automation platform." Name the product and, ideally, who it's for. ~10–20 words.
- The problem / status quo. One or two sentences, or three tight bullets, in the reader's own words. You can skip this on a pure sell sheet where the buyer already feels the pain. ~40–60 words.
- The solution / what it is. A short paragraph or three or four bullets in plain language. One product screenshot or diagram earns its place here. ~60–100 words.
- Proof. The trust block — metrics, a customer logo strip, one punchy named testimonial, an award, "used by X companies." This is where a page wins or dies. Specifics beat adjectives every time. ~30–60 words.
- Key features / differentiators. Three or four items, iconed. Only the ones that move the decision. Cut the rest — really.
- The ask / next step. Exactly one primary action, phrased as a thing to do: "Book a 20-minute assessment," "Reply with your monthly invoice volume," a calendar link, a QR code. A price is not a CTA — include one only if it genuinely helps this reader decide. Vague endings ("Learn more") kill response. Under 20 words.
- Contact + identity footer. Name, email, phone, site, logo. Obvious, and routinely forgotten — which defeats the entire point.
Startup / investor swap. The spine becomes: one-liner → problem → solution → market size (TAM/SAM) → business model → traction → team → the ask (how much you're raising and what it buys) → contact. What leads is stage-dependent: a pre-seed page can lead with founder insight and early evidence of demand, because there may be little revenue yet; a later-stage page should foreground revenue, growth, retention, and unit economics. Make whichever is your strongest evidence the visual center. State the raise amount and use of funds when it's appropriate to; include valuation or round terms only deliberately, not by default.
Product / PM swap. Problem → who it's for → proposed solution → scope (in, and explicitly out) → success metric → risks / open questions → timeline. The "out of scope" line is the single highest-value part and the one everyone skips. So is naming one success metric instead of five.
A few rules that hold across all types:
- One page means one page. If it spills to two, it's a brief. The discipline is the value.
- Lead with the outcome, support with the mechanism. Readers buy the result, not the plumbing.
- Numbers beat adjectives. "40% fewer support tickets," not "dramatically reduces tickets."
- One CTA. Three competing asks means no action.
- Write the headline last — after you know what your proof actually says.
How do you make one (tools, layout, length)?
Length. One side of US Letter or A4 for a print or PDF leave-behind. For digital delivery, keep it to one document page or one short, clearly bounded web page, and test it on both desktop and mobile. Word count isn't the real constraint — the one-page constraint is — but a useful starting range is roughly 250–400 words of copy, budgeted by block as above (about 10–20 for the headline, 40–60 for the problem, 60–100 for the solution, 30–60 for proof, under 20 for the CTA). Treat those as a starting range, not a rule. The rest of the page is whitespace, hierarchy, and one image. Design for someone scanning in 10–20 seconds, not reading.
Layout. Strong hierarchy (the headline dominates), generous whitespace (crowding is the number-one amateur tell), a two-to-three color palette plus one accent, no more than two fonts, left-aligned body, icons for scannability, and a clear top-to-bottom reading path.
The workflow that actually works:
- Write the copy first, in plain text — headline, problem, solution, proof, CTA. Most bad one-pagers are a copy problem hiding inside a design problem.
- Pick a template that matches your type.
- Pour the copy in and cut ruthlessly to fit one page.
- Add one image and the proof block.
- **Export a PDF and keep a link version.** You'll want both.
Tools, honestly (free/paid tiers move — check each tool's current pricing page before you rely on a specific limit):
- Canva — the default for non-designers. Huge "one-pager" / "one-sheet" template library, drag-and-drop, a usable free tier, and PDF/PNG export. The best starting point for most people. (pricing)
- Google Slides / Docs — free, universal, everyone can edit. Set a Slides page to a custom single-page size and export to PDF; it's an underrated designed-one-pager workflow. Docs for a text-forward brief. Zero cost, zero learning curve, weaker polish.
- PowerPoint / Word — same story for the Microsoft world. A single PowerPoint slide exported to PDF is a legitimate pro workflow.
- Xtensio — purpose-built for one-pagers and one-sheets, with a written framework and templates. Outputs a shareable link or a PDF. Good "steal this structure" destination. (pricing)
- Infographic-leaning editors — a good fit when the page is data-heavy; most are freemium with watermark or export limits on the free tier, so check the current terms.
- Gamma — the current "type a prompt, get a designed one-pager" path. Fast; output can look templated. Good if you don't want to touch a template. (pricing)
- The AI-HTML path. Plenty of people now just ask Claude or ChatGPT: "make me a one-page sell sheet as self-contained HTML, single page, here are the details." You get pixel control, it's instantly a web page, and it's free. The catch: you then need somewhere to put it and a way to send and track it. More on that below.
A worked example (and patterns worth stealing)
Labels only get you so far. Here's a complete, fictional sell sheet written out — real headline, real numbers — so you can see finished copy, not slots:
PayLoop — Cut invoice processing from 3 days to 3 minutes AP automation for finance teams still keying invoices by hand. > The problem - Your team keys in 400+ invoices a month by hand — 60 hours nobody has. - Late payments strain suppliers and forfeit the 2% early-pay discounts you're entitled to. - Month-end close slips because approvals sit unseen in someone's inbox. > What it is PayLoop reads every invoice, matches it to the purchase order, flags exceptions, and routes the rest for one-click approval — no manual entry, no chasing. > Proof - A mid-market manufacturer cut AP labor 74% in its first quarter on PayLoop. - Average processing time: 3 days → 3 minutes. - Captured $180K in early-payment discounts in year one. > Next step Reply with your monthly invoice volume and we'll size your time savings in 24 hours.
Notice what's doing the work: an outcome headline (not "AP automation platform"), problem bullets in the buyer's own words, a solution line that leads with the result, a proof block that's all specifics, and exactly one CTA that's an action — not a price. Now the patterns behind the four common types. Steal the pattern, not the pixels:
The sales sell sheet (above). Product shot top-right, benefit headline across the top, three outcome-led bullets, a proof/logo strip, single CTA at the bottom. Steal: the outcome headline and exactly one CTA.
The startup investor one-pager. Dense but strictly hierarchical — your strongest evidence is the hero of the page, the team block builds trust, the ask is unmissable. Steal: put whatever proves the business at the visual center — traction if you have it, sharp founder insight and demand signals if you're earlier. If Y Combinator's startup library is useful here, it's as a place to study how investors reason, not as a source of one-pager templates.
The narrative product brief (PM). Prose, not bullets. Problem → solution → metric in full sentences, because writing it as sentences exposes fuzzy thinking that bullets let you hide. Steal: the explicit "out of scope" line and a single named success metric.
The consultant / freelancer one-sheet. Who I help, how, proof, packages, book-a-call. Steal: the specificity of "who this is for." "I help Series-A SaaS teams fix onboarding activation" pulls; "I help businesses grow" doesn't.
How do you actually send a one-pager so it gets read?
This is the part most guides skip, and it's where a good one-pager quietly dies. You made a filter and a door-opener — then you email it as one-pager-v2-FINAL.pdf and never learn if anyone opened it.
The tradeoffs, straight:
- PDF attachment. Universal, works offline, prints. But you have no idea if or when it was opened, the recipient keeps an old version forever, big files hit spam filters, and you can't fix a typo after sending. Fine as a printed leave-behind; weak for a send you plan to follow up on. On cold outreach it's worse — attachments hurt deliverability, so paste the key line plus a link instead.
- Hosted PDF (Google Drive / Dropbox link). Fixes size and version drift, but the links look internal, often hit a "request access" wall, give you only crude view data, and look unbranded.
- A web page link. The modern default when you'll follow up. One URL, always current, opens instantly on any device. But a plain hosted page tells you nothing on its own — seeing whether it was opened, and roughly when, means adding privacy-conscious analytics or using a tracked-sharing service. The other cost: you need somewhere to host it.
- A tracked-sharing tool (DocSend and similar). The incumbent approach for tracked sending, with page-by-page analytics and access controls — common in fundraising. Powerful, but priced and built for teams and multi-page decks, so it's often heavier than a solo founder or salesperson needs for one sheet. Check the current pricing before assuming a tier.
A note on what tracking actually tells you. A tracked link is a much stronger signal than an email open pixel: the fetch is the document itself loading, not a proxy image that mail clients preload. But it still isn't proof of who read it or how closely — a corporate security scanner can fetch the link independently of any human, inflating opens and masking location, and a forwarded or shared link muddies whose eyes are on it. And there's a difference between an email-capture gate (a self-reported address the viewer types, which can be faked) and a verified-email login (which actually confirms the address). Treat opens as a timing hint, not a receipt.
A short delivery playbook:
- Send a link, not an attachment, whenever you'll want to follow up.
- Name the next step in the email body, not only inside the document.
- Use view data to time your follow-up, not to prove who read it — reaching out shortly after a view tends to land better than a blind "just checking in."
- Use a password for moderately sensitive material like pricing or unreleased details — but remember a shared password can be forwarded. When access must be limited to specific named people, use verified-recipient access or a data room instead.
- Keep the URL stable and update the page in place so a link you sent last week shows this week's numbers. Never re-send "v2 final FINAL."
- Put a QR code on the printed leave-behind pointing at the live version.
If your one-pager is already a web page — or you built it as HTML with Claude or ChatGPT — Pagelive turns that HTML into a private-by-default link that reports whether it was opened, when, how long the viewer spent, how many times, and which country, and re-publishing the same link updates it in place (the "never send v2 again" fix). The free tier is 5 live pages, no card — often enough when a full tracked-sharing suite feels like too much for a single sheet.
Where it's the wrong tool: Pagelive isn't a builder — no templates, no drag-and-drop — so if you haven't designed the one-pager yet, make it in Canva, Xtensio, Gamma, or Slides first. It makes web links, not files, so it's no help when you need a printed sheet or a PDF to attach. And it's a link plus an optional password, not identity-gated: anyone with the link and password can open it, so if you truly need "only this named investor can view," reach for a tool with named-recipient controls or a data room. Note that even there, named-viewer restriction is usually plan-dependent and works only when paired with email verification — DocSend, for instance, documents its allow-list feature for higher tiers (see its Restrict Access documentation).
The mistakes to avoid (fast checklist)
- Cramming everything on — treating it as a brochure instead of a filter. Whitespace is a feature.
- No single clear CTA, or three competing ones.
- Listing features instead of leading with outcomes.
- Adjectives with no numbers ("innovative, powerful, seamless").
- Forgetting contact info and who it's from.
- Spilling to two pages and still calling it a one-pager.
- Designing before writing — polishing weak copy.
- Sending a heavy PDF attachment on cold outreach.
- An investor one-pager with no evidence — no traction, and no founder insight or demand signal in its place.
- A PM one-pager with no "out of scope" and no success metric.
The one-pager on the one-pager: one audience, one decision, one page, one CTA — lead with the outcome, prove it with numbers, and send it as a link you can update and time your follow-up around. Write the copy first, cut it in half, and make the biggest thing on the page the thing you most want them to remember.
Frequently asked
What is a one-pager? +
A single summary sheet that gives one audience exactly enough to make one decision. Think trailer, not the movie — its job is to earn the next step (a reply, a meeting, a forward), not to tell the whole story.
What should go on a one-pager? +
A dominant headline stating the outcome, the problem, what it is, proof (numbers and logos), three or four differentiators, and one clear CTA — plus contact info. Investor and PM one-pagers swap in traction and team, or scope and success metric.
How long should a one-pager be? +
One page — one side of Letter or A4, or a single screen. Roughly 250 to 400 words of actual copy; the rest is whitespace, hierarchy, and one image. If it spills to two pages, it's a brief, not a one-pager.
What's the best tool to make a one-pager? +
Canva for most non-designers, with a huge template library and a usable free tier. Google Slides or PowerPoint exported to PDF is a legitimate pro workflow. Xtensio is purpose-built. Or have an AI generate it as self-contained HTML for full control.
How do you send a one-pager so it gets read? +
Send a link, not a heavy PDF attachment, whenever you'll follow up — it's always current, opens on any device, and lets you see if it was opened. Name the next step in the email body, and password-protect anything with pricing before it can be forwarded.
Related: executive summary examples · how to send a pitch deck
Made a one-pager? Send it as a tracked link.
If your one-pager is HTML, Pagelive turns it into a private link you can update in place and track — off Google by default, with an optional password. Free for 5 pages, no card.