Ask How Onboarding Works. If the Answer Is a Name, That Is the Problem.

Big Idea 09 from MSP to MVP. The five lifecycle playbooks, why the client who cooled down was a process failure, and what drilling teaches about falling behind.

Try this diagnostic in your own shop. Ask how onboarding works.

If the answer is a process, good. If the answer is a name, as in "oh, Sarah handles that," you have found a single point of failure that walks out the door at 5 p.m., takes vacations, and can resign. The outcome might currently be excellent. It is also unrepeatable, uninspectable, and impossible to hand off, which means it is not an asset. It is a dependency.

Chapter 9 of MSP to MVP is the operational core of the book. It is about turning the heroics that feel like excellence into plays that anyone can run. "Plays scale," the chapter's lesson goes. "Heroics don't. The work that grows your business is the work you can hand to someone else and trust the outcome."

Five playbooks, one journey

The industry talks about this work in role names, such as account management, vCIO, and sales, but almost never captures the client lifecycle as a connected set of plays. Framed as a bow tie, it is five playbooks across three phases. Acquire covers consultative sales. Commit and deliver covers closing and onboarding, once-in-a-lifetime events for each client. Grow and retain covers engagement as the ongoing core, with expansion and at-risk as the situational plays that need active management.

The habitual error is treating the big friction points, onboarding and projects, as independent events rather than stations on one journey. They are not independent. You meet the client long before onboarding, in marketing and in sales, and their goals should already be captured by the time onboarding begins. A lifecycle view is what lets a busy owner finally work on the operation instead of permanently in it.

Before this sounds like a mountain, there is a reassurance that makes it climbable. Standing up playbooks is not a greenfield exercise. You have already been doing elements of Customer Success. You just did not call it that. The playbook is a gut check first: what are we already doing, who owns it, what is missing? What the play adds is organization for everything currently floating loose. Business goals get discussed constantly, but who captures them, where do they live, and how do they get reused downstream? Each play pins down its inputs, the meeting itself, the follow-ups, the loop upward into roadmap and strategy, and the tooling, with its why. That last one quietly fixes a chronic failure, tool-first thinking, where the tool dictates a process the client never agreed to. Top-down, the process explains why each tool exists. Bottom-up, the client gets lost.

Two plays that only exist under pressure

Two of the five playbooks almost never exist on paper, and they are the two that run under the worst conditions.

The first is expansion. The failure pattern is universal enough to hurt. A big opportunity surfaces, the client is energized in the room, and then the provider goes home. The emails pile up. The proposal lands a week later. The enthusiasm is gone, and now someone has to get back in the car and rebuild a moment that already happened. That deal did not die of price. It died in the gap, a process failure wearing a sales costume. An expansion play is designed backward from that fact. What has to happen in the meeting to reach decisions while the energy exists? Scoping ready, business case framed, sign-off path known. The play is not bureaucracy around the sale. It is the container that keeps the sale warm.

The second is at-risk. This one goes undocumented for an emotional reason. Churn risk feels like personal failure, a negative to be avoided, which is exactly why it gets acted on late. Processed, it turns neutral: detection, diagnosis, executive briefing, recovery plan, execution, stabilization. The diagnosis usually deflates the drama. Most risk turns out to be misalignment, not rejection. Something needed was not purchased, or something important was communicated in technical verbiage and never landed. It is a miscommunication problem, not an intention problem. Naming at-risk as a standard play is what gives a team permission to run it early, when it still works.

Why nobody sold you these SOPs

A fair question from the field: we have had SOPs for ticket triage forever, so why has nobody shipped SOPs for this?

Ticket triage is nearly identical across every client and every MSP size, and these plays are not. They vary by client segment, because appetite and maturity decide which version of a play each client receives. They vary dramatically by MSP size, because a 5-person shop, a 20-person shop, and a 100-person shop engage in genuinely different ways. So the plays cannot be bought off a shelf. But "can't be cookie-cutter" is not "can't be documented." Your size, philosophy, and segments define a lane that limits the choices, and the play encodes its own variation. The alternative to a documented play was never flexibility. It was a permutation per client that only one person can run.

Seeing the full mature process has a second use, and it is the anti-overwhelm device. It makes the build chunkable. This is the two-year picture, and we start here. A standard you can see end to end stops being a mountain and becomes an implementation path.

A shape, not a list

The chapter's companion exercise makes the plays physical. Five playbooks, six steps each, every step owned by a role, and the connectors are drawn before you place anything. Assembling them in the Playbook Builder teaches the lesson kinesthetically: no playbook is a straight line. Onboarding forks into parallel workstreams and merges at a graduation review. Engagement is three always-on streams feeding a QBR loop. Expansion carries a fast track. At-risk carries an escalation branch.

The shape is not decoration. It is precisely what makes a play handable. Loops, parallels, and branches are where tribal knowledge hides. A list can live in someone's head, but a shape has to be drawn, and once drawn, anyone can walk it. Notice where you expected a line and found a fork. That is where your current mental model loses information in handoffs. Notice which playbook you assemble slowest. It is usually the one that does not exist in your operation at all.

Where to put the next foot

The instinct under pressure is the shortcut. Skip the prep, skip the follow-up, we are behind. It feels like help. It is consistently where the trouble starts, because deviation is when clients slip and backlogs compound. This is the logic of drilling. The plan is rehearsed precisely so that under fire, you do not improvise. You execute. Nobody is shooting at an MSP, but the mechanism holds. When you are overwhelmed, the process is what tells you where to put the next foot. Falling behind with a process is recoverable. Falling behind without one is drift.

This week

Do not document all thirty plays. Document one: the heroic that scares you most if its owner quit tomorrow. Sit with the owner and write down what actually happens, including the inputs, the steps, the loops ("and if they don't respond?"), the handoff, and the tooling and its why. One page. The owner narrating it will surface three steps nobody knew existed. Those three steps are the tribal knowledge you just banked.

If you want a second twenty minutes, write the engagement play for one meeting type as five lines: preparation, the meeting, follow-ups, loop upward, tooling and why. That is a play. Then run the cooled-down-client test on your last lost expansion. If it died in the gap between an energized meeting and a late proposal, you already have the business case for play number two.

Five playbooks. Thirty plays. One repeatable loop, and no name where a process should be.

Big Idea 9 of 12, from MSP to MVP: Building Unbreakable Partnerships in the Customer Success Era by Chris Day (Forbes Books, 2026). Previous: Customer Success Deliverables. Next: Customer Success People, on why every role that touches a client is a Customer Success role.