When to Hire Your First Employee and Add a Second Tech

Name the Work You Need to Hand Over

Start with the tasks taking the owner's time and the service work waiting for help. Record the skills each task needs. If the gap is technical support, choose the role from that work instead of assuming every first hire should be the same grade.

The model's Tier 2 salary is useful for costing an example, not a hiring prescription. If the technician must work independently on the clients you serve, test for those skills. Keep the work that still needs the owner visible in the plan.

Count the owner's delivery time too. The model pays the owner a fair-market salary before profit and treats time spent working as a technician as direct labor. A desk doesn't become affordable by leaving the owner's tickets out of its cost.

Build the Full Cost Beside the Salary

The US calculation is $62,000 times 1.25, or $77,500 annually. The model's general burden covers payroll taxes, benefits, and insurance. It excludes other items such as recruiting and training, so don't label that result the complete cost of the hiring decision.

Use your actual planned payments to finish the budget. Add the tools and equipment the role needs, then include recruiting and training commitments. Keep supervision and onboarding time in the workload plan instead of assuming the new employee arrives fully productive.

Check where each item already sits in your accounts. A delivery tool bought once shouldn't appear again as a separate new purchase just because the employee uses it. The same rule applies when existing staff provide training during time already covered by payroll.

What MRR Pays for One Tech, Then Two?

Say you are costing one US Tier 2 technician at the model's $62,000 salary and 1.25 burden. That is $77,500 a year, or about $6,458 a month. Keep that monthly wage beside the recurring revenue that must fund it.

The model targets 50% managed services margin after delivery labor and tools. At its $225 seat price, the $22.50 tool allowance takes 10% of managed revenue, leaving 40% for delivery labor. For this illustration, assign that whole labor allowance to the proposed technician, before adding any other delivery roles.

Divide $77,500 by 12, then divide by 0.40. The result is about $16,150 of managed services MRR to fund that one technician's burdened pay at the stated margin, or about 72 seats at $225. A second identical technician doubles the people cost and the required MRR.

This is a wage-funding subtotal, not the revenue that makes the whole MSP break even. It leaves out TAM and vCIO work, centralized services, on-call pay, and the owner's delivery time, as well as the other hiring costs and overhead. Add those costs before treating the hire as affordable; the model's $60,000 MRR per support FTE remains a separate cross-check rather than this single-role calculation.

My test is what this does to the board on Monday morning: who covers the work this calculation leaves out? Put that person and their cost beside the proposed hire before deciding that the payroll fits.

Treat the Revenue Ratio as a Check

The model retains $60,000 of monthly recurring revenue per support full-time equivalent as a cross-check. It staffs the desk from ticket capacity instead. That ratio doesn't tell you which work arrives or whether the people available can cover it.

Monthly recurring revenue is the recurring amount billed each month. It isn't the amount left to pay a new employee. Product purchases and existing delivery commitments still need funding before the remaining contribution can support another role.

I'd compare the proposed budget with your current margin and actual cash forecast. Add the hire's payments on their scheduled dates and include the work the owner still carries. A client invoice can support the revenue plan without clearing the bank before payroll.

Use your own records to calculate what additional recurring contribution is needed. Keep the other costs and the profit you intend to preserve visible. The $60,000 cross-check cannot supply that answer on its own.

Calculate the Desk From Tickets and Alerts

Measure ticket volume and the labor needed to handle it, then add residual alert work. Compare that workload with productive time the proposed team can actually provide. Look at coverage during busy periods as well as the monthly total.

The model's staffing ladder shows why the ticket rate matters. At 300 seats and a well-run rate of 0.5 tickets per seat per month, it has 1.37 full-time equivalents of desk work and staffs 2 technicians. A full-time equivalent expresses the work as a share of a person's productive capacity.

A typical MSP runs 1.0 to 1.4 tickets per seat per month. At 1.0, the same 300-seat ladder has 2.62 full-time equivalents of desk work and staffs 3 technicians. The seat count hasn't changed, but the work has.

Keep the timing beside that calculation. A roster can have enough total hours and still lack a capable person when requests overlap. Check the service window you sell and who takes the next ticket while someone is already committed.

Plan the Second Hire Around Cover Too

The model's minimum desk is 2 people, because a desk of one has no internal cover for leave or sickness. That is a model staffing assumption. It doesn't mean every owner must hire two employees at once.

If the owner will cover the first technician, put that work in the roster. Check which other responsibilities the owner must leave to do it. Cover exists only if a qualified person can actually take the work, not because the owner's phone number appears at the bottom of the sheet.

Use the same check for the second hire. Ticket work may justify more capacity, or the missing cover may be the immediate problem. Price the solution you can fund and check that it fills the gap before deciding the answer is another identical role.

Keep the Next Roles Attached to Their Work

The model staffs account roles on monthly recurring revenue too: $70,000 per technical alignment manager and $140,000 per vCIO. Those ratios size different jobs. They don't add support capacity to the desk calculation.

The technical alignment manager handles standards and the environment; the vCIO handles the business conversation and budget. Assign those responsibilities while they remain part-time. Don't assume the technician you've hired to clear the queue can absorb them without changing the workload plan.

Administration needs the same treatment. The model's larger US example has an operations and office manager at a $72,000 salary. That isn't a rule for the next hire in a smaller business; identify the administration that needs doing and price the role that fits it.

Make the Decision Before Posting the Job

• Owner: list the work to hand over and the skills it requires. Record what will still stay with you.
• Owner: calculate the full hiring budget from the salary and actual additional costs, without counting an existing payment twice.
• Owner: measure ticket and alert effort, then check who covers the service window during absences and busy periods.
• Owner: put the payments into the cash forecast and check the recurring contribution available after existing commitments.
• Owner: choose the role that fills the funded gap and name who will train and supervise the person.

If the need is clear but the funding is missing, the decision still needs work. Recheck the service scope and costs before committing to payroll you cannot support. If the money is available but the job is vague, finish defining it before recruiting.

Start with the next period when the proposed technician would be unavailable. Name the person who could take their tickets and the work that person would have to set aside. That check makes the first hire and the second hire part of a staffed service, rather than two isolated salary decisions.