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. Use the network support median as a comparison when an L1 takes on that work, then discuss the duties, local pay evidence and the technician’s pay expectations before agreeing the role and salary.

In Canada, check Job Bank wages for user support technicians (NOC 22221) in your province and region, then compare the duties and experience with your L1 role.

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.

Ask candidates how the whole offer fits their needs. Discuss remote or hybrid work, the schedule, paid certification time and the path to the next role alongside salary. Record which parts matter to the person rather than assuming they make up for a lower offer.

• 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

Use 1.25 times annual salary as a US planning allowance for payroll taxes, benefits and insurance, excluding paid leave, which is already covered by salary. At the $60,440 industry median, $60,440 × 1.25 = $75,550 in annual salary and those employer costs before role-specific costs.

BLS's broader June 2026 ratio is about 1.43x (100% ÷ 70.0% = about 1.43), but that measure is per hour worked and includes paid leave as a benefit. Do not substitute it for the 1.25x salary allowance. Check that allowance against your actual payroll taxes, benefits and insurance, and account for paid leave in available working hours rather than adding it again as a salary cost.

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. Count those senior coaching hours when estimating the cost of the hire. 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 could take off senior engineers. Plan which tickets an L1 would handle so your L2 and L3 technicians can spend their time on the work you assign to them. Compare the cost of a higher offer with the first-contact resolution and senior cover you expect, then check those assumptions against actual results.

What You Should Expect for the Pay

Assess an L1 role against the simple tickets it handles and the L2 and L3 work it requires. Use the measures below alongside ticket reviews to discuss performance and progression. Check the quality of the work before rewarding a higher ticket count.

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

Discuss pay and progression with each L1 technician. Show what the next level pays and what it takes to get there, then ask what would help them stay. If someone is considering another role, investigate the pay, workload and progression on offer rather than assuming that a raise is the only cause.

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, and plan how to cover the L1 seat they leave. Discuss the next role and its requirements rather than delaying that conversation because the current seat needs filling.

The technician hub collects the resources technicians at each level use, which is a practical place to point a new hire during onboarding. Ask a technician who is learning on their own time what they want to do next and what support they need. Do not infer their intention to stay from that learning alone.

What Underpaying Costs

Cost a replacement from your own recruiting and onboarding records. Include any senior time needed to cover the queue and the work required to hand over client knowledge. If repeated departures create those costs again, investigate the reasons before choosing a response.

Compare new-hire offers with the pay of existing L1 technicians doing comparable work. Discuss any mismatch against responsibilities, experience and the published band. Review existing pay when the market moves rather than only when someone resigns, and do not assume that a counteroffer resolves the reason for leaving.

Watch your employee turnover rate and employee Net Promoter Score for the service desk specifically. If turnover rises, ask why people are leaving and compare the cost of proposed pay or progression changes with recruiting, onboarding and cover in your own records. Track escalations, senior time and managed services gross margin to check what changes after the decision.

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 that cost exceeds what your current pricing can fund, review the service price, delivery costs and role design before making an offer.

Write the band down, share it with the people in it, and review it every year. Explain what supports the next pay step and ask whether the path matches the work the technician wants to do. Record the response alongside the pay decision for the next review.