Why the Fastest AI Companies Are Ditching Traditional Customer Success
The customer success playbook that dominated the last decade is now actively hurting AI companies. Leaders from Lovable, Harvey, and Assembly AI revealed at SaaStr AI 2026 that the structural shift away from traditional customer success management (CSM) roles is not a rebrand, but a fundamental reorganization of where customer-facing work actually happens. The data tells the story: the CSM role grew over 700% through mid-2022, then flatlined for four years running. Meanwhile, forward-deployed engineering positions have climbed more than 1,000% and continue rising.
What's Actually Changing in Customer Success?
The problem starts with job titles themselves. Ryan Seams, head of customer success at Assembly AI, noticed that technical buyers would visibly tense up the moment he introduced himself with the "head of customer success" title. When he rebranded the role to "forward-deployed engineer," the recruiting pipeline transformed dramatically. Instead of struggling to fill positions, he went from two candidates in 2.5 months to a full pipeline, with no change to the actual work being done.
This shift reflects a deeper truth about AI products: they move too fast for traditional quarterly cycles and annual renewal playbooks. Monica Perez, who leads customer success at Lovable, the fastest company in the world to reach $400 million in annual recurring revenue, explained that the entire rhythm of customer engagement needs to change. "Quarterly cycles, 90-day plans, QBRs, annual renewals. All of it was built for products that shipped a couple times a year," she noted. Lovable ships multiple times a day, so customer success has to move at product speed.
"The moment you stop saying AI in every sentence is the moment you actually become AI-native," said Monica Perez.
Monica Perez, Customer Success Leader at Lovable
Perez also challenged the assumption that leading with AI as a headline signals innovation. In fact, it signals the opposite. "AI is becoming the baseline, the ambient layer that powers everything, not the story," she explained. If you're the fish, AI is the water. Lovable's onboarding no longer starts with what AI can do; it starts with what the customer will unlock.
How Are Leading AI Companies Restructuring Customer Success?
- Rewire the Clock: Replace quarterly cycles and 90-day plans with weekly or daily rhythms that match product velocity. Lovable provides every customer with a Slack channel powered by an AI bot scoped to their specific instance, projects, users, and contract terms, with hundreds of individualized bots built with no additional complexity.
- Design for Experiences, Not Activities: Stop organizing customer success around who runs onboarding or handles renewals. Instead, focus on outcomes. Lovable runs full-time hackathons at customer offices; at T-Mobile, customer teams shipped over 100 working applications in a single day. The company offers product management and engineering as a service.
- Control Your Stack: Don't wait for vendor roadmaps. Lovable rebuilt its entire customer success platform on Lovable itself, replacing Gainsight with a command center versioned weekly. This tracks the customer portfolio in real time, surfaces risks and expansion opportunities before they become crises, and generates individualized living customer hubs.
- Align Revenue and Value: Consumption and credit-based billing flip the incentive structure. The more a customer uses the product, the more they pay, so revenue is driven by adoption, and adoption is driven by everything customer success does. No awkward upsell, just "let me help you do more of what's working."
Tom Ronen, who leads customer success at Harvey, an $11 billion company, takes a different but equally revealing approach. He runs executive business reviews (EBRs) with heavy on-site work and old-school change management frameworks. His insight: selling AI into a law firm isn't selling software; it's selling a change in how 30-year partners work. Adoption, in his view, is now the starting line, not the finish line. A firm can log into Harvey constantly without changing how it operates, so daily use of the wrong workflows still means churn.
Ronen cited a Harvard study of 1,515 startups that proved the power of the human layer over the model itself. The study found that startups using the same AI tools and receiving the same training showed dramatically different outcomes based on one variable: a single change-management document. The group that received documentation on how teams like theirs had succeeded showed 2x more revenue and was 18% more likely to acquire paying customers.
What Metrics Actually Matter Now?
The panel of customer success leaders at SaaStr AI 2026 unanimously declared that Net Promoter Score (NPS), a metric that has dominated customer success strategy for years, is now dead. Bobby Cooper, CEO of Retention Intelligence, explained the problem: low response rates where non-responders are the churners, no clean correlation to gross revenue retention (GRR), and a heavy translation layer required to turn NPS into actionable insights. Ursula Llabres from Content Square flagged a real gap: companies can have a great NPS score sitting right next to weak retention.
Cooper's platform data revealed an even more troubling finding: over 50% of what customer success managers do has zero correlation with retention. The fix, according to Ashvin Vaidyanathan from LinkedIn, is to map every activity, human or agent-driven, to whether it changes the product outcome in the intended window, and cut what doesn't.
One case study proved the power of this reframing. Weave, a customer success platform, moved the "closed-won" line into implementation rather than at signature. A deal only counted as booked once the customer hit a success threshold inside implementation. This single change fixed the handoff between sales and customer success, aligned sales to qualify better, and took monthly churn from 4% down to roughly half a percent while scaling from $8 million to $200 million in annual recurring revenue through IPO.
John Gleason from SuccessVP noted that the fastest companies to reach $100 million in annual recurring revenue are all developer tools: Cursor reached that milestone in 12 months, Bolt in 14, Lovable in 8, and Replit's agent went from $10 million to $100 million in six months. "Code inherits high context and verifiable correctness for free," Gleason explained. "Every other domain has to engineer those conditions, and that engineering is the new job of customer success".
How Should Your Team Adapt to This Shift?
- Hire Builders, Not Playbook-Runners: Look for people who can show you their projects and what they've built, not just their process documentation. The customer success team should include forward-deployed engineers, product managers, and people who can run hackathons and masterminds, not just account managers.
- Build Your Own Tools: You don't need to be technical to own your customer success stack. Perez emphasized that the team closest to the customer should build the tool, and waiting on a vendor's roadmap is now the constraint, not the budget. Version your tools weekly like a product, with a feature backlog and continuous releases.
- Measure Adoption Outcomes, Not Activity: Stop tracking CSM calls, email touches, and QBR attendance. Instead, measure whether customers are using the product in ways that drive their intended outcomes. Cut activities that don't correlate with retention and expansion.
- Embed Customer Success in Implementation: Move the sales-to-success handoff earlier. Make adoption and outcome achievement part of the deal closure criteria, not something that happens after the contract is signed.
The evidence is clear: the companies winning in AI are not the ones perfecting the traditional customer success playbook. They're the ones willing to dismantle it entirely and rebuild customer-facing operations around speed, outcomes, and the unique demands of products that ship multiple times a day. For companies still operating on quarterly cycles and annual renewals, the clock is ticking.