You can buy IT cheaply. That's not the debate.

You can absolutely buy IT support for very little money.

There are providers who'll manage your IT for £30-£40 per user or device each month, sometimes with no minimum fee at all. On paper, that can look like a sensible - and attractive - decision, especially if things mostly work.

The problem isn't whether cheap IT exists.

It's what has to be true for that price to work.

Sometimes the cost is pushed elsewhere - slower responses, more chargeable work, or improvement projects that only happen after something breaks.

But just as often, something simpler is happening: the work just isn't being done.

At that level of pricing, there's rarely time for proper documentation, meaningful review of the environment, or deliberate improvement. Knowledge lives in old tickets, not in something anyone actively maintains. Standards drift. Settings vary. Nothing is broken enough to escalate, but nothing is being brought back into line either.

That's how businesses end up with IT that technically works, but quietly accumulates friction year after year.

Pricing models shape behaviour (even if no one says so)

One of the most useful questions a business owner can ask isn't "how much does this cost?"

It's: "What behaviour does this pricing model encourage?"

The way an IT service is priced quietly dictates where time and attention go. If a provider is paid mainly to respond to tickets, the focus will be on closing tickets. If they're paid mainly to deploy tools, the focus will be on tools.

Neither of those is wrong.

But neither naturally leads to calm, steadily improving IT unless something else exists alongside them.

 

Sidebar: "Proactive monitoring" is a bit of a myth

You can monitor systems.
You can be alerted quickly.

But the work itself is always reactive.

Something happens, an alert fires, and someone responds.

The genuinely proactive part comes after that - when someone steps back and asks "why did this happen, and how do we stop it happening again elsewhere?"

That second step is the one that disappears in low-cost models, because it isn't tied to a ticket or a billable event. It requires time, context, and ownership of the whole system - not just the alert.

How we think about pricing

We don't start with a per-seat price.

We start by looking at the environment and asking a more practical question:
what does it take to run this properly, month after month, without cutting corners?

That means considering how many people rely on the systems day-to-day, how many devices need to be kept consistent and secure, whether there are servers, firewalls, or multiple locations adding complexity, and what level of security and governance is appropriate for the business.

From there, we arrive at one monthly managed services figure.

Internally, we can absolutely show how changes affect that number. If you add a user, we can give you a sensible indication of what that means for the monthly cost.

What we won't do is pretend it's always a flat number. Adding someone into a simple environment is very different from adding someone into something more complex, and being honest about that upfront avoids awkward conversations later.

Continuous alignment (what the monthly fee actually supports)

One thing that's often misunderstood about managed IT is what the monthly fee actually pays for.

That fee supports ongoing management of the environment as it exists today - keeping it running, keeping it secure, and continuously reviewing whether it still makes sense for how the business operates.

A key part of that is regular alignment reviews.

These reviews are where we step back from day-to-day support and look at the environment as a whole: where it's drifting away from best practice, where risk is increasing, and where the setup no longer matches how the business works.

Importantly, those reviews don't automatically mean change.

They create a shared understanding of what "good" looks like, where things stand today, and what the trade-offs actually are.

Why the monthly fee doesn't mean "fix everything"

Paying a monthly managed services fee does not mean your environment is brought into perfect alignment immediately.

Improvement work - upgrading systems, re-architecting setups, replacing legacy approaches - is deliberate work. It's usually best handled as projects, agreed and prioritised with the business based on risk appetite, budget, and timing.

Separating that work keeps pricing honest.

The monthly fee supports the ongoing operation and oversight of the environment. Projects move it closer to the standards you agree are appropriate.

Once those improvements are made, the monthly fee generally doesn't jump again - it continues to support the new baseline.

Why we bundle what's essential

If a tool or system is genuinely needed to keep devices secure, enforce consistent standards, reduce repeat issues, or allow the environment to be managed coherently, it's included as part of the service.

We don't believe in "optional basics."

