What Actually Sets Your Per-User IT Support Price?
Two offices in the same district, same headcount, both get a per-user support quote labeled “managed IT.” One comes in at roughly 250 TL per user a month, the other at 900 TL. Neither number is arbitrary. Behind each one sits an assumption about how much capacity is reserved, what response time is promised, and what’s actually bundled into the fee. Worth asking about all three before the number means anything.
Same Label, Different Math
“Per user” isn’t a fixed unit. Some providers price it by seat (one person, however many devices they carry); others price by managed device. If a user’s laptop, phone and desktop each get counted separately, a quote that looks like “250 TL per user” can quietly turn into three times that once you count devices instead of people.
Here’s what pulls the number up or down:
| Factor | Pulls price down | Pulls price up |
|---|---|---|
| Counting unit | Flat per seat, device count ignored | Priced per managed device |
| Response time | Business-hours, first reply in a few hours | 24/7, 15-30 minute first response |
| Coverage window | Business hours only | Nights and weekends included |
| Remote vs on-site | Mostly resolved remotely | Frequent on-site visits (shift work, factory floor) |
| Bundled tooling | Ticketing system only | EDR, backup, password manager included |
| Contract length | 2-3 year commitment | Month-to-month, no commitment |
Each row can swing the price 10-30% on its own; stack three or four of them in the same direction and the final number doubles without anyone changing the actual work. A 20-person office where each person carries three devices — desktop, laptop, phone — and the provider bills per device can see a quote that reads “400 TL per user” land closer to 1,200 TL once the math is device-based instead of seat-based. Worth pinning down which one you’re actually being quoted before signing.
Flat Fee or Pay-Per-Ticket?
Two billing models carry the risk differently.
A flat per-user fee stays the same no matter how many tickets you file. Budgeting gets easier, but it also gives the provider an incentive to keep ticket volume down — which cuts both ways: it can mean better proactive monitoring, or it can mean tickets sitting unanswered if the provider is cutting corners.
Pay-per-ticket charges for each support request individually. A quiet month costs little; a month with a server migration or a ransomware recovery can blow past the flat-fee equivalent fast. This model tends to work for stable, low-incident environments and gets shaky fast for a growing office where ticket volume is unpredictable.
There’s also a hybrid: a lower flat monthly fee covers monitoring, patching and baseline advisory work, with a set number of tickets included before per-ticket charges kick in. For smaller offices this splits the risk — it keeps the predictability of a flat fee without removing the provider’s incentive to actually prevent issues.
What we see across client conversations: offices above roughly 15 users almost always move to flat pricing, because predictability becomes worth more as the organization scales.
What’s Missing From the Quote Until It Isn’t
A few questions rarely get asked at quote stage, and then show up as extra line items later:
- Are projects included? New-office setup, server migrations, mass hardware refreshes — these are usually billed separately. Check what “out of scope” actually covers.
- Who supports third-party software? If the provider doesn’t take responsibility for your accounting or production-line software, you’ll be paying for that vendor’s own support separately.
- Is hardware and licensing bundled or billed apart? Antivirus, backup storage, a new firewall appliance — these sometimes sit outside the “support” line entirely.
- Is after-hours emergency response extra? If the contracted response time only covers business hours, a 2 a.m. call can carry its own charge.
Asking these four questions at quote stage is what prevents the “wait, we’re paying for this too?” conversation three months in.
Frequently Asked Questions
Is there a reasonable price range for a 10-15 person office? It depends on coverage hours, bundled tools and how often on-site visits are needed — there’s no single “correct” number. The more useful comparison is asking multiple providers to quote the exact same scope (same response time, same bundled tools) rather than comparing headline numbers from different scopes.
Per-user or per-device — which is fairer? In most offices where one person carries more than one device (desktop, laptop, phone), a flat per-seat price tends to be more predictable. Per-device pricing means the bill grows automatically as your device count does, whether or not headcount changes.
What’s the single most useful question when comparing quotes? “What are the first three things that aren’t included in this price?” That one question surfaces most of the hidden cost before you sign anything.
What happens if the quote doesn’t mention a response time at all? Without a written SLA, there’s a gap between what you expect during a critical outage and what actually happens. A verbal “we’ll get right on it” isn’t binding — a quote with no written response-time clause should be treated as incomplete, however attractive the headline price looks.
Related Posts
How to Write an IT Support Request That Gets Fixed the First Time
A ticket that says 'my computer is not working' means the technician has to call you first. Here are the five details that let a support team start work from the first message, how to take a useful screenshot, and when to phone instead.
Read more: How to Write an IT Support Request That Gets Fixed the First Time
What Happens When the One Person Who Knows Your IT Leaves?
In most offices one person knows the router password, who owns the domain name and where the backup goes. Here is what access, records and ownership the company should hold before that person walks out, step by step.
Read more: What Happens When the One Person Who Knows Your IT Leaves?
Scan-to-Email May Stop Working in December 2026: What to Check
Microsoft will disable Basic authentication for SMTP AUTH by default in Exchange Online at the end of December 2026. Here is how to find the printers, scanners and old apps that depend on it, and what to replace it with.
Read more: Scan-to-Email May Stop Working in December 2026: What to Check