The Agentic
CS Sprint
CS teams are being asked to do more with less. More accounts. Same team. Higher expectations. And everyone from your CEO to your board has an opinion about what you should be doing with AI.
Most of it is noise. This isn't.
If you're a Head of CS, you need something real you can point to. Not a strategy. Not a pilot. Something actually working in your operation before the next leadership meeting.
If you're a CSM, you need to stay relevant. The job is changing. The people who figure this out now are going to be in a completely different position than the ones who wait. Not because AI is going to take your job. Because someone who knows how to use it will.
The Agentic CS Sprint is three live sessions where you stop talking about AI in CS and start actually building it.
No code. No technical background required. We're going to talk to Claude, tell it what we want, and it'll build it. By the end you'll have something running in your CS motion. Guaranteed.
Three live sessions. Lincoln Murphy and Lewis Thompson. One agent deployed in your CS motion by the end. Guaranteed.
Registration for the April cohort is now closed.
Join the waitlist to be first to know when the next cohort opens.
Join the WaitlistThis Is for You If:
You're a Head of CS who needs to show up to the next leadership conversation with something real — not a roadmap, not a pilot proposal, but an agent actually running in your operation.
Or you're a CSM who wants to stay ahead of what's coming. You want to walk into your next review or your next interview with something you can actually show — not just a bullet point on your resume that says you 'leverage AI tools.'
You don't need to be technical. You need to be willing to show up and build.
And if you're leading a CS team trying to bring AI in: meet your CSMs where they are. Or you'll lose them before you start. The sprint is built around that principle.
This Is Not for You If:
This is not passive learning. There are no lectures to sit through. This is three live sessions where you show up, build something real, and leave with it running. If you're not ready to do the work, this isn't for you.
Before the Sprint Starts
We send you three things to get ready:
A setup guide to get your environment ready before Call 1.
A video walkthrough to help you identify which of the five agents will have the highest immediate impact for your operation — and how to use the Agentic CS Business Case Calculator if you haven't already.
A mindset video. The biggest thing stopping most people isn't the technology. It's the story they're telling themselves about it. We address that head on before we ever get on a call.
No Production Environment? No Problem.
We built one for you.
Before you ever connect your real systems, you'll build and test your agents against a fully loaded mock tech stack — seven interconnected SaaS systems, all populated with realistic data from ten fictional B2B companies at every stage of the customer lifecycle.
CRM. Call recordings. Helpdesk. CS platform. Billing. Product usage. Knowledge base. All connected. All talking to each other.
No single system tells the full story. The signals only emerge when you correlate across systems. Just like in real life.
Acme has a P1 ticket open 8 days with no CS response — and renewal is in 28 days.
BlueWave has an NPS of 10 and 48 of 50 seats used — but nobody's had the upsell conversation.
Ironclad was a champion six months ago. NPS dropped from 9 to 5 after a $340 billing dispute on a $2,400 contract. Nobody caught it.
ForgePath's billing dispute is actually valid — the duplicate charge exists in the data.
Sound familiar?
When you're ready to go live after the sprint, you swap our demo URLs for your real systems. The agents don't change. Just the data source.
If you have privacy concerns about connecting internal systems, this solves that. If you're between roles and don't have a production environment, this solves that too.
The Schedule
Three sessions. One deployed workflow.
Call 1
April 7
CS Audit and Agent Selection
Lincoln leads your CS audit. We look at your operation, identify your highest-leverage gap, and confirm which of the five agents you're building.
This is also where we answer the question that changes how you think about your CS operation: what complexity are you currently forcing onto your customer that you could eat?
One company we worked with was giving away 15% off their contracts just to get customers to complete one technical setup step. They built an agent to handle that step for the customer. Got the 15% back. That conversation starts here.
Lewis maps the audit to what's buildable. You confirm your agent. You're ready to build.
Call 2
April 8
Hands-On Build Session
Lewis solo. Hands on keyboard, real data. Anyone stuck gets unblocked first.
You do not need to be a developer. You do not need to know how to write code. We're just going to talk to Claude and tell it what we want. By the end of this session, it will be doing it.
End of call: working draft running locally on your machine.
Call 3
April 13
Deploy to Production
Your agent goes live. Real data. Your actual CS motion.
Lewis and Lincoln close with the strategic picture — how the other four agents in your repo fit into your operation, what to build next, and the sequencing that makes sense for where you are right now.
You leave with one agent in production, a clear picture of what comes next, and the ability to build more on your own.
What You Get
We start you with a repo of five pre-built agents covering the highest-leverage CS use cases. In Call 1 we identify which one will have the highest immediate impact for your specific situation. We take that agent, make it work for your operation, and deploy it. In the process you learn exactly how to deploy the other four — and how to build your own from scratch.
The five agents:
Churn Risk Summarizer
Turns recent account activity into a plain-language risk narrative so your CSMs know exactly where to focus.
Expansion Signal Detector
Spots upsell signals in call notes and transcripts before the opportunity goes cold.
Invisible Handoff
Turns a closed-won deal into a complete CSM handoff brief so CS starts the relationship with full context instead of piecing it together after the fact.
Earned Ask
Decides when to ask for a G2 review and drafts the email so your team asks at the right moment every time.
Trust Radar
Reads win-back calls and tells you whether you're dealing with genuine loss of trust or a negotiating tactic, so your team responds accordingly.
You also get:
Recordings of all three sessions — keep them, refer back, share them with your team.
A ranked build-next list — the other four agents prioritized by impact for your specific setup.
A completed CS audit — a clear map of where agents can move the needle in your operation.
Private cohort Slack — access during the sprint and 48 hours after for questions and follow-up.
Our Guarantee
By the end of the sprint you will have at least one agent fully deployed in your CS motion — doing real work on real data.
If that doesn't happen, Lewis and Lincoln will get on a call with you personally and build it with you until it's done.
No asterisks. No fine print. No "results may vary." One working agent in production or we show up until it is.
What This Unlocks
Once you have one agent running, something shifts. You stop asking whether this is possible and start asking what else you can build.
For CS leaders, that means a team that's more consistent, more proactive, and more capable without adding headcount. Churn signals caught earlier. Expansion opportunities surfaced before they go cold. Handoffs that actually work. The KPIs that matter — NRR, LTV, CAC efficiency — start moving because the work that drives them is finally getting done.
For CSMs, it means showing up differently. Less time on the administrative layer. More time on the relationship. More capacity to actually do the work that makes you good at this.
And as AI becomes part of everything and technology gets commoditized, the relationship your team has with your customers is what's defensible. The expertise. The trusted advisor. The human who knows when a customer needs a call instead of an email.
Agentic workflows are what give your people the capacity to be that. At a scale that was never possible before.
The sprint is where it starts.
Your Instructors
Lincoln Murphy
Wrote the book on Customer Success in 2016. Invented the discipline that changed how the entire SaaS industry thinks about retention, expansion, and customer lifetime value. Ten years later, the second wave is here — and he's been at the beginning of this once before.
Lewis Thompson
Deployed agentic workflows across thousands of client engagements. He doesn't talk about what's theoretically possible. He builds it, ships it, and shows you exactly how it works. Not a developer by background. Which means when he says you don't need to be one either, he means it.
Registration Closed
Join the Waitlist for the Next Cohort
The April cohort is full. Sign up below to be the first to know when we open registration for the next one.