How Many Clients per vCIO? Set a Workable Account Load

Give Each Role Its Own Work

The TAM owns technical alignment: the client's environment and its standards. The vCIO owns the business conversation and the budget. Keep those roles distinct, and write the assignments separately before counting the people who will carry them.

For your own team, name the deliverable and the person responsible for it. I'd have the TAM record the environment's gaps and proposed technical work. I'd have the vCIO take that work into the client's business plan, with the decision and its owner recorded.

Keep the service manager responsible for the desk. Also keep new-business hunters separate from account management. Don't solve an account-capacity shortage by quietly adding the job to either role and leaving its original workload untouched.

A small team still needs a written allocation if someone covers more than one responsibility. Record the time available to each role and what that person will stop doing to make room. A title doesn't add hours to the calendar.

Calculate Capacity From Managed MRR

Use the monthly managed services fee for this division. The US example has $157,500 of managed services MRR across 35 clients. Its separate product revenue is not part of the revenue base used to staff these account roles.

FTE means full-time equivalent. These are amounts of role capacity in the model, not a claim that your payroll contains fractional people. Map that capacity to named people and actual assignments before deciding whether you have room for another client.

Client count comes from a different division. Divide each role's MRR allowance by the average managed fee per client to get the implied count. The example uses $4,500; your own calculation needs the average for the clients you are assigning.

A higher fee produces fewer clients per person at the same MRR allowance. That is an arithmetic result, not evidence that the larger client needs proportionately more work. Keep the revenue calculation and test the work separately.

Check the Hours Without Replacing the Staffing Basis

The model budgets 6 TAM hours per client per month and 3 vCIO hours. The TAM allowance includes a monthly call; the vCIO allowance includes the quarterly business review. Don't add the same meeting again when totaling the planned work.

Service-role productivity is 1,660 available hours a year multiplied by 70%, then divided by 12. That gives about 96.83 productive hours per FTE per month. Leave and administration have already been deducted in the available-hour input.

For 35 clients, TAM work is 35 × 6 = 210 monthly hours. Dividing 210 by 96.83 productive hours gives about 2.17 FTE. The vCIO calculation is 35 × 3 = 105 hours, then 105 ÷ 96.83 = about 1.08 FTE.

Those results are close to the MRR-based capacity. The hours are a workload cross-check, not a replacement staffing rule. Use your own logged work to test whether the model's allowances fit the scope you have sold.

If the logs are incomplete, treat the result as incomplete. I'd agree what work belongs to each role and review the entries with the person doing it. A low logged total doesn't establish that the client needs little attention.

Investigate a Gap Before Calling It a Hiring Problem

Suppose a TAM's recorded hours exceed the allowance while the MRR calculation shows enough capacity. I'd inspect the assignments with that TAM. The excess could involve unusual environments or a scope that is broader than the model assumes.

Other possibilities include work that belongs to another role or entries recorded against the wrong task. These are hypotheses to check, not an exhaustive diagnosis. Follow the work through the record before changing the staffing ratio.

A missed alignment review needs the same care. Logged hours are evidence to consider alongside task ownership, scope, and scheduling. They don't establish by themselves whether the delay came from too much work or another problem.

I'd ask the account owner to identify what remains unfinished and what prevented the next action. Then decide whether the response is additional capacity or a change in how the existing work is assigned. Record the reason so you can test that decision afterward.

Test the vCIO Client Count Separately

The example's revenue ratio implies 31.1 clients per vCIO. The model checks that against an account-manager span of 20 to 25 clients and flags it as high. Passing the aggregate hours check doesn't remove that separate issue.

A cap of 25 clients per vCIO adds $34,210 in annual cost in the US example, reducing EBITDA margin by about 0.9 percentage points with everything else held constant. That is the model's capacity sensitivity. It is not a quote for a whole new hire.

I'd compare the cap with your actual review calendar and the assignments each vCIO must own. If you are also the vCIO, show the portion of your time available for that role. Don't give yourself a full account book while budgeting all of your hours elsewhere.

Keep the Cost in Delivery

The US model budgets a $70,000 TAM salary and a $90,000 vCIO salary. Its 1.25 burden for non-owner employees makes the annual costs $87,500 and $112,500 per FTE. Use your actual compensation costs when building your own plan.

Both roles sit in managed services delivery labor in the model. Putting them in sales would move the cost out of the service margin you are trying to judge. Keep the allocation consistent when comparing client profitability.

The model has TAMs and vCIOs report to the owner, with no added manager share. Owner time is already funded through the owner's salary. If you allocate that salary across responsibilities, allocate the existing cost rather than counting it again.

Put the Next Assignment Through the Capacity Check

I'd keep a short account-capacity record and update it when you plan a new client assignment. Give every line an owner so the check has someone responsible for acting on it.

• Finance supplies managed services MRR and the delivery-cost allocation.
• The owner compares the MRR-based role capacity with the time actually assigned to named people.
• Each TAM reviews logged alignment work against the scope and the unfinished assignments.
• Each vCIO checks the client count and review calendar alongside the logged workload.
• The owner records the capacity decision, the work it covers, and any change needed before the assignment starts.

If you decide to hire, build the forecast around when the new capacity will actually be available. The model gives no universal recruitment lead time to borrow. Use your own hiring plan and decide who covers the work until that start date.

I ask one question of this plan: what does this do to the board on Monday morning? Finish with an assigned client book you can explain. Keep the revenue basis beside the hours check and the calendar. When they disagree, name what you need to investigate before giving someone another account.