Customer Story

However accurate a company's description of its own product is, it carries one weakness: the seller wrote it. A one-pager listing ten features says roughly what the competitor's one-pager says, and nobody who receives either takes it at face value.

Meetings kept stalling at the same point. Sales says "use us and the time you spend writing meeting notes goes down," and the other side answers, "everyone we've talked to says that." There's no second card to play. And the person across the table is usually not the decision maker, so once the meeting ends they have to make the case again inside their own company. Forwarding the vendor's brochure isn't an option, so evaluations tended to die right there.

A customer story puts somebody else's results in that spot. It shows a company in the same industry, at a similar size, that changed something specific and watched a number move. All that shifts is who is speaking — from the side selling to the side that already bought — and that shift carries weight at the moment of decision. It's one form of social proof, the signal that other people already use this.

One story runs one to two pages and holds six blocks. Reorder them and the reader sees the results before deciding whether any of it applies to them.

1. Who the customer is. Industry, headcount, the team using the product and what that team does, in two or three lines. This is where readers decide whether the company resembles theirs, so a big logo with no size attached kills half the value.
2. The situation before. What was painful, stated with a number. "Six hours a week went into writing up meetings" gives the later change something to be measured against.
3. Why they chose you. What they compared and what decided it. If naming the competitor is off limits, keep the comparison criteria. This block often becomes raw material for a battlecard.
4. How they used it. Which features they turned on, in what order, how many people started using it, and how many weeks it took to settle in. The evaluator's real question isn't whether it works but whether it will run inside their own team.
5. Results. Before and after, measured the same way, with the time frame attached. "Six hours a week down to one" needs "in three months" next to it.
6. What the customer said. One or two quotes with a real name and job title. An unattributed quote is indistinguishable from a line the vendor wrote.

Put a three-line summary of all six at the top. A large share of readers get that far and close the attachment, so the summary has to carry the customer's name, the number that moved, and the period it moved over.

A product marketer writes it, but can't start alone, so three other people get involved. Sales knows which customers are worth asking. The customer success manager holds the relationship that makes the ask possible. The marketer runs a 45-minute interview, drafts the piece, and sends the draft back to the customer for review.

The slow part is approval, not writing. The customer's communications or legal team takes two weeks to a month to decide whether the name and the numbers can be published, and if the contact changes during that window the clock restarts. Some companies refuse to publish figures at all, which is worth asking about before the interview rather than after the draft. A story that has to land alongside a launch gets started two months out.

Readers split into three. First, visitors on the website who haven't started evaluating anything and read the three-line summary and the logo. Second, the practitioner who just finished a sales meeting — this person reads the longest, and studies the results and the time-to-value most closely. Third, the decision maker that practitioner forwards it to, who spends the least time reading it but can stop the deal outright.

Three audiences means one story can't serve all of them. Keeping four stories that differ by industry and company size, and choosing which one to send, beats writing a single excellent piece and sending it to everybody. Getting sales to actually reach for these is the job of sales enablement.

"If you can attach one customer story, I think I can get this approved internally."

Product claims won't clear the internal review; somebody else's results might.

"Recommend one customer worth writing up — ideally a team above 50 people."

We have no story that matches the segment we're selling into right now.

"It only says they liked it. No numbers, so it can't go out as a story."

Without the size of the change, the document does no work.

At Pagedeck, Ravi produces one story a quarter. This one came from Sofia. A 40-person company that had been spending six hours a week writing up meetings had been on the product for six months, and in a renewal call Sofia heard that the six hours had become one.

Ravi booked a 45-minute call with their operations lead and walked through it in order, starting from the situation before. The draft recorded that the drop from six hours to one took three months, and that the team ran the old process alongside the new one for two weeks before dropping it in week three. The customer's communications team took three weeks to approve. Since it went live, it's the first thing Sofia attaches when she meets a company of similar size.

The most common mistake is treating a customer story as a collection of compliments. More praise feels like more persuasion, so that's what gets written. But readers aren't looking for approval — they're looking for conditions that overlap with their own and the numbers those conditions produced. Give them ten lines of satisfaction and one line with a figure in it and they read the figure and skip the rest. Stories built out of praise sit unused, because sales never reaches for them, and a page nobody opens is indistinguishable from a page that was never written.

Assuming more stories is better is the other one. A deep library looks reassuring, but nobody reads the library — each reader hunts for the one piece that resembles them. Four stories spanning different industries and company sizes reach more people than twenty from the same industry. Before adding volume, look at which square of the market you're selling into has nothing in it. That usually points at one missing story rather than five more of what you already have.