Most AI content in customer success is purely hypothetical.

You read frameworks for what teams could do. You scan takes on what automation might mean for the role. You see thought leadership dressed up as strategy.

We did something different.

We recently ran our second Uncommon AI Demo Day. We banned recording devices, transcription tools, and the standard content marketing machine. Just 600 customer success leaders watching their peers demo the actual tools they built.

No slides. No theoretical roadmaps. Just execution.

The first builder showcased a system that captures customer praise.

The application scans Fathom call recordings for positive customer quotes. It processes the text using Claude via Cowork and routes the output into a dedicated Slack channel automatically.

Most organizations have a chaotic relationship with customer love. A sales rep screenshots an email. A CSM pastes a message into a document. A marketer asks around for testimonials before a launch.

This automation closes the loop. Every genuine moment of praise surfaces in one workspace in real time.

The goal is a living proof library that marketing, sales, and executive leadership can access instantly. It treats the voice of the customer as infrastructure rather than an afterthought.

The second builder turned passive call data into an active resource.

The team constructed a vector database for call recordings using Claude Code, Supabase, and Google OAuth. They designed a tagging system that allows users to query their entire history of customer conversations.

Most companies treat call recordings like a digital graveyard. You search for a customer name, locate a file, and scrub through the audio.

This infrastructure inverts that process. The conversational data becomes searchable at scale.

Leaders can query the database to find exactly what customers say about onboarding friction. They can isolate the objections that appear before a churn event. They can map what their healthiest accounts have in common.

The data transforms from a stagnant repository into the core intelligence layer of the company.

The final builder shipped a proprietary customer success platform directly into production.

The software uses Claude Code, Vercel, Supabase, Salesforce, Gong, and Zendesk. The features help CSMs prioritize accounts and structure their weekly calendar.

Dozens of customer success tools exist on the market. Most are built by product teams who interview users but have never actually run a portfolio.

This platform was built by practitioners who refused to wait for a vendor roadmap. The result is software that mirrors how a CSM actually views their book of business. It integrates data from the exact systems the team uses every day.

The team spends less time figuring out where to look and more time executing the work that secures retention.

The conversation during the event focused heavily on structural momentum.

Teams must build the data architecture that AI initiatives require to plug into the business. The gap between experimenting with an LLM and executing software in production is wide.

That friction point is where most customer success organizations remain stuck. They’re trapped in a loop of endless pilots and prompt testing.

The builders in that room moved past the testing phase. They stopped talking about what’s possible and started deploying code.

If you want to join the room for our next session, you can register here.

Stop analyzing the trend. Start building the solution.

🤘

We’re grateful you choose to read each week. When you’re ready for more, there are a couple ways we can help:

» Cover Your SaaS is a financial literacy course for go-to-market leaders. Grab your copy here.

» Promote your product and services to over 5,500+ senior SaaS Customer Success pros by sponsoring our weekly newsletter and podcast.

Was this email forwarded to you? Sign up at ChiefCustomerOfficer.io.