Everyone Tells You Not to Send the One-Pager. Send It, Then Build It Around the Objections.

A cybersecurity discovery call ends the way the good ones often end. The prospect says some version of the same sentence: send me a one-pager and I'll circulate it internally. Standard sales advice has a ready response, and the response is some flavor of don't. Don't just send a document. Qualify harder. Ask a question that tests whether the request is genuine interest or a polite way off the call. Find out who internally actually means before committing to anything.

None of that is wrong. A request for a one-pager can be a brush-off, and a rep who fires a PDF at every request is doing nothing but generating attachments. But the advice skips a fact that does not care how well the rep qualified the moment: the circulation is going to happen. Whether or not the rep sends a document they built, the deal will be discussed in rooms the rep never sits in, and something will stand in for the product there. Gartner's most recent sales survey found that 67 percent of B2B buyers say they would prefer to buy with no sales rep involved at all. A buyer asking for a document to pass around is often not stalling. They are doing what buyers now do.

So the useful question is not whether to send a one-pager. It is what the one-pager is built to do. A rep who treats the document as a formality sends a brochure and loses control of it the moment it leaves the outbox. A rep who treats it as an instrument can build it to work on their behalf in rooms they will never enter.

This article covers why the document is unavoidable in a cybersecurity buying group, why the standard feature-brochure one-pager dies in committee, how to build the document around the objections the committee will raise instead of around features, how that turns circulation into discovery, and the one conversation to have with a champion before sending anything.

The Document Goes Into Rooms You'll Never Enter

Start with the structure of a cybersecurity buying group, because it is the reason the document matters at all. Gartner's research on the B2B buying journey puts the typical buying group for a complex solution at six to 10 decision makers, each arriving with four or five pieces of information they gathered independently and have to reconcile with the group. An enterprise security platform sits at the complex end of that range. The purchase pulls in the security team that will operate the tool, whoever already owns an overlapping product, compliance or GRC, IT, procurement, and whoever controls the budget. The rep meets two or three of them and never speaks directly to the rest.

The rep's share of the group's attention is smaller than it feels, too. Gartner's data shows B2B buyers spend only 17 percent of the entire purchase evaluating all vendors combined; when a buyer is comparing several vendors at once, the time spent with any single rep can be as low as 5 or 6 percent. The other 94 percent is independent research and internal debate with no vendor in the room. And the group usually forms a view before the rep arrives. 6sense's 2025 Buyer Experience Report found that 94 percent of buying groups rank their shortlist in order of preference before they ever engage a seller.

Put those numbers together and the picture is uncomfortable but clear. The deal is decided largely by people the rep never meets, during a process the rep is mostly absent from, after a ranking the rep had no hand in. Some artifact has to represent the product inside that process. If the rep does not supply it, the buying group uses whatever is closest to hand: a competitor's framing, a half-remembered demo, an LLM summary, the opinion of the loudest skeptic. The one-pager is the rep's one reliable chance to place a controlled artifact into a process they otherwise cannot reach.

This is why refusing to send the document is weaker than it appears. Withholding the one-pager does not keep the rep in the room. It guarantees that when the deal gets discussed, the rep is represented by nothing, or by something built by a person with no stake in the deal closing. Demandbase's research found that 72 percent of B2B purchases involve multi-stakeholder complex buying groups. The multi-threaded deal is the normal deal, and a rep who cannot scale into rooms they are not in does not win it.

Why the Feature-Brochure One-Pager Dies in Committee

Most one-pagers are brochures. The rep pulls the capability slide, the integrations slide, and the customer-logo slide, arranges them on a single page, adds the boilerplate, and sends it. It looks professional. It is also almost perfectly designed to lose.

Here is how a feature brochure dies. It gets circulated, exactly as the prospect promised, and reaches someone on the committee who owns a tool that overlaps with part of what it describes. That person scans the capability list, recognizes three items their existing tool already covers, and says the sentence that has ended more cybersecurity deals than any competitor ever has: we already have a tool that does that. A feature list invites that comparison instead of defusing it, and the brochure has no answer to it.

