LEADERSHIP
The CCO Isn’t Going Extinct. The Job Is Getting Bigger.
The CCO Isn’t Going Extinct. The Job Is Getting Bigger.
The CCO Isn’t Going Extinct. The Job Is Getting Bigger.
There’s been a lot of discussion about whether AI will make the Chief Customer Officer less relevant. I think that question starts from an outdated definition of the role.
If the CCO is primarily responsible for managing Customer Success, monitoring satisfaction, and escalating customer issues, then yes, technology can take on more of that work. But I don’t think that’s the job companies need from a CCO anymore.
The more interesting question is why a company needs a CCO in the first place.
It isn’t because one executive should “own the customer.” I’ve never particularly liked that idea. Customers have a relationship with the company, and nearly every part of the business shapes that relationship. Sales sets expectations. Product creates value. Implementation gets customers started. Customer Success drives adoption. Support solves problems. Finance, Operations, and Marketing all influence the experience in ways customers can feel.
The problem is that nobody experiences those functions separately except the company itself.
The customer sees one company. The company often sees a collection of functions. That gap is where I believe the CCO matters most.
For me, the role is increasingly about connecting what the company knows about its customers to how the business operates and grows.
That becomes much more powerful with AI. We can now bring together signals that historically lived in different places: product usage, adoption, support interactions, sentiment, implementation progress, commercial history, and direct customer feedback. We can identify patterns earlier, understand risk differently, and see opportunities that were difficult to recognize when each function was looking at its own piece of the customer.
But having more customer intelligence doesn’t create value by itself. What matters is whether it changes a decision.
If customers repeatedly struggle with the same issue, does Product see it quickly enough to remove the friction? If adoption patterns predict churn, do we change how and when we engage? If the healthiest customers behave differently, are we using that knowledge to improve onboarding and expansion? If we know what creates unnecessary support demand, are we fixing the underlying experience or simply getting better at handling the contacts?
That’s where I see the CCO mandate expanding.
Customer intelligence should influence product priorities, operating investments, service models, commercial strategy, and where people spend their time. The CCO should be able to move comfortably between the customer conversation and the business conversation because increasingly they are the same conversation.
That also means the measures of success have to evolve. NPS and CSAT still tell us something useful, but they aren’t enough. I care about whether customers adopt, stay, grow, advocate, and realize the value they came to us for. I also care about what it costs to deliver that experience and whether the operating model can scale as the business grows.
A customer organization shouldn’t just report what customers are telling us. It should change what the business does next.
That, to me, is the bigger future for the CCO.
AI will automate parts of customer work, and it should. It will also give every function access to more customer information, which is a good thing. Neither eliminates the need for customer leadership. They raise the expectation for it.
The CCO isn’t going extinct. The narrower version of the job might be.
What replaces it is a more commercially accountable executive who can connect customer intelligence, operating decisions, and growth across the enterprise. That’s a much bigger job, and I think it’s where the role should have been heading all along.
There’s been a lot of discussion about whether AI will make the Chief Customer Officer less relevant. I think that question starts from an outdated definition of the role.
If the CCO is primarily responsible for managing Customer Success, monitoring satisfaction, and escalating customer issues, then yes, technology can take on more of that work. But I don’t think that’s the job companies need from a CCO anymore.
The more interesting question is why a company needs a CCO in the first place.
It isn’t because one executive should “own the customer.” I’ve never particularly liked that idea. Customers have a relationship with the company, and nearly every part of the business shapes that relationship. Sales sets expectations. Product creates value. Implementation gets customers started. Customer Success drives adoption. Support solves problems. Finance, Operations, and Marketing all influence the experience in ways customers can feel.
The problem is that nobody experiences those functions separately except the company itself.
The customer sees one company. The company often sees a collection of functions. That gap is where I believe the CCO matters most.
For me, the role is increasingly about connecting what the company knows about its customers to how the business operates and grows.
That becomes much more powerful with AI. We can now bring together signals that historically lived in different places: product usage, adoption, support interactions, sentiment, implementation progress, commercial history, and direct customer feedback. We can identify patterns earlier, understand risk differently, and see opportunities that were difficult to recognize when each function was looking at its own piece of the customer.
But having more customer intelligence doesn’t create value by itself. What matters is whether it changes a decision.
If customers repeatedly struggle with the same issue, does Product see it quickly enough to remove the friction? If adoption patterns predict churn, do we change how and when we engage? If the healthiest customers behave differently, are we using that knowledge to improve onboarding and expansion? If we know what creates unnecessary support demand, are we fixing the underlying experience or simply getting better at handling the contacts?
That’s where I see the CCO mandate expanding.
Customer intelligence should influence product priorities, operating investments, service models, commercial strategy, and where people spend their time. The CCO should be able to move comfortably between the customer conversation and the business conversation because increasingly they are the same conversation.
That also means the measures of success have to evolve. NPS and CSAT still tell us something useful, but they aren’t enough. I care about whether customers adopt, stay, grow, advocate, and realize the value they came to us for. I also care about what it costs to deliver that experience and whether the operating model can scale as the business grows.
A customer organization shouldn’t just report what customers are telling us. It should change what the business does next.
That, to me, is the bigger future for the CCO.
AI will automate parts of customer work, and it should. It will also give every function access to more customer information, which is a good thing. Neither eliminates the need for customer leadership. They raise the expectation for it.
The CCO isn’t going extinct. The narrower version of the job might be.
What replaces it is a more commercially accountable executive who can connect customer intelligence, operating decisions, and growth across the enterprise. That’s a much bigger job, and I think it’s where the role should have been heading all along.
There’s been a lot of discussion about whether AI will make the Chief Customer Officer less relevant. I think that question starts from an outdated definition of the role.
If the CCO is primarily responsible for managing Customer Success, monitoring satisfaction, and escalating customer issues, then yes, technology can take on more of that work. But I don’t think that’s the job companies need from a CCO anymore.
The more interesting question is why a company needs a CCO in the first place.
It isn’t because one executive should “own the customer.” I’ve never particularly liked that idea. Customers have a relationship with the company, and nearly every part of the business shapes that relationship. Sales sets expectations. Product creates value. Implementation gets customers started. Customer Success drives adoption. Support solves problems. Finance, Operations, and Marketing all influence the experience in ways customers can feel.
The problem is that nobody experiences those functions separately except the company itself.
The customer sees one company. The company often sees a collection of functions. That gap is where I believe the CCO matters most.
For me, the role is increasingly about connecting what the company knows about its customers to how the business operates and grows.
That becomes much more powerful with AI. We can now bring together signals that historically lived in different places: product usage, adoption, support interactions, sentiment, implementation progress, commercial history, and direct customer feedback. We can identify patterns earlier, understand risk differently, and see opportunities that were difficult to recognize when each function was looking at its own piece of the customer.
But having more customer intelligence doesn’t create value by itself. What matters is whether it changes a decision.
If customers repeatedly struggle with the same issue, does Product see it quickly enough to remove the friction? If adoption patterns predict churn, do we change how and when we engage? If the healthiest customers behave differently, are we using that knowledge to improve onboarding and expansion? If we know what creates unnecessary support demand, are we fixing the underlying experience or simply getting better at handling the contacts?
That’s where I see the CCO mandate expanding.
Customer intelligence should influence product priorities, operating investments, service models, commercial strategy, and where people spend their time. The CCO should be able to move comfortably between the customer conversation and the business conversation because increasingly they are the same conversation.
That also means the measures of success have to evolve. NPS and CSAT still tell us something useful, but they aren’t enough. I care about whether customers adopt, stay, grow, advocate, and realize the value they came to us for. I also care about what it costs to deliver that experience and whether the operating model can scale as the business grows.
A customer organization shouldn’t just report what customers are telling us. It should change what the business does next.
That, to me, is the bigger future for the CCO.
AI will automate parts of customer work, and it should. It will also give every function access to more customer information, which is a good thing. Neither eliminates the need for customer leadership. They raise the expectation for it.
The CCO isn’t going extinct. The narrower version of the job might be.
What replaces it is a more commercially accountable executive who can connect customer intelligence, operating decisions, and growth across the enterprise. That’s a much bigger job, and I think it’s where the role should have been heading all along.
KEEP READING
