There Is No Customer Success Role. Every Client-Facing Role Is One.
Big Idea 10 from MSP to MVP. Why activities get sorted before people, what "we all kind of handle that" actually means, and the four jobs that never disappear, only split.
The SaaS world gave us the Customer Success Manager, and the MSP world has been trying to hire one ever since. Chapter 10 of MSP to MVP starts by breaking the frame. In an MSP, Customer Success is not a seat. It is a distributed function. The account manager, the vCIO, the TAM, the architect, and the executive who joins the occasional review are all performing a Customer Success role. Anyone who touches the client in any shape is.
The distinction matters because of what the dedicated-hire framing quietly licenses. Treating Customer Success as one person's job is how eleven other people get permission to stop thinking about it.
At five clients, one person does four jobs
The chapter is built on a structural fact. At five clients, one person is quietly doing four jobs, account manager, strategist, technical lead, and architect, all at once and all in their head. At fifty clients, those four jobs still exist. Nothing about growth removes them. The only question is whether you have named who owns them.
The four functions map on two axes, Business to Technical and Operational to Strategic:
- AM owns the commercial relationship and day-to-day cadence (operational-business)
- vCIO owns roadmap, budget, and business case (strategic-business)
- TAM owns hands-on delivery, monitoring, and remediation (operational-technical)
- vCTO owns architecture, design, and innovation (strategic-technical)
In a solo shop, one seat holds all four. In a small shop, two seats: an operational lead carrying AM and TAM, and a strategic lead carrying vCIO and vCTO. Mid-size runs three. Large runs four distinct seats. At enterprise scale, the seats become teams. The chapter's lesson sits in the transitions: "The jobs don't go away as you grow. They separate, and every handoff you haven't named is a handoff that quietly breaks." Growth does not create the seams. It exposes the ones that were never named.
Even the new titles arriving with the AI wave fit without a new framework. A vCAIO is not a fifth function. It is a bundle of activities that land in the quadrant, mostly overlapping vCIO and vCTO.
Sort activities first. Assign people second.
The practical heart of the chapter is an ordering rule that sounds trivial and changes everything. You do not place people on the grid. You place activities.
A renewal is an operational-business conversation. AI strategy is strategic-business. Budget planning is strategic-technical. Monitoring is operational-technical. List last month's actual client-facing activities and give each one coordinates, before any names enter the room. Then, and only then, match people. Who on the team has the skills for that quadrant?
Run it people-first, the way it usually happens, and you get the familiar failure: round pegs shuffled between square holes based on titles they gravitated into years ago, rather than activities anyone examined. Run it activities-first, with the team in the room, because agreement is part of the product, and three lists fall out. What we are doing, and who actually does it. What nobody owns, meaning the orphan tasks someone raised a hand for once and has carried by habit ever since. And what we are not doing at all.
Every operation has orphan activities. Naming them is not bureaucracy. It is the difference between coverage and coincidence, and it is why "we all kind of handle that" is the most dangerous sentence in the exercise. We all do it is the same as no one does.
The people practices around the seats
Four ideas from the chapter turn the seat map into an operating culture.
Hire the skill set, not the title. Sequencing your first Customer Success hires is a skills question. My first account manager must be able to do these five things, and which five depends on which quadrant is bleeding. Every hire triggers the owner's question that rarely gets asked deliberately: what comes off my plate, and what do I do with the reclaimed hours? Unbanked, they evaporate into the inbox. Banked, they become the strategic capacity this whole book keeps spending.
Upskilling runs along the grid. The quadrant doubles as a development map. People grow from operational seats toward strategic ones, along either track, technical from TAM toward vCTO or business from AM toward vCIO. Framed that way, role definition stops being a threat ("am I being boxed in?") and becomes a ladder. It is worth asking each person, explicitly, which direction they want to grow.
Build relationship redundancy. Personal relationships are the glue of MSP client work, and a single-threaded relationship is a single point of failure wearing a friendship costume. Know deliberately who on your team connects with whom on theirs, and build multiple connection points per key client. If the champion CEO gets replaced, or one relationship takes strain after a mistake, the account holds through the others. The mirror side matters too. Match presenter to audience. The hard-charging sales-type CEO gets a different QBR voice than the detail-oriented legal principal.
Adopt the mistake rule. This is a practice borrowed from the best engineering organizations. If you make a mistake, you must tell everyone. Not as self-flagellation, but so the team can learn, find the gap, and get ahead of it before the client notices. The framing that makes it stick: we have already made the investment in your mistake, so now let us collect the return. Teams without that cohesion hide problems until clients discover them. Teams with it dive on the grenade early. That is a culture practice with a direct Customer Success payoff.
Underneath all of it, compensation follows Customer Success. If Customer Success is a distributed function, incentives should say so, with clear, defined objectives for everyone in some shape, rather than a year-end bonus tied to nothing in particular. People attend to what pays. A Customer Success motion whose incentives all point at ticket throughput will get ticket throughput.
Watching the jobs split
The chapter's companion tool makes the growth story physical. A size slider, from Solo to Enterprise, reshapes the seat layout on the grid, and responsibility cards get dragged onto seats, with overloaded seats warning "N jobs, 1 seat."
Two reads are worth the ten minutes in the Roles and Onboarding Planner. First, slide to your actual size and compare the suggested seats to your real org chart. A mismatch is not a wrong answer. It is a question: which seat are we running that our size does not support, or missing that it demands? Second, find the "N jobs, 1 seat" warning in your own shop. The person holding two seats is simultaneously your most valuable asset and your most exposed one. If a card's placement sparks debate in the room, that debate is the finding. The team currently disagrees about who owns that work, which means the client experiences whoever got there first.
This week
Name the owner of one quadrant, the one you would describe as "we all kind of handle that." Write one name next to it. That is the whole move, and it is a five-minute exercise now instead of a reorganization later.
Then run two checks that cost nothing. Run the relationship-redundancy count on your top five clients. Any client with a single genuine connection point is one departure away from being a stranger. And write the skill spec, not the title, for your next client-facing hire, with the pre-decision of what comes off whose plate when they land.
Four roles. Named owners. Handoffs that hold. That is how the relationship stays whole while the team grows around it.
Big Idea 10 of 12, from MSP to MVP: Building Unbreakable Partnerships in the Customer Success Era by Chris Day (Forbes Books, 2026). Previous: Customer Success Process. Next: Customer Success Technology, on lots of signals, lots of tools, and no single view of the client.