Skip Nav
Search Results
Request a Demo
LIVE WEBINAR Stop managing external risk. Eliminate it.

Why Customer Success is under more pressure than ever

Steve Frost
Steve Frost
  • March 5
  • 6 Minute Read
Customer success managers identify and mitigate churn risks using Certinia PSA's customer success tool

Customer Success was supposed to be the growth engine of the subscription economy. Instead, in many organizations, it has become the function most accountable for revenue outcomes — and the least able to control the conditions that determine them.

Executives want predictable growth. Boards want retention. Security teams want reduced risk. Finance wants proof of value. And Customer Success is expected to deliver all of it while often operating across systems it doesn’t own and processes it can’t fully enforce.

The issue isn’t a lack of expertise. Most CS leaders know what healthy customer relationships look like. The challenge is sustaining that health when the customer story is scattered across departments, tools, and reporting structures.

The risk builds in the gaps between teams

When organizations investigate churn, they often search for a specific cause — a sale rushed through at the end of the quarter, a failed implementation, a support breakdown, a pricing dispute. But revenue loss rarely starts with one event. More often, it accumulates gradually as context erodes across internal handoffs.

Sales closes a deal based on assumptions that aren’t well documented and never fully translate into delivery planning. Implementation teams adapt as conditions change, but lack a consistent way to communicate those changes downstream. By the time a Customer Success Manager prepares for renewal, the official account narrative no longer reflects reality. No single team failed. Yet the outcome is in doubt.

This is why many renewals that once looked secure (and enjoyed a “green” health score) suddenly become tense conversations. Warning signs existed, but they were distributed across systems and timelines, never forming a complete picture early enough for proactive action.

More tools haven’t solved the coordination problem

Over the past decade, companies have invested heavily in technology to manage the customer lifecycle. Each solution improves visibility into a specific domain. Together, they promise comprehensive insight. In practice, they often create fragmentation.

Customer information moves between platforms on different schedules. Metrics are calculated using slightly different definitions. Updates occur in parallel but not in sync. When scope shifts, adoption stalls, or commercial terms change, there is rarely a single system that reflects the full impact in real time.

Even advanced analytics struggle here. AI can identify patterns, but it cannot compensate for missing or contradictory inputs. Automation can accelerate workflows, but it cannot determine which version of the truth should guide decisions.

So teams default to what feels reliable: meetings, manual updates, and spreadsheets that attempt to reconcile competing data sources. This puts customer success leaders in a huge bind, and brings the bullseye squarely onto their chest.


EXPERT PANEL

Security, Silos, and Scrutiny: 
Confronting the Archenemies of Customer Success

Stop managing risk. Eliminate it.

Register Here


Security concerns are raising the stakes

The architecture behind many Customer Success operations is attracting new scrutiny. Each integration, external database, or third-party platform expands the footprint of sensitive customer information and opens a new hole in the fence for the bad guys to sneak in.

Security and compliance teams increasingly view fragmented ecosystems as potential liabilities. Governance becomes harder to enforce when data flows across multiple environments, each with its own controls and vulnerabilities.

For CS leaders, this creates a difficult paradox. The tools introduced to demonstrate value and improve coordination can also increase perceived (and real) risk, slowing approvals and complicating future initiatives.

“Proving Value” now means proving impact on revenue

Customer Success is also being evaluated differently. Relationship health and customer satisfaction scores are no longer sufficient indicators of performance. Executive teams want clear evidence of business impact: retention, expansion, margin contribution, and forecast confidence.

Producing that evidence requires connecting operational outcomes to financial results across the entire lifecycle — something many organizations were never architected to do.

Without that connectivity, renewal preparation can feel less like strategic planning and more like investigation. Teams assemble data from multiple systems to explain what actually happened over the contract period, often discovering gaps or inconsistencies along the way.

The effort required to reconstruct the past leaves less time to shape the future.

Alignment is structural—not cultural

Organizations often treat alignment as a communication issue, solvable through meetings or joint planning sessions. While those efforts help, they rarely eliminate the underlying disconnects created by separate platforms and processes.

When Sales, Customer Success, Services, Support, and Finance operate in isolation, context must be translated at every transition. Details are lost, priorities shift, and ownership becomes ambiguous. By contrast, high-performing companies tend to maintain continuity: the customer record evolves over time but never resets.

Changes in delivery status, adoption, or commercial exposure are visible across teams without requiring manual interpretation. This doesn’t remove complexity, but it prevents complexity from becoming uncertainty.

Economic conditions have elevated the importance of existing revenue. Acquiring new customers is expensive; losing current ones is increasingly unacceptable. Retention and expansion have become central to growth strategies, not secondary metrics.

At the same time, organizations are modernizing operations, strengthening governance, and preparing for AI-enabled decision-making. All of these initiatives depend on reliable, connected data.

Customer Success sits at the intersection of these priorities. It is where expectations converge — and where breakdowns become visible first.

A conversation worth having now

These pressures are not isolated to one industry or maturity level. They reflect a broader shift in how organizations manage customer relationships in a more constrained, accountable environment.

On March 12, I am participating in a live expert panel along with my colleague Will Spice, examining how companies are confronting the combined challenges of security, operational silos, and heightened executive scrutiny. Rather than abstract theory, the discussion will focus on practical approaches to simplifying complex environments, improving coordination across revenue teams, and creating conditions where Customer Success can demonstrate value without reconstructing the customer story from scratch.

March 12, 2026
10 AM CT | 4 PM GMT

For leaders navigating these dynamics, hearing how peers are addressing them may provide both clarity and reassurance that the challenges are solvable.

You can reserve your place here.

Final thought: Continuity is the new competitive advantage

Customer Success rarely struggles because teams lack commitment or capability. It struggles when the system surrounding them cannot carry context forward.

The organizations most likely to protect and grow revenue over the next decade will be those where the customer journey remains intact from first conversation to renewal — where no team has to guess what happened before they became involved.

Understanding how to achieve that continuity may be one of the most important conversations a leadership team can have right now.

Steve Frost
Head of Industry & Executive Advisory - Customer Success

Maximize your Salesforce investment with Certinia

See the impact Certinia + Salesforce could have on your services business.
Certinia dashboards give real-time visibility into project actuals, expenses, and resource requests