What to Send When a Buyer Asks for a One-Pager

“Can you send me a one-pager?” is one of the most common requests in B2B sales, and one of the most ambiguous. It might mean the buyer wants something to forward to a colleague. It might mean they want a quick reminder of what you discussed. It might mean they want to end the call politely without committing to anything.

The default response is to attach the company overview that marketing made last year. That is fast, but it usually answers a question the buyer did not ask. A better response starts with one short question, then sends a page built around what the buyer is actually trying to decide. We have covered writing a one-page brief a buyer can forward in detail. This post is about the moment of the request itself: what to ask, what to put on the page, and how to tell whether the request signals real interest.

Read the signal

A one-pager request can come from very different places. Before you send anything, try to work out which of these it is.

Four common meanings

“I need to share this with someone.” The buyer is interested and needs to bring a colleague, manager, or committee up to speed. This is the most promising version. The page will be read by people who were not on your call, so it has to stand on its own.

“I need to remember this.” The buyer is evaluating several options and wants a short record of yours. The page will sit in a folder next to competitors’ materials. Clarity and accuracy matter more than persuasion.

“I need to justify spending more time on this.” The buyer is not sure yet and wants to check whether a longer conversation is worth it. The page needs to connect quickly to a problem they recognize.

“I need to end this conversation.” Sometimes a one-pager request is a polite way to close a call. The buyer may never open it. That is not a failure on your part; it is useful information.

Why the page has to work quickly

Whatever the reason for the request, assume the page will be scanned rather than read closely. Research from Nielsen Norman Group estimated that on an average web page, people have time to read at most 28% of the words, and 20% is more likely [1]. That study looked at web pages rather than sales documents, but the lesson transfers: a reader under time pressure will look at headings, the first line of each block, and anything that looks like a number or a decision.

Buyers also have limited time with sellers in general. Gartner has reported that buyers spend only about 17% of their purchase consideration time meeting with potential suppliers [2]. Much of the rest goes to research and internal discussion. Your one-pager may be one of the few pieces of your story that is present in those conversations.

Make the next move

Ask one clarifying question, then build a page that answers the buyer’s actual question.

Annotated one-page outlineBuild the page around the buyer's decision

1. 1HeadlineThe buyer's problem in one line, in their words. A scanning reader sees this first.
2. 2ContextWhat you heard on the call, so the buyer can correct you before the page travels.
3. 3ApproachOnly the parts of your offer that matter for this buyer. Relevance beats completeness.
4. 4Evidence or open questionsSeparate what is known from what still needs testing.
5. 5Practical detailsScope, rough timeline, and pricing structure, using only figures you can stand behind.
6. 6Next stepOne specific, reasonable action. A page without one is a brochure.

Ask one question first

Keep it short. You are not trying to run a second discovery call. You are trying to learn who will read the page and what they need from it.

• “Happy to. Who is it for, so I can make sure it covers what they will care about?”
• “Of course. Is this mainly for you to compare options, or for someone else on your team?”

If the buyer answers, you have what you need to tailor the page. If they say “just send whatever you have,” that is also informative. It may point to the third or fourth meaning above.

The annotated one-page outline

Use these sections, in this order. Each annotation explains what the section is for.

1. Headline: the buyer’s problem in one line. Write it in the buyer’s words, not your tagline. Annotation: this is what a scanning reader will see first. If it does not sound like their situation, they will stop here.
2. Context: what you heard. Two or three short lines summarizing what the buyer told you about their current situation. Annotation: this shows you listened and lets the buyer correct you before the page travels further.
3. Approach: what you would do. A brief description of how your product or service addresses the problem, limited to the parts that matter for this buyer. Annotation: resist the urge to list every feature. Relevance beats completeness.
4. Evidence or open questions. What is known, such as a relevant capability the buyer saw in a demo, and what still needs to be tested. Annotation: separating these keeps the page honest and protects your contact if a colleague asks hard questions.
5. Practical details. Scope, rough timeline, and pricing structure if the buyer asked. Only include figures you can stand behind. Annotation: vague practical details invite delay; inaccurate ones damage trust.
6. Next step. One specific, reasonable action, such as a 30-minute call with the operations lead or a review of the integration question. Annotation: a page without a next step is a brochure.

Keep the whole thing on a single page. If it spills over, cut product detail first.

Common mistakes to avoid

A few habits make one-pagers less useful, even when the content is accurate:

• Leading with the company. Founding year, office locations, and mission statements rarely help a buyer decide anything. If they matter, put them at the bottom.
• Cramming. Shrinking the font to fit more onto the page defeats the purpose. A scanning reader will skip a dense block entirely.
• Generic customer logos. A row of logos without context tells the reader little. If you include an example, choose one the buyer would recognize as similar to their situation, and describe it accurately.
• Hiding the price question. If the buyer asked about cost and the page avoids it, the reader will notice. Give a structure or range you can support, or say plainly when pricing depends on scope.
• No date or version. Pages travel and get reused. A date in the footer helps everyone know whether the content is current.

Reuse without being generic

You do not need to write a new page from scratch every time. Keep a template with the six sections and swap in the headline, context, and next step for each buyer. Over time you will build a small set of tailored versions for common situations. The post on building a small sales materials library covers how to organize them.

Language you can adapt

Illustrative example, fictional buyer and details:

Asking the clarifying question:

Glad to. So I can make it useful, who will see it besides you? If it is going to your finance lead, I will lead with cost and scope. If it is for your operations team, I will focus on the handoff process you described.

Sending the page:

Here is a one-page summary based on our call. I used your description of the handoff delays at the top so it reads the way you would explain it. The section on open questions lists the integration item we still need to confirm. Would a 30-minute call with your operations lead next week be a useful next step, or is there someone else who should see this first?

If the buyer said “just send whatever you have”:

Sure, I have attached a short overview. If it turns out there is a specific question you or a colleague need answered, let me know and I can put together something more focused.

These are examples to adapt, not templates that guarantee a reply. Replace the problem, roles, and next step with details the buyer actually gave you. If you do not have those details, a clarifying question is usually worth more than a polished attachment.

Decide what happens next

The buyer’s response to your question and your page tells you how active the evaluation is.

Signs of active evaluation

• They answer your clarifying question with a specific person or purpose.
• They correct something in the context section.
• They forward the page and tell you who received it.
• They agree to the next step or suggest a different one.

Signs of polite deferral

• They decline to say who the page is for.
• They do not respond to the page at all after a reasonable follow-up.
• They reply with thanks but no comment, question, or next step.
• They ask for “more information” without saying what is missing.

Neither set of signs is final. A busy buyer may take a week to respond. But if several deferral signs appear together, it is reasonable to send one short follow-up and then move on. The post on following up after sending information covers timing and wording.

If the signs point to active evaluation, prepare for the page to generate questions. The person who receives the forward may ask about something you left out on purpose, such as integration detail or contract terms. Have the answer ready, or know who on your team owns it, so the next exchange moves the conversation forward instead of starting a new round of document requests.

Keep a short note in your deal record: who asked for the page, who it was for, what you sent, and what happened next. A request for a one-pager is a small moment, but it is also one of the clearest early signals of whether a buyer is actively evaluating or simply being polite.

Use these examples responsibly. Describe your product, pricing, and customer results accurately, and adapt every suggestion to the buyer’s stated process.