Story structure and series planning
The structure
Six sections, in this order. Roughly 700 to 1,100 words for a page a sales team will actually send.
1. The recognition line. One or two sentences placing the client by durable attributes and naming the problem in the buyer's vocabulary. This is the first hundred words the whole story depends on. A buyer who does not recognize themselves here never reaches the numbers.
2. Before. What they were doing, what it cost, what they had already tried and abandoned. The abandoned attempts are the most-read part of the story for a skeptical buyer, because they have tried the same things and want to know why this was different.
3. What was done. Chronological, specific, with the decisions visible. Not a feature list. A buyer is assessing whether the causality holds, and causality lives in the sequence.
4. The wobble. Where it nearly failed and what was done about it. One paragraph. This is the section that separates a case study from an advertisement, and the one most often cut by someone trying to make the story cleaner.
5. After. One or two anchor numbers, then the operational texture: what stopped happening, which meeting got shorter, what the team does now instead. The texture is longer than the numbers.
6. What it required. What the client had to give: hours, access, a hire, an uncomfortable internal conversation. Advice with no cost reads as a pitch. Stating the cost is what makes the rest credible.
Close on the client's own words where an approved quote exists. No summary paragraph, no call to action inside the story. The page it lives on handles that.
What not to include
- A metrics grid. Two anchor numbers in prose beat eight in a table.
- Stock photography of people in meetings.
- The vendor's origin story or methodology branding.
- Superlatives about the result. The number carries it or it does not.
- Causality the delivery team will not defend in the room.
Worked example: the recognition line
Weak, no recognition:
A leading company in the financial services space was struggling with inefficient lead generation processes and sought a scalable solution.
Nothing here is false and nothing is usable. No reader sees themselves, and the phrasing signals that the specifics were removed because they were never collected.
Strong, anonymized:
A specialty insurance brokerage in the US Midwest, about 60 people, two producers doing all the new business. They had bought lists twice and hired an SDR who left in five months. The owner was still personally sourcing the pipeline that paid for everyone else.
Same level of anonymity. The attributes are durable and the combination describes a wide field. But a broker in that situation reads the third sentence and recognizes their own Tuesday.
The difference is not the amount of information. It is that the second version keeps the texture the anonymization rubric says to keep, and the first bleached it out.
Planning the series
One case study is an anecdote. Five or six is evidence.
Plan for coverage, not for the best stories. Map the priority segments, specialties, and problem shapes, then assign one story to each cell. A set of five stories about the same segment proves depth in one place and leaves every other buyer without a mirror.
Sequence by verifiability. Ship the stories with the cleanest approved numbers first. They set the credibility level the rest of the set inherits, and they are the ones the sales team reaches for while the set is still small.
Keep one page per story. A combined "success stories" page reads as a brochure. Separate pages get sent individually, which is the actual use case.
Track which stories the sales team sends. The ones nobody sends are telling you something about the segment, the problem shape, or the credibility of the numbers. That signal is worth more than a traffic metric.
Refresh annually. Numbers go stale, clients change, approvals lapse. Re-confirm the figures and the permissions once a year, and retire stories whose champion has left the client organization.