Sales Enablement

For a long time the work ended the moment the material landed in a shared folder. From the side that produced it the job looked finished, and the folder was the proof. Sales, meanwhile, kept selling in the words they already had.

Pagedeck went through this. A messaging document organizing the core phrases and a battlecard holding competitive responses on one page both went up, and two months later the call recordings had three reps describing the product three different ways. One called it a collaborative document tool, one called it a meeting-notes tool, and one called it a knowledge management system. A customer who happened to hear all three would have come away believing there were three different products.

The problem wasn't a missing document. The document never made it into anybody's mouth. People can't deliver somebody else's sentence as their own the first time they see it, and when an answer stalls in a meeting they fall back to the explanation they already trust, because a meeting gives nobody time to go look something up.

Sales enablement fills that gap. Within product marketing — translating what a product does into the language of its market — it sits on the activity side, the half that moves the language, rather than the side that writes the documents.

One cycle usually spans a quarter, in five steps.

1. Collect where the field gets stuck. Listen to call recordings, read the reasons deals were lost, and ask reps to write down the question they couldn't answer last month. Skip this and you build material answering questions nobody ever asked.
2. Build the material. Four pieces: the messaging that fixes the core phrases, a battlecard carrying the response logic against each competitor, a customer story presenting the results a customer got as a narrative, and a set pairing frequent objections with their answers. Add one more, a script for the order in which the demo gets shown.
3. Deliver it. Uploading a document is not delivery. Book 45 minutes and have the reps say the words out loud themselves. One person taking the customer role and throwing objections while another answers is the fastest version. A phrase somebody has said aloud once shows up in meetings at a completely different rate from a phrase they have only read on a page.
4. Check it. Counting how many documents were produced isn't checking. Pull ten call recordings from the following month and count how many contain the agreed phrasing. Two out of ten means the delivery step failed rather than the material; eight means you can move on to the next piece. When it isn't being used, the reason is usually one of two: the phrasing is too long for the pace of a meeting, or the rep doesn't believe it.
5. Fix it. Strip out what didn't land. Words customers don't recognize, feature explanations nobody asked about, and answers that cite a price the competitor already changed all come out here, and what's left is shorter than what went in.

Nobody does this alone, and different people enter at different points.

1. Product marketing settles the language and builds the material. The work belongs to them, and so does the outcome.
2. Sales brings in what's getting stuck and then actually uses what gets built. They supply raw material as much as they receive it.
3. The product team confirms that what the material claims is true. A feature that hasn't been built yet, sitting in a sales document, becomes somebody else's problem after the contract is signed, usually customer success's.
4. Customer success reports how customers who adopted the product actually use it. That's where the raw material for customer stories comes from.
5. Whoever owns competitive intelligence flags it when a rival changes pricing or features. That flag is the only channel that keeps the battlecard from going stale.

There are four moments where this work belongs on the calendar. A new hire's first two weeks, ahead of shipping a new feature or product, right after a competitor makes a large move, and once every quarter. The pre-launch slot interlocks with the launch plan: keeping sales from hearing about a feature on release day means the training has to sit in front of the announcement.

At Pagedeck, Ravi builds the material and Sofia collects the questions from the field. Once a quarter the two of them book 45 minutes, with Mia joining only to confirm what's factually true about the features. Grace doesn't attend. With the CEO in the room, nobody volunteers the question they failed to answer.

"We have a battlecard and nobody opens it. What's missing isn't material, it's training."

Separating the act of producing material from the act of delivering it.

"Let's book an enablement session before this launch. They can't be hearing about it on release day."

Proposing that the training slot sit ahead of the announcement rather than behind it.

"Have you used that phrasing in a meeting yet? I want to hear whether it lands."

Checking whether the material actually works in front of a customer.

At Pagedeck this conversation usually starts with Sofia. If she gave a customer the answer written in the material and the same question came back, that means one line wasn't narrowed enough. Ravi takes that follow-up question and adds a line to the objection set.

The most common reading is that this is the work of producing a lot of material. The artifacts are the only part of this work visible from outside, so it reads that way. But twenty pieces sitting in a folder and used in no meeting is worse than three pieces all of which get used. Start managing by count and the material that's easy to produce multiplies, while the genuinely hard piece — the objection set — keeps getting postponed.

The other frequent assumption is that this belongs to a sales manager, since the word training is attached. Deciding what to say, though, is a seat that watches the product and the market together, while the sales manager's job is getting the language used. Pile both onto one side and the urgent one wins. A manager carrying this month's number copies the explanation from whoever sells best to everybody else instead of revising the material, and when that explanation is wrong the whole team is wrong together.