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/.