Your Customers Are Quietly Building Replacements. Here’s the Data That Proves It.
Most SaaS churn you can see coming. Usage drops. Support tickets spike. They ask about export tools. You get the signal.
Then there's the other kind. The one that starts when you stop shipping. Jason Lemkin over at SaaStr just lived it: after six years as a happy, paying customer, he ditched a newsletter tool in about two hours of vibe coding. Not because it was bad. Because it had frozen in time. His piece is a must-read for any B2B founder—part cautionary tale, part pragmatic guide. He calls it "stealth churn," and if you run a point solution, it might already be happening to you.
Here's the part we want to zoom in on: this isn't just one vendor's bad luck. It's a pattern. And we have numbers.
On PainSignal, the problem "Newsletter tool lacks AI-powered content curation" scores a severity of 3.8 out of 5. That's significant. This isn't a niche gripe—it's a pain shared across 12 businesses we track, with a severity that signals real frustration, not just feature requests. Users are annoyed enough to be looking for alternatives. Or building them.
Lemkin's experience was specifically about a tool that didn't auto-populate newsletters with content, didn't summarize posts, and didn't pull from APIs. The "lacks AI-powered content curation" problem encapsulates exactly that gap. It's not that the tool was broken. It's that the tool didn't evolve, and now the expectation has shifted. The market knows AI can do this. When a tool sits still while the world around it moves, loyalty doesn't hold.
We track 20 active problems in the Communication space alone, and many of them share a DNA with this newsletter example: tools that are single-purpose, slow to adopt AI, and ripe for replacement by a custom build. These are point solutions where the buy-vs-build math has changed. AI coding tools didn't just make it cheaper to build—they made it possible for a non-engineering founder to ship something tailored in a weekend. That wasn't true five years ago. Now it is.
But here's the upside Lemkin doesn't fully explore: where there's stagnant pain, there's hungry founders. Across the 11,013 app ideas on PainSignal, several are AI-native newsletter builders. The market isn't just complaining—it's trying to fix it. That's a signal for both investors and indie hackers. The gap between "this tool stinks" and "someone should build a better one" is shrinking. In some cases, the person who thinks "someone should build this" is already opening Replit.
If you're a vibe coder or indie hacker reading this, the takeaway isn't just "watch out for frozen tools." The takeaway is: go look at those severity scores on PainSignal. Find a point solution category where the frustration is high and the features being asked for are actually just AI-wrapping basic integrations and content APIs. You can build that. And the first-mover advantage is real—especially if the incumbents are asleep at the wheel.
For seed investors, the pattern is even clearer. When a known, well-liked tool has a "lack of AI" problem with a high severity score and multiple businesses flagging it, that's a red flag for incumbents and a green light for AI-native upstarts. This isn't disruption by a cheaper clone. It's displacement by something that actually fits the modern workflow, built by someone who understands that a newsletter isn't just an email blast anymore—it's a curated content surface.
Lemkin's advice to SaaS founders is sound: ship faster, build moats, integrate AI deeply. But I'd add one more: listen to the pain signals. Not the feature requests that land in your support queue. The ones your best customers feel but never say out loud. They're out there, quietly scoring 3.8 on a pain index while you wonder why retention dipped three months later.
That's the real insight behind Lemkin's anecdote. The newsletter vendor probably had no idea he was unhappy. He paid his bill. He used the product. And then one Saturday, he replaced it. By the time they notice, he's gone—and Amelia is saving 90 minutes a week. If you're a founder, go find your own "newsletter tool." It's probably hiding in your customer base, with a 3.8/5 frustration level and a weekend free to build.
This article is commentary on the original article by Jason Lemkin at SaaStr. We encourage you to read the original.
Explore more problems and app ideas across SaaS, Marketing Technology.
Browse App Ideas