Your Customer Success Promise Has a Headcount. You Have Never Done the Math.

Big Idea 06 from MSP to MVP. The five forces that set your Customer Success staffing, the positioning decision nobody makes, and who is currently paying for the gap.

Every MSP makes a Customer Success promise. Sometimes it is written into the agreement: quarterly reviews, an annual roadmap, budget planning. More often it is implicit. Someone here is thinking about your future, not just your tickets.

That promise has a headcount. Five forces set it: which high-engagement services you take on, the vertical you serve, how many clients you manage, what they pay on average, and how deep an engagement model you choose. Multiply them and out comes a number, a specific fraction of specific roles that the promise requires.

Chapter 6 of MSP to MVP is about the fact that almost nobody has ever run that multiplication. When staffing is not computed, it is improvised. In practice that means instinct staffs the loudest clients, and the promise gets kept selectively.

The decision nobody makes

Underneath the staffing question sits a positioning question the industry has collectively skipped. Are we a premium provider or a cost-effective one?

Everyone wants the premium mindset. Walk any conference floor and you will hear it: strategic partner, trusted advisor, seat at the table. Almost nobody has a delivery concept behind the mindset, because the decision was never made as a decision. It has a number attached, namely what percentage of revenue goes into the Customer Success layer around your core services. A light touch runs around 2.5 percent. A steady rhythm runs about 5 percent. Genuinely in the room, the level the premium language implies, runs about 10 percent.

Choosing the percentage is choosing the positioning. Refusing to choose is also a choice. It is called drift, and it produces the familiar shape: premium marketing, ad hoc delivery, and a nagging sense that the strategic work happens only when someone finds the time.

The math is clarifying, and slightly brutal

Run a worked example through the model. A $2.5M-revenue MSP chooses the in-the-room model, with 10 percent of revenue into Customer Success, in a moderately complex vertical. The output is roughly 1.4 full-time people. Decomposed by role, that is nearly a full-time vCIO, half an account manager, and a fractional security and compliance function.

Two reactions follow, in order. The first is that we do not have those people. The second is the one that matters: the work is already being done. The reviews happen, eventually. The roadmap thinking happens, somewhere. The strategic conversations happen, unplanned and unnamed, mostly by the owner, mostly on evenings and weekends. The model does not reveal a new cost. It reveals an existing, unbudgeted one, currently being paid in leadership burnout.

That reframes the standard objection, that we cannot afford dedicated Customer Success headcount because we are not big enough, into its honest form. The question was never whether you can afford Customer Success. It is who is currently paying for it, and in what currency.

To give the industry its due, many MSPs did follow a staffing method: techs per endpoint, account managers per book. Those ratios were computed for delivery, and the demand has shifted underneath them. Clients now want outcomes, not deployments, and outcome conversations consume exactly the scarcest resource on the payroll, senior strategic time. An MSP adequately staffed for delivery can be badly understaffed for engagement, and the gap widens every year expectations rise.

Five forces, one number, one role mix

The chapter's companion tool walks the five decisions one at a time, with a running estimate updating in the center as you go. You choose the high-engagement services you will actually commit to, up to four of ten. Roadmaps, budget planning, QBRs and renewals, innovation workshops, and risk and compliance are among them. Then you set the vertical and its complexity multiplier, clients under management, average MRR, and the engagement depth.

The math is transparent all the way down: revenue times depth, scaled by vertical and service load, divided into hours and then FTE. The output that changes the conversation is not the headcount. It is the role mix. The number decomposes across five roles, vCIO, account management, TAM, vCTO, and vCISO, based on which services you selected. The typical discovery is not "we need two more people." It is "the vCIO function is 0.9 FTE of the promise we've made, and it exists nowhere on the org chart."

Ten minutes in the Staffing Canvas is worth the honesty it forces, and two runs are better than one. Run it once with the services you claim, and once with the services you consistently deliver. The FTE gap between those runs is the measured size of the overpromise. Watch the vertical multiplier too. The same book of clients costs meaningfully more to serve well in healthcare or government than in professional services, and your pricing should know that even if it currently does not.

The model's verdicts scale honestly. Under about 0.8 FTE, you are in the danger zone the book names directly: "part of someone's job" is exactly how Customer Success dies. A single stretched account manager owning a 2.5-FTE promise is running at half capacity, whatever the effort. Above that, if the org chart does not show the roles, the work is not happening.

For a smaller MSP, "less than one person" is a legitimate answer, provided the fraction has a name. What kills Customer Success is not small allocation. It is anonymous allocation. Fractional and named beats invisible, every time.

The cascade

This chapter sits inside Strategy rather than Operations for a reason. The five forces are the middle of a cascade of conscious decisions. The segmentation decision from Chapter 4 shapes the engagement model. The engagement model determines the competencies your organization must hold. Those competencies define the services you can credibly support, and alignment sets expectations you can actually meet. Made consciously, each decision explains the next. Skipped, each gap compounds into the next.

Some clients will not like where the cascade lands. The engagement is more than they want, or less than they demand at the price. That is not a failure of the model. That is ICP selection working as intended. "Customer Success strategy is about building the DNA of how you engage customers," as one MSP-industry CEO puts it in the book, "so it doesn't depend on one person, and it doesn't only show up after something breaks."

This week

Do not hire five people. Find the gap first.

Walk the five forces with your real numbers. Then count the people actually assigned to Customer Success today, by name and with hours, and write down the difference. That is the whole move.

If you want the calendar-side view of the same gap, run the meeting audit. List the client meetings you are actually holding. For each one, ask who attends, honestly, whether it is a valuable meeting, what gets delivered, whether the right people are in the room, and whether every client needs the same frequency. The audit usually reveals both halves of the misallocation at once: the over-served stable clients and the under-served ambitious ones.

Then make the one decision in writing. Light touch, steady rhythm, or in the room, as a percentage of revenue. One sentence. Everything downstream gets easier once it exists.

Five decisions. One headcount. Staffed on purpose.

Big Idea 6 of 12, from MSP to MVP: Building Unbreakable Partnerships in the Customer Success Era by Chris Day (Forbes Books, 2026). Previous: Three Forces, One Honest Read. Next: Customer Success Health, on the signals that drift weeks before the renewal conversation does.