When Your Systems Go Down, Who Do You Call?

Your business runs on a stack of things you probably haven't thought about this month. The domain name. The DNS records behind it. The hosting. The email. The server in the back office, the Wi-Fi, the passwords, the backups — if there are backups.

It all works, quietly, right up until the moment it doesn't. And that moment has a habit of arriving at 2am on a Friday, the week of your biggest order.

So here's the only question that matters in that moment: who do you call?

The way most businesses are actually set up

When we look under the hood at a growing business, we usually find some version of this:

• The website was built by a freelancer who has since moved on.
• The domain is registered under someone's personal email — sometimes someone who no longer works there.
• The hosting, the email, the phone system and the software each come from a different company.
• The server was set up years ago by "someone's nephew who's good with computers."
• The passwords live in one person's head, or in a spreadsheet.
• Nobody is sure whether the backups run, where they go, or whether they've ever been restored.

Every piece works on its own. Nobody owns the whole picture.

So when something breaks, you get five companies each pointing at the other four — while your business sits offline and your customers go somewhere else.

One accountable owner

The single most valuable thing you can buy for your infrastructure isn't a faster server. It's one team that is responsible for all of it.

That means:

• Someone to call. One number, one team, that already knows how your systems fit together — no explaining your setup from scratch in the middle of an outage.
• Someone accountable. When something goes wrong, the question isn't "whose fault is it?" It's already answered. It's ours to fix, and we own the result.
• Someone keeping the records. Accounts in the business's name, documentation of how everything is built, and access that doesn't vanish when one person leaves.
• Someone watching. Monitoring that raises the alarm the moment a server, a site or a backup misbehaves — ideally before a single customer notices.

Backups: the difference between a bad day and the end

Most businesses believe they have backups. Far fewer have ever tried to restore one.

A backup you've never restored isn't a backup — it's a hope. And a backup stored on the same machine it protects disappears in the same fire, flood, failed drive or ransomware attack as everything else.

The standard professionals work to is the 3-2-1 rule:

• 3 copies of your data,
• on 2 different kinds of storage,
• with 1 kept off-site, away from the original.

Then, crucially: test the restore, on a schedule, so the first time you find out whether it works isn't the day you need it.

These are decisions made by people who plan to be around

Nobody buys insurance for the days everything goes right. Handing your infrastructure to an accountable team is the same decision: you're paying so that the bad day — the dead drive, the hacked site, the expired domain, the server that won't come back — is an inconvenience instead of a catastrophe.

The owners who make this call early aren't the ones who've been burned. They're the ones who've decided they never want to be.

How we handle it

We design, build and run the infrastructure behind our clients' businesses — and our own. That means:

• Automated, off-site backups on a schedule, with restores we actually test.
• Monitoring and alerts around the clock, so problems surface before customers feel them.
• Private, secured networks for internal tools, with nothing exposed to the internet that doesn't need to be.
• Documentation and handover, so your systems are never a mystery locked in one person's head.
• Ongoing maintenance, from $200 a month, so it keeps running without you babysitting it.

Read more about our self-hosting and infrastructure work and our security hardening.

The bottom line

Every system fails eventually. What decides whether it costs you an afternoon or your business is whether someone is responsible for it, and whether there's a backup ready when it happens.

Don't find out who to call at 2am. Get a tech quote and let's put a name — and a backup — behind your systems today.