When a business owner asks me what IT support should cost, my honest first answer is another question: how do you want to pay for it? The pricing model you choose shapes how your provider behaves far more than the number on the invoice. It decides who benefits when things go wrong, who pays for prevention, and whether your staff feel free to ask for help.
There are three common models: break/fix, block hours, and a flat monthly fee per user. Below is how each one works, the incentives it creates, the costs that tend to hide inside it, and which organizations it actually suits.
Break/fix: pay when something breaks
Break/fix is the oldest model. You call when something is wrong, a technician fixes it, and you get an invoice for the time and any parts. There is no monthly commitment, and nothing to pay in a quiet month.
It is easy to understand and easy to start. For a very small office with a handful of computers and simple needs, it can be perfectly reasonable.
The incentive problem
The trouble is the incentive. A break/fix provider earns money when your systems fail. Nobody in that arrangement is paid to prevent the failure in the first place. I do not think most break/fix technicians act in bad faith, but the structure does not reward patching on schedule, checking that backups restore, or tidying up old accounts. That work is invisible until the day it matters.
The hidden costs
- Downtime. The invoice covers the technician's time, not the hours your staff could not work.
- Hesitation. When every call costs money, people stop calling. Small problems get worked around until they become large ones.
- No baseline. Without regular maintenance, nobody can tell you with confidence which devices are patched, whether backups work, or who still has access.
- Unpredictable spend. A quiet year and a bad year look very different, which makes budgeting hard.
Block hours: prepaid time, drawn down
With block hours, you buy a bank of hours in advance, often at a better rate than ad hoc work, and the provider draws it down as they work. Some arrangements roll unused hours over. Many expire them.
Block hours give you some predictability, and usually faster attention than pure break/fix, because you are a committed customer. They work well for defined work: a project, a set of advisory sessions, or a known list of small tasks.
The incentive problem
The incentive is better than break/fix but still mixed. The provider is paid for time, so efficiency is not rewarded directly. On your side, the meter creates a quiet pressure. Managers start asking whether a request is worth the hours, and staff learn to save up problems or solve them on their own.
The hidden costs
- Expiry. Hours that expire unused are money spent on nothing.
- Administration. Someone has to watch the balance, approve top-ups and query line items.
- Scope gaps. Proactive work like patching, monitoring and security reviews often sits outside the block or eats into it, so it gets deferred.
- Disputes. Arguments about whether a task really took two hours wear down a working relationship.
Flat monthly fee per user: one predictable number
In a flat-fee model, you pay a fixed monthly amount for each person the provider supports. In exchange, the provider takes responsibility for keeping your environment running: helpdesk, monitoring, patching, security tooling and the routine administration that goes with it. This is the model Ceifa uses: one flat monthly fee per user, with unlimited helpdesk support during business hours.
Pricing per user, rather than per device, matches how work actually happens. People have a laptop, a phone, maybe a tablet and a shared workstation. Counting people keeps the bill simple and stops you from being penalized for giving staff the tools they need.
The incentive shift
This is the important part. When the provider's revenue is fixed, every ticket costs them money. The only way to do well is to prevent problems: patch on schedule, monitor before users notice, standardize devices, and fix root causes instead of symptoms. The provider's interest and yours point the same way: fewer incidents and less downtime.
It also changes how your staff behave. When asking for help does not trigger an invoice, people ask early. A strange pop-up gets reported instead of clicked. A slow laptop gets looked at before it fails during a deadline.
What to watch for
Flat fee is not automatically better. It has its own failure modes, and you should know them.
- Fuzzy scope. "All-inclusive" can mean very different things. Ask what is excluded: projects, after-hours work, on-site visits, new hardware setup, third-party software.
- Underservicing. A provider on a fixed fee could be tempted to do the minimum. Regular reporting and business reviews are how you check that the proactive work is actually happening.
- Paying for quiet months. Some months you will barely call. That is the point, but it can feel odd at first. The value is in what did not break.
- Who counts as a user. Clarify how part-time staff, seasonal workers, shared mailboxes and board members are treated.
Which model fits whom
There is no single right answer, but there are clear patterns.
- Break/fix can make sense for a very small office with simple, stable needs, little sensitive data, and a tolerance for the occasional bad week.
- Block hours suit organizations with their own IT staff who need specialist help on demand, or anyone buying a defined project or advisory work.
- A flat fee per user suits organizations that depend on technology every day, handle client or financial data, are growing, or simply want IT to be a known line in the budget instead of a surprise.
Many organizations end up with a mix: a flat fee for day-to-day support and security, with projects such as an office move or a major migration quoted separately. That is healthy, as long as the boundary between the two is written down.
How to compare quotes fairly
Quotes built on different models are hard to compare directly. A few steps help:
- Work out what you actually spent on IT last year, including emergency invoices, software bought in a hurry, and the internal time someone spent being the unofficial IT person.
- Ask each provider to show what is included and excluded, in writing.
- Ask how proactive work is evidenced: reports, patch status, backup test results.
- Ask what happens to the price as you grow or shrink.
- Ask what it costs to leave.
The cheapest monthly number is rarely the cheapest year.
Frequently asked questions
Is flat-fee IT support more expensive than break/fix?
In a quiet month, yes, because you pay more than zero. Over a full year, the comparison depends on how much downtime, emergency work and lost staff time you were absorbing under break/fix. Many organizations find the total is similar or lower and far more predictable, but it varies with your size, your systems and your market.
What does unlimited helpdesk support actually mean?
It should mean your staff can ask for help as often as they need during the stated support hours without being billed per ticket. It does not usually cover projects, new system rollouts or work outside support hours. Read the scope document so you know where the line sits.
Why price per user instead of per device?
People, not devices, create support needs. Per-user pricing keeps the bill simple when staff use several devices, and adding a phone or tablet does not change your invoice.
Can we move from block hours to a flat fee partway through a contract?
Usually, but check your current agreement for notice periods and what happens to unused hours. Plan the change so the new arrangement starts before the old one ends, rather than leaving a gap.
How Ceifa approaches pricing
We chose the flat-fee per-user model at Ceifa because it puts our incentives where our clients' are. You pay one predictable monthly fee per user, your staff get unlimited helpdesk support during business hours, and critical issues get a response within 30 minutes during business hours. Every managed client gets the same security baseline and a monthly report, so you can see the proactive work instead of taking our word for it.
We do not publish prices, because the right scope depends on your environment, but I am happy to walk you through how it would work for your organization. See how our managed IT services are structured, or get in touch and we will talk it through.