The rep hears none of this. The objection lands, the deal cools, and what comes back, if anything does, is a soft note from the champion that the team wants to hold off for now. The real reason sits in a room the rep was never in. The brochure went where the rep could not follow and lost to an argument the rep never got to answer. This is one of the quieter mechanics behind the no-decision loss, which already outnumbers competitive losses in cybersecurity pipelines: the deal does not die because a competitor won it, it dies because a document failed to defend itself, and the rep mistook the silence for a slow quarter.

The deeper flaw is that a feature brochure answers a question nobody on the committee is asking. A capability list answers what does it do. But a buying group evaluating a new security tool is rarely stuck on that. They are stuck on whether it overlaps with what they already own, whether the fully-loaded cost is defensible, and whether it will get deployed or join the shelf of tools the company paid for and never switched on. A document that leads with features brings a feature answer to an objection fight.

Build It Around the Objections, Not the Features

The fix is a different design principle: build the one-pager around the objections the buying group will raise, not the features the product has. The rep already knows those objections. In a competitive cybersecurity deal they are remarkably predictable, and each one belongs to a specific person on the committee.

The overlap objection belongs to whoever owns the adjacent tool. Every security org runs a portfolio of tools with an owner assigned to each. When a new tool enters evaluation, the owner of anything adjacent has both the expertise to spot the overlap and a quiet incentive to raise it, because a new tool can read as a verdict on the old one. This is the person who says we already have something that does that. The document has to reach them with a precise answer: where this tool overlaps with the category they already own, what it does that theirs does not, and why running both is a deliberate decision rather than a redundancy. Naming the overlap first is what disarms it.

The cost objection belongs to finance or procurement. Someone is accountable for whether the number is defensible, and they are not looking at the sticker price. They are evaluating fully-loaded cost: license, implementation, the headcount to run it, integration work, and the renewal trajectory. If the document only states a price, or worse just says contact us, the finance reader fills the gap with a pessimistic estimate, and that estimate is what gets repeated in the budget conversation. The document should do the loaded-cost math first: what it costs to operate, what it replaces or lets the team avoid buying, and what year-two renewal looks like.

The deployment objection belongs to the security team. The people who will operate the tool have been sold shelfware before; they keep a drawer of licenses for products that were bought, half-deployed, and quietly abandoned. Their question is not whether the tool is good. It is how long until it runs in production and produces value, and what it demands from a team with no spare capacity. The document needs a concrete, honest deployment answer: what the first 30 days look like, what the team must provide, and when the tool starts earning its place. Vague language about fast time-to-value reads, to a SOC lead, as a warning.

The principle underneath all three: write the document so each person who matters finds the section built for them. The tool owner finds the overlap section with their objection already answered. The finance reader finds the cost frame. The security lead finds the deployment timeline. Nobody has to raise their objection from a standing start, because the document raised it and answered it. The conversation in the room the rep cannot reach begins from the rep's answer instead of the skeptic's question.

What the Objection-Built One-Pager Looks Like on the Page

Designing around objections changes the layout of the page, not just its tone. A few things follow directly.

Lead with the buyer's problem, in the buyer's language. The first thing on the page is the problem the buying group already agrees they have, written the way they would write it. A reader who recognizes their own problem in the first two lines keeps reading; a reader who hits a product description and a tagline starts skimming. The product is the second thing on the page, never the first.

Give each objection its own labeled section. The overlap answer, the cost answer, and the deployment answer should be visually distinct and easy to find, so a reader scanning for their specific concern lands on it in seconds. This also makes the document a multi-threading tool: the rep can point each stakeholder at the section written for them instead of asking everyone to read everything.

Replace the logo wall with dated, specific proof. A row of customer logos proves only that other companies signed a contract; it answers no objection. A short, recent, specific proof point does. It is a named outcome from a comparable team, with a number and a date on it. Proof from last quarter survives scrutiny that a generic, undated case study does not.

