MSP Revenue per Employee: Check Profit Before Hiring

Make the People Count Comparable

A full-time equivalent, or FTE, expresses staffing in full-time units, with part-time work prorated. Count the owner and the support functions alongside delivery staff. The model's denominator includes sales and administration rather than asking technicians alone to carry the ratio.

For your annual comparison, have finance reconcile the staffing basis with the period covered by revenue and profit. A person who joins during the year isn't present for that whole period. Show how you treat starters and departures instead of dividing annual revenue by an unexplained year-end snapshot.

Document the treatment of outside labor too. If you change which contractors or outsourced roles the denominator includes, keep a separate comparable view. Otherwise a change in who appears on payroll can be mistaken for a change in the output of the work.

Use the Same Revenue Definition

The model's revenue-per-employee goal uses total revenue. Include managed services and recurring products, then include hardware and project revenue. Divide that annual total by your consistently calculated FTE count.

A ratio using managed-service revenue alone has a different numerator. Label it separately if it helps your review, and compare it with a benchmark using the same definition. It cannot be substituted for the total-revenue ratio merely because both say revenue per employee.

For the profit calculation, divide normalized EBITDA by that same FTE count. Normalized means adjusted to the comparison basis, including required owner compensation. Identify any owner-pay adjustment beside the result so unpaid management work isn't presented as employee leverage.

Put Both Results Beside the Model

The model sets the following US planning levels. They are reference points for investigation, not evidence that every business below a line has the same operating problem.

The goals connect through margin: $250,000 × 20% = $50,000. Raising revenue per employee without preserving the margin doesn't produce the profit goal. Check the costs behind the added revenue before describing the higher sales ratio as better leverage.

The model's US example makes that distinction visible. It holds the starting revenue constant while the growth setting adds marketing capacity and more onboarding work. The staffing and spending change before the comparison adds revenue from the extra clients.

The growth result of $39,578 falls below the model's $40,000 minimum even though the extra investment is deliberate. That explains why the ratio needs a plan beside it. The model uses unrounded inputs, so displayed FTE counts and results are rounded independently.

Investigate the Cause Before Headcount

If both results are low, examine the price and revenue mix alongside the work being delivered. Check whether staffing or sales spending was deliberately added ahead of revenue. Then test the cash forecast before deciding whether the team is unaffordable or the investment should continue.

If revenue per employee is strong while profit per employee is weak, inspect the margin and overhead that sit between them. The model's hardware line is 19% of revenue and uses a 30% product margin. A revenue stream can add substantial sales without contributing the same gross profit as a higher-margin stream.

If revenue per employee is below goal while profit per employee meets your plan, examine the underlying margin and work before assuming you need more volume. Compare the proposed growth with the delivery capacity it would consume. Set the decision from that calculation rather than treating a larger revenue numerator as the objective by itself.

Strong results on both measures still leave a workload question. Ask the service lead to identify the work that lacks capacity and the skills it requires. The ratios don't establish who is available when a client needs help.

Price the Work the Hire Would Take

Build the proposed hire into the same forecast before approving it. Add the loaded compensation and the genuinely additional costs of the role, then include the revenue and delivery work the plan expects. Show the start dates rather than assuming the extra revenue appears when payroll starts.

The model staffs support from tickets and labor minutes, with residual alert work included. Use that workload check for a desk hire rather than turning a company-wide revenue ratio into a seats-per-technician rule. Account for work that a new person would take from the owner or another role.

Compare the proposed workload with other ways of assigning it. The model favors the cheapest capable resource and automation of suitable level-one work. Price the specific alternative and the work still requiring human effort before treating it as a saving.

My view is that a staffing ratio should end with an investigation, not a vacancy or a dismissal. A rule of thumb doesn't answer the next ticket. Record which constraint the proposed change removes and where its cost and output will appear in the forecast.

Keep a Decision Record Beside the Ratios

Have finance retain the revenue definition and FTE calculation with each comparison. Ask the service lead to record the capacity issue, and have the owner identify any planned investment affecting the period. Revisit the explanation when the recorded result differs from the forecast.

For a hiring proposal, name the work to be covered and the date the additional cost begins. State the expected revenue or delivery change separately, with the assumption behind it. If the plan depends on future wins, show what happens to cash when those starts move.

Start with a completed annual period and reconcile both ratios using the same people count. Compare the result with the model and your own approved plan, then choose the unresolved question that matters to the hiring decision. Price that question before changing the team.