MSP Service Manager: When the Desk Can Support the Role

Count the Desk Separately From the Business

Count desk staff. The model adds a service manager or working lead around 8 desk people, a dedicated dispatcher around 10, and a split into pods or tiers at 12 to 15. Those are different staffing decisions. They aren't milestones in total company headcount.

The US example has 12.50 full-time equivalents across the business. Its support desk has 4 technicians. Below the dedicated-dispatcher point, a team lead dispatches from the pool. The org chart won't take the next call.

Start with the people doing the support work. Then list the lead's dispatch, supervision, coaching, and escalation duties alongside their tickets. Check who covers those duties when the lead is unavailable. That gives you the work to cost.

Use Ticket Work to Interpret the Size Rule

The example's 700 seats produce different staffing needs at different ticket rates. At the well-run assumption of 0.5 tickets per seat a month, the model staffs 4 technicians. A typical MSP runs 1.0 to 1.4. In the model’s size ladder, the 700-seat row at 1.0 tickets per seat a month has 7 technicians.

The seat count hasn't changed. The modeled work has. Use your own ticket count and labor per ticket before deciding how much coordination the lead must handle.

Look at when the work arrives as well as its total. Check which escalations need the lead, which assignments they must change, and which decisions wait when they're already on a client task. A staffing ratio doesn't show those clashes on its own.

The pooled desk also has a model minimum of 2 people. That is a coverage assumption. It doesn't establish how much management work your particular desk needs. Use the ladder to start the check, then inspect the board and the lead's schedule.

Separate Management From Dispatch and Account Work

Give each duty a person and an authority limit. The same person can hold duties that fit their schedule. Don't give the same hours to several roles on paper.

The model keeps account management out of the service manager's job. It also separates technical alignment, which handles standards and the environment, from vCIO work on business priorities and budgets. Keep those responsibilities visible when you write the new role.

If you choose a working lead, put the management duties on their schedule. State how much ticket and escalation work they're still expected to carry. A title change doesn't make their existing workload disappear.

Price the Full Decision

The model's US service-manager salary is $102,500 before burden. The role sits in delivery labor, inside the managed-services gross margin calculation. Keep it there when costing the hire. Moving the expense to overhead doesn't make delivery cheaper.

The model tests hiring the manager at 4 desk people instead of waiting until 8. In that US sensitivity, annual EBITDA falls by $140,025, or 3.9 percentage points. EBITDA means earnings before interest, tax, depreciation, and amortization. The result is the model's total effect of the early hire, not just the salary figure.

Use the sensitivity to question an early hire. Then build your own budget from the actual pay offer and the other costs you add or remove. Name each change. Keep assumptions beside the figures so finance can check them.

Keep time and cash separate. If the owner stops doing dispatch but payroll doesn't fall, the business has freed some owner time. It hasn't saved that salary. Decide what the owner will do with the time before counting an earnings benefit.

Find the Work That Justifies the Role

Collect the management work that isn't getting done or is pushing other work aside. Put a task and a consequence on each line. Lead is busy isn't enough to tell you whether to fund management, dispatch, or another technical skill.

• The team lead lists coaching and quality reviews that were delayed, with the person responsible and the work that displaced them.
• The technical lead checks escalations waiting for help and records whether the block was skill, availability, or an assignment decision.
• The owner lists service decisions still coming back to them and marks which authority the proposed manager should take.
• The service lead checks unclear ownership and unreliable ticket records before treating those problems as a staffing shortage.
• The owner and finance lead cost the management duties that remain and compare them with alternatives the team can actually staff.

Fix an authority gap by assigning authority. Fix a dispatch gap with a person who can cover dispatch. Fund a service manager when you can show the management work and the means to pay for it. Don't make a management hire do the job of an unexplained queue.

Plan the Handoff Before the Start Date

Write the decisions the manager can make and the matters that still go to the owner. Name technical escalation cover. Check the work left with the people handing over duties, including any transition work they must still do.

Choose what you'll inspect after the handoff. Use the same definitions as the starting record: the delayed coaching, blocked escalations, or owner decisions that justified the role. Check whether the work changed and what else could explain the result.

A better response report after the hire doesn't prove the hire caused it. Ticket volume, client changes, staffing, and tooling can change the result too. Review the work the manager actually took on before claiming a saving.

Put the lead's current responsibilities beside the open board. Mark who owns each duty, what isn't getting done, and what ticket work it displaces. Cost the management job you find there. Then decide whether to fund it.