ClearPath Conversations

In Episode 30 of ClearPath Conversations, host Mark Bernardin wraps up the three-part mini-series on the Program Resiliency Plan (PRP) by addressing a critical question shared by many Customer Success Managers: If an account already has a traditional success plan, why is a PRP necessary? This episode provides immediate clarity by contrasting the distinct purposes of an account success plan - the navigation tool that outlines where a customer is going - and the PRP, which serves as a structural assessment to determine if the account is actually capable of making the journey.

Listeners will learn how to read risk signals accurately and select the appropriate framework based on three distinct account scenarios: stable accounts, early-instability accounts, and active recovery accounts. Mark breaks down how the customer-facing, joint success plan temporarily moves to the background during an active, internal 30-day PRP cycle so CSMs can focus energy on rebuilding structural foundations like Relationship Density and Narrative Strength. By understanding exactly when to deploy the success plan, the PRP, or a full Path to Green recovery motion, CS professionals can avoid the invisible traps of superficial activity and ensure their portfolios are built to hold under pressure.

In this second installment of a three-part series on the Program Resiliency Plan (PRP), host Mark Bernardin moves from theory to operational execution. While the previous episode defined the four dimensions of resiliency, Episode 29 details the mechanics of the 30-day PRP cycle: Diagnose, Act, and Validate. Mark emphasizes that the PRP is not a comprehensive remediation plan but a targeted strike on an account’s weakest structural dimension. By limiting the "Diagnose" phase to just three days, the framework prevents "analysis paralysis" and forces teams to focus on the single vulnerability - such as Relationship Density or Narrative Strength - that most threatens the account's structural integrity.

The episode further explores the shared ownership model required to make the PRP successful. Mark argues that a PRP activation is a business-level signal that revenue is at risk, requiring mandatory participation from Sales, Services, and Leadership rather than optional support. Listeners will learn how to set "Minimum Viable Resiliency" as a clear exit criterion and how the "disruption test" serves as the ultimate truth-teller for account health. Finally, the discussion covers how the PRP integrates into existing enterprise CSM workflows, helping professionals improve forecast accuracy by aligning commercial confidence with structural reality.

In Episode 28, Mark Bernardin breaks down the dangerous assumption that high adoption and positive QBRs equal account stability. He explains that many CSMs are blindsided by churn because they focus on what is happening now rather than whether the account can withstand future pressure, such as a champion departure or a budget reorganization. To bridge this gap, Mark introduces the Program Resiliency Plan (PRP), a structural assessment tool that moves beyond the dashboard to evaluate an account’s actual integrity.

The episode details the PRP’s "gating condition" - priority alignment - which requires CSMs to verify if a customer can articulate the value of a solution in their own words without vendor assistance. If this condition isn't met, the problem isn't resiliency; it’s relevance. Mark then walks through the four critical dimensions of the PRP:

1. Relationship Density
2. Narrative Strength
3. Early Risk Signals
4. Services Stability

Crucially, he explains why these dimensions cannot be averaged, as a single point of failure can destabilize an entire enterprise relationship. This episode is a deep dive into proactive prevention for CSMs who want to secure their renewals months before the contract expires.

The PRP Framework and Worksheet are available for download at https://www.clearpathcx.com.

In this episode of ClearPath Conversations, host Mark Bernardin moves beyond the technical dashboards of Customer Success to explore the behavioral traits that separate good CSMs from truly great ones. Drawing on over a decade of experience managing enterprise portfolios and rescuing at-risk accounts for organizations like Palo Alto Networks, Ernst & Young, and Lowe's, Mark outlines seven "non-negotiable" traits for professional excellence.

The episode challenges the notion that greatness is tied to specific tools or certifications. Instead, it focuses on a mindset of ownership, where CSMs proactively manage narratives and relationships rather than just forwarding tickets. Mark also delves into the "operational curiosity" required to uncover hidden growth opportunities and the strategic thinking necessary to identify churn risks months before they appear on a health score.

Listeners will gain practical frameworks for high-stakes situations, including:

• The Turnaround Specialist Mindset: How to maintain calm under pressure and use "Verbal Judo" to shift tense customer confrontations into collaborative problem-solving.

• Systematic Reliability: Why follow-through is a business outcome, and how to use a four-element commitment model to build impenetrable trust.

• Strategic Storytelling: Techniques for turning raw data into compelling narratives that move both customers and internal stakeholders to action.

Most Customer Success teams are drowning in data while starving for insight. They track login frequency, NPS scores, support ticket volume, and dozens of other metrics that look impressive in dashboards but don't actually predict whether customers will renew, expand, or advocate. In Episode 26 of ClearPath Conversations, Mark Bernardin cuts through the noise to reveal which metrics actually matter and how to build a measurement system that drives real outcomes. 

