The Story
Jason Lemkin, co-founder of SaaStr and one of Marketo's first 10 customers in 2006, spent weeks escalating a broken unsubscribe link with Adobe Marketo support. No resolution. Multiple calls. Support blamed integrations, Salesforce, Beehiiv (which SaaStr does not use). Eventually, Lemkin's team coded their own unsubscribe handler using Claude and Replit in an afternoon, replacing a core feature of a $60k+ per year product.
Marketo, acquired by Adobe in 2018, competes with HubSpot, Salesforce Marketing Cloud, and Oracle Eloqua in the marketing automation segment. The failure sits inside a classic installed-base retention risk: a 20-year customer relationship breaking down over a CAN-SPAM compliance issue on basic functionality.
The Retention Pattern
Lemkin's argument: B2B vendors bend over backwards for new logos, white glove onboarding, custom integrations, steak dinners, then abandon long-tenured customers to renewal emails, price increases, and support queues. The 20-year customer gets a rotated CSM every 14 months, nobody who remembers the original deal, and blame when something breaks.
That worked when switching costs were high and building alternatives was impossible. Now Claude plus Replit ships production workarounds in hours, not weeks. Every patch customers build is one more reason they do not renew.
What This Means for Sales Teams
If you are carrying an enterprise book or managing key accounts:
- Do your five-plus year customers get the same treatment as new logos? Not renewal emails. Actual support, relationship ownership, response times.
- Does your support queue treat ARR equally? Or do new accounts get fast lanes while loyal customers wait three days for someone to blame their stack?
- Does your pricing reflect the relationship? A 20-year customer paying more than a brand-new logo for the same product is a sign you have stopped competing for them and started taxing them.
- Are you tracking churn risk by tenure? High-value, long-tenured accounts often churn quietly, stealth-churning modules or usage before the renewal conversation even starts.
The switching cost equation has collapsed. Customers can now build around your limitations faster than you can ship fixes. That changes the math on account management, retention strategy, and what loyalty actually costs when support breaks.
Worth noting: Lemkin has been vocal on SaaS retention economics for years. This is not a hot take. It is a $60k account walking because basic support failed for weeks. If it can happen to a founder with a 20-year relationship and a large platform, it is happening to your accounts too.