Ep. 113 - Customer Success Excellence: Chad Stephen

What’s Your Baseline? Enterprise Architecture & BPM Demystified

Ep. 113 - Customer Success Excellence: Chad Stephen

What’s Your Baseline? Enterprise Architecture & BPM DemystifiedMay 11, 2026

Why It Matters

Understanding customer success as a value‑creation engine helps businesses shift from reactive support to proactive partnership, reducing churn and unlocking revenue growth. As SaaS adoption accelerates across industries, mastering this discipline is essential for any organization that wants to retain clients and scale sustainably.

Key Takeaways

  • Customer success centers on delivering measurable client value.
  • Proactive engagement beats reactive issue handling for retention.
  • Align success metrics with buyer’s goals, not just usage stats.
  • Regular, flexible check‑ins foster relationships and prevent escalations.
  • Distinguish financial buyers from end‑users to tailor communication.

Pulse Analysis

Episode 113 brings Chad Stephen, a veteran of high‑growth B2B SaaS, to discuss why customer success has become a strategic discipline rather than a support afterthought. Stephen describes customer success as the systematic delivery of measurable value to both the client and the provider, linking onboarding, adoption, and renewal under a single engine. He cites work with brands like McDonald’s, JPMorgan Chase, and the Yankees to illustrate how a clear value proposition drives predictable renewals and upsell opportunities. In today’s subscription economy, that focus on value is the cornerstone of sustainable revenue.

Stephen stresses that proactive, not reactive, engagement separates thriving CS programs from fire‑fighting operations. Regular, flexible check‑ins—whether high‑touch calls or digital touchpoints—create a predictable cadence that can be adjusted based on triggers rather than fixed schedules. He warns against bloated quarterly business reviews that prioritize slide decks over client problems, advocating instead for concise, problem‑focused conversations that tie every recommendation back to the client’s original goals. This structure gives CS teams a ready channel for escalation handling while respecting the customer’s time, ultimately turning potential issues into opportunities for added value.

Metrics become actionable when they reflect the buyer’s strategic outcomes, not merely platform usage. Stephen recommends mapping success indicators—such as Net Promoter Score, adoption rates, and revenue impact—to the distinct needs of financial buyers and end‑users, ensuring each stakeholder sees tangible ROI. By embedding these metrics into a unified CS engine, organizations can forecast renewals, identify upsell windows, and conduct targeted health checks without overwhelming the client. The episode concludes that a disciplined, value‑first approach to customer success turns every interaction into a growth lever for both the client and the SaaS provider.

Episode Description

Once you've sold the licenses you are done. Right? Well, not so fast, young Jedi. While the salesperson happily turns around and goes hunting elsewhere, the customer has high expectations about the treatment they get after the sale.

Even today I see organizations who treat 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 discuss this topic with Chad Stephen.

Chad has led cross-functional teams of 65, scaled Customer Success orgs through 4x ARR growth, cut renewal process complexity by two thirds, and reduced time-to-value by 50% — more than once, at different 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? — 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 in every day. A good CS function speaks to both audiences and translates value into something meaningful for each.

CS as a function, not just a job title — Customer success 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 focus on 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.

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 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; 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 incentives produce misaligned behavior.

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 align, 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, making the long-term relationship even more critical.

Onboarding is the most critical phase — Getting a customer up and running quickly, with a clear understanding of the value they bought, sets the tone for the entire relationship. A poor start rarely fully recovers.

Keep it simple — Over-engineered CS motions with 12 segmentation layers and elaborate playbooks often collapse under their own weight. Always ask: How does this actually drive more value for the customer?

You can find Chad on LinkedIn: https://www.linkedin.com/in/chadstephen/. And he has a website at https://www.doublewindconsulting.com/.

Reach out by emailing hello@whatsyourbaseline.com or subscribe to our newsletter and articles on Substack at whatsyourbaseline.substack.com.

Show Notes

Comments

Want to join the conversation?

Loading comments...