Commit the specifics to writing. Most one-pagers will not put a deployment timeline or a cost range on the page, because either can be checked later. That reluctance is exactly why writing them down persuades. A concrete account of the first 30 days tells a SOC lead the vendor expects to be held to it. An honest cost frame gives a range and the variables that move it. That tells a finance reader the vendor has done this math and is not afraid of it. A document that hides the number tells finance the number is bad.

None of this makes the document longer. An objection-built one-pager is usually shorter than a feature brochure, because it is not trying to list everything the product does. It is trying to win five or six specific arguments, and everything that does not serve one of them comes off the page.

Now Circulation Does Your Discovery

Here is what changes once the document is built this way: circulation stops being a risk the rep absorbs and becomes an instrument the rep reads.

A feature brochure that gets circulated returns almost no information. It produces a vague positive like the team liked it, or a vague negative like let's revisit next quarter. Neither is actionable, because the objection that actually moved the deal stayed in the room. An objection-built document returns something far more useful. Because each section is aimed at a named concern and a likely owner, any objection that still comes back comes back attached to that structure. The champion does not relay a fuzzy bad feeling; they relay that finance pushed back on the cost section, or the SOC lead did not believe the deployment timeline, or the tool owner still thinks the overlap is real.

That is not a stalled deal. That is a map. A rep who knows finance flagged the cost section knows exactly what the next conversation is, who it is with, and what it has to accomplish. A rep who only knows the deal went quiet knows nothing, and tends to respond by following up about nothing. A one-pager built around objections has effectively run a discovery call inside a room the rep was never in, and handed back the notes.

This is what most reps miss when they treat the one-pager as a formality. A document built around features is a liability that wanders off and gets beaten in private. A document built around objections is a sensor: it goes where the rep cannot, provokes the real objections on purpose, and reports back which ones are live and who holds them. The rep stops guessing why a deal slowed down and starts seeing it.

The Conversation to Have Before You Send Anything

One move makes the whole approach sharper, and it happens before the document goes out. Most reps treat the one-pager as a fixed asset: one document, built once, sent to everyone. The stronger version is built per deal, and it starts with a short conversation with the champion. Before sending anything, ask two questions. Who, specifically, is most likely to push back on this, and what will they push back on?

A champion engaged enough to circulate a document internally almost always knows. They know the tool owner is territorial. They know finance is tight this quarter. They know the SOC lead is short-staffed and allergic to anything that sounds like more work. That answer tells the rep how to build the document. If the tool owner is the real risk, the overlap section moves to the top and gets the most space; if finance is the risk, the cost frame leads. The one-pager stops being a static brochure and becomes a custom-built argument, aimed before it is sent at the person most able to kill the deal.

The conversation does something else, too. It turns the champion into a genuine collaborator instead of a courier. A champion who helped shape the document, and knows it was built to answer their colleague's specific objection, defends it differently in the room. They are not forwarding a vendor PDF. They are carrying an argument they had a hand in building into a meeting the rep cannot attend.

The One-Pager Is an Instrument, Not a Brochure

The standard advice not to send the one-pager comes from a real observation. Reps do waste effort firing documents at requests that were never serious. But the conclusion drawn from it is wrong. The problem was never that the document gets circulated. The problem is that most documents are not built to survive being circulated.

A cybersecurity deal is decided by a group, over months, mostly in the rep's absence. Some artifact will represent the product through that process. The only real decision the rep controls is whether that artifact is a feature brochure that invites we already have a tool that does that, or a document built to answer the overlap, cost, and deployment objections before they are spoken aloud, and to report back which ones are live.

So send the one-pager. Refusing it does not keep the rep in the room; it sends the rep into the most important meetings of the deal unrepresented. Send it, and build it to do the job a brochure was never meant for: to carry the rep's argument into rooms the rep will never enter, and to come back with a map of where the deal actually stands. Giving cybersecurity reps that kind of unfair informational advantage in competitive deals is the reason we are building KillChain Overwatch.

