Latest / The Copywriting Podcast with Fexingo: Sales Letters, Headlines, and Persuasive Writing / How a Story in a Sales Letter Outperformed a List of Features
Transcript
- Lucas: So earlier this year, a B2B SaaS company called Planhat — they make customer success software — ran an A/B test on their main sales page. Control was a solid, well-written features and benefits page. Treatment was a story. And the story beat the control by 62 percent in revenue per visitor. Luna: 62 percent — that's huge. But was the story made up, or was it a real customer case? Lucas: Real customer. That's actually the first thing that matters. They picked a single customer — a mid-market logistics firm that had been churning customers before using Planhat. The story followed that company's operations manager, Maria, through a specific quarter where she was losing accounts because support tickets were falling through the cracks. The copy named her role, the company size, the exact problem. Luna: So specificity — not 'a logistics company lost customers', but 'Maria at a 200-person logistics firm lost three accounts in Q2 because tickets routed to the wrong team'. Lucas: Exactly. The control page said 'reduce churn with automated workflows'. That's fine. But the story page opened with a scene: Maria staring at a spreadsheet at 11 PM, realizing she just lost a fourth account. The headline was 'The night Maria realized her customer success software was losing her customers'. Luna: That's a hook. But what about the skeptics who think stories are just fluff? Lucas: Right — the objection is that stories waste time, and business buyers want efficiency. So here's the thing: the story page was actually longer — 1,200 words versus 800 for the control. But the time on page was 40 percent higher, and the bounce rate dropped 22 percent. People read it. Because the story had tension, and tension creates momentum. Luna: Tension — that's the part most B2B copy skips. It's just 'problem, solution, call to action'. No middle. Lucas: Right. The middle is where the story earns the sale. In the Planhat story, the middle section described Maria trying three different fixes — spreadsheets, email reminders, a shared Slack channel — and each one failed. That's the 'dark night of the soul' beat. It validates the reader's own failed attempts. Luna: And it makes the solution feel earned. By the time Planhat is introduced, it's not a random tool — it's the only thing that worked. Lucas: Exactly. The copy uses what I'd call the 'bridge sentence' — right before the solution reveal, it says: 'Maria realized she needed a system that automatically routed tickets based on account tier and assigned ownership. She found Planhat.' That sentence did a specific thing: it stated the criteria before naming the product. So when the product appears, it matches the need the reader already agreed with. Luna: That's clever. It's like a mini-logic trap. You can't argue with the solution because you already conceded the requirement. Lucas: Exactly. The data backs this up. The treatment page saw a 19 percentage point lift in click-through to the demo request form. And the demo requests themselves were 34 percent more likely to convert to a paid trial. Because the story pre-qualified the leads — people who read that story and clicked were already imagining themselves in Maria's shoes. Luna: So the story didn't just sell — it filtered. You got better leads, not just more. Lucas: That's the underrated benefit. A good story attracts the right reader and repels the wrong one. Someone who doesn't have Maria's problem reads the story and thinks 'this isn't for me' — and they bounce. That's fine. You don't want them. Luna: I want to talk about the structure for a second. Most B2B story templates follow a linear arc: situation, complication, resolution. But this one had a twist — the complication had three escalating failures. That's not typical. Lucas: Right. The structure was: 1) The specific person in a specific moment of crisis. 2) Three failed attempts that each get a paragraph. 3) The realization that the problem is structural, not tactical. 4) The solution revealed as the only logical answer. 5) A specific result — Maria reduced churn by 40 percent in six months. Luna: The three failures are key. One failure feels like bad luck. Two feels like a pattern. Three feels like a systemic problem. That's when the reader thinks 'I need a system, not a hack'. Lucas: Exactly. And the copy used micro-tension within each failure. The first failure paragraph ended with 'The spreadsheet worked — for about two weeks.' The second: 'The Slack channel created more noise than signal.' The third: 'The email reminders just annoyed her team.' Each sentence is a mini-cliffhanger. Luna: That's the craft. It's not just 'we tried things and they didn't work'. It's 'we tried X, it almost worked, then it broke'. Lucas: There's another layer. The story used what copywriters call 'negative visualization' — describing the cost of inaction in vivid terms. After the third failure, the copy said: 'Maria started printing resignation letters. Not for herself — for the two account managers who would have to leave if the churn continued.' That's a gut punch. Luna: Wow. That's specific. It makes the reader imagine the human cost. Most B2B copy just says 'reduce churn by X percent' — abstract. Lucas: And that line — the resignation letters — was the single highest-clicking sentence in the entire page. The heatmap showed readers hovering there, re-reading it. That's where the emotional commitment happened. Luna: So how do you test whether your own story will work? Not every story beats the control. Lucas: Planhat actually ran a second test with a different customer story — and it only lifted revenue by 11 percent. So the first story wasn't magic; it was crafted. The difference was that the winning story had a protagonist the target audience could mirror — operations managers at growing companies — while the second story featured a CTO at a large enterprise. The audience didn't identify as strongly. Luna: So the lesson is: pick a protagonist who matches your best customer, not your biggest customer. Lucas: Exactly. And keep the stakes proportional. Maria's stakes were losing accounts and letting team members go. A CTO's stakes might be missing a revenue target — less visceral. The best stories have stakes that feel personal, not corporate. Luna: That's a good framework. I want to hold onto that for my own writing. Lucas: If these marketing conversations have sparked something you've actually used — a headline change, a structure tweak — we should mention that a handful of listeners chip in to keep this show ad-free. It's buy me a coffee dot com slash fexingo. That's the whole model. Luna: Yeah, it's a small group, but it makes a difference. We can keep drilling into experiments like this one because of that support. Lucas: And that support lets us stay independent. So — back to the Planhat story — the last element worth pulling out is the testimonial placement. Instead of a separate testimonial box, they wove a quote from Maria into the story's resolution paragraph. Luna: So the testimonial isn't an interruption. It's the climax. Lucas: Right. The quote was: 'I finally slept through the night. I knew the system would catch a ticket before the customer had to chase it.' That sentence — 'I finally slept through the night' — is the emotional payoff. It's not about features. It's about peace of mind. Luna: And that's the real product benefit for a customer success manager: not 'automated workflows' but 'I can stop worrying at 2 AM'. Lucas: Exactly. That's the copywriting principle that runs through every effective story. The features are the how. The story is the why. And when you combine them in a narrative arc with tension, specificity, and a relatable protagonist, you don't just get more conversions — you get the right ones. Luna: So next time you're writing a sales page, ask: who is Maria? What's the one line they'd say if the problem disappeared? Write that. Lucas: That's a perfect takeaway. Let's try that.