How Much Should an L1 Technician Make?

What Public Pay Data Says

An L1 technician at an MSP maps most closely to what the US Bureau of Labor Statistics calls a computer user support specialist: the person who takes the call, works the ticket and escalates what they cannot fix. BLS publishes pay for that role every year, split by industry, and the industry it calls computer systems design and related services is the category MSPs generally fall under.

The spread between the lowest and highest tenth is wide because the title covers everything from a first job on a help desk to an experienced specialist in a government agency. Expect an entry-level L1 toward the lower part of that range and a strong L1 who is close to moving up nearer the median. The network support median is a useful ceiling for the role: once an L1 is doing that work, they will expect that pay.

Why Your Local Market Decides the Number

A national median is a check, not an answer. The candidate you want is comparing your offer with the hospital, the school district and the other MSPs within commuting distance, and in the BLS industry table government employers pay this role well above computer systems design firms. If a remote role is on the table, your market widens, and so does the range of offers your candidate is weighing.

Remember that the candidate is weighing the whole offer. Remote or hybrid work, a predictable schedule, paid certification time and a manager who explains the path forward all count, and a smaller MSP can often compete on those when it cannot match a larger employer on salary alone.

• Check current job postings for L1 and help desk roles within your hiring radius, including in-house IT roles, not only MSPs.
• Ask recent candidates what other offers they had, and write the answers down.
• Look at the state or metro pay data BLS publishes for the same occupation code.
• Revisit the band every year, because the local market moves whether or not you review it.

What an L1 Actually Costs You

Salary is the smallest part of the decision. BLS's employer cost data for June 2026 found that wages and salaries made up 70.0% of private industry compensation costs and benefits the other 30.0%. On those proportions, a salary at the $60,440 industry median carries total compensation of roughly $86,000 before you add anything specific to the role.

Those figures are national averages across private industry, so treat them as a starting point rather than a quote. Your own benefits package, payroll taxes in your state and the tools you license per technician will move the real number, and your accountant can give you the exact ratio from last year's payroll.

On top of that sit the costs that are specific to an MSP: licenses for your PSA, RMM and documentation tools, a laptop and phone, certification fees, and the hours a senior engineer spends coaching a new technician through their first months. Those coaching hours are the ones most MSPs never count, and they fall on your most expensive people. The Staffing Calculator helps you model the loaded cost against the seats that technician will cover.

Compare that loaded cost with the work the role takes off senior engineers. When an L1 resolves the password resets, printer faults and new user setups, your L2 and L3 technicians spend their time on the work clients pay a premium for. That is where an L1 salary earns its keep, and it is why a slightly higher offer that brings in someone who resolves more at first contact is often the cheaper choice.

What You Should Expect for the Pay

An L1 role pays for itself when it keeps simple tickets away from L2 and L3. That makes its output measurable, and it gives you a fair way to connect pay to performance without turning the help desk into a race for ticket counts.

Track these as first contact resolution, first response time, tickets closed per technician per day and ticket reopen rate. Review them over a quarter, not a week, and use them to decide who moves up the band rather than to set monthly bonuses that encourage closing tickets early.

Structuring Pay So People Stay

What holds people at L1 is usually a path more than a number. First-line work is repetitive by design, and a technician who can see what the next level pays and what it takes to get there will put up with a year of password resets. One who cannot see a path will leave for a small raise elsewhere, and the raise is rarely the real reason.

1. Publish a band for L1, L2 and L3 with the skills and results each step requires.
2. Tie a raise to each certification you actually want the technician to hold, and pay the exam fee.
3. Review every L1 twice in their first year against the measures above, and say plainly what stands between them and L2.
4. Give L1 technicians a project or an automation to own, so the job is not only the queue.
5. Move people up when they are ready, even if it leaves an L1 seat to fill. Holding them back is how you lose them entirely.

The technician hub collects the resources technicians at each level use, which is a practical place to point a new hire during onboarding. A technician who is learning on their own time is usually one who intends to stay and move up.

What Underpaying Costs

Replacing an L1 means recruiting, onboarding and a stretch where a more expensive engineer absorbs the queue. Clients notice the change too, because the person who knew their office is gone. If the replacement leaves for the same reason, you pay all of it again.

Pay is also a signal to the rest of the team. If new L1 hires start close to what experienced L1 technicians earn, the experienced ones notice quickly, and they are the ones with the most options. Adjust existing pay when the market moves rather than only when someone resigns, because a counteroffer made after a resignation rarely keeps a technician for long.

Watch your employee turnover rate and employee Net Promoter Score for the service desk specifically. A rising turnover rate at L1 is often cheaper to fix with a modest raise and a visible path than with another round of hiring, and the fix shows up in your managed services gross margin as fewer escalations and less senior time spent on basic tickets.

Setting the Number

Put the pieces together in order. Start with what candidates in your area are being offered, check it against the public data, then add the loaded cost and decide how many seats the role needs to support to be worth it. If the number that keeps a good technician is more than your pricing allows, the problem is your seat price, not the salary.

Write the band down, share it with the people in it, and review it every year. A clear number with a visible path beats a slightly higher number with no explanation, and it saves you from rebuilding the help desk every time a competitor raises its offer.