Trading Product Slides for Outcome Reporting Builds Renewal Strength From Day One

Customer success spent years defined by product adoption, tracking performance based on metrics like log-ins, feature usage, and support tickets resolved. While those data points tell teams whether customers are using the product, they say almost nothing about whether customers are actually getting value from it. The distinction determines whether a customer renews with conviction or drifts toward the exit while every dashboard still shows green. The CS organizations pulling ahead have started leading with outcomes over adoption, building every conversation, touchpoint, and piece of infrastructure around what the customer is actually trying to accomplish.

Oren Cohen understands the mechanics of that transition better than most. As Director of Customer Success & Support at technology solutions firm Cognizant who previously managed a $45 million annual contract value portfolio at Hewlett Packard Enterprise, he's seen the industry mature firsthand. He now manages a team of twenty CSMs alongside a cohort of AI agents that function as a parallel operational layer. He views the current moment as the most consequential shift the discipline has experienced.

"Customer success is going through a transition from being product-oriented and talking about adoption to understanding value. If you're not tied to what the customer is actually trying to achieve, you're having the wrong conversation." He contends that the ability to bridge the gap between technical features and business outcomes is no longer a soft skill, but a core mechanical requirement for managing high-value portfolios.

• Speak the customer's language: The value-first approach demands an industry fluency most CS teams haven't traditionally been asked to develop. From Cohen's perspective, the days of a CSM moving seamlessly from banking to pharma to manufacturing are over. Understanding the customer's world, like their competitive landscape and business objectives, is now table stakes. "You need to understand the industry. You need to understand the ecosystem. With that, you can speak the customer's language and understand what they hope to achieve. Features alone won't bring them where they want to go."

• Defining the value contract: This doesn't mean CSMs need to become domain experts overnight, but it does mean that the first conversation with a customer should establish a clear contract around expected value rather than being a product walkthrough. "No matter if it's a small customer or a big one, you need to agree on what exactly they expect and what they're going to get from you at each step," Cohen advises. "On the second meeting, you come with a plan. 'Last time we discussed these priorities, here's how we're going to achieve them and when.'"

Cohen is quick to emphasize that AI is a tool, not a strategy. He views it as an infrastructure layer that makes everything faster and more precise, but notes that it does not replace the human judgment that drives customer relationships. In practice, his team uses AI agents to prepare for every customer meeting automatically. CRM data, usage signals, ticketing patterns, and renewal timelines are consolidated into a single view. "Before I even drink my coffee, I have agents that give me a summary of all the day's meetings together with highlights of the history of these accounts and what the challenges are. Everything is ready to go." He coaches junior CSMs to build the infrastructure that delivers context automatically so they can spend their time on the conversation, not the preparation. "Before, you'd spend a day or two preparing for a single customer call. Today, you can get the same value in 10% of the time, but you have to be willing to build and maintain those tools. The CSMs who still prefer to do things manually are the ones falling behind."

• Value conversations replace generic QBRs: If Cohen had to name the single most impactful behavior change in modern CS, it would be the shift from quarterly business reviews to ongoing value conversations. He says the traditional QBR exhausts customers without delivering what they care about. "Customers have very little time, very little patience, and tons of vendors. Bringing them to a call and presenting forty slides from a deck doesn't bring value. Instead, we're transitioning to value conversations that tell the customer exactly what they expect to hear. We communicate the value they gained with us during the past month or quarter."

• Positive data drives renewals: The difference is concrete. Instead of showing a customer that they logged in a hundred times, Cohen's team shows them they saved $20,000 or grew market share by 20%. "If I can show you value, I'm not going to waste your time. If I wasn't able to show that value along the way, I lost the renewal from day one," he says. 

• Segmentation shapes the journey: Not every customer gets the same motion, and Cohen sees segmentation as the foundational decision that determines everything else. Enterprise accounts get formal, personal, high-touch engagement with structured value milestones, while SMB and scale accounts get faster, more automated, more digital motions built in collaboration with marketing and product teams. "Building the customer journey on top of segmentation creates visibility, trust, and a good understanding from the customer side."

Even with the best data infrastructure, Cohen insists that nothing replaces a human advocate inside the customer's organization. His team runs what he calls a champion academy, qualifying and nurturing internal advocates who serve as the CS team's eyes and ears. "They know us, we know them, and they know exactly what we're doing and why. Before a call, I can reach out and ask, 'Anything specific you want to see today? Who's joining? Are you bringing your manager or your CFO?' They're my real-time context layer inside the account." The champion model also serves as an early warning system. If a CSM is surprised on a call, Cohen treats it as a diagnostic signal that something is broken in the data, the alerting, or the relationship. "You can't come surprised to a call. If you are, go back and figure out what your alerts missed. That's a process problem, not a customer problem." Renewal, in Cohen's view, is not a single moment, but a cumulative outcome of every value conversation, milestone delivered, and expectation met along the way. The teams that build those systems from the first meeting are the ones that never have to scramble at the end.