Executive sponsor departure is one of the highest-risk events in enterprise Customer Success. Most playbooks respond to it with a single line of guidance: identify a successor and update your stakeholder map. That advice is not wrong. It is wildly insufficient for what actually needs to happen.

In this episode of ClearPath Conversations, Mark Bernardin breaks down the real mechanism of risk when a sponsor leaves, what the first 48 hours should look like, and the specific mistakes that cause CSMs to mishandle the successor relationship even when they think they're doing it right.

Mark opens by explaining what a departing executive sponsor actually takes with them, and it is more than most CSMs account for. The organizational credibility they lent the program. The internal narrative they were reinforcing upward to their leadership. The political capital that had been protecting the initiative from competing budget priorities. The shared context that made difficult conversations manageable. None of that transfers automatically to whoever steps in next. What remains is exactly what the Program Resiliency Plan is designed to measure in advance: whether the account can stand without that individual.

The accounts that survive sponsor departure, Mark explains, are the ones where the CSM was already building depth before it became necessary. Multiple stakeholder relationships. A value narrative embedded in the organization's own language, not just in one person's memory. More than one person who can tell the story of why the program matters. The accounts that collapse are single-thread accounts, where everything ran through one person, and when that person left, there was nothing structural left to hold the relationship regardless of how strong the product performance had been.

From there, the episode gets operationally specific. Mark walks through what the first 48 hours should look like, including why the first call is not to the successor, but to the departing sponsor, and why timing matters more than most CSMs realize. He covers what that conversation needs to accomplish: gathering context that cannot be obtained anywhere else, and asking for the introduction in a way that is likely to be granted because it serves the departing sponsor's interests as much as it serves yours.

The successor relationship gets its own focused treatment, including the most common mistake CSMs make when walking into that first meeting: treating it like a re-sell. Mark explains why coming in with a history deck and a summary of program achievements is tone-deaf to where the new executive actually is, and what that first meeting should look like instead. The questions that open a genuine discovery conversation with a successor, and what those questions communicate about the CSM asking them, are covered in practical detail.

Mark also addresses the scenario many CSMs are least prepared for: sponsor departure with no clear successor named. When the organization is in transition, restructuring, or hasn't decided who picks up the program, there is no obvious next step. How a CSM navigates that period of opacity depends almost entirely on whether they built relationship depth before it was needed.