Latest / The Newsletter Podcast with Fexingo: Substack, Beehiiv, and Email Newsletter Business / How Newsletters Use Provenance Stories to Convert Readers to Paid
Transcript
- Lucas: So there's this newsletter in the cybersecurity space — it's called 'The Shift,' run by a guy named Mark Devine. He was a chief information security officer at a mid-sized bank for about eight years, and last September he launched a paid tier. Luna: And I'm guessing he didn't just put up a 'subscribe for $10 a month' button and call it a day. Lucas: Exactly. He did something that I think a lot of newsletter writers overlook. He sent a welcome sequence — four emails — that didn't pitch the paid tier. Instead, they told the story of why he left that CISO job and started writing. He called it his 'origin memo.' Luna: A provenance story. I've seen this work in other contexts — for brands, for authors. But for newsletters, it's almost like the narrative behind the newsletter is the product itself. Lucas: That's exactly the framing I want to dig into today. Provenance — the origin story, the 'why this exists' — is becoming one of the most effective conversion tools for paid newsletters. And the data from Devine's launch backs it up. Luna: What was his conversion rate? Lucas: On day one of the paid launch — the first day he opened the gates — he converted 34 percent of his free subscribers who read that origin memo. Now, that's a self-selected group — only about 40 percent of his list actually opened the email. But of those, more than a third paid immediately. Luna: Thirty-four percent is huge. Most newsletters I see are thrilled with 5 to 10 percent conversion on a launch day. Lucas: Right. And the key difference is, he wasn't selling a promise of future content. He was selling the journey that led him to create the content. It's a trust transfer — from the story to the subscription. Luna: So what does that origin memo actually look like? I'm imagining a long post about his career, but that could easily come across as self-indulgent. Lucas: It's four emails, each one about 400 words. The first one is the hook — the moment he realized he had to leave the CISO role. He describes a specific board meeting where a director asked him, 'Why should we care about ransomware? It's not our problem.' And he just thought, 'I need to talk to people who actually want to understand this.' Luna: So the origin is anchored to a specific incident, not a vague 'I wanted to help people.' That makes a difference. Lucas: Huge difference. The second email is about the first three months of the newsletter — how he almost quit because open rates were below 20 percent. The third is about a reader who emailed him saying a post helped them convince their CEO to invest in security tools. The fourth is the ask — 'If you want to support this work, here's what paid gets you.' Luna: So the ask comes after three emails of building emotional investment. That's a classic narrative arc — setup, conflict, resolution, call to action. Lucas: Exactly. And what's interesting is, he didn't offer any exclusive paid content in that launch. The paid tier was just early access and a private Discord. The value proposition was entirely emotional — 'I want to keep doing this, and your subscription makes that possible.' Luna: That's a big bet. Most launch guides say you need a content upgrade or a course or something tangible. Lucas: And that advice works for some niches. But Devine's numbers suggest that for a certain kind of newsletter — especially one where the writer's voice and perspective are the core differentiator — provenance can outperform a features list. He did a split test later, by the way. Luna: A split test on the welcome sequence itself? Lucas: Yeah. Three months after launch, he ran an A-B test on new subscribers. Group A got the origin memo sequence. Group B got a standard welcome — 'Thanks for subscribing, here's what you'll get, here's the paid option.' Over a 30-day window, Group A converted to paid at 2.5 times the rate of Group B. Luna: Two and a half times. That's not marginal. That's a game-changer for a writer deciding where to spend their creative energy. Lucas: And it's not just Devine. I've been tracking this pattern across about a dozen newsletters in different verticals — finance, parenting, software engineering. The common thread is that the provenance story is built into the onboarding, not buried in an 'about' page. Luna: Let's talk about the parenting example. I remember you mentioned a writer named Rachel something. Lucas: Rachel Morris — she writes 'The Long Game,' a newsletter about raising kids with a growth mindset. She started her paid tier last November, and her origin story is about her daughter's ADHD diagnosis. She talks about how the school system failed to accommodate her, and how Rachel had to become an expert in executive functioning to advocate for her child. Luna: That's deeply personal. Does that feel like oversharing for a business newsletter? Lucas: She was afraid of that. But her readers — mostly parents — responded with an outpouring of similar stories. Her conversion rate was 18 percent in the first week. Not as high as Devine's, but still well above the industry average for a parenting niche. Luna: So the provenance story works when it aligns with the reader's own identity. It's not just 'here's my story,' it's 'here's a story that explains why I understand your problem.' Lucas: That's a perfect way to put it. And that leads to a tactical question — how do you find your provenance angle if you don't have a dramatic origin? Luna: Right, not every newsletter writer left a high-stakes job or has a personal diagnosis to share. Some people just built a list around a hobby or a professional interest. Lucas: I talked to a writer in the marketing space — his name is Tom Meehan — and his newsletter is about B2B content strategy. His origin story is that he was a junior copywriter who got assigned to write a white paper for a client and completely bombed it. He spent the next six months obsessively studying white papers to figure out what made them work. Luna: So the origin is about competence earned through failure, not a dramatic life change. Lucas: Exactly. And that story — 'I was bad at this, then I got good, and here's what I learned' — is actually a really common and effective template. You don't need a tearjerker. You need a specific moment where you realized you had to learn something, and then you did. Luna: What about newsletters that are more analytical, like data-heavy finance or tech analysis? Does a personal story feel out of place? Lucas: It depends on the execution. There's a financial analyst named Priya Shah who writes 'The Yield Curve,' a daily macro newsletter. Her origin story is literally about a spreadsheet. She was a junior analyst at a hedge fund, and she built a model that predicted a bond market move that her seniors missed. She says that spreadsheet was her 'first love.' Luna: A love story about a spreadsheet. That's oddly charming. Lucas: It is. And it works because it's honest. Her paid subscribers — about 4,000 of them — say they trust her analysis because they know she's been obsessed with this stuff since her first job. The provenance story becomes a credential that no resume can replicate. Luna: I want to ask about the mechanics. How do you actually test a provenance story without rewriting your entire welcome sequence? Because that's a big investment. Lucas: Start small. You don't have to do a four-email arc. Write one 300-word 'why I started this' post and put it as the second email in your existing welcome sequence. Run an A-B test against your control — which is probably just a 'thanks for subscribing' email with a link to your most popular post. Luna: And what metric do you look at in the test? Lucas: Click-through rate to the paid landing page is a good proxy. But the real metric is conversion to paid within 14 days. Devine's data showed that the provenance sequence had a 40 percent higher click rate to the paid page, and that translated directly to the 2.5x conversion number. Luna: So you can test with a single email and see if the click-through lifts. If it does, then you invest in the full arc. Lucas: Exactly. And one more thing — don't lead with the paid ask in that first provenance email. The whole point is that you're giving the story without an immediate ask. The ask comes later, after the reader has had time to connect with you. Luna: That's a counterintuitive lesson for a lot of newsletter writers who are trained to put the offer front and center. Lucas: If today was actually useful to you — maybe you're thinking about testing a provenance story yourself — the way these episodes stay ad-free is listener support. You can buy me a coffee at buy me a coffee dot com slash fexingo. It genuinely helps keep this show going without sponsors. Luna: Yeah, and we love hearing from listeners who try these strategies. It's one of the best parts of doing this show. Lucas: Okay, back to the data. There's one more number I want to share. Devine tracked his paid subscriber churn over six months, and the readers who came through the provenance sequence had a 12 percent lower churn rate than those who subscribed through other channels, like a guest post or a referral. Luna: That makes sense. If they bought into the story, they're less likely to feel like the newsletter isn't delivering value. They're invested in the narrative, not just the content. Lucas: Right. And that's the real argument for provenance. It's not just a conversion tool — it's a retention tool. The story keeps them subscribed even during weeks when the content is a little weaker. Luna: So what's the one takeaway for someone listening right now who wants to try this? Lucas: Write down your origin story in 200 words. Focus on one specific moment — a failure, a realization, a conversation that changed your direction. Put that at the top of your welcome sequence. Measure your paid conversion rate for the next 30 days. If it moves, you've found something worth building on. Luna: And if it doesn't move? Lucas: Then your story might not be the right one, or the timing might be off. But the test costs you one email. That's a cheap experiment for a potential 2.5x improvement.