A single point of failure is any part of your business that, if it stops working, brings everything else to a standstill. In a large corporation, these are usually identified by expensive consultants and mitigated with redundant systems. In a UK SME, they are more often found in a cupboard under the stairs, or inside the head of a single employee. Most small businesses operate on the assumption that as long as the lights are on and the emails are sending, the system is fine. This works until the day it doesn't.
When we talk about IT resilience, we are simply talking about how many things can go wrong before you have to send your staff home for the day. Identifying these risks does not always require a massive budget, but it does require a bit of honesty about what keeps the lights on. It is about moving from a state of 'hoping it works' to 'knowing what happens when it breaks'.
What a single point of failure actually means
A single point of failure (SPOF) is a technical or operational bottleneck. If you have one broadband line and it gets cut by a digger in the street, you have a SPOF. If you have one server that hosts your files and its power supply dies, you have a SPOF. If only one person in the company knows the password to the domain registrar, you have a SPOF.
In technical terms, we look for redundancy. Redundancy is the inclusion of extra components which are not strictly necessary to functioning, but which take over if the primary component fails. For a small business, redundancy is often seen as an unnecessary cost until the moment the primary system fails. At that point, the cost of the redundant system usually looks like a bargain compared to the cost of 20 people sitting idle for two days.
The 'Knowledge Silo' and the Person SPOF
The most common single point of failure in a UK SME is not a piece of hardware. It is a person. This is often the 'IT guy' who has been with the company since it started, or a business owner who insists on holding all the keys.
A pattern we see on most tenants we take on is the 'everything' account, a single global administrator login used by several different people, including external contractors and the business owner, with no record of who has accessed what or when. If that one account is compromised, or if the person who manages it leaves on bad terms, the business is effectively locked out of its own digital estate.
We also see the 'Knowledge Silo'. This happens when one person manages a specific, critical process, such as the monthly payroll run or the configuration of a niche piece of industry software. If that person is ill or leaves, nobody else knows how to keep the process moving. This is an IT risk because it usually involves undocumented workarounds and local files that are not backed up. To fix this, you do not necessarily need more staff, but you do need documentation. Every critical IT process should be written down in a way that a competent stranger could follow it.
Connectivity and the physical bottleneck
Most modern businesses are entirely dependent on the cloud. If the internet goes down, work stops. Yet, many firms still rely on a single, consumer-grade broadband connection. This is a classic single point of failure.
It is quite common to find a business with a £5,000 firewall connected to a £30-a-month home broadband line. If that line fails, the business is offline. A managed IT support provider will usually suggest a secondary connection. This does not have to be an identical, expensive leased line. It could be a cheaper FTTP (Fibre to the Premises) line from a different provider, or even a 4G/5G failover router that kicks in automatically when the main line drops.
The goal is not necessarily to have 100% speed at all times, but to ensure that critical functions, like processing payments or sending emails, can continue while the main line is repaired. Without this, you are at the mercy of your provider's service level agreement, which for basic broadband can be 'best endeavours' rather than a guaranteed fix time.
The legacy server in the corner
While many businesses have moved to Microsoft 365 or Google Workspace, many still keep a physical server in the office for specific tasks. This might be for an old version of Sage, a bespoke database, or simply because 'that is where the files have always been'.
If that server is more than five years old, it is a ticking clock. Hardware fails. Hard drives wear out, and power supplies pop. If you have one server and no recent, tested backup, that server is a single point of failure that could end the business. We often find servers that are physically fine but are running operating systems, like Windows Server 2012, that no longer receive security patches. This makes them a single point of failure for your security; one unpatched vulnerability can lead to a ransomware attack that encrypts the whole network.
Replacing a server does not always mean buying a new box. Often, it means cloud migration and server decommissioning, moving those legacy functions into a more resilient cloud environment where the hardware is managed by someone else and redundancy is built-in.
The financial cost of a single failure
To understand why mitigating these risks matters, you have to model the cost of downtime. This is not just the cost of the repair; it is the cost of the silence.
Consider a hypothetical UK firm with 25 employees. If the average salary cost, including National Insurance and pension, is £25 per hour, the business is spending £625 an hour just on people. If a single point of failure (like a dead server or a cut internet line) takes the office offline for a full working day (7.5 hours), the direct cost in lost wages is £4,687.50. This does not include lost revenue, missed deadlines, or the reputational damage of not being able to answer the phone to clients.
When you look at it this way, spending £500 a year on a backup internet line or £2,000 on a proper Microsoft 365 backup solution is not a cost; it is an insurance policy. The goal of a well-run IT setup is to make emergencies rare and site visits unnecessary. If your IT provider is constantly on-site 'fighting fires', it is usually because they haven't helped you identify and remove these single points of failure.
Building an IT risk register
You do not need to fix everything at once. The first step is to create an IT risk register. This is a simple document that lists every critical part of your IT, what happens if it fails, and what the plan is to fix it.
- Identify the asset (e.g., The Office Broadband).
- Identify the failure (e.g., The line is cut).
- Estimate the impact (e.g., Total office downtime, 20 staff idle).
- Estimate the cost of downtime (e.g., £500 per hour).
- Identify the mitigation (e.g., Install a 4G failover router).
- Identify the cost of mitigation (e.g., £40 per month).
Once you have this list, you can make informed business decisions. You might decide that the risk of a server failure is too high and move to the cloud. Or, you might decide that the risk of a specific software vendor going bust is acceptable because you have a manual workaround. The point is that you are making a choice, rather than being surprised when the failure occurs.
The supply chain and documentation gap
Single points of failure often exist outside your office walls. If your business relies on a specific piece of software that is only supported by one small company, you have a supply chain SPOF. What happens if that company goes into administration?
Similarly, we often see businesses where the domain name, the very foundation of their email and website, is registered to the personal email address of a former employee or a long-gone web agency. If that domain expires and you cannot log in to renew it, your email stops. This can take days or even weeks to unpick.
We recommend a central, secure repository for all IT documentation and credentials. This should not be a spreadsheet on someone's desktop. It should be a secure, encrypted password manager with access controlled by the business, ensuring that even if your primary IT contact disappears, the business retains control of its assets.
How Black Sheep Support helps
We specialise in finding the things that are likely to break and fixing them before they do. Our approach is to remove the drama from IT support by building resilience into every client environment we manage. We don't just wait for you to call us with a problem; our RMM (Remote Monitoring and Management) tooling monitors your systems 24/7, raising alerts to our helpdesk during office hours (Monday to Thursday 08:45 to 17:00 and Friday 08:45 to 16:00).
If you are worried that your business is one broken wire away from a crisis
and we'll help you map out where your single points of failure are.
Not ready to talk yet? Run our free IT Health Check to assess your business risk and security posture: 30 to 60 minutes with one of our engineers on a Teams call, or 15 to 20 minutes on your own, with no commitment. We can also help with hardware, broadband, mobile and networking to ensure your physical infrastructure is as resilient as your software.
Single Points of Failure FAQ
What is the most common single point of failure?
In our experience, it is usually a person or a lack of documentation. Whether it is the owner holding all the passwords or a single staff member who knows how to run a critical piece of software, human-centric failure points are more common and harder to fix than technical ones.
Is the cloud a single point of failure?
While the cloud adds massive redundancy, it can be a SPOF if you do not have a backup. If you use Microsoft 365 and your data is deleted or corrupted, Microsoft is not responsible for restoring it. You need a third-party backup to ensure the cloud provider itself isn't a single point of failure.
How much does it cost to remove SPOFs?
It varies wildly. Adding a 4G failover for broadband might cost £30-£50 a month. Moving a legacy server to the cloud might have a larger upfront cost but removes the risk of hardware failure and ongoing maintenance. The cost should always be weighed against the hourly cost of your staff sitting idle.
Can I have a 100% fail-safe IT system?
No system is perfect, but you can get very close. The goal for most SMEs is not 'perfection' but 'recoverability'. You want to ensure that no single failure can stop your business for more than a few hours, rather than several days.
Want this handled for you? See Managed IT support.
Based in Brighton or Hove? We are too: see IT support in Brighton.