He opens with a lesson from Cofense, where one of his healthiest-looking accounts churned despite green health scores, strong NPS, and consistent usage. The customer's explanation was simple: their threat landscape had changed, and the product no longer solved their problem. Mark was tracking engagement, not value. He was measuring activity, not outcomes. That conversation fundamentally changed how he approaches metrics. The episode introduces Mark's Three Questions Framework. Every metric should answer: Is this customer going to renew? Is this customer going to grow? Is this customer going to advocate? If a metric doesn't answer one of these questions, it's not worth tracking. Mark breaks down specific leading and lagging indicators for each category, explaining why executive engagement predicts churn better than health scores, why adoption depth matters more than breadth, and why behavioral advocacy metrics trump sentiment scores.

Mark shares two detailed portfolio examples. At Palo Alto Networks, he managed an account where every activity metric looked perfect, but the executive sponsor hadn't attended a QBR in six months. Mark flagged it as at-risk despite manager pushback. Six weeks later, the customer announced they were evaluating alternatives. Without an executive champion when Finance cut budgets, the account contracted from $425K to $280K - a $145K ARR loss.

The second example comes from Deepwatch, where Mark identified a pattern: customers who stopped attending monthly operational reviews - even with strong usage - were planning their exit. They'd shifted from proactive partners to reactive users. Mark added "strategic engagement" as a core metric and built a re-engagement playbook. That single metric change reduced churn by four percentage points, retaining approximately $1.8 million in ARR.

Mark didn't keep that insight to himself. He brought the framework to Deepwatch's VP, partnered with RevOps to build it into Gainsight with automated alerts, created a standardized playbook, and trained newer CSMs. Within six months, strategic engagement became a core metric company-wide.

He also shares a mentoring story from Palo Alto Networks, where he led seven CSMs. One CSM had an account that wasn't converting expansion. Mark had her check power user percentage - only 18% of licensed users were engaging. After focusing on adoption, it reached 52% and expansion happened naturally.

The episode provides a complete implementation roadmap. Mark explains how to define metrics based on business model - consumption-based pricing requires different indicators than seat-based licensing. He details setting data-driven thresholds by analyzing churned accounts. He walks through automation approaches, including building custom Gainsight dashboards, configuring automated CTAs, and setting up Slack alerts.

Mark emphasizes that metrics are only useful if they drive action. Every metric needs a playbook with clear owners and escalation paths. He stresses reporting the right metrics to the right audience: operational detail for internal teams, retention risk and expansion pipeline for CS leadership, gross and net retention for the C-suite.

Episode 26 delivers the frameworks, thresholds, and real-world examples CSMs need to stop tracking vanity metrics and start measuring what actually predicts customer outcomes. The companion download includes the CS Metrics Framework with audit worksheets, threshold-setting tools, playbook builders, and a 30-day implementation plan.

In this episode of ClearPath Conversations, Mark Bernardin breaks down one of the most misunderstood topics in Customer Success: personal branding.

Most CSMs either ignore it entirely or approach it the wrong way. They associate “personal brand” with performative LinkedIn content, recycled advice, and visibility without substance. Mark challenges that assumption directly and reframes the concept around what actually matters: professional credibility built on real results.

Drawing from his own experience managing enterprise portfolios and turning around at-risk accounts, Mark explains why relying on internal reputation alone limits career growth. He outlines the moment he realized that strong execution inside a company does not automatically translate into external credibility or opportunity.

This episode introduces a clear, practical framework for building a professional reputation the right way. Mark walks through the three levels of visibility in Customer Success: internal credibility, peer visibility, and industry recognition. He explains how to move between each level using documented results, real-world frameworks, and consistent contribution rather than noise or self-promotion.

He also addresses where most CSMs get it wrong. Many attempt to build visibility before they have proof of competence. Others prioritize content over performance or try to position themselves as experts without the experience to support it. Mark makes it clear that credibility is earned through execution first, then demonstrated through sharing what actually works.

Listeners will walk away with a practical approach to documenting their work, turning real customer outcomes into transferable frameworks, and contributing to the Customer Success community in a way that strengthens both their reputation and their performance.

This episode is paired with a companion toolkit that includes a professional visibility assessment, results documentation templates, LinkedIn content frameworks, and a 90-day credibility plan designed to help CSMs build reputation without losing focus on the work that matters .

The goal is not to become an influencer. The goal is to become a stronger operator with more control over your career.

In Episode 24 of ClearPath Conversations, Mark Bernardin examines one of the most overlooked drivers of Customer Success performance: internal documentation. He outlines four core components required to scale effectively: the onboarding deck, runbooks, a health scorecard, and a risk log. He also addresses a common reality, most CSMs end up building these systems themselves when leadership does not.

