Guide · Updated October 11, 2026 · 16 min read
One-Pager Examples: 8 Real Layouts You Can Copy (and Send as a Link)
Eight complete one-pager examples, one for each job a one-pager usually does: raising money, selling a service, pitching an agency, selling a product, finding sponsors, reporting impact, listing a home, and getting a proposal approved. For each one you get the screenshot, what it is for, the structure it uses, and a prompt that rebuilds the same layout in Claude or ChatGPT with your details.
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, that's a different thing. The companies in every example are fictional, and so are their numbers.
8 one-pager examples you can copy
Each example is a self-contained HTML page: one file, no external scripts, readable on a phone. That is also why the prompts ask for HTML: you get the layout exactly, and the result is already a web page you can turn into a link instead of a PDF attachment.
- Startup investor one-pager
- Consulting services one-pager
- Agency capabilities one-pager
- Product sales sheet (sell sheet)
- Event sponsorship one-pager
- Nonprofit impact one-pager
- Real estate listing one-pager
- Project proposal summary one-pager
1. Startup investor one-pager
What it is for. The pre-deck. An investor reads it in a minute and decides whether to open the full deck or take the call. Also works for accelerator applications and warm intros a friend forwards.
The structure it uses:
- One-line outcome headline, with what the company does in the sentence below it
- A traction strip of four numbers, placed where the eye lands second
- Problem, solution, business model and market as four short blocks in a 2x2 grid
- Team in one row: name, role, one credential each
- The ask in a contrasting block: amount, use of funds as a bar, what it buys, and one next step
Worth stealing: The traction strip sits directly under the headline. Whatever proves the business best goes there; at pre-seed that can be pilot demand or founder insight instead of revenue.
Copy this layout: a prompt for Claude or ChatGPT (fill in the brackets)
Make me an investor one-pager as a single self-contained HTML file (inline CSS, no external scripts or fonts, responsive down to a phone). Layout, top to bottom: 1. Header: company name and logo mark on the left; round name and "Confidential" on the right. 2. A one-line outcome headline, then two sentences on what we do. 3. A strip of four traction numbers with short labels. 4. A 2x2 grid: The problem (3 bullets), The solution (one paragraph), Business model (3 bullets), Market (3 bullets). 5. Team: three people in a row, initials avatar, name, role, one credential. 6. A dark "The ask" block: amount raised, use of funds as a stacked bar with a legend, what it gets us to, and one next step. 7. Footer with company name and website. Use one accent color. My details: [company, one-liner, traction numbers, team, raise amount and use of funds, contact].
2. Consulting services one-pager
What it is for. What a consultant, fractional exec or freelancer sends after a first call, or when someone asks "do you have something I can share with my partner?" It qualifies the reader and makes the first step small.
If this is your job, Pagelive for consultants covers sending proposals and service sheets as tracked links.
The structure it uses:
- Who you help, stated so specifically that the wrong reader self-selects out
- A "you probably need us if" checklist written in the client's own words
- Packages side by side with prices, the recommended one highlighted
- One named quote plus a small before-and-after table
- A low-friction first step (a free review) with one button
Worth stealing: The "you probably need us if" list. Readers recognise their own situation faster than they parse a list of services.
Copy this layout: a prompt for Claude or ChatGPT (fill in the brackets)
Make me a one-page consulting services sheet as a single self-contained HTML file (inline CSS, no external scripts, works on a phone). Layout: 1. Top line: firm name in a serif wordmark, a short tagline on the right in small caps. 2. A serif headline saying the outcome I deliver, then one sentence on exactly who I work with. 3. Two columns: left, "You probably need us if" with 4 ringed checklist items; right, "How we work" with 3 package cards (name, price, 2 to 3 bullets), the middle one highlighted. 4. A proof row: one client quote on the left, a three-line before/after table on the right. 5. A call-to-action box: a small first step and one button. 6. Footer with contact details. Warm paper background, one rust accent. My details: [who I help, packages and prices, a quote, the first step].
3. Agency capabilities one-pager
What it is for. The capabilities sheet an agency sends to a procurement contact or a marketing lead who is building a shortlist. It answers "what do you do, for whom, and have you done it before" in one scroll.
The structure it uses:
- A headline that names the client type, not the agency's adjectives
- Service chips for scanning, three capability cards for depth
- Three short case studies, each with one concrete result
- How an engagement runs, in four numbered steps
- Starting price and next start date in the call to action
Worth stealing: Putting the starting price and the next free start date in the CTA. It filters out budgets that do not fit before anyone books a call.
Copy this layout: a prompt for Claude or ChatGPT (fill in the brackets)
Make me an agency capabilities one-pager as a single self-contained HTML file (inline CSS, no external scripts, responsive). Layout on a dark background: 1. Small nav line: studio name with a simple SVG mark, "Capabilities" and the year on the right. 2. A very large headline naming the kind of client we serve, with one phrase in the accent color. 3. One sentence about the studio next to a row of service chips. 4. Three capability cards (number, area, a headline, 3 deliverables). 5. Three case study cards: a gradient image area, client name, project type, one concrete result. 6. "How an engagement runs": four numbered steps in a bordered row. 7. A bright CTA bar: starting price, next start date, one button. My details: [studio name, client type, services, three projects with results, process, price, contact].
4. Product sales sheet (sell sheet)
What it is for. The sales sheet a rep sends after a demo or leaves behind at a trade show. The buyer already knows the problem; the sheet has to make the product easy to compare and the first step easy to say yes to.
The structure it uses:
- Outcome headline with the product shot on the right
- Three benefits, each a short title and one line of proof
- Specs as a two-column table, so it survives being forwarded to an engineer
- A comparison table against the thing the buyer uses today
- One customer quote, then a risk-free trial as the single CTA
Worth stealing: The comparison against the status quo, not against a named competitor. It is the table the buyer would build anyway.
Copy this layout: a prompt for Claude or ChatGPT (fill in the brackets)
Make me a product sales sheet (sell sheet) as a single self-contained HTML file (inline CSS, no external scripts, phone-friendly). Layout: 1. Hero: product tag, an outcome headline and two sentences on the left; an inline SVG illustration of the product on the right. 2. Three benefit columns, each with a small icon, a short title and one line. 3. Two tables side by side: Specs (label, value) and "Compared with [what buyers use today]" (Yes/No rows and a cost row). 4. One customer quote in a tinted box with an initials avatar. 5. A dark full-width CTA band: a free pilot or trial offer and one button. 6. Footer with company and contact. Clean white layout, one blue accent. My details: [product, buyer, benefits, specs, comparison, quote, offer].
5. Event sponsorship one-pager
What it is for. What an event organiser sends to a marketing team deciding where to spend a sponsorship budget. Sponsors buy an audience, so the audience comes before the packages.
The structure it uses:
- Event name, dates and venue in a bold banner
- Four audience numbers directly under it
- Who attends, as a simple bar chart by role
- Packages with price, what is included and how many slots exist
- Past sponsors, then a deadline and one named contact
Worth stealing: Showing how many slots each package has. Scarcity that is real (a cap of twelve sponsors) is also the reason the sponsorship is worth more.
Copy this layout: a prompt for Claude or ChatGPT (fill in the brackets)
Make me an event sponsorship one-pager as a single self-contained HTML file (inline CSS, no external scripts, works on mobile). Layout: 1. A dark banner: dates and venue in small caps, the event name as a big headline, one sentence on the audience; a simple decorative SVG in the corner. 2. A row of four audience stats. 3. Two columns: "Who attends" as horizontal bars by role with percentages; "Why sponsors come back" as a short paragraph. 4. Three package cards: name, price, slots available, 3 to 4 included items; the top package tinted. 5. A row of past sponsor names in dashed boxes. 6. CTA: a deadline to hold a slot, what to reply with, one button with the contact's name. My details: [event, dates, venue, audience numbers, roles, packages, past sponsors, contact].
6. Nonprofit impact one-pager
What it is for. The impact sheet a nonprofit sends to a donor, a foundation program officer or a corporate giving lead. It has to show the change, show the money was spent well, and make the next gift concrete.
The structure it uses:
- The mission as an outcome headline, not the organisation's name
- The one chart that proves the change, next to one human story
- Three impact numbers with a baseline to compare against
- How it works in four steps, next to where each dollar went as a small table
- Giving levels tied to something tangible, then the next goal
Worth stealing: Giving levels that each buy a specific thing. "$480 is a full year of tutoring for one child" is easier to give than "any amount helps".
Copy this layout: a prompt for Claude or ChatGPT (fill in the brackets)
Make me a nonprofit impact one-pager as a single self-contained HTML file (inline CSS, no external scripts, readable on a phone). Layout: 1. A masthead: organisation name left, "Impact report" right, a heavy rule, then the period and the area served in small type. 2. A serif headline stating the mission as an outcome, then one sentence on what we do. 3. Two columns: a simple horizontal bar chart of the key outcome at three points in the year (CSS bars, labelled values); and one short pull quote from someone who saw the change. 4. Three impact numbers between thin rules, each with a baseline. 5. Two columns: "How it works" as 4 numbered steps; "Where each dollar went" as a table with a total. 6. Three giving levels in one bordered row, each tied to something concrete. 7. CTA: next year's goal and one button. Off-white paper, dark ink, one green accent. No illustrations or clip art. My details: [mission, story, numbers, steps, spending split, giving levels, contact].
7. Real estate listing one-pager
What it is for. The feature sheet an agent sends to a buyer after a showing request, or prints for an open house. Buyers compare several homes at once, so the facts have to be findable in the same place every time.
The structure it uses:
- A header band with the status, a headline about how it is to live there, the address and the price
- Five key facts in a single row
- Description, highlights and floor area on the left, running costs and nearby places on the right
- Recent sales on the same street, so the price has context
- Agent name, phone, email and one button
Worth stealing: The costs table and the recent sales. Property tax, utilities and "what did the neighbours get" are the questions every buyer asks next, and answering them on the sheet saves a round of email.
Copy this layout: a prompt for Claude or ChatGPT (fill in the brackets)
Make me a real estate listing one-pager as a single self-contained HTML file (inline CSS, no external scripts or images, no illustrations; responsive, two columns of facts on a phone).
Layout:
1. A dark header band: a small line with the status ("For sale" plus open house time) and the agency, then a serif headline about living there with the address, and the price with the offer date on the right.
2. A row of five key facts between thin rules: bedrooms, bathrooms, square feet, lot, year built.
3. Two columns: "About the home" paragraph, a two-column highlights list and a small floor-area bar chart (CSS bars); on the right, Costs (tax, HOA, utilities) and Nearby (place, distance) as simple tables.
4. "Recent sales on the street": a table with address, square feet, month sold and price.
5. Agent row under a heavy rule: name, agency, phone, email, and a "Book a private viewing" button.
6. A small disclaimer line.
If I add a photo later, it goes above the header band.
My details: [address, price, facts, description, highlights, floor areas, costs, nearby, recent sales, agent].8. Project proposal summary one-pager
What it is for. The one page a freelancer or consultant sends with (or instead of) a full proposal, so the decision-maker can approve without reading twelve pages. The full proposal is the reference; this is the page that gets signed off.
Need the full document behind the summary? Start from the proposal template.
The structure it uses:
- For, from and valid-until on the first line
- A headline that restates the client's goal, then one measurable success metric
- What we heard and what we will do, side by side
- In scope and out of scope, as two lists of equal weight
- Timeline, fixed price with a breakdown, payment terms, and how to approve
Worth stealing: The out-of-scope list. It is the part that prevents the argument three weeks in, and clients read it as a sign you have done this before.
Copy this layout: a prompt for Claude or ChatGPT (fill in the brackets)
Make me a one-page proposal summary as a single self-contained HTML file (inline CSS, no external scripts, prints and reads well on a phone). Layout: 1. Top line: "For: [client]" on the left, "From: [me] · Valid until [date]" on the right. 2. A small "Proposal summary" label, then a headline that restates the client's goal. 3. A tinted box: "Success looks like:" with one measurable target. 4. A 2x2 grid of numbered blocks: What we heard, What we will do, In scope (+ list), Out of scope (x list). 5. A timeline row of 4 phases with week ranges. 6. Investment table with a bold fixed-price total, next to payment terms. 7. A bordered box with exactly how to approve and one reply button. My details: [client, goal, success metric, scope in and out, phases, prices, terms].
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 (any of the eight above works as one).
- 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." That is what the eight prompts above do. 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, written out
Screenshots show layout; they hide the copy. 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. The same moves run through the eight examples above. Steal the pattern, not the pixels:
The sales sell sheet. 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 link that is noindex by default and shows a view count, and re-publishing the same link updates it in place (the "never send v2 again" fix). The free tier is 2 public pages, often enough for a single sheet; Solo adds whether it was opened, when, how long the viewer spent, how many times, and which country.
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, or start from one of the prompts above. 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 (on Solo and Team), 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
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.
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.
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.
Each of the 8 examples on this page comes with a copy-this-layout prompt: paste it into Claude or ChatGPT with your own details and you get the same layout as a self-contained HTML page. Canva and Xtensio also have large one-pager template libraries if you prefer a drag-and-drop editor.
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.
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 · Pagelive for founders
Made a one-pager? Send it as a tracked link.
If your one-pager is HTML, Pagelive turns it into a link you can update in place, noindex by default, with a view count on every page and a password on Solo. Free for 2 public pages.