Guide

How IT support pricing models actually work

Per user, per hour, flat fee, monthly plan: the labels sound interchangeable and behave nothing alike. This is what each model really measures, and the questions that stop the first invoice being a surprise.

Small business IT support is priced in a handful of recurring shapes: per user or per device, per hour or in prepaid blocks, a flat monthly fee, or per project. None of them is a trick and none of them is universally right. Each one measures something different, and each one quietly shapes how you and the provider behave.

This page explains the models without attaching figures, because we do not publish prices anywhere on this site. What moves the number inside whichever model you choose is a separate question, answered in what IT support costs.

The models, one at a time

Per user

You pay for each person covered, whatever mix of laptop, phone and accounts they carry. It is the most common model for managed support because it scales with the thing a business actually thinks in: headcount. Hiring someone has a known support cost attached; someone leaving should reduce the bill, and checking that it actually does is a surprisingly good test of your provider's attention. The soft spot is the counting rule: shared mailboxes, service accounts and part-timers all need a written answer before the first invoice, not after.

Per device

The same idea measured in hardware. It fits businesses where devices are shared or outnumber people: shop floors, warehouses, clinics, anywhere a workstation belongs to a shift rather than a person. In a one-laptop-per-person office it is just the per user model with more counting.

Per hour

You pay when something breaks, for the time it takes. Honest for genuinely occasional needs, and you pay nothing in a quiet month. The behavioural cost is real though: hourly billing quietly discourages the early, small call, and IT problems are cheapest exactly when they are small. Nobody is paid to prevent anything under this model, only to repair it.

Blocks of hours

Prepaid bundles of hourly time, usually at a better effective rate. A sensible middle ground for the business that needs help several times a year but not every week. Ask two questions before buying one: do the hours expire, and what happens when the block runs dry in the middle of a problem.

Flat monthly fee

One figure, agreed scope, everything inside it covered. This is what "fixed price IT support" and "monthly IT support plan" usually mean in practice. Predictable for you, and it puts the incentive where you want it: under a flat fee, prevention is the provider's profit margin, so things being set up properly is suddenly in both your interests. The entire model lives or dies on scope. A flat fee with a vague scope is not fixed pricing, it is a recurring argument with a direct debit attached.

Per project

A defined job at a quoted price: a migration, a rebuild, a cleanup. The right model for work with a beginning and an end, and the wrong one for ongoing cover, because the day after the project closes, nobody is responsible for anything. Most businesses end up pairing it with one of the models above rather than choosing between them.

Questions that expose the real shape of any quote

Every one of these has a short, checkable answer. A provider who will not give one is answering a different way.

  • What exactly is counted? Users, accounts or devices, and which edge cases are in: shared mailboxes, service accounts, the owner's home laptop.
  • What is explicitly out of scope? The exclusions list is where flat fees stop being flat. Projects, site visits and new starters are the usual suspects.
  • Do unused hours expire? For block arrangements. If they expire, the effective rate is higher than the quoted one and you should judge it accordingly.
  • What happens when headcount changes? Adding a person mid-month is easy to bill. Check that removing one is handled with the same enthusiasm.
  • Is prevention included, or only response? A monthly fee that only buys reaction is hourly support with a subscription. The point of paying monthly is that someone is paid to stop things breaking.
  • What does leaving look like? Whatever the model: who owns the accounts, what gets handed over, and what notice is required. A good price you cannot walk away from is not a good price. If you suspect that has already happened, see technical cleanup.

Who this is for

  • Owners comparing quotes built on different models and struggling to line them up
  • Businesses moving from calling someone when it breaks to something more deliberate
  • Anyone who has been offered a per user price and wants to know what to ask before signing
  • Businesses whose current arrangement produces surprise invoices and recurring scope arguments

When this is not the right fit

  • Anyone looking for a price list. We do not publish figures, here or anywhere, because a number without your situation attached would be invented. The reasoning is on what IT support costs.
  • Businesses big enough for internal IT. The models above still exist at that size, but the comparison that matters is against a salary, and that is a different calculation.
  • Anyone whose real question is how to pay less. That has its own honest answer: how to reduce IT support costs.

What Tech True Point can help with

We support small businesses on the ordinary things: computers, email, accounts, domains, the website, and the systems around them. Which model that should be sold under depends on your situation, and we will tell you honestly, including when the answer is a model with a smaller bill.

  • A straight recommendation on which model fits how your business actually runs
  • Reading a quote you already have and translating its counting rules
  • Ongoing IT support with the scope in writing
  • Microsoft 365 and Google Workspace administration
  • One-off projects quoted as projects, not smuggled into a monthly fee
  • Care plans for the website side of the same decision

Common questions

Why is there no price list on this page?

Because a price list for IT support is a list of answers to a question nobody has asked yet. The honest inputs, how many people, what state the setup is in, how fast you need answers, what is in scope, change the number so much that a published figure is either padded to cover the worst case or a teaser that will not survive contact with your actual situation.

We do not publish figures anywhere on this site for exactly that reason. What we can publish is how each model works, which is what this page is, and what moves the number, which is the what IT support costs guide.

Is per user or per device better?

Neither is better; they measure different things and suit different businesses. Per user fits when each person carries a predictable bundle of technology. Per device fits when the devices outnumber the people or do not belong to anyone in particular: shared workstations, a shop floor machine, meeting room kit.

What matters is that the counting rule matches your reality. A per user price in a business full of shared devices leaves half the estate uncovered or argued about, and a per device price in a laptop-only office just makes the same number harder to predict.

What actually counts as a user?

Ask, because providers genuinely differ. Sometimes it is every human. Sometimes every account, which matters once you notice that shared mailboxes, service accounts and that one login the old system uses are all accounts. Sometimes it is only people who can raise a ticket.

The gap between those definitions is where the surprise on the first invoice comes from. It is also why two quotes that look far apart are sometimes the same quote with different counting rules.

Are prepaid blocks of hours worth it?

They sit between hourly and monthly, and they inherit a bit of both. You get a better effective rate than ad hoc hourly and some budgeting certainty, without committing to a monthly arrangement. That is genuinely useful for a business with occasional but real needs.

The two things to check before buying one: whether the hours expire, and what happens when the block runs out mid-problem. A block that quietly evaporates at year end was a donation, not a plan.

Can we mix models?

Yes, and mature arrangements usually do. A common shape: a monthly agreement covering the routine, with project work quoted separately per job. That separation is healthy, because it stops big one-off jobs being smuggled into the monthly fee, and it stops the monthly fee being inflated to cover jobs that may never happen.

The thing to keep in writing is the boundary: what the monthly covers, and what triggers a separate quote. Most billing disputes in IT support are two people with different memories of that line.

Get a Quote

Want to know which model fits your business

Tell us how many people you are, what you run on, and how often things go wrong. You get a straight recommendation, including if it is a model we do not offer.

Call now Request a quote