The episode opens with a story from Mark’s time building with a new CS team. Rapid growth exposed a major gap: new CSMs were onboarding with no context, no documentation, and no clear framework for how the team operated. Senior CSMs were repeatedly answering the same questions, pulling focus from their accounts and slowing overall productivity. Mark responded by building the missing infrastructure. Within six months, ramp time dropped from twelve weeks to six, and the team grew from eight to fifteen CSMs without added management overhead.

Mark breaks down each component in practical terms. The onboarding deck includes six critical areas: CS mission, team structure, customer journey, tools and systems, key metrics, and a 30-60-90 day plan. This became the baseline for setting expectations and giving new hires a clear path.

Runbooks focus on three essential workflows: Sales-to-CS handoff, escalation management, and renewal preparation. Drawing on experience from Palo Alto Networks, Cofense, and Swimlane, Mark shows how documented processes prevent breakdowns during transitions, bring structure to escalations, and convert last-minute renewal scrambles into disciplined 90-day plans. He also makes a key point: not everything needs to be built from scratch. At Swimlane, he improved an existing renewal process by identifying gaps and fixing them, rather than rebuilding it.

The health scorecard introduces a five-part model: product adoption, business outcomes, stakeholder engagement, sentiment, and risk. This moves beyond automated scoring and creates a fuller picture of account health. Using this model, his team identified and saved four at-risk renewals worth $280K in ARR within two quarters.

The risk log focuses on disciplined issue tracking. Mark shares a six-column framework used at Lowe’s to manage complex deployments: risk description, severity, owner, status, target resolution date, and actions taken. The log served both as an operational tool and a record for leadership when renewals were at risk.

Across the episode, Mark addresses a consistent pattern: most CS leaders will not build this documentation for you. They will acknowledge its value, but execution often stalls. Waiting for direction leads to delay. The alternative is to build what is needed, prove it works, and let results drive adoption. His Deepwatch work became the team standard, and collaboration with peers at Palo Alto Networks strengthened adoption and usability.

The episode closes with a clear directive: audit your current documentation, identify gaps, and start building. Whether you are an individual contributor or leading a team, this work has direct impact on retention, scalability, and performance. A companion download includes ready-to-use templates so listeners can act immediately.

This episode is aimed at CSMs dealing with chaos, team leads scaling without added headcount, and CS leaders who want to understand what infrastructure actually supports consistent results.

The companion download for this episode is available at https://clearpathcx.com/.

In Episode 23 of ClearPath Conversations, Mark Bernardin tackles one of the most undervalued skills in customer success: the ability to say "no" without damaging trust or credibility.

Mark opens with a story from his early days at Cofense, where he said yes to every customer request - custom reports, extra training sessions, one-off integrations, priority support for non-urgent issues. He believed he was building the relationship. Instead, he was training the customer to expect unlimited accommodation. When he finally had to say no to something genuinely out of scope, the customer responded with betrayal: "But you've always made this work before." Mark had set an unsustainable precedent, and breaking it felt like breaking a promise.

This experience taught him a critical lesson: if you say yes to everything, you're not a strategic partner. You're an order-taker.

Mark breaks down the four categories where CSMs need to set boundaries: scope creep, timing and prioritization, resource allocation, and situations where the customer is asking for something that's genuinely not in their best interest. For each category, he provides specific language templates and frameworks for delivering the "no" while offering productive alternatives.

He shares a story from Palo Alto Networks about a large retail customer who wanted to deploy a new security module in under two weeks. Mark knew their team capacity and understood that rushing the deployment would lead to failure and poor adoption. He held the line, guided them toward a phased approach, and three months later their CISO told the account executive that Mark's team was the most professional vendor they'd worked with.

But Mark doesn't stop at customer boundaries. He addresses the harder challenge: saying no internally. He shares a story where a sales leader wanted him to commit to a custom integration timeline for a six-figure deal before engineering had scoped the work. Mark refused to make a commitment without data. The sales leader pushed back. Mark held firm: "If you want me to own the customer relationship after the sale, you need to let me protect the integrity of what we're promising." Engineering scoped it at 60 days instead of 30. Mark communicated the realistic timeline with a phased rollout plan. The deal closed anyway, and the customer trusted them because they'd been honest from the beginning.

Mark then shifts to system-building at scale. After having the same boundary conversation three times in one quarter, he built a one-page service tier definition document. The result: out-of-scope requests dropped 40 percent over six months. The team freed up six hours per CSM per week, which got reallocated to strategic accounts and expansion conversations. The team saw a 25 percent increase in expansion opportunities identified that quarter.

Mark closes with insights from mentoring the CSM team at Palo Alto Networks, where boundary-setting was one of the first skills he taught. CSMs who couldn't hold boundaries burned out within 18 months. But CSMs who learned to say no strategically built sustainable portfolios, earned trust, and got promoted.

