What SLA does my business actually need?

Most guides about SLAs try to sell you the strongest one on the shelf. That isn't how a sensible buyer should think about it. The right service level agreement is the one that matches what an outage actually does to your business, and for some businesses that means a heavyweight leased-line guarantee, while for others it means a solid response-time commitment on a good business line. This guide is a decision framework. It walks you through judging downtime risk, reading the parts of an SLA that matter, and landing on a level you can justify.

The aim isn't to talk you into the most expensive option. It's to help you buy deliberately, so you don't overpay for assurance you'll never use, and you don't underbuy and discover the gap on the worst possible morning.

The right SLA depends on what downtime does to the business. If a fault would only be inconvenient, a lighter SLA may be fine. If lost connectivity stops trading, customer service, or revenue, you need a stronger SLA with faster response, clearer accountability, and a recovery target the business can live with.

What does an SLA actually cover on a business connection?

An SLA (service level agreement) is a contractual promise about the standard of service you'll receive. On a business connection it usually wraps three things together: an availability target (how much of the time the line is expected to be up), a response time (how quickly the provider commits to acknowledging and starting work on a fault), and a fix time (how quickly they aim to have you back working). Some SLAs add proactive monitoring, named contacts and compensation if the targets slip.

The word matters less than the detail behind it. Two providers can both say "SLA" and mean wildly different things. One might promise a four-hour fix backed by compensation. Another might just mean your fault joins a slightly faster queue than the home product. Before you compare prices, you have to compare what each SLA actually commits to, in writing, because that is what you're really buying.

How do I judge the SLA the business really needs?

Start with one question: what happens in the first hour the connection goes down? Not the worst case, the ordinary case. The honest answer tells you almost everything. If the team can carry on with cached files, mobile data and a bit of patience, your downtime risk is low. If the tills stop, the phones die, the bookings stop, or the warehouse can't dispatch, your downtime risk is high, and the SLA conversation gets serious.

Work through these in order. Each one nudges you up or down the scale:

• What does an hour of downtime cost? Put a rough figure on it: lost sales, idle staff, refunds, reputational damage. If an hour costs more than a month of a stronger SLA, the maths makes itself.
• How long could you survive on a fallback? A 4G or 5G backup buys time. If you have one and it covers your essentials, you can tolerate a slower fix time. If you have none, fix time becomes critical.
• Is the connection customer-facing or back-office? A line that runs card payments and live bookings needs more assurance than one that mostly syncs files overnight.
• How many people and processes depend on it? One person who can hotspot is a different risk from forty staff and a hosted phone system all on the same line.
• Are there hard external deadlines? Dispatch cut-offs, payroll runs and regulatory filings don't wait for a fault to clear. If you have them, you need a fix time you can trust.

Add the answers up. A low-risk office lands comfortably on a strong business broadband SLA. A high-risk operation, where downtime stops the money coming in, points toward leased-line-grade assurance. Most businesses sit somewhere in between, and the point of this exercise is to find where, rather than defaulting to either extreme.

What do uptime, response time, and MTTR mean in practice?

Three numbers do the heavy lifting in any SLA, and they answer three different questions. Get them straight and you can compare any two offers honestly.

• Uptime (availability) answers how often the line fails. A 99.5% target allows for a few hours of downtime across a year. A 99.9% target tightens that considerably. The percentage looks small on the page, so it helps to translate it into hours per year before you judge it.
• Response time answers how fast someone starts. It's the gap between you logging a fault and the provider acknowledging it and getting to work. A tight response time is worth a lot, because nothing else can happen until the clock on it stops.
• Fix time (MTTR) answers how long you stay broken. MTTR (mean time to repair) is the average time committed to restoring service once a fault is open. This is the number most buyers underweight and later regret.

Here is the trap. A line can have a flattering uptime figure and still hurt you, because uptime tells you how rarely it breaks, not how long you sit broken when it does. A business that trades on its connection should read uptime and MTTR together, and often weight MTTR higher. A short, predictable fix time is worth more on a bad day than a fraction of a percent on the availability figure.

When is a stronger SLA worth paying for?

A stronger SLA earns its cost when the price of downtime clearly exceeds the price of the assurance. That sounds obvious, but it's the test most buyers skip. They either grab the cheapest line and gamble, or pay for a guarantee far beyond anything their day actually demands. Neither is buying deliberately.

Lean toward a stronger SLA when more than one of these is true for you:

• An outage stops you taking money, not just slows you down.
• You have no usable fallback, so a fault means a hard stop.
• Your customers feel the outage directly, through phones, bookings or payments going dark.
• A few hours offline would breach a deadline, a contract or a service promise of your own.
• The cost of one bad outage would dwarf the yearly difference between a basic and a strong SLA.

Conversely, if downtime is genuinely an inconvenience rather than a stoppage, a lighter SLA on a quality line is the deliberate, defensible choice, and there's no merit in paying for a guarantee you'll never lean on. The goal is fit, not the biggest number. For home workers who run a business from a spare room, our home office broadband sits at the lighter end of this scale while still prioritising work traffic.

What kinds of businesses need leased-line-grade assurance?

A leased line is a dedicated, uncontended connection, and it comes with the strongest assurance of any business product: a committed fix time, a high availability target and an SLA written into the contract rather than implied. Inspire's leased lines carry a 99.5% SLA. You don't buy that for the speed alone, you buy it for the certainty that someone is contractually on the hook when something breaks.

It tends to make sense for businesses where the connection is the business, such as:

• Anyone running real-time payments or live transactions where a stalled line means lost sales the moment it happens.
• Larger sites where dozens of staff and a hosted phone system all depend on one connection.
• Operations with hard external deadlines, like dispatch warehouses, clinics or professional practices.
• Businesses where upload matters as much as download, because they push data, run cloud systems or host services others rely on.
• Anyone whose customers would notice and complain within minutes of an outage.

If that describes you, the right next step is to get a leased-line quote for your address and weigh the cost against what an outage genuinely does to your numbers. If it doesn't describe you, don't force it. A strong business broadband SLA is the smarter spend.

What questions should I ask a provider about SLA and support?

Once you know roughly where you sit on the scale, pin the provider down on specifics. Vague answers here are a warning in themselves. Ask these, and ask for the answers in writing:

• What is the committed fix time, and is it a target or a guarantee? A target you hope for and a guarantee you can rely on are not the same thing.
• What is the response time, and when does the clock start? Some clocks start when you call, others when the fault is "accepted". The difference can be hours.
• What is the availability target, in hours of downtime per year? Make them translate the percentage so you can picture it.
• Is there compensation if the SLA is missed, and how is it claimed? An SLA with no consequence for breaching it is a softer promise than it looks.
• Who do I actually speak to, and where are they? A dedicated UK contact who knows your account beats an offshore queue when the line is down.
• What are the support hours? Inspire's standard support runs Monday to Friday 9 to 5 and Saturday 9 to 2, and the phone is answered in 60 seconds. Match the cover to when your business actually trades.

Run those questions past any provider and the differences between a real SLA and a marketing word become obvious fast. The best answer is one where the commitments are specific, accountable and matched to what your business needs, not the one with the longest list of features you'll never use.

Frequently asked questions