658 WORDS | READ TIME: 2.8 MIN | CHANGE FLAG: FEATURES
Allow me a minute to walk down memory lane
Episode 8 went live on Veterans Day, so we're tying this writeup to my grandfather's famous army stories, from when he served as a codebreaker in WWII.
He'd chuckle as he told us about the guy across the mess hall who, so engrossed in conversation, didn't notice he was sprinkling an entire layer of pepper across his bowl of soup. Until he took a taste, frowned slightly – and shook in some more!
Then there was his buddy, Rodriguez Rodriguez, who, pointing insistently at the skull and crossbones on the label, refused to share the chili peppers his mom sent from Mexico. Rodriguez eventually caved to my grandfather's bravado, telling him to just place the pepper against his lip.
"Smoke came pouring out of my ears! My mouth blistered! I was red for weeks!"
But my favorite story was his chocolate Slurpee story.
He and another soldier got lost in a blizzard, in hostile territory. They wandered for days, until all they had left of their rations were a few squares of chocolate. They melted it in their soup cans, added snow, and – voila, chocolate Slurpees!
Thankfully, they stumbled on another US base. After pop culture questioning to confirm they were true Americans (What was Popeye's wife's name? What about his baby?), they were ushered into the mess hall, and served "the best bowl of potato soup I'd ever tasted."
What in the world does this have to do with SaaS?
My grandfather's stories would hold the room. Even as he told them for the 897th time. He never got sick of them – and because he told them with the same fire each time – neither did we. Every telling was another adventure.
There's no such thing as a free push
There's been a lot of talk about what shipping costs now that AI has made coding "free." Operators bemoan product bloat. Irrelevant messaging. Code that isn't being maintained. Duplicate features even.
But there's one cost that I've only heard one mention of:
When it's easy to create something new, we don't actually get value from what we've already built
This isn't actually a new problem (though it is a "new" problem)
We've always loved shipping new features. In fact, there's a neurological reason for loving launches. In 2006, two neuroscientists found that a midbrain region tied to motivation and reward lights up for novelty. We're literally motivated by new.
That new buzz is also what makes our whole industry fall for acquisition and "forget" about retention. A new account gets a Slack emoji storm and the gong. A renewal gets… a calendar reminder.
New is exciting. Existing feels like maintenance. And we staff, budget, prioritize, and celebrate accordingly.
Which is frustrating (and illogical), because existing is where the biggest wins live.
One page, lots of use cases
In Episode 8 of Churn Flags, Collin Mayjack (who ran product marketing at Sybill when we recorded, and is now Head of Product Marketing at Storylane) launched a "What's New" page that he's used again and again:
"I don't want to put all this work into this page for it to not get any distribution."
So, when there's no obvious CTA for the product emails, buttons point to the "What's New" page. The founders drop the link to the page in the comments under launch posts. And Sybill AEs started walking prospects through the page on sales calls (a page full of recent releases makes a pretty convincing case that the team moves fast).
But even more apropos, the page itself gives every release a second, third, and fourth shot at being seen. Every time they share the page, a customer scrolls around and stumbles on a feature they almost missed.
The page helps Sybill get the most out of their features. Which really means their customers are getting the most out of the product too.
Kind of ironic for a page called "What's New."
Your release notes are a feature adoption asset in disguise | ft. Collin Mayjack, ex-PMM at Sybill, current Head of PMM at Storylane
What else did we dive into in Episode 8 of Churn Flags?
The reply to a renewal email that kicked off this whole page: a customer about to leave because Sybill "didn't have" a feature that Sybill very much had.
The 20-versus-500 queries a week gap that showed who actually needed the feature – and it wasn't the user Sybill was built around.
And my favorite: six months of weekly use-case emails that moved older customers past "it's a call recorder" (and the three numbers that prove it).
EP. 8 | FEATURES FLAG Sybill doesn't have MCP connectors (spoiler: they do) No you don't. Yes we do. No you don't. Yes we do.This is not the conversation Collin Mayjack had when one of his customers almost churned.But it might've been less absurd than the one they did have. Because this customer almost left because they needed a provider with MCP connectors. And Sybill has MCP connectors. Collin's got some bold ideas on how to stop this from happening again: Your release notes are a feature...
*ducking the rotten tomatoes you'll fling my way if you're a corny joke hater How do you get from First Click to Renewal in 3 days? .........(ready?) You join the Scaling SaaS Summit! Corn (and tomatoes) aside, most summits cover just one piece of the lifecycle. And this one spans the whole thing. That's a lot to cover in 3 days, but you're in good hands. Everything from pricing tests, revenue blockers, and AI (of course). By excellent operators like Gia Laudi, Asia Orangio, Marcos Rivera,...
757 WORDS | READ TIME: 3.2 MIN | CHANGE FLAG: PERCEPTION How do you say anesthesiologist in 3-year-old? The costume my oldest picked as soon as she had an opinion? An “anasneezeologist,” complete with scrubs, a shower-turned-surgical cap, and a stethoscope that stayed around her neck for weeks. Every stuffed animal in the house was subject to surgery that year. She was inspired by her Papo, my father. And let me tell you, it was good fun growing up with a doctor for a father. While everyone...