The episode delivers practical frameworks, real-world examples, and specific language templates that CSMs can use immediately when facing difficult requests, unrealistic timelines, or situations where saying yes would compromise their ability to deliver real value.

The companion download is available at https://clearpathcx.com/.

When a security incident, service outage, or product bug hits your portfolio, you don't get extra hours in the day. You get the same twenty-four hours as everyone else to protect millions in ARR and keep twenty accounts from going red simultaneously.

In this episode, Mark Bernardin walks through the systematic frameworks he's used to manage portfolio crises at companies like Cofense, Deepwatch, and Palo Alto Networks. He explains why the biggest mistake CSMs make during a crisis is treating every account the same - and why that approach fails every single time.

Mark breaks down his crisis triage methodology, showing how to categorize accounts into Critical, Standard, and Stable tiers based on business impact, relationship risk, and strategic value. He shares specific examples from a Saturday morning SOC platform outage at Deepwatch and a critical security vulnerability at Palo Alto Networks, demonstrating how proper triage and communication saved accounts that could have easily churned.

The episode covers crisis communication strategies that maintain trust when everything else is broken. Mark provides the exact template he uses for initial customer acknowledgment within the first hour, and explains how to customize communication for technical stakeholders, executive stakeholders, and operational stakeholders - because they all need different information to do their jobs during a crisis.

Mark also addresses internal coordination, explaining how to prevent your own team from creating additional communication chaos during an emergency. He outlines the four-step coordination protocol: establishing a single source of truth, defining communication ownership, creating internal update cadences, and documenting everything for the post-mortem.

The episode tackles one of the hardest aspects of crisis management: post-crisis relationship recovery. Mark explains why the crisis isn't over when the technical problem is solved - it's over when your customers say it's over. He shares his framework for scheduling post-crisis debriefs with critical accounts, asking for feedback, and acting on what you learn to rebuild confidence in the relationship.

Mark doesn't shy away from the difficult decisions CSMs face during portfolio crises. He discusses how to prioritize resources when you can't give everyone everything they want, how to decline customer requests professionally without making promises you can't keep, and how to make business decisions without apology while still maintaining customer relationships.

This episode is essential listening for any CSM who manages enterprise portfolios, works in high-stakes industries like cybersecurity or financial services, or wants to build crisis management capability before an emergency hits. Mark includes specific guidance for different crisis types - security incidents, service outages, product bugs, M&A announcements, and leadership changes - making this a comprehensive playbook for portfolio crisis management.

The companion download includes crisis triage frameworks, communication templates for initial acknowledgment and stakeholder updates, internal coordination protocols, post-crisis recovery checklists, and a 30-day crisis preparedness plan to help you build response capability before you need it.

In Episode 21 of ClearPath Conversations, Mark Bernardin examines what happens when customer relationships are built too heavily around one champion and that person leaves, gets reassigned, or loses influence. Framed as an advanced follow-up to basic stakeholder mapping, this episode focuses on how Customer Success Managers can protect renewals, preserve momentum, and reduce account risk when org charts shift and decision-making power moves.

Drawing from enterprise account experience in cybersecurity, Mark explains why a contact list is not a stakeholder strategy. He breaks stakeholder mapping into three practical questions: who actually makes decisions, who is vulnerable to change, and who can provide continuity when disruption happens. He outlines how title and authority often diverge, why informal influence matters as much as budget ownership, and why strong but fragile relationships can create hidden exposure inside an account.

The episode also presents a five-step playbook for navigating change once it begins. Mark covers how to assess the impact of departures quickly, map the new power structure, re-establish value with incoming leaders, maintain ties with former champions, and document relationship intelligence so it survives future transitions. He argues that new stakeholders rarely care about historical goodwill on its own. They care about present relevance, clear outcomes, and language that matches their priorities.

Listeners also get a prevention framework built around relationship redundancy. Mark makes the case for building 3 to 5 meaningful stakeholder relationships across functions such as executive leadership, technical ownership, compliance, finance, procurement, and business operations. He explains why these relationships should span departments rather than sit inside one reporting chain, and why executive business reviews should include a broader set of participants if the goal is long-term account resilience.

This episode is intended for Customer Success Managers, account leaders, and CS executives who manage strategic accounts where personnel change can create immediate commercial risk. It offers a practical structure for protecting account health in volatile environments and for replacing single-threaded relationship management with a more durable architecture.

The episode includes the Influence and Continuity Map, a stakeholder tracking and continuity planning tool designed to help teams document decision roles, relationship strength, vulnerability ratings, and continuity options before a major transition occurs. The companion download is available at https://clearpathcx.com/.