FAQ

Should I send a one-pager when a prospect asks for one?

Yes, with one condition. Send it, but do not send a feature brochure. In a cybersecurity buying group the document will be circulated to people the rep never meets, so the only question that matters is whether it is built to survive that circulation. Refusing to send anything does not keep the rep in the room; it leaves the rep unrepresented when the deal is discussed. Qualify the request, find out who internally actually means, and then send a document built to answer the buying group's objections.

What should a cybersecurity sales one-pager include?

Lead with the buyer's problem in their own language, then address the three objections a security buying group reliably raises: tool overlap, or how this fits alongside what they already own; fully-loaded cost, meaning license plus implementation plus headcount rather than sticker price; and deployment, with a concrete timeline to production value instead of a phrase like fast time-to-value. Replace the customer logo wall with one or two dated, specific proof points. Skip the exhaustive capability list. The document should win five or six arguments, not catalog every feature.

How do I keep a one-pager from being killed by 'we already have a tool that does that'?

Name the overlap before the committee does. The person who owns an adjacent tool has both the expertise to find the overlap and an incentive to raise it. A document that pretends the overlap does not exist hands them the objection intact. A document that states exactly where the two tools overlap, what each does that the other does not, and why running both is a deliberate choice disarms it. The overlap objection is most dangerous when a skeptic discovers it, and weak when the vendor has already named and answered it.

Who in a cybersecurity buying group actually reads the one-pager?

More people than the rep meets. Gartner puts a complex-B2B buying group at six to 10 decision makers, and an enterprise security purchase typically pulls in the security team, the owner of any overlapping tool, compliance or GRC, IT, procurement, and finance. The rep usually meets only two or three of them directly. The rest form their view of the product from secondhand sources, which is exactly why the circulated document needs a section aimed at each of those stakeholders.

How does a one-pager help in a multi-threaded or buying-group deal?

A one-pager built around objections lets the rep scale into rooms they cannot attend. Each labeled section is aimed at a specific stakeholder, so the rep can point the tool owner, finance, and the security lead each at the part written for them. When an objection comes back, it comes back attached to a section and a person. The champion reports that finance pushed on cost, or the SOC lead doubted the timeline. That converts a vague stall into a specific, named next step the rep can actually work.

What should I ask my champion before sending a one-pager?

Two questions: who is most likely to push back, and what will they push back on. An engaged champion almost always knows whether the tool owner is territorial, finance is tight this quarter, or the security team is short-staffed. Their answer tells the rep which objection to place first and give the most space. Asking also turns the champion into a collaborator who helped shape the document, rather than a courier forwarding a vendor PDF into a room the rep cannot enter.

References

1. Gartner. The B2B Buying Journey. The typical buying group for a complex B2B solution involves six to 10 decision makers; B2B buyers spend just 17 percent of total purchase time meeting with potential suppliers, and as little as 5 to 6 percent with any single sales representative. Gartner
2. Gartner. "Gartner Sales Survey Finds 67% of B2B Buyers Prefer a Rep-Free Experience." Press release, March 9, 2026, based on a survey of 646 B2B buyers conducted August through September 2025. Gartner
3. 6sense. 2025 Buyer Experience Report, published November 12, 2025. 94 percent of buying groups rank their shortlist in order of preference before engaging a seller; typical B2B buying groups involve 10 or more people. 6sense
4. Demandbase. Understanding the State of the B2B Buyer, 2025. 72 percent of B2B purchases involve multi-stakeholder complex buying groups. Demandbase

*Written by Jonathan, co-founder of KillChain Sales. Ten years across software engineering, cybersecurity, and cybersecurity sales. If you are a cybersecurity AE or sales leader who has watched a deal go quiet after a one-pager got circulated, join the waitlist or connect on LinkedIn.*