Episode 113 — Customer Success Excellence: Chad Stephen

Once you’ve sold the licenses you are done. Right? Well, not so fast, young Jedi.

While the salesperson happily will turn around and go hunting elsewhere, the customer has high expectations about the treatment that he gets after the sale.

And even today I see organizations who see Customer Success teams as an afterthought and then wonder why they see churn or nastygrams from their customers. But it doesn’t have to be this way. We are discussing this interesting topic and organizational setup with Chad Stephen.

Chad has led cross-functional teams of 65, scaled the Customer Success org through 4x ARR growth, cut renewal process complexity by two thirds, and reduced time-to-value by 50%. More than once, at different companies. He has done it multiple times, at companies ranging from early-stage to scaled SaaS, across industries from FinTech to HealthTech to Restaurant & Hospitality.

In this episode of the podcast, we talk about:

• What is customer success, really? — Customer success means different things to different people, but the most important definition centers on one thing: driving value for clients. Renewals, onboarding, and account management are elements of CS, not the definition of it.
• The buyer vs. the end user — The person who signs the contract is rarely the one logging into the platform every day. A good CS function speaks to both audiences and translates the value proposition into something meaningful for each one.
• CS as a function, not just a job title — In any project or transformation, customer success is a function that can be owned by a team, a role, or — dangerously — “everyone,” which usually means no one. The discipline matters regardless of what you call it.
• The QBR trap — Quarterly business reviews that run 80 slides and double as sales pitches miss the point entirely. The best QBRs are about the customer’s problems, not the vendor’s product roadmap.
• Proactive vs. reactive CS — Waiting for a customer to come to you with a problem is reactive. True proactive CS means monitoring usage metrics, NPS surveys, and engagement signals before a crisis happens — not just crossing your fingers.
• The relay race handoff — The baton cannot hit the floor between sales, professional services, and customer success. There must always be a clear, singular point of contact for the client at every stage of the journey.
• When to involve CS in the sales cycle — CS should never be absent from a deal entirely, but timing matters. Bringing them in too early creates confusion; bringing them in at the right moment builds the bridge between “excited to sign” and “ready to succeed.”
• The hunter vs. farmer problem — When account executives are compensated only for net-new deals, they make poor customer success managers. Misaligned incentive plans produce misaligned behavior — something always falls through the cracks.
• Compensation drives behavior — If you want your CS team to own renewals and upsells, you have to pay them for renewals and upsells. Comp plans and job expectations must be in alignment, or you get animosity and dropped balls.
• Start CS early — even at Series A — Smaller organizations often default to the AE managing the account post-sale. The sooner a dedicated CS function exists, the better. Stickiness in SaaS is decreasing, which makes the long-term relationship even more critical.
• Onboarding is the most critical phase — Getting a customer up and running quickly, and with a clear understanding of the value they bought, sets the tone for the entire relationship. A poor start rarely gets fully recovered.
• Keep it simple — Over-engineered CS motions with 12 segmentation layers and elaborate playbooks often collapse under their own weight. The question to always ask: How does this actually drive more value for the customer?

You can find Chad on LinkedIn here: https://www.linkedin.com/in/chadstephen/. And, of course, he has a website—https://www.doublewindconsulting.com/.

Please reach out to us by either sending an email to hello@whatsyourbaseline.com or signing up for our newsletter and reading articles about process and architecture on our Substack… Go and subscribe at whatsyourbaseline.substack.com.

And if you like to support “the little podcast that could,” become a Patron at https://www.patreon.com/c/whatsyourbaseline. We appreciate you!

Additional information

• This is the Presales episode with Max that we mentioned a couple of times: https://www.whatsyourbaseline.com/blog/2026/04/13/episode-111-presales-max-lupertz/

Credits

Music by Jeremy Voltz, www.jeremyvoltzmusic.com