When to Hire Another MSP Technician: Count Desk Hours

Start With the Hours You Have Left

The US example staffs four technicians at about 96.83 productive hours each per month against about 309.8 hours of ticket and residual alert work; its unrounded inputs leave 0.80 of a full-time role unused. That assumes 700 seats at the well-run rate of 0.5 tickets per seat per month, while a typical MSP runs 1.0 to 1.4. Use Service Desk Staffing: Turn Ticket Work Into Headcount for the full sizing walkthrough.

For this decision, bring the hours left and the assumptions behind them. Check whether those hours belong to people qualified for the expected work and available when it arrives. Spare capacity across a month doesn't identify who can take an escalation during a particular shift.

Test What Fills the Slack First

Treat extra tickets, longer handling, and more alert work as different ways of spending the same remaining hours. Hold the other inputs constant to see each effect. Then combine the changes you actually expect; don't give every change its own copy of the headroom.

Those are sensitivities for the example, not universal hiring cutoffs. The extra ticket rate is an increase from its baseline, not the total rate you should target. Use your measured workload and the unrounded inputs when you set your own boundary.

For a planned client addition, forecast its ticket labor and residual alert work together. Keep any onboarding work visible too: the model assigns that work to project engineers. If your desk will do it, reserve the people and hours rather than treating the new contract as revenue without a delivery assignment.

Forecast to Useful Capacity

Build the hiring forecast across your actual recruiting and training lead time. Start with the dates from your own hiring records and the steps this role needs. An accepted offer and independent desk capacity are different milestones.

Ask the service lead when the new technician could handle the intended assignment and what support they would still need. Put the mentor's displaced delivery time into the same forecast. Don't count the learner as fully available while leaving the mentor fully booked elsewhere.

Have the account owner distinguish committed client changes from uncertain opportunities. Say a client is due to join while the role is still vacant. Compare the expected workload at that start date with the people you will actually have, then test what changes if recruitment or supervised training takes longer than planned.

Include known leave and the required skills in that comparison. If the forecast shows a gap before the recruit can do the work, the decision needs both a recruitment date and a coverage plan. Waiting for every spare hour to disappear leaves that coverage question unanswered.

Name Who Covers the Gap

I'd settle interim coverage before making the offer. Ask the person managing the schedule what can be moved within the service commitments, and which work needs qualified cover. Agree any changed client commitment with the account owner rather than quietly pushing its date.

• The service lead checks whether a documented fix, suitable automation, or a different qualified resource can remove forecast work. Count the change only after checking its result and remaining supervision.
• The scheduler assesses temporary cover, including an existing approved partner where appropriate. Confirm the scope, access, availability, and actual cost before relying on it.
• The owner records any delivery work they will cover and which existing responsibility will move. Owner time needs an assignment too; it is not free capacity to add twice.

If none of those arrangements can cover the work, take the gap back to the owner before promising another client start. Change the delivery plan or the commercial commitment through the normal approval process. A recruitment plan doesn't authorize service the current team cannot provide.

Fund the Whole Staffing Step

The example's next whole pooled technician carries about $80,326 of annual burdened pay at its blended US wage. That is the model's staffing step, not a quote for the particular person you will hire. Use the actual role and compensation plan for the budget, alongside recruiting, training, and any temporary cover.

Keep the capacity calculation beside that budget. Fractional spare hours don't pay a whole salary, and a funded vacancy doesn't create trained cover immediately. Approve the spending and the delivery arrangement together.

Put the Trigger on the Service Board

Keep a short decision record with the next staffing review. Update it when measured demand or an approved commitment changes. The useful trigger is the expected capacity gap across the lead time you can actually deliver.

• The service lead reconciles ticket labor and residual alert work, then identifies the assumptions changing the forecast.
• The scheduler confirms available hours and skills, including leave, supervision, and the named people covering the gap.
• The account or sales owner supplies committed client starts and scope changes, separately from uncertain pipeline.
• The owner approves the role, funding, and recruiting dates, with a clear decision on interim cover.
• The service lead reviews the new technician’s demonstrated capacity before removing the temporary arrangement.

My test for the plan is this: what does it do to the board on Monday morning? The scheduler should be able to point to the work, its owner, and the cover while the hire learns. Bring those assignments with the forecast when you ask for approval.