Not the version of CS that exists in most companies today. The version where you were responsible for the full customer relationship — adoption, outcomes, retention, and growth. Where upsell and cross-sell were part of the job, not someone else's quota. Where working with partners to drive expansion was expected, not exceptional.
I was 24. I had never done anything sales-related in my life.
And I loved it.
I loved it because it made sense. If a customer was succeeding with the product, achieving real business outcomes, getting value they could measure — of course they would want more. And who better to spot that opportunity than the person who had been working alongside them, understanding their business, guiding their adoption journey?
That year, I made President's Club. Not as a salesperson. As a CSM, on the channel side.
Not because I was selling. Because I was succeeding — and success, when it's genuine, creates its own commercial momentum.
A few years later, I watched Customer Success transform into something different.
The mandate narrowed. CS became about relationship management. Product adoption. QBR execution. Keeping customers happy enough to renew.
The commercial conversation moved firmly into Sales territory. CSMs became measured on health scores and NPS. Expansion became someone else's job. The partner ecosystem, once a core part of driving customer outcomes, became a separate workstream — managed by a different team, in a different conversation.
And CS, slowly but decisively, became a cost centre.
Not because the function had less value. Because it had been redesigned — deliberately or not — to deliver less.
I have a fundamental problem with that.
CS doesn't become a predictable revenue driver by accident.
It doesn't happen because you deploy better tooling or run more QBRs or hire a few more CSMs. It happens when you make a deliberate architectural decision: that CS exists not just to protect revenue, but to grow it.
That decision has consequences. It changes who you hire. It changes how you measure performance. It changes how you think about the partner ecosystem. It changes the mandate CS carries into every customer conversation.
And it changes what you build.
If a customer is achieving genuine business outcomes — if they're realising value, hitting milestones, expanding their use of the platform in ways that matter to their business — they will want more. They will be ready to buy more. The expansion conversation doesn't need to be forced or handed off. It emerges naturally from the success motion.
But only if CS is designed to see it. And act on it.
Making CS a predictable revenue driver requires three things working together.
A growth mandate, not just a retention mandate. CS needs to own not just the renewal conversation but the expansion signal — the moment a customer is ready to go further. That requires CSMs with genuine business acumen. People who understand the customer's business well enough to connect product capability to commercial opportunity. People who ask "where are you leaving value on the table?" not just "are you happy with the platform?"
Incentives aligned to growth, not just survival. You get the behaviour you measure and reward. If CSMs are only measured on health scores and renewal rates, that's where their attention goes. Building CS as a revenue driver means creating accountability for expansion — not necessarily through quota, but through clear ownership of the conditions that make expansion possible.
AI as the intelligence layer, not the replacement layer. The Post-Sales Operating System doesn't automate the human relationship. It makes the human relationship more valuable by surfacing the signals that matter — which customers are ready to expand, which are at risk, which have unmet needs that map to specific partner capabilities. AI doesn't replace the CSM's commercial instinct. It sharpens it.
CS as a predictable revenue driver isn't a positioning statement. It's an engineering challenge.
And like any engineering challenge, it requires the right architecture.
Building an effective post-sales operating system is that architecture. Not a tool. Not a methodology. A designed system — built from the ground up to make retention systematic, expansion intelligent, and the partner ecosystem a precision instrument rather than an afterthought.
This is what it looks like when post-sales stops being managed and starts being designed.
Next in the series: From Customer Signal to Product Roadmap