Product one pager: the eight blocks a buyer reads in two minutes
A product one pager is a single buyer-facing page that answers what it is, who it is for, and what to do next. Here are the eight blocks, a fill-in template, and the checks before you send it.

A product one pager is a single buyer-facing page that answers what a product is, who it is for, what proof exists, and what to do next. The format is one page, eight blocks, and roughly 250 to 400 words. It is not a pitch deck with the slides deleted, and it is not an internal product brief. This chapter gives the eight blocks, a fill-in template, and the checks to run before the page goes to a directory, a partner, or a buyer.
What a product one pager is, and what it is not
A product one pager is a decision aid for someone who has no context and no time. That reader may be a directory editor, a partner evaluating an integration, or a buyer who opened your link between meetings. The page has one job: help that person decide whether to take the next step.
- Not a deck. A deck controls the order of the conversation. A one pager gets forwarded, skimmed, and read out of order.
- Not an internal brief. An internal brief answers what the team plans to build. A one pager answers what the buyer can use today.
- Not a landing page. A landing page can ask for a signup. A one pager usually asks for a smaller step: a reply, a call, or a trial.
One page is a forcing function. When you cannot add a ninth section, you have to decide which claim matters, which proof survives, and which action you actually want.
If a block cannot change the buyer's next action, it does not belong on the page.
The eight blocks, in reading order
The order follows the questions a buyer asks, not the order your team likes to present. Each step below has a completion check, so you can tell whether the block is finished or merely filled.
Eight is a ceiling, not a target. If two blocks say the same thing, merge them. If a block has no evidence behind it, cut it and leave the space empty. A page with seven honest blocks reads better than a page with eight blocks where one is filler. The same rule applies to length: the word limits in the template are upper bounds, not quotas.
- Name and tagline. Put the product name first, then one line that says what it does in plain language. Avoid a category label that needs a second explanation. Done when a reader can repeat the line to a colleague without opening the page.
- The problem in the buyer's words. Describe the moment the buyer notices the problem, not the market size. Use one short paragraph. Done when the paragraph contains no product name.
- What the product does. Three concrete capabilities, each tied to the problem above. Verbs first, adjectives last. Done when each capability could be demonstrated in a screenshot or a short demo.
- Who it is for. Name the role, the team size, and the situation. Add one line for who it is not for. Done when a reader can decide whether they are in the target group.
- Proof. One number, one named customer, or one reproducible example. Every proof item needs a source and a date. Done when a skeptical reader could check the claim without asking you.
- How it works. Three steps from signup to the first useful result. Keep the setup time honest. Done when a new user could follow the steps without a call.
- Price or plan shape. Give the starting price, the unit, and what is included. If pricing is custom, say what drives the quote. Done when the reader knows whether the product is in their budget range.
- Next step. One action, one link, and one expectation for what happens after the click. Done when the action can be completed in under two minutes.
Fill-in template
Copy this table into a document and replace the right-hand column. The limits are deliberately tight. They are there to stop the page from turning into a brochure.
| Block | Write this | Limit | Done when |
|---|---|---|---|
| Name | Product name plus a plain-language line | 12 words | A colleague can repeat it |
| Problem | The moment the buyer notices the cost | 40 words | No product name appears |
| Capabilities | Three verbs tied to that moment | 60 words | Each one is demonstrable |
| Audience | Role, team size, situation, and exclusions | 30 words | The reader can self-select |
| Proof | One number or one named example with a date | 35 words | It can be checked |
| How it works | Three steps to the first result | 50 words | A new user can follow it |
| Price | Starting price, unit, and inclusions | 20 words | The budget question is answered |
| Next step | One action and one link | 15 words | It takes under two minutes |
The two-minute test before you send it
Read the page as if you were the buyer and you had never heard of the company. Then run these five checks. A fail is not a style issue; it means the page is not ready to send.
| Test | Pass | Fix |
|---|---|---|
| First screen | Name, audience, and outcome are visible without scrolling | Move the tagline above the fold |
| Skim path | Reading only the headings still tells the story | Rewrite headings as answers |
| Proof | At least one claim has a source and a date | Replace the adjective with an example |
| Next step | One action, not three | Remove competing buttons and links |
| Forward test | Someone else can explain the product after one read | Cut the section they stumbled on |
Where the page goes
The same page feeds several promotion jobs. It can sit behind a directory submission, open a partner conversation, or follow up after a call. The wording changes slightly by channel, but the eight blocks stay the same. Keep a master copy and mark the three places that change: the headline, the proof item, and the next step.
Build the page after you have a product positioning statement, because that sentence decides which audience and which proof belong on the page. If you already maintain a longer description, use the method for reusing one product description across channels and cut it down rather than writing from a blank page. Then use the channel preparation workflow to send the right version to the right place.
Three ways it fails
These failures look like progress. Each one produces a page that is longer, safer, and less useful.
- Writing for the whole market. The page tries to include every use case, so no reader recognizes themselves. Pick one buyer and one situation.
- Replacing proof with adjectives. "Fast", "easy", and "powerful" cannot be checked. A before-and-after number can.
- Adding a second next step. Two calls to action usually mean the team has not decided what the page is for. Pick the smaller step that leads to the larger one.
Common questions
How long should a product one pager be?
One page, usually 250 to 400 words, with a table or a short list carrying part of the load. If it runs longer, the problem is usually scope, not layout.
Is a product one pager the same as a pitch deck?
No. A pitch deck is presented in a fixed order. A one pager is read alone, often after a forward, so every block has to stand on its own.
Should I put the price on it?
Put the starting price and the unit. If the price is custom, say what changes it. Hiding the range wastes the reader's time and yours.
Can one page serve every channel?
One page can serve most channels, but the next step should match the channel. A directory may need a listing link; a partner may need a call link. Keep the body stable and change the final action.
What if I do not have a customer example yet?
Use a reproducible example instead: a before-and-after screenshot, a sample output, or a public dataset. Do not invent a customer. We do not know which block a given buyer reads first; the order above is a default, not a measured sequence.
Next step
Start with the positioning sentence, then fill the eight blocks in order. The first draft should take under an hour. The harder work is cutting the page until a stranger can repeat the offer after one read. That is the version worth sending.
If the sentence is still fuzzy, fix it first with the four-check positioning statement and come back to the page.
Part of the QueryWin handbook · Level 2


