How Much Does Outsourced IT Support Cost Per User?

Outsourced IT support runs $100 to $250 per user per month nationwide. Standard coverage lands near $150 to $200. Anything under $100 usually means the provider is carrying more users per technician than the math supports.

That band isn't a market convention. It's arithmetic, and you can rebuild it yourself from public wage data in about four minutes. This guide shows you the math, then shows you how to take two quotes apart so you're comparing the same work.

Two quotes on your desk. One says $95 per user. The other says $190. Same headcount, same scope description, same promises about response times.

Neither number tells you which provider picks up at 4pm on a Friday.

Per-user is now the default way outsourced IT helpdesk services get priced, and it's the easiest model to quote misleadingly, because a per-user rate looks like a unit price when it's really a ratio in disguise. The gap between $95 and $190 isn't a negotiation problem. It's a definitional one. Those two providers aren't selling the same work, and the per-user format hides that better than any other billing model on the market.

What Does Outsourced IT Support Cost Per User?

Nationwide, $100 to $250 per user per month. Standard coverage, meaning helpdesk, monitoring, patching, endpoint protection, and backup, sits at $150 to $200. Compliance work and 24/7 coverage push past $250.

The spread is wide because the label is doing almost no work. Two providers can both write "per user, fully managed" on a proposal and mean completely different scopes. Identical phrase. Different product. One is selling ticket resolution. The other is selling ticket resolution plus threat detection plus a documented recovery position. Both call it managed IT.

Those are national figures. Local markets move, and they move more than you'd expect. Pricing in the Los Angeles market sits above the national band. What California SMBs actually pay tracks the state more broadly. Buying in one specific metro? Start with the local number, then come back here to take the quote apart.

Where Does the Per-User Number Actually Come From?

Labor, mostly. One support technician costs roughly $88,500 a year fully loaded. That's about $7,375 a month. Divide that by how many users the technician covers and you have the band every provider quotes from.

The Bureau of Labor Statistics puts the median wage for a computer user support specialist at $61,860 as of May 2025. Wages aren't the whole cost of employing someone. Benefits ran 30.1% of total compensation for private industry workers in March 2026. That's an economy-wide average rather than an IT-specific one, so treat it as a close approximation. Work backward and the loaded annual figure lands near $88,500.

Then it's division.

That's labor alone. No monitoring tools, no security licensing, no account management, no after-hours rotation, no margin, and nothing set aside for the senior engineer you actually want on the phone when a domain controller falls over at 6am on a Tuesday.

Now look at the $95 quote again.

A provider quoting $95 per user is running above 75 users per technician, or absorbing a loss to win the logo, or covering considerably less work than you assumed it did on the day you read the proposal. Usually the first. It's a fair thing to ask out loud, and the answer tells you more about your future response times than any service level agreement will. The same arithmetic is what makes in-house against outsourced a real comparison rather than a slogan.

What Counts as a "User" on Your Invoice?

Whatever the contract says it is. And providers define it differently.

Some count every person holding a company email address. Others count named humans who actually touch a managed device. On a 90-person distributor where 20 warehouse staff share four floor terminals, that definitional difference is 16 billable users, worth about $2,800 a month at a $175 rate. Annualized, that's more than the backup platform they'll spend three meetings arguing about separately. It rarely comes up during the sales cycle. It reliably comes up at renewal. Ask early.

Where the arguments start:

• Shared logins. Four people, one terminal, one shift each. Is that one user or four?
• Service accounts and shared mailboxes that no human ever signs into
• Contractors and seasonal staff, plus whether the count gets measured monthly or trued up once a year
• An executive with a laptop, a home desktop, a tablet, and a phone. Per-user calls that one. Per-device calls it four.
• The people who have email and nothing else

Get the definition in writing, with the counting date, and with what happens when the number moves in both directions, because a headcount that swings 15% between your busy season and your slow one turns an unexamined definition into a line item nobody agreed to. A company that hires 12 people in October and lets 12 go in January shouldn't still be paying peak headcount in June.

Per User, Per Device, or Flat Fee?

Per-user won the market because it budgets cleanly and it stops charging people extra for owning a phone. Both of those are real. It also makes two proposals look comparable when they aren't. That's the trade you're making when you accept the format.