If something is necessary to do the job properly, it shouldn't be debated line by line every month. Bundling those essentials removes ambiguity and avoids the slow erosion that happens when important work is quietly deferred because it's viewed as "extra."

Sometimes, we may trial a tool that we feel could become part of our baseline in the future. For those, we'll have an up front conversation about the cost implications and whether you want to go ahead with it. If we find the tool becomes beneficial across all standard baselines, we'll fold it into our core stack, which might affect the pricing.

What we don't bundle - and why that's intentional

Microsoft licensing is a good example.

We don't bundle Microsoft 365 licenses into the managed services fee. Many businesses already own licences, some prefer to buy direct, and requirements vary wildly depending on use case.

That's without having to have the awkward mid-year conversations when the licensing cost has change dramatically, forcing us to increase our managed services fee mid-contract if it was bundled.

Our responsibility is to advise what licensing is appropriate, configure it securely, and support it day-to-day.

Separating the license from the service keeps the focus where it should be: on outcomes, not resale.

The uncomfortable part: minimum monthly fees

Every managed IT relationship has a baseline cost.

Even a small environment requires documentation, standards oversight, security review, escalation paths, training, and the internal systems needed to support it properly. That work exists whether you have ten users or fifty.

For us, that baseline is £2,500 per month.

That figure isn't arbitrary. It's the point at which we can confidently say we're able to run the relationship properly - not just respond to issues as they come up, but maintain documentation, carry out regular alignment reviews, invest in staff training, and keep enough slack in the system to improve things rather than constantly firefight.

From one business owner to another, it's worth pausing on that for a moment.

If an IT provider doesn't cover the base cost of running the relationship, how are they paying their staff, retaining experienced engineers, investing in better processes, and keeping their own business healthy? Something has to absorb that gap - and it's usually either the quality of the service or the people delivering it.

Businesses that under-price their services don't just cut corners for clients. Over time, they cut corners internally too. That's when staff turnover increases, knowledge walks out of the door, and the service becomes fragile - even if it looks fine on the surface.

A minimum fee isn't about exclusion.

It's about acknowledging the reality of running a stable service business, and being honest about what it takes to do the job well.

 

What a minimum fee actually protects you from

A minimum fee doesn't mean "you're paying for things you don't need."

It means:

• documentation isn't an afterthought
• alignment reviews actually happen
• staff aren't permanently stretched
• and improvement work isn't endlessly deferred

If there's no minimum at all, ask what work isn't happening - or who is absorbing the cost.

IT services don't become sustainable by accident.

So what about "£30 per seat" IT?

Yes, it exists.

The more useful question isn't "can I get IT at that price?"
It's "what has to be missing for that price to work?"

If you're comparing providers, the questions that matter the most are:

• Where does documentation live - and who owns it?
• How are standards enforced across devices?
• What happens when the same issue keeps coming back?
• How much time is spent improving the environment, not just reacting to it?

Clear answers here matter far more than the headline number.

A calmer way to think about value

Good IT rarely feels dramatic.

When it's working well, it's mostly invisible. Fewer interruptions. Fewer workarounds. Fewer "we'll deal with that later" conversations that never quite get dealt with.

Pricing that supports that kind of outcome isn't about being the cheapest. It's about being honest, sustainable, and aligned with how businesses actually operate.

That's the approach we've chosen - not because it sounds good, but because it's the only one I've seen work consistently over the long term.

Closing

If there's one thing I hope this page does, it's help you think more clearly about what you're actually buying when you pay for IT.

Pricing isn't just a number. It's a signal. It tells you what work is valued, what work is optional, and what work probably isn't happening at all.

Whether you work with us or someone else, understanding how a provider thinks about alignment, improvement, and sustainability will put you in a much stronger position to choose well - and to avoid models that look good on paper but quietly create friction over time.

If you'd like to talk through your current set up - not to be sold to, but to understand whether it's structured to stay calm as your business grows - you're welcome to get in touch.

Clarity first. Decisions second.