Ask two providers of managed IT services to quote for the same 60-user business and you will get two very different shapes of number. One is an hourly rate with no commitment. The other is a fixed monthly fee covering work nobody has needed yet.
The break-fix vs managed IT cost question keeps getting answered badly because it is almost always answered over twelve months. Break-fix bills you for repairs after something has already failed. Managed IT charges a predictable subscription to stop most of those failures happening at all. The two models put money in different places, on different timelines, so a single year of invoices tells you very little about which one is genuinely cheaper.
This guide runs the break-fix vs managed IT cost comparison across a full five years: what each model bills in year one, where the two lines cross, what the invoices never show, and how to rebuild the same model with your own numbers before you sign anything.
Table of contents
- What Break-Fix and Managed IT Actually Buy
- Why Five Years Is the Right Window for a Break-Fix vs Managed IT Cost Comparison
- Year One: Where Break-Fix Genuinely Looks Cheaper
- Years Two and Three: Where the Lines Cross
- Years Four and Five: Compounding Costs
- The Hidden Costs a Break-Fix Invoice Never Shows
- Downtime: The Largest Line in Any Break-Fix vs Managed IT Cost Model
- Security, Compliance and Insurance Across Five Years
- A Worked Five-Year Example: A 60-User Business
- How to Model Break-Fix vs Managed IT Cost With Your Own Numbers
- Making the Decision Over a Five-Year Horizon
What Break-Fix and Managed IT Actually Buy
Before any figures are useful, it helps to be precise about what each contract is for. A break-fix vs managed IT cost comparison is not two prices for the same thing. These are two different products that happen to be sold by the same kind of company.
Break-fix buys repairs, not readiness
Under break-fix you buy engineer time by the hour, after an incident. There is no retainer, no monitoring, and no obligation on either side between jobs. A server dies, you call, someone attends, you get an invoice. It is honest, transparent, and on the break-fix vs managed IT cost ledger a quiet month genuinely costs nothing.
Managed IT buys prevention and availability
A managed agreement buys a defined outcome instead: systems patched, backups verified, alerts answered, a response target in writing. Most of the work is invisible because it happens before anything visibly breaks. You are paying for the failures that never reach your staff, which is exactly why the managed side of a break-fix vs managed IT cost comparison is so hard to see on a quiet month.
The unit you are purchasing is different
This is why a straight rate-versus-rate view distorts the break-fix vs managed IT cost picture. One model prices an input — an engineer hour. The other prices an outcome — a working estate. Comparing £95 an hour against £65 per user per month is comparing a cost of repair against a cost of readiness, and the two are not interchangeable.
Why most comparisons start in the wrong place
Buyers usually open a break-fix vs managed IT cost review by pulling last year’s spend and holding it next to a proposed monthly fee. That comparison is not wrong so much as incomplete: it captures what you paid, but not what the model cost you in time, disruption and deferred work. Those omissions are where the five-year gap comes from.
Why Five Years Is the Right Window for a Break-Fix vs Managed IT Cost Comparison
One year is a marketing window. Five years is roughly one full cycle of the assets and agreements that IT actually runs on, which makes it the shortest honest horizon for this decision.
Twelve months flatters the reactive model
In any given year a reasonably healthy estate will not have a catastrophe. Priced over that year, reactive support looks like a bargain, because you are effectively comparing a full insurance premium against a period in which you did not claim. Insurance is never cheap in the years you do not use it, and a one-year break-fix vs managed IT cost review is exactly that comparison.
Hardware and licensing run on multi-year cycles
Workstations run three to five years. Servers and firewalls run four to six. Licence agreements and connectivity contracts commonly run three. A five-year window contains at least one full refresh of nearly everything you own, so it captures the replacement decisions that a one-year break-fix vs managed IT cost snapshot conveniently excludes.
Neglect compounds slowly, then quickly
Unpatched systems, expired warranties, undocumented changes and unverified backups do not fail on a schedule. They accumulate quietly for two or three years and then produce a cluster of expensive incidents. A shorter window measures the accumulation phase and misses the bill.
What a five-year view makes visible
Stretch the timeline and three things appear that a single year hides: the true frequency of incidents, the cost of the replacements you kept postponing, and the compounding hours your own staff spent absorbing problems. Every serious break-fix vs managed IT cost model has to price all three.
Year One: Where Break-Fix Genuinely Looks Cheaper
It is worth saying plainly, because most vendor content will not: in year one, the reactive model usually is cheaper, and pretending otherwise damages the credibility of the whole break-fix vs managed IT cost argument.
The invoice pattern in a quiet first year
A stable 60-user business on break-fix might use ten to twenty engineer hours a month across support calls, small changes and the occasional failure. At typical UK rates of £75 to £125 an hour, that is somewhere between £9,000 and £30,000 a year, arriving unevenly and always after the fact. That is the opening entry in the break-fix vs managed IT cost ledger.
What the managed IT baseline costs
Fully managed support in the UK commonly runs £45 to £110 per user per month depending on scope, with security tooling, backup and out-of-hours cover pushing towards the upper end. For sixty users at £65, that is £46,800 a year, invoiced in identical monthly instalments whether the month was quiet or brutal. It is the flat side of the break-fix vs managed IT cost comparison, and it does not move.
Onboarding and first-quarter remediation
Managed agreements also front-load work. The first ninety days typically include documenting the estate, deploying monitoring agents, fixing years of accumulated configuration drift and standing up backup testing. Some providers absorb this, some charge a one-off onboarding fee. Either way, year one carries costs that years two to five do not.
The honest year-one verdict
On paper, break-fix wins the first year in most stable environments, often by £15,000 to £25,000 for a business this size. Any break-fix vs managed IT cost comparison that hides this is selling rather than advising. The point is not that year one is close — it is that year one is not the whole question.
Years Two and Three: Where the Lines Cross
The middle years are where the two models stop tracking each other. Nothing dramatic needs to happen; the estate simply gets older and the reactive hours quietly climb.
Ageing estates consume more hours
Hardware entering years three and four fails more often, and software that has not been maintained needs more intervention per incident. The same business that used twelve hours a month in year one commonly uses twenty to thirty by year three, which turns a £14,000 reactive spend into a £30,000 one without a single disaster, and closes most of the break-fix vs managed IT cost gap on its own.
Rate rises, minimum charges and out-of-hours premiums
Reactive work also carries structural premiums. Most break-fix agreements bill minimum call-out blocks, charge 1.5 to 2 times the standard rate outside business hours, and raise rates annually. Because failures do not respect office hours, a meaningful share of reactive hours land at the premium rate, which quietly inflates the break-fix vs managed IT cost gap.
The cost of institutional forgetting
Reactive engineers arrive without context. Every visit spends time rediscovering how your network is put together, where the backups run and why that one application needs a legacy protocol. You pay for that rediscovery repeatedly, at full rate, and it never accumulates into documentation you own — a standing charge on the reactive side of the break-fix vs managed IT cost ledger.
Where the crossover usually happens
For most SME estates the two lines meet somewhere in year two or year three. After that point the break-fix vs managed IT cost comparison inverts, and the gap widens rather than stabilises, because the causes of the extra hours are themselves untreated.
Years Four and Five: Compounding Costs
By the back half of the window, the difference is no longer about support hours at all. It is about the condition of the estate that each model has produced.
Deferred replacement becomes emergency replacement
Reactive support has no natural mechanism for planned refresh, so kit tends to run until it dies. Replacing a failed server under pressure costs more than replacing a working one on schedule: expedited hardware, out-of-hours migration, data recovery and lost days. That premium is a real line in the break-fix vs managed IT cost model, and it lands almost entirely in years four and five.
Technical debt in the network and identity layer
Years of undocumented fixes leave residue — firewall rules nobody dares remove, service accounts with permanent passwords, three overlapping remote access methods. Untangling that later is project work billed at project rates, and it is work a managed agreement would have prevented by never allowing the sprawl.
Staff time absorbed by workarounds
When support is transactional, people stop reporting small problems and start working around them. The finance manager who reboots a machine daily, the team that keeps a spreadsheet because the system is slow — none of it appears on an invoice, all of it is paid for in salary, and none of it reaches a naive break-fix vs managed IT cost comparison.
What the five-year totals tend to show
Add the reactive escalation, the premium replacements and the remediation projects, and the five-year break-fix vs managed IT cost totals usually land far closer than the year-one figures suggest — frequently with the managed column ahead once downtime and internal time are priced at all.
The largest weakness of a reactive model is not its hourly rate. It is that its invoice is a very incomplete record of what the model actually cost you, which is why any credible break-fix vs managed IT cost exercise has to go looking outside the invoices.
Internal time spent triaging and chasing
Someone in your business decides whether an issue is worth a call, describes the problem, arranges access, chases progress and confirms the fix. On a reactive model that co-ordination role usually falls to an office manager or a capable colleague, and two to four hours a week of it is a five-figure annual cost in salary alone.
Procurement and vendor management overhead
Reactive estates accumulate suppliers: one for the phones, another for the firewall, a third for the line, a fourth for the copier. Someone has to own renewals, chase faults across boundaries and referee blame. Consolidated vendor management is a standard inclusion in managed agreements and a standing internal cost without one.
Licence sprawl and duplicated tooling
Without a maintained inventory, businesses routinely pay for licences nobody uses, duplicate backup products bought in two different panics, and security tools that overlap. Audits of this kind regularly recover five to fifteen per cent of software spend — money that sits invisibly on the wrong side of the break-fix vs managed IT cost ledger.
Data loss, rebuild time and lost work
Backups that are configured but never tested are the most common expensive discovery in reactive environments. The cost of a partial restore is not the engineer’s hours; it is the days of re-entered work, the client deliverables missed and the confidence lost internally.
The cost of not knowing what you own
Reactive support produces no asset register, no warranty schedule and no dependency map. Every budget request becomes guesswork, every project scoping exercise starts from zero, and every insurance or compliance questionnaire needs a fresh investigation. Ignorance of your own estate has an ongoing price even in a year where nothing breaks.
Downtime: The Largest Line in Any Break-Fix vs Managed IT Cost Model
Downtime is the one cost that dwarfs everything else and the one most businesses leave out entirely, usually because they have no agreed method for pricing it.
How to put a defensible price on an hour
The workable method is simple: take total annual payroll for the affected group, add employer costs and overhead, divide by working hours, then multiply by a productivity loss factor between 0.5 and 1.0. Sixty staff at an average fully loaded £42,000 gives roughly £1,300 an hour at full stoppage, and half that for a partial outage. Fix that rate before you build the break-fix vs managed IT cost model, not after.
Response time is not resolution time
Break-fix has no contractual response obligation at all — you join a queue behind clients who pay retainers. Managed agreements commit to response targets and, in better contracts, to resolution targets with credits attached. A four-hour difference in response, six times a year, is roughly £30,000 of exposure in this example, and it belongs in the break-fix vs managed IT cost calculation.
Frequency hurts more than severity
One catastrophic day is memorable, but ten two-hour disruptions cost more and damage delivery habits further. Reactive models are structurally worse at frequency because the small recurring faults that cause it are precisely the ones nobody bothers to raise a paid call for.
What proactive maintenance actually removes
Patch automation, disk and memory alerting, backup verification, certificate expiry tracking and capacity monitoring remove a specific and well-understood category of outage. That is the mechanism by which managed support earns back its premium, and it is the single largest swing factor in the break-fix vs managed IT cost outcome.
Security, Compliance and Insurance Across Five Years
Security is where a five-year break-fix vs managed IT cost comparison stops being an efficiency question and becomes a risk question, because the downside is no longer proportional to the monthly fee.
Patch latency is a cost, not a chore
Under a reactive agreement, patching is somebody’s spare-time task and typically runs weeks or months behind release. Most successful attacks exploit vulnerabilities that were patched long before the breach. Sustained cybersecurity hygiene is a scheduled, monitored activity, and scheduling is exactly what a purely reactive model does not provide.
Cyber insurance now prices your controls
Insurers have moved from asking whether you have cover to asking what controls you operate: multi-factor authentication, endpoint detection, tested backups, patch cadence, privileged access management. Weak answers mean higher premiums, higher excesses or refused claims — a direct, quantifiable cost of the reactive model that never appears on any support invoice but belongs firmly in the break-fix vs managed IT cost total.
Compliance evidence has an hourly cost
Client security questionnaires, Cyber Essentials, ISO 27001 and data protection audits all require evidence rather than assurances. Producing that evidence from an undocumented estate takes days of senior time per exercise, and it recurs annually, which is why the compliance line matters in a break-fix vs managed IT cost model for any business that sells to larger organisations.
The tail risk nobody puts in the model
A serious ransomware event in a 60-user business routinely costs six figures once recovery, downtime, legal advice, notification and lost trade are counted. You cannot put that number directly into a break-fix vs managed IT cost spreadsheet, but you can weight it by likelihood — and the likelihood differs materially between an estate that is monitored and one that is not.
A Worked Five-Year Example: A 60-User Business
Numbers make the argument concrete. The figures below are illustrative UK market ranges rather than a survey, and the assumptions are stated so you can substitute your own and reach a different answer honestly.
The assumptions behind the model
Sixty users, two servers, a firewall, cloud email and productivity, a line-of-business application, and a mixed laptop estate replaced on a four-year cycle. Break-fix at £95 an hour with a two-hour minimum call-out and time-and-a-half outside hours. Managed support at £65 per user per month, all-inclusive, with onboarding waived over a three-year term.
The break-fix column
Support hours run twelve a month in year one and climb to roughly thirty by year five, giving about £150,000 of engineer time across the period. Add £45,000 of emergency and unplanned replacement, £20,000 of remediation projects, and internal co-ordination at three hours a week valued at £35 an hour, or £27,000. Running total: roughly £242,000 before downtime.
The managed IT column
Sixty users at £65 per month is £46,800 a year, or £234,000 across five years, with modest uplifts offset here by the waived onboarding. Planned replacement over the same period costs about £38,000 but arrives on schedule and at standard rates. Internal co-ordination drops to roughly an hour a week, or £9,000. Running total: roughly £281,000.
Where the two columns diverge
At that point break-fix is £39,000 ahead, and this is where most break-fix vs managed IT cost comparisons stop. Now add downtime: at forty-eight disrupted hours a year on reactive support against twelve on managed, valued at £650 an hour, the reactive column takes on £156,000 and the managed column £39,000. The five-year totals become roughly £398,000 against £320,000.
Reading the result honestly
That £78,000 swing is entirely a function of the downtime rate and incident frequency you assume. Halve both and the models finish within a few thousand pounds of each other. This is the real lesson of any break-fix vs managed IT cost exercise: the answer is decided by the assumptions, so the assumptions are what deserve the argument.
How to Model Break-Fix vs Managed IT Cost With Your Own Numbers
You do not need a consultant to run this. You need four inputs, an afternoon, and a willingness to include the lines that are uncomfortable to look at.
Start with three years of actual invoices
Pull every IT-related invoice for the last three years — support, hardware, licences, connectivity, one-off projects and emergency call-outs. Most businesses find the total is thirty to fifty per cent higher than the figure they carry in their heads, because the spend is scattered across suppliers and cost codes.
Price your internal hours properly
Estimate the hours your own people spend on IT co-ordination, workarounds and chasing, then value them at fully loaded cost rather than salary. This single line moves the break-fix vs managed IT cost result more often than any other, and it is the one buyers most reliably leave at zero.
Add downtime at a rate you can defend
Use the payroll method above, agree the productivity factor with your finance lead, and write the assumption down. A defensible £600 an hour that everyone has signed off is far more useful than a precise-looking number that the board rejects the moment it appears on a slide.
Include the replacement schedule you keep postponing
List every asset with its age and expected replacement year, then place the cost in the year it is actually due. Reactive estates habitually push these dates back until failure forces them, so model the same kit twice: once replaced on plan, once replaced in an emergency at a thirty per cent premium.
Compare against scope, not against price
Finally, line up what each proposal covers rather than what it charges. A cheaper managed quote that excludes out-of-hours cover, security tooling or third-party vendor management is not cheaper — it has simply moved those costs back onto you, which makes the break-fix vs managed IT cost comparison meaningless unless the scopes are matched first.
Making the Decision Over a Five-Year Horizon
The output of this exercise should not be a single winning number. It should be a clear view of which risks you are choosing to carry yourself and what you are paying for the privilege.
When break-fix still makes sense
Very small teams, newly purchased estates still under warranty, businesses with genuine in-house technical depth, and organisations whose operations tolerate a day offline can all rationally choose reactive support. If an outage is an inconvenience rather than a revenue event, the break-fix vs managed IT cost maths may genuinely favour paying only when something breaks.
When managed IT pays for itself
If downtime stops billing, if you hold client data under contractual security obligations, if you have no internal IT capability, or if you are growing past forty or fifty users, the break-fix vs managed IT cost model tends to resolve in favour of the managed column well before year five — usually on downtime and insurance alone.
The hybrid option most buyers overlook
Between the two sits co-managed support: you keep an internal person or team and buy monitoring, out-of-hours cover, security tooling and escalation from a provider. It often produces a better five-year number than either pure model, particularly for businesses that have already hired but are exposed whenever that individual is unavailable. Run it as a third column in your break-fix vs managed IT cost model rather than as an afterthought.
The decision is about risk, not just price
Read at five years rather than twelve months, the break-fix vs managed IT cost question is really a question about who absorbs variance. Reactive support keeps your average cost lower and your worst case unbounded. Managed support raises the average slightly and caps the worst case. Which of those you should buy depends on how much a bad month would actually cost your business.