What's Inside the Number, and What Isn't

Helpdesk, remote monitoring, patching, endpoint protection, backup, and vendor coordination are usually inside the per-user number. Software licensing, hardware, projects, migrations, and compliance evidence are usually outside it.

Patch management means keeping software updated so known holes get closed on a schedule instead of whenever somebody notices. Endpoint detection and response, usually written as EDR, is software that watches a laptop for attacker behavior rather than just matching against a list of known viruses. Remote monitoring is the agent that tells the provider a disk is filling up before you call them about it.

Licensing is the line item that surprises people. Microsoft 365 Business Premium lists at $22.00 per user per month on an annual commitment, and Microsoft has confirmed it holds there through the July 1, 2026 packaging update, while Business Basic goes to $7.00 and Business Standard to $14.00. Month-to-month billing costs more, which is its own line worth checking. If your provider folds licensing into a $170 quote, you're paying $148 for the service itself. If they don't, your true all-in cost is $192. Same provider, same work, two numbers that look nothing alike on a spreadsheet.

Ask for licensing as a separate line every time. It's the fastest way to make two proposals commensurate. One email. That's the whole intervention.

One more scoping question worth settling early, because the words get used interchangeably and they shouldn't be. IT support and managed IT aren't the same thing, and a per-user rate attached to the wrong one is how companies end up paying managed-IT money for a ticket queue.

What the Cheap Quotes Leave Out

CISA's Cyber Essentials treats multi-factor authentication, endpoint detection, continuous backup, and activity logging as the floor for any business connected to the internet, which is a rather different starting point from the one a thin proposal quietly assumes. Not the premium tier. The floor. Multi-factor authentication, if it needs saying, is the second step at login, the code or the prompt on your phone.

Price a quote against that list and the thin tier gets easier to read. A $79 per-user plan covering password resets and printer queues is a helpdesk contract. Not a security program. That's a legitimate thing to buy. Just buy it knowingly, and budget the security work as its own line rather than assuming somebody folded it in for you.

IBM put the global average cost of a breach at $4.99 million in 2026, a record high and up 12% year over year, with US organizations averaging considerably more. Set that against the $50 per user per month you'd save on a thin plan. Across 80 users that's $48,000 a year. Real money, and worth arguing about. Run both numbers. It also isn't the same order of magnitude as the thing it's protecting against.

Three Questions That Make Two Quotes Comparable

Ask what the technician-to-user ratio is, what the contract counts as a user, and who owns incident response when something actually breaks. Three answers, and two quotes stop being guesswork.

• What's your technician-to-user ratio, and how is escalation staffed? A provider running 40 to 1 with two senior engineers behind the desk is selling something different from one running 90 to 1. Both will quote per user. Neither ratio is wrong on its own, but only one of them matches a $95 rate.
• How does the contract define a user, and when is the count taken? Covered above. Ask it in writing.
• Who owns detection, hardening, and incident response? This is the one nobody asks.

That third question isn't really a pricing question, which is exactly why it belongs in a pricing conversation. CISA's joint advisory on managed service providers tells customers to make the contract specify whether the provider or the customer owns hardening, detection, and incident response, and to require multi-factor authentication on every provider account that reaches into your environment.

Read that again as a budget document. A provider who owns detection and response is selling something structurally more expensive than one who owns ticket resolution. The gap between $95 and $190 stops being mysterious the moment you know which one you're buying. And if a provider can't answer question three cleanly, the price was never the thing you should have been worried about.

When Per-User Is the Wrong Model for You

Skip per-user pricing if your headcount and your device count don't track each other.

A 60-person distributor where 45 people share 11 shop-floor terminals overpays badly on per-user and underpays on per-device, and the honest answer there is a hybrid quote nobody publishes on a pricing page. Ask for one anyway. If you already run a functioning internal IT team, a full per-user managed contract duplicates work you're already paying salaries for, and the overlap usually surfaces about four months in, when somebody notices two separate teams are both patching the same servers. A co-managed arrangement priced against named functions usually lands lower and overlaps less.

Under about 20 users, the fixed cost of onboarding a provider gets spread across too few people for the per-user math to look reasonable. It can still be the right call. It just won't look cheap on a spreadsheet, and anyone who tells you otherwise is selling.