What a sales one-pager is
A sales one-pager, also called a one-page sales sheet or sell sheet, is the shortest complete argument for buying. It fits on one side of A4 or US Letter, and it has to work without the seller in the room. That is its real job: a champion forwards it to a finance director, a procurement lead or a colleague the seller never meets, and the page has to explain the problem, the answer and the proof on its own.
Most one-pagers fail the same way. They list features in the seller's vocabulary, make claims with nothing behind them and end with a vague invitation to learn more. A good one is written in the words buyers use on discovery calls, backs each claim with one specific proof point and ends with a single, concrete next step and a named contact.
The structure is stable across companies: a headline value proposition, the problem, how it works in three steps, proof (a metric, a quote and a strip of customer logos used with permission), differentiators against the status quo, who it is for, pricing or the next step, and the call to action. What changes is the reader. A product one-pager speaks to the person evaluating the product; an executive one-pager speaks to the person who signs; a competitive one-pager speaks to a buyer who already owns an incumbent; an industry one-pager speaks to one sector's problem in that sector's language.
A one-pager is downstream of the messaging framework. The framework holds the approved value proposition, pillars and proof; the one-pager selects from it for one reader and one moment in the deal. Because it is short and widely forwarded, it also goes out of date faster than anything else in the library, which is why this template gives every page an owner, a version and an expiry date.
When to use a sales one-pager
- After a first meeting, as the leave-behind the champion can forward internally.
- Before a meeting with an economic buyer who will not sit through a deck.
- When a buyer already owns an incumbent tool and needs a short case for switching.
- When entering a new industry or use case, to test whether the message lands before building a full campaign.
- At events and in partner channels, where the page is read without a seller present.
- Not as a substitute for discovery: a one-pager sent before you know the problem is a brochure.
One-pager, battlecard, case study, deck or messaging framework
Five documents carry the same story at different lengths and to different readers. The one-pager is the only one built to be forwarded by the buyer.
| Document | Who reads it | What it does | What it does not do |
|---|---|---|---|
| Sales one-pager (this template) | Buyers, including people the seller never meets | Makes the case for one product, buyer or use case on one page | Cover every feature, persona or objection |
| Messaging framework | Product marketing, sales and marketing internally | Holds the approved value proposition, pillars and proof | Go to buyers as written |
| Battlecard | Sellers only | Helps a rep win against one named competitor | Leave the building; it is internal |
| Case study | Buyers comparing themselves with a similar customer | Tells one customer's story in depth, with results | Explain the product to someone new to it |
| Pitch deck | Buyers in a meeting, with the seller presenting | Walks through the story with the seller narrating | Work on its own once forwarded |
The template
Fill in the header first: it stays internal and decides everything on the page. Then write the eight blocks, fill the proof register before you publish, and choose a variant. Replace everything in brackets. Download the Word version to draft the page, the Excel version to track proof and reviews across many one-pagers, or the PDF to print.
One-pager header (internal, not printed)
| Field | What to write |
|---|---|
| Title and variant | [Product, executive, competitive, or industry or use case] |
| Reader | [The one role this page is written for, and the stage of the deal it is sent at] |
| Source messaging | [Messaging framework version the claims come from] |
| Owner | [One named person in product marketing who answers for the page] |
| Version | [Version number and date published] |
| Expiry date | [Date the page must be reviewed or retired; three to six months is typical] |
| Approved for | [Send by email, print, event use, partner use; any restriction on use] |
| Library tags | [Product, persona, stage, industry, competitor] |
The eight blocks of a one-page sales sheet
| Block | What to write | Length | Rule |
|---|---|---|---|
| 1. Headline value proposition | [The outcome the reader gets, in their words, not your category name] | One line, under 12 words | A buyer should be able to repeat it to their boss |
| 2. The problem in the buyer's words | [What is going wrong today and what it costs, taken from discovery notes] | Two or three sentences | Quote or paraphrase real buyers; no invented pain |
| 3. How it works in three steps | [Step 1], [step 2], [step 3] | One line per step | Describe what the buyer does, not your architecture |
| 4. Proof | [One metric], [one quote with name and role], [logo strip placeholder] | Three short items | One proof point per claim; logos only with written permission |
| 5. Differentiators versus the status quo | [Two or three ways this is better than what they do today] | Two or three bullets | Compare with the real alternative, often a spreadsheet or doing nothing |
| 6. Who it is for | [Company type, size and the trigger that makes it a fit] | One or two lines | Saying who it is not for builds trust |
| 7. Pricing or next step | [Pricing model or starting price if you publish it; otherwise the next step] | One line | Never a price that sales cannot honour |
| 8. Call to action and contact | [One action, a named person, an email address and a link] | One line | One call to action, not three |
Proof register
| Claim on the page | Proof point | Type (metric, quote, logo) | Source and date | Approved for external use? | Expires |
|---|---|---|---|---|---|
| [Claim in the headline] | [Specific result] | Metric | [Customer, report or internal data; date] | [Yes / pending / no] | [Date] |
| [Claim in the problem or how it works] | [Customer quote] | Quote | [Name, role, company; date of approval] | [Yes / pending / no] | [Date] |
| [Claim in the differentiators] | [Specific result or comparison] | Metric | [Source; date] | [Yes / pending / no] | [Date] |
| [Logo strip] | [Customer logos in the reader's segment] | Logo | [Written permission on file; date] | [Yes / pending / no] | [Date] |
Variants: product, executive, competitive, industry or use case
| Block | Product one-pager | Executive one-pager | Competitive one-pager | Industry or use-case one-pager |
|---|---|---|---|---|
| Reader | The person evaluating the product | The economic buyer who signs | A buyer who already owns an incumbent | Buyers in one sector or with one use case |
| Headline | The outcome the product delivers | The business result and the cost of waiting | Why switching is worth the effort now | The sector's problem, named in its own terms |
| Problem | The day-to-day pain of the user | The risk or cost at company level | Where the incumbent falls short for this buyer | The problem as that sector describes it |
| How it works | Three product steps | Three steps from decision to result, with a timeline | Three steps to move off the incumbent | Three steps in the sector's workflow |
| Proof | A usage or time-saved metric and a user quote | A financial metric and an executive quote | A result from a customer who switched | A metric and a quote from the same sector |
| Differentiators | Against doing it manually | Against doing nothing this year | Against the incumbent, fairly stated and verifiable | Against generic tools that ignore the sector |
| Next step | A trial, demo or pilot | A short meeting to agree a business case | A migration assessment | A sector-specific demo or reference call |
| Watch out for | Turning into a feature list | Product detail the reader will not read | Claims about the competitor you cannot prove | A page that only swaps the logo and the sector name |
Writing rules
| Rule | Standard | How to check |
|---|---|---|
| One page | Fits on one side of A4 or US Letter at a readable size | Print it; nothing runs to a second page |
| 150 to 300 words | Body copy between 150 and 300 words, excluding the footer | Word count before review |
| Buyer language | Problem and headline use words buyers used on calls | Each phrase traces to discovery notes or win/loss interviews |
| One proof point per claim | Every claim has exactly one specific proof point beside it | Every row of the proof register is filled and approved |
| Version and expiry date | Version number, publish date and expiry date in the footer | Footer present; expiry no more than six months out |
| Owner | One named owner who answers questions and retires the page | Owner field filled with a person, not a team |
| One call to action | One next step, one contact | Count the asks on the page |
Review checklist before publishing
| Check | Pass standard | Checked by | Done |
|---|---|---|---|
| Reader | The page is written for the one reader in the header | [Product marketing] | [ ] |
| Headline | States an outcome, not a category; under 12 words | [Product marketing] | [ ] |
| Messaging match | Every claim appears in the current messaging framework | [Product marketing] | [ ] |
| Proof | Every claim has one approved proof point with a date | [Product marketing] | [ ] |
| Permissions | Quotes and logos have written customer permission on file | [Customer marketing] | [ ] |
| Competitive claims | Statements about other vendors are factual, dated and verifiable | [Legal or compliance] | [ ] |
| Pricing | Any price or pricing model matches what sales is quoting | [Sales leadership] | [ ] |
| Field test | Two sellers have read it and would send it | [Sales enablement] | [ ] |
| Footer | Version, publish date, expiry date and owner are on the page | [Content owner] | [ ] |
Keeping one-pagers current in the content library
| Practice | What to set | Who |
|---|---|---|
| One home | Publish every one-pager to the content library, not to email threads or desktops | [Content owner] |
| Tags | Product, persona, deal stage, industry and competitor, so sellers can find the right variant | [Content owner] |
| Share by link | Sellers send a link to the library copy, so an update reaches pages already sent | [Sales enablement] |
| Expiry and review | A review reminder before each expiry date; expired pages come out of search | [Content owner] |
| Usage review | Each quarter, check which one-pagers are sent and opened, and in which deals | [Product marketing] |
| Gaps | Log what sellers searched for and could not find; that is the next one-pager to write | [Sales enablement] |
| Retire | Archive superseded versions and point their links at the current one | [Content owner] |
Prefer a file? We email the Word, Excel and PDF versions to your work address, free.
Email me the filesFour worked examples
Example: fictional company
The same invented company in three variants, and a second invented company for the industry variant. Each example shows the eight blocks as they would read on the page.
Ferncastle Analytics sells revenue-forecasting software to mid-market sales teams. Its product marketing manager, Ines Calloway, wrote three one-pagers from the company's messaging framework: a product page, an executive page for finance leaders and a competitive page for buyers already on Harborview Metrics. Harborview Metrics, which sells analytics software to retail and logistics companies, wrote the fourth for retail. All companies, people, quotes and figures are invented for illustration and are not benchmarks.
Example 1: product one-pager (Ferncastle Analytics)
| Block | What the page says |
|---|---|
| Headline | A sales forecast you can defend, ready on Monday morning. |
| Problem | Your managers spend two days a month rebuilding the forecast in spreadsheets, and the number still moves after the board has seen it. |
| How it works | 1. Connect your CRM. 2. Ferncastle scores every open deal on its activity and stage history. 3. Managers review exceptions, not every line. |
| Proof | Metric: forecast preparation cut from two days to half a day at Marlow & Finch Logistics. Quote: "We stopped arguing about the number and started working the deals." Dana Okafor, Director of Revenue Operations. Logo strip: [three logistics and distribution customers, with permission]. |
| Differentiators | Updates daily from the CRM, not monthly from exports. Shows why a deal moved, not only that it moved. Live in two weeks without a data team. |
| Who it is for | B2B sales teams of 30 to 300 sellers with a monthly forecast call. |
| Next step | A 30-day pilot on last quarter's data. |
| Call to action | Book the pilot with Ines Calloway, ines@ferncastle.example, ferncastle.example/pilot. |
| Footer | Version 3.1, published 1 October, expires 31 March. Owner: Ines Calloway. 154 words of body copy. |
Example 2: executive one-pager for the economic buyer (Ferncastle Analytics)
| Block | What the page says |
|---|---|
| Headline | Plan next year on a forecast that holds. |
| Problem | When the forecast misses, hiring, spend and guidance are set on the wrong number, and finance only finds out at quarter end. |
| How it works | 1. A two-week set-up on your CRM. 2. A daily forecast with the risk on each large deal. 3. A monthly review between finance and sales on one shared number. |
| Proof | Metric: forecast variance at quarter end fell from 18 to 6 per cent in three quarters at Marlow & Finch Logistics. Quote: "For the first time, finance and sales walked into planning with the same number." Chief Financial Officer, Marlow & Finch Logistics. |
| Differentiators | Against doing nothing this year: every quarter on spreadsheets is another plan set on a number nobody trusts. |
| Who it is for | CFOs and CROs of mid-market companies with a quarterly board forecast. |
| Pricing or next step | Priced per seller, annual contract. Next step: a 20-minute meeting to size the business case. |
| Call to action | Reply to your account executive, or email ines@ferncastle.example. |
| Footer | Version 1.4, published 1 October, expires 31 January. Owner: Ines Calloway. 155 words of body copy. |
Example 3: competitive one-pager against an incumbent (Ferncastle Analytics)
| Block | What the page says |
|---|---|
| Headline | Already on Harborview Metrics? Keep your dashboards and fix the forecast. |
| Problem | Harborview's forecasting add-on works from weekly exports, so managers still adjust the number by hand before every call. |
| How it works | 1. Connect Ferncastle to the same CRM, alongside Harborview. 2. Run both forecasts side by side for one quarter. 3. Switch the forecast call to Ferncastle when the numbers prove it. |
| Proof | Metric: a distribution company that ran both side by side retired its manual adjustments in one quarter. Quote: "We kept Harborview for reporting and moved the forecast." Head of Sales Operations, [customer name with permission]. |
| Differentiators | Daily CRM updates rather than weekly exports (Harborview product documentation, checked 1 October). Deal-level reasons for every change. No change to existing dashboards. |
| Who it is for | Harborview Metrics customers whose forecast still depends on manual adjustment before every weekly call. |
| Next step | A migration assessment: one call to map your current forecast process. |
| Call to action | Book the assessment with your account executive at ferncastle.example/switch. |
| Footer | Version 2.0, published 1 October, expires 31 December (competitive pages expire sooner). Owner: Ines Calloway. Reviewed by legal. 152 words of body copy. |
Example 4: industry one-pager for retail (Harborview Metrics)
| Block | What the page says |
|---|---|
| Headline | Know which stores will miss the week by Tuesday, not Monday after. |
| Problem | Regional managers see store performance a week late, in reports built by hand, after the chance to act on staffing and stock has passed. |
| How it works | 1. Connect point-of-sale and staffing data. 2. Harborview flags stores trending below plan each morning. 3. Regional managers get the list and the likely cause. |
| Proof | Metric: weekly reporting time for regional managers cut from six hours to one at a 40-store homeware chain. Quote: "My Monday is now about fixing stores, not finding them." Regional Operations Director. Logo strip: [three retail customers, with permission]. |
| Differentiators | Built around the retail week, store hierarchy and staffing, not a generic dashboard that each chain has to configure. |
| Who it is for | Retail chains with 20 to 500 stores, regional managers and a weekly trading meeting. |
| Next step | A retail demo on a sample of your own store data. |
| Call to action | Book the demo with Leah Marsh, leah@harborview.example, harborview.example/retail. |
| Footer | Version 1.0, published 1 October, expires 31 March. Owner: Leah Marsh, retail product marketing. 152 words of body copy. |
Example: fictional company. Ferncastle Analytics, Harborview Metrics, Marlow & Finch Logistics and every person named in this example are invented for illustration. Any resemblance to real companies or people is coincidental.
How to write a sales one-pager
Start from the messaging framework
Take the value proposition, pillars and proof from the current framework. A one-pager that invents new claims creates a second story that sales and marketing then have to reconcile.
Pick one reader and one variant
Write the header first: the role, the deal stage and whether this is a product, executive, competitive or industry page. If the page has to serve two readers, write two pages.
Write the problem before the headline
Use words from discovery calls and win/loss interviews. The headline is easier to write, and more accurate, once the problem is down in the buyer's language.
Fill the proof register before you publish
Every claim gets one specific proof point with a source, a date and approval for external use. A claim you cannot prove comes off the page.
Cut to 300 words
Count the body copy and cut until it is between 150 and 300 words. Cut adjectives first, then features the reader did not ask about.
Review, version and publish to the library
Run the review checklist, add the version, owner and expiry date to the footer, and publish to the content library so sellers share a link to the current copy.
Where sales one-pagers go wrong
A feature list
Twelve features with icons tell the buyer what you built, not what changes for them. Lead with the outcome and keep only the features that prove it.
Written in your words
Category names and internal product names mean nothing to someone forwarded the page. Use the words buyers used on calls.
Claims with no proof
Faster, easier and more accurate are claims every vendor makes. One specific, sourced proof point per claim is what makes yours believable.
Every persona on one page
A page that speaks to the user, the CFO and IT at once speaks to none of them. Write a variant for each reader who matters.
No expiry date
One-pagers outlive the pricing, logos and product names on them. Without an expiry date and an owner, old versions keep circulating in deals.
Copies on desktops
A one-pager saved as an attachment cannot be updated. Share links to the library copy so a correction reaches every page already sent.
How Revspire keeps one-pagers current
The template works in any document tool. The hard part comes later: twenty one-pagers in four variants, each with an owner and an expiry date, and sellers who need the right one in the middle of a deal rather than the one saved on their desktop last year.
Revspire Content Hub is a governed sales content repository. Sellers find the right one-pager by searching on meaning, context and tags such as persona, stage, industry and competitor, and content recommendations appear inside the CRM. Versioning keeps every shared link current, so when the owner publishes version 3.2 the buyer who opens a link sent months ago sees the new page. Two-way sync with SharePoint and OneDrive lets product marketing keep drafting where it already works.
Usage and performance analytics show which one-pagers sellers send and buyers open, which feeds the quarterly usage review in the template. Content gap insights show what sellers searched for and could not find, which is usually the next variant worth writing.
Sales one-pager template FAQs
What should a sales one-pager include?
Eight blocks: a headline value proposition, the problem in the buyer's words, how it works in three steps, proof (a metric, a quote and customer logos used with permission), differentiators against the status quo, who it is for, pricing or the next step, and one call to action with a named contact. Add a footer with the version, owner and expiry date.
How long should a sales one-pager be?
One side of A4 or US Letter, with 150 to 300 words of body copy. Under 150 words usually means the proof is missing; over 300 means the page is trying to serve more than one reader. If you need more, write a second variant rather than a second page.
Is a one-pager the same as a one-page sales sheet or sell sheet?
In B2B sales the terms are used interchangeably: one page that makes the case for buying and works without the seller present. Sell sheet is more common in manufacturing and retail, where the page often carries product specifications and ordering details. The template covers both.
What are examples of sales one-pagers?
The four most useful are a product one-pager for the person evaluating the product, an executive one-pager for the economic buyer, a competitive one-pager for a buyer who already owns an incumbent, and an industry or use-case one-pager. The worked examples above show each one filled in for a fictional company.
How do you keep sales one-pagers up to date?
Give each page one owner, a version number and an expiry date three to six months out. Publish it to the content library and share links rather than attachments, so an update reaches pages already sent. Review usage each quarter and retire pages nobody sends.
Related templates and reading
- Free templateSales playbook templateA B2B sales playbook outline: ICP, personas, stages with exit criteria, discovery questions, plays for common situations and objection responses.
- Free templateSales content audit templateOne row per asset, with the usage evidence and the verdict beside it: retire, fix or keep, each with an owner and a date.
- Free templateMutual action plan templateA shared, dated plan from discovery to go-live, with a buyer owner and a seller owner on every milestone.
- Free templateStakeholder map templateEvery person in the buying group on one page, with buying role, influence, stance, priorities and a next action.
- Template: the approved story every one-pager draws onMessaging framework template
- Template: the internal, seller-only card per competitorSales battlecard template
- Template: the evidence behind a competitive one-pagerCompetitive analysis template
- Blog: running the library one-pagers live inSales content management
- Glossary: sales collateralWhat is sales collateral?