If a customer asked you today, "What's your customer success roadmap for the next 18 months?" could you genuinely answer it?

And I don’t mean it in vague terms. I’m talking about specificity with timelines, deliverables, and a clear sense of what they'd be getting and when.

Most CS leaders can't. 97.2% of CS professionals believe their function contributes directly or indirectly to revenue, yet 54.3% have no dedicated CS Operations role and 66.8% have no CS Enablement function to back that belief up with structure.

That gap, more than anything else, is what holds customer success back from becoming the strategic revenue function it should be.

I've spent the last 18 months or so working through exactly this challenge at MuleSoft, a Salesforce company, where I lead CS as a regional VP. What follows isn't a polished framework that arrived fully formed; it's a journey we're still on, and one a lot of CS professionals will recognize from their own organizations.

The self-serving CS organization problem

Let's start with something uncomfortable: customer success organizations have, slowly and often unintentionally, become quite self-serving.

When customers interact with different parts of your post-sales team, they can sense the disconnection:

  • Support has its own SLAs
  • CS managers have their own KPIs
  • Training runs its own calendar
  • Leadership across these functions reports to different places and measures different things

Customers notice. They see that the people responsible for their success aren't operating from a shared mission.

Then there are the playbooks. Most CS teams have them, covering renewals, adoption, expansion, and advocacy. Valuable internally, sure. But if you're a customer, none of that is what you care about. You care about whether your vendor will show up in the moments that matter, and whether they understand your business well enough to help you succeed. 

Renewals and expansions are a byproduct of that relationship. When they become the primary KPI, the alignment with what customers actually need starts to drift.

This plays out in practical ways too. A CSM tries to escalate a support case because they know the business impact. Support, operating under different metrics, doesn't share the same sense of urgency. The CSM gets frustrated, the customer feels the friction, and nobody intended for any of it to happen. 

It happens constantly because there's no cohesive product holding the experience together.