Sales Collateral

For a long time every rep built their own material. Someone who joined last month edited a file inherited from a colleague. Someone who had been around for years kept sending the same deck they built three years ago. One customer heard the product described as a collaboration tool, another heard it described as a document archive, and both descriptions came from the same company. The reps thought they were adapting to each buyer. Then two of those buyers met at an industry event and found they had been sold different products.

The sharper problem showed up outside the meeting room. At Pagedeck, Sofia once ran an hour-long demo for a thirty-person company and walked out with a yes. Two weeks later the deal went quiet. When she asked why, the contact told her it had gone up the chain and come back rejected. The person who rejected it had never seen the demo. What that person saw was two slides the contact had hurriedly pasted into an internal memo, and neither slide said anything about why the company should spend money.

It wasn't a case of having no material. Sofia had a demo script and a price sheet. Both were built for the person sitting across the table, so neither of them said a word to the person who wasn't in the room.

Both stories point at the same gap. Persuasion doesn't end when the rep stops talking. Far more of it happens later, in rooms the rep will never enter, where a document has to carry the argument alone. So companies started gathering everything used for persuasion under one name and treating it as a team asset rather than a folder on someone's laptop.

There are two reasons to manage it that way. When each rep says something different, the same product looks like a different product to every buyer. And the person who approves the spending usually skips the meetings and reads only the documents. Deciding who builds each piece and when it gets refreshed has its own name, sales enablement — the function that supplies reps with material and training. In a growing company that role usually ends up inside marketing.

Everything under this name belongs to one branch: types of material. What separates them isn't what they contain but where in the deal they land and who reads them. There are five, and they tend to appear in this order.

1. Pitch deck — the slides a rep puts on screen and narrates in a meeting. The running order is close to fixed: the problem the buyer has, what the current approach costs them, the proposed answer, real screens, a similar company that adopted it, pricing, and the next step. Ten to fifteen slides is enough. It gets built by a marketer who knows the product together with the people who actually sell, and it's read by the hands-on staff who show up to the meeting.
2. One-sheeter — the essentials on a single page. It's what a rep leaves behind and what the contact forwards upward, so it's written on the assumption that nobody will be there to narrate it. It carries a one-line description, three problems the buyer recognizes, three capabilities that touch those problems, a price range, and contact details. It isn't a shortened pitch deck; it has a different reader. This page gets read alone by someone seeing the product for the first time.
3. ROI calculator — a tool that turns adoption into a number. Usually a spreadsheet or a web page where the buyer enters their own figures and sees how much a year of this saves them. There are normally three inputs: headcount, hours per week spent on the task, and hourly labor cost. Forty-five people spending two hours a week hunting for documents at 30,000 won an hour comes to 140 million won a year. Its reader is the person who looks at numbers rather than product — the one holding the budget. The inputs matter more than the arithmetic: a calculator that fills itself with vendor-friendly defaults gets dismissed the moment a finance reviewer opens it, while one the buyer types their own headcount into survives the meeting.
4. Reference call — an existing customer telling a prospect what the experience was like. It parts ways with the other four because a person goes in rather than a file. Three things need preparing: a list of customers similar in size and industry, a rough map of what the prospect is likely to ask, and a case study sent ahead of the call. A case study writes up one customer's before and after with numbers attached. This piece usually appears last, at the moment when the terms all work and the only remaining doubt is whether it really works. The customer doing the favor is spending their time, so leaning on the same account repeatedly wears the relationship out. Lining up three or four willing references and rotating them is part of the preparation.
5. Security questionnaire — the review document a buyer sends before adoption. It runs the opposite direction from the other four: the buyer sends it and the vendor fills it in. Where is data stored, is it encrypted in transit, which employees can see customer data, how many hours until a breach is reported. Anywhere from dozens to hundreds of items arrive. The people who know those answers are engineers and security staff rather than sales, so without a prepared answer bank a single reply can eat two weeks.

