The short answer: There is no single „price of IT support" — the figure depends on how many workstations and servers you have, the scope of services and the guaranteed response time. A monthly retainer pays off the moment your business depends on IT every day: you run a server or a business-critical application, downtime costs you money, and you need monitoring, backups and updates to happen on their own. Hourly billing is fine where there are a handful of computers, everything runs in the cloud, and a day without technology won’t sink the company. When comparing quotes, don’t just line up the monthly figures — look at exactly what each one covers: without a defined scope and SLA you’re comparing two different services that happen to share a name.
Small business owners usually start thinking about IT support only when something stops working: e-mail is down, the bookkeeper can’t get into the accounting system, the server didn’t come back up after a power cut. Then comes the question „what would it cost to have someone look after this" — and the quotes that arrive can differ several times over. This article explains why that is, what makes up the price, and how to choose between a retainer and hourly billing without paying for something you don’t need.
What you’re actually buying: IT support isn’t „a repairman on call"
Before we talk about price, it’s worth clarifying what IT support actually covers. Well-designed support is mostly invisible work that goes on even when nothing is broken:
- Monitoring — automated oversight of servers, workstations, disk space, drive health (SMART), backups and service availability. The goal is to learn about a full disk or a dying RAID array before the staff do.
- Backups and restore testing — not just „the backup is running", but regular verification that the data can genuinely be brought back. A backup nobody has ever tried to restore is just hope. What a sensible multi-copy strategy looks like is covered in the article on the 3-2-1 rule and using an external drive as your only backup.
- Updates and patch management — controlled installation of Windows updates, server roles, firmware and applications. Controlled means: test it, deploy it outside working hours, keep a way back.
- User administration — onboarding and offboarding staff, access rights, shared folders, mailboxes. An employee leaving without their access being revoked is one of the most common security failures in small businesses.
- Security — antivirus/EDR on workstations, firewall, multi-factor authentication, a separate Wi-Fi network for guests.
- Helpdesk — a single place where staff report problems, with tickets on record. Not „call Frank’s mobile and hope he’s free".
- Documentation — what runs where, which licences you hold, passwords, configurations, contracts with internet and service providers.
An hourly IT guy on call typically covers only the helpdesk item from this list — and reactively, once something has already happened. That’s not a criticism, just worth knowing: you’re paying to put out fires, not to stop them starting.
What a retainer should cover (and what usually sits outside it)
A retainer contract makes sense when it has a clearly defined scope. The minimum sensible content for a small business:
- A list of covered devices — a specific number of workstations, servers, network devices. Not a vague „the company’s IT".
- Monitoring with a response — not merely collecting data, but a commitment that somebody acts on a critical state (a failed backup, a disk filling up, a server outage).
- Backups including periodic restore tests — with the contract stating how often the test is performed.
- Updates — for workstations, servers and network devices, at a defined frequency.
- Response times (SLA) — by when work starts on a critical outage and by when on a routine request, and whether the guarantee applies only during business hours or outside them too.
- A helpdesk with a defined volume — either unlimited routine requests, or a defined block of hours with a clear rate for anything beyond it.
It matters just as much to know what a retainer usually doesn’t include: projects (replacing a server, an office move, a new Wi-Fi network, a cloud migration), hardware purchases, third-party licences (Microsoft 365, antivirus, backup software — unless explicitly included) and the aftermath of work the company does itself or orders elsewhere. A reputable provider will spell these boundaries out unprompted; if the quote is silent on them, ask.
Scope is precisely why two „IT support" quotes can differ several times over and both be honest. A retainer that includes licences, an unlimited helpdesk and a guaranteed response within hours is a different service from one that covers a monthly backup check and nothing else.
When hourly billing or „an IT guy on the phone" is enough
An hourly rate with no commitment is a legitimate model — for a certain type of company. Do you recognise yourself here?
- You have up to five, maybe ten computers and no server of your own.
- E-mail, documents and accounting all run in the cloud with major providers.
- If one computer is down for a day it’s annoying, but it doesn’t stop the business.
- You don’t hold data whose breach would mean an existential or legal problem.
If so, a retainer is probably an unnecessary luxury and hourly billing makes more sense — ideally combined with a one-off setup of the basics: automated backups with an occasional check, updates, multi-factor authentication and a written list of access credentials.
Hourly billing does carry three hidden costs that the rate doesn’t reflect. First, nobody is watching anything — you’ll find out about a faulty disk in the NAS when the second one fails too; what recovery costs then is covered in the article on how much data recovery from a drive costs. Second, you have no availability guarantee — a freelancer on an hourly rate has other clients too, and during an outage you may be waiting days. Third, the documentation tends to live in one person’s head — and when that person moves on, their successor inherits a network with no passwords and no map.
„The IT guy on the phone" — a friend, a neighbour, a former colleague — is a category of its own. For a household, that’s fine. For a business it’s fair to admit that this is a relationship with no contract, no accountability and no cover when they’re unavailable. That needn’t be a problem until the data the company runs on is at stake.
What makes up the price
Our numbers, so you have a starting point
An article about price without a single figure is useless, so here are ours — all excluding VAT and all published openly in our IT for business price list:
| Item | Price |
|---|---|
| A typical company with 10–30 employees | CZK 8,000–18,000 / month for a full retainer within the agreed SLA |
| Technician’s work — contract customer | CZK 1,000 / h |
| Technician’s work — no contract | CZK 1,300–1,700 / h |
| Minimum charge for any work | CZK 1,300 |
| Outside business hours (16:00–10:00, weekends, public holidays) | +50 % |
| Service call-out — contract / no contract | CZK 800 / CZK 1,400 |
| Emergency call-out within 2 hours — contract / no contract | CZK 1,300 / CZK 2,600 |
Those two hourly-rate lines show the whole logic of a retainer: the gap between CZK 1,000 and CZK 1,700 an hour is 70 %, and for an emergency call-out it’s double. A contract doesn’t pay off because of the discount on the hourly rate, but because the retainer includes the work that would otherwise be billed by the hour — monitoring, updates and backup checks, in other words the work that prevents outages in the first place.
Whether it’s a retainer or hourly billing, the price is made up of several specific items. Once you know them, you can compare quotes on substance:
- The number and type of devices. Workstations, laptops, servers, network devices. A server is a more expensive item than a workstation — it carries more roles, more risk and more work around updates and backups.
- Server roles. A file server is a different discipline from a server running accounting, ERP or terminal sessions, where an outage stops the entire company.
- Response times. A guarantee of „we’ll start work by the end of the next business day„ costs differently from „within two hours, any time". Every reduction means the provider has to keep staff on standby.
- Hours of coverage. Business days only, or evenings and weekends too? Manufacturers and e-shops often need the latter, offices usually don’t.
- Licences included vs. billed separately. Antivirus/EDR, backup software, monitoring, Microsoft 365 — some providers bundle them into the retainer, others invoice them separately. Both are fine, but when comparing quotes you have to add them up.
- On-site vs. remote. Most routine support is done remotely these days. Regular physical visits or travel to an outage push the price up — and so does the distance from the provider’s base.
- The state of the IT you’re taking over. Technical debt always feeds into the price: out-of-date systems, missing documentation, backups „set up somehow" years ago. That’s why some providers start with an entry audit and only then set the retainer.
Billing models vary: a monthly amount per workstation and per server, an amount per user, a flat fee for the whole company, or a prepaid block of hours. None is objectively best — what matters is that you understand what happens when an employee or a server is added, and what work beyond the agreed scope costs. I’m deliberately not putting specific figures here: the market is wide, and a figure without a defined scope is worthless information. How we calculate support and what it includes can be found in our IT support price list for business — even if you’re getting quotes elsewhere, it works as a benchmark for what a quote should contain.
What to watch for in the contract
An IT support contract is easy reading while everything is fine. These points decide matters when it isn’t — or when you part ways:
- An SLA that distinguishes response from resolution. „Four-hour response time" means somebody starts work within four hours — not that it will be finished. Insist on defined priorities (critical outage vs. routine request) and a response time for each; for critical states, a target time to restore service as well.
- Who owns the passwords and documentation. The most important paragraph in the whole contract. Administrator passwords, access to the domain, licences and cloud accounts, and the documentation belong to the company, not the provider. Insist on receiving up-to-date handover documentation on an ongoing basis, not only when the contract ends. A domain and hosting registered in the IT guy’s name are a classic trap.
- Notice period and exit. A reasonable notice period protects both sides, but the contract must state what is handed over on termination, in what format and by when — and that cooperation during handover isn’t billed separately as „work outside the contract".
- What happens to the backups. If the backups sit in the provider’s storage, it must be clear how you get them and how long they exist after the contract ends.
- Whose name the licences are in. The Microsoft 365 tenant, antivirus consoles, monitoring — the accounts should be held by the company, with the provider given delegated access. Otherwise the licences walk out of the door with the provider.
- Reporting. A monthly summary: what was dealt with, the state of the backups, updates carried out, recommendations. Without it you don’t know what you’re paying for — and an honest provider doesn’t mind reporting, because it makes their work visible.
- Liability and insurance. Ask whether the provider carries professional indemnity insurance. The answer will tell you a lot about how seriously they take their own mistakes.
Three typical real-world scenarios
An office of six, everything in the cloud. Accounting online, documents and mail in Microsoft 365, no server. Here hourly billing plus a one-off setup of the basics makes sense: backups of cloud data, multi-factor authentication, update management. On a retainer they’d be paying for capacity they never use.
Fifteen people, a server running ERP and the warehouse. Orders, production and invoicing all go through one system; when the server stops, the company stops. This is a textbook candidate for a retainer with monitoring, a guaranteed response during business hours, controlled updates and a tested backup. Here the cost of the retainer is measured against an hour of downtime, not against a technician’s hourly rate.
A company being taken over from a freelancer. There’s no documentation, the passwords are with „Mr Novák, who used to do it", and there are no guarantees. Starting straight in with a blind retainer is a mistake here — the first step is mapping the current state, ideally as a network and infrastructure audit, and only against a real picture can the scope and price of support be set fairly.
How to decide
Ask yourself two questions. What does a day without IT cost us? If the answer involves halted invoicing, halted production or lost orders, you need a retainer with an SLA — hourly billing with no guarantee is, in that situation, just a cheaper ticket to a more expensive outage. Who finds out when something is going wrong? If the answer is „nobody, until it falls over", you don’t have IT support, you have a repair service. That can be fine — but it should be a decision, not an accident.
And when choosing a provider, ask for three things in writing: the exact scope, the response times, and confirmation that the passwords and documentation belong to you. Anyone who squirms at those three points has just told you everything you need to know. If you’re weighing up what support would look like at your company, our range of services for businesses is set out on the IT for business page.
Frequently asked questions
Is a retainer worth it even for a company with five computers?
Usually only if the business runs on those five computers — a medical practice, a law firm or an e-shop, for example. What decides it is the cost of downtime and the sensitivity of the data, not the number of workstations.
What does response time in an SLA mean?
By when the provider starts work on the problem, not by when they resolve it. Ask about both: the response and the target time to restore service for critical outages, and whether the guarantee also applies outside business hours.
Is managing a server more expensive than managing a workstation?
Yes, usually considerably. A server carries backups, updates with planned downtime, monitoring and risks a workstation doesn’t have. That’s why quotes bill it as a separate item — and why a quote that doesn’t distinguish between a workstation and a server is suspect.
What exactly should I have handed over by my current IT provider?
Administrator passwords, access to the domain, DNS, hosting and cloud accounts, licence information, network device configurations, backup documentation and a list of contracts with providers. Ideally on an ongoing basis, not only when you part ways.
Can I combine a retainer with hourly billing?
Yes, and it’s common: the retainer covers monitoring, backups, updates and the helpdesk, while projects and larger changes are done to order at an hourly or fixed price. What matters is that the contract clearly states what falls where.