Putting the writers and the readers side by side explains why there are five pieces instead of one. Three groups write. Product marketing supplies the argument and the stories, sales feeds back the sentences that actually landed in live conversations, and engineering and security supply the technical answers. Three groups read: the staff who will use the product, the executive who approves the money, and the reviewer who weighs the risk. The full set of people involved in one purchase goes by the name buying committee. The hands-on user asks whether this makes their day easier, the approver asks what it's worth, and the reviewer asks where it breaks. One document trying to satisfy all three leaves all three without an answer.

A deal at a two-hundred-person company shows the split clearly. The hands-on contact reads the pitch deck and asks how long migrating off the current tool takes. Once that person is convinced, the one-sheeter travels to their manager, who looks only at cost per person and total cost for the year. A level above, the executive sees the calculator's 140 million won sitting next to an actual spend of 40 million. Meanwhile the information security lead has sent the questionnaire and is waiting on a reply. Four people are each holding a different document, and if any one of them can't find their answer the deal stops there.

The five connect along a single deal. The pitch deck opens the meeting, the one-sheeter walks out of that meeting on its own, the calculator justifies the amount, the reference call removes the last doubt, and the questionnaire opens the door in front of the signature. Other pieces attach depending on the situation — a battlecard, for instance, condenses the counter-argument against a named competitor onto one page — but those five are the frame. Whichever pieces exist, they only have value as one current set in one place. Five slightly different versions scattered across five laptops make it an asset in name and a personal file in practice. Companies that manage this well settle two questions together: where the material lives and who is allowed to change it. Answering only one collapses. Fix the location and edited forks pile up; fix the permissions and people ask which inbox holds the current version every single time.

"Where's the current deck for this meeting? The one I have still has last year's pricing."

A sign that the material isn't collected in one place and nobody owns refreshing it.

"Our contact is sold but has nothing to take upstairs. I'll send the one-sheeter and the ROI output."

There needs to be a document that argues on its own in front of someone who never attended a meeting.

"Forty-item security questionnaire just came in. Eight aren't in our answer bank, so I'm passing those to Theo."

The same questions keep arriving, so answers are being stored and reused.

Every quarter Sofia and Ravi block an hour at Pagedeck to go through the material. Sofia walks back through the deals that actually ran and points at the moments where the conversation stalled; Ravi rewrites the sentences and swaps in stories that fit those moments. Last quarter the sticking point was teams on the free plan moving to a paid one. Asked why they should pay for something they were already getting free, each rep gave a different answer. The two of them rebuilt the entire back of the one-sheeter around that single question: a two-column table of what the free plan does and doesn't cover, with a line underneath about what starts breaking once more than ten people share a document.

After the rewrite they check whether anything gets used. Half the material ever produced goes unopened, and that half is better deleted. When the list is long, a rep in a hurry gives up searching and reaches for their old file. Pagedeck has a rule that anything opened fewer than five times in a quarter comes off the list.

The most common mistake is reading this as a design job that produces attractive slides. The visible output is a deck, so the assumption is easy to make. But the value sits in the sentences, not the layout. Whether the problem is written in words the buyer actually uses, whether the numbers are from this quarter, and whether the meaning survives being read with nobody there to narrate it — those are what the material is judged on. Polish the design alone and a new deck appears every six months while the win rate stays flat. Reps keep using their own files, because the new deck looks good and doesn't answer what buyers ask. To see whether anything improved, watch the win rate or the sales cycle — the time from first contact to a signed contract. When material does its job, the meetings booked to repeat an explanation disappear and that span gets shorter.

Treating it as something finished once and filed is the other frequent mistake. A document looks like an object that reaches completion, which makes the belief natural. In practice pricing, capability lists, customer stories, and the competitive picture all keep moving, and the material has to follow. That's why many companies attach an owner and a refresh interval to each piece. Left alone, a rep sends last year's price sheet and gets asked to honor it, or promises a capability in a demo that was removed months ago. Correcting it later costs more than the error itself, because from the buyer's side it doesn't read as a slip about a number. It reads as a vendor who never looked closely at their business. Trust built across four months of conversations comes apart over a single stale figure.