There is a particular sequence of events that every professional dreads — a slow-motion disaster that unfolds in stages, each one worse than the last, with just enough time between them to hope that maybe, somehow, it stops here.
It does not stop here.
Xavier Thompson had been at Meridian Group for just over three months. By this point, he had survived a catastrophic first week, a financial system lockout, a misdirected email to clients, and a laptop abandoned in a Detroit airport. He had developed, through sheer necessity, a reasonably high tolerance for technology-related chaos.
None of that prepared him for the morning of the Caldwell Industries presentation.
The Setup
Caldwell Industries was the kind of opportunity that doesn’t come along often for a company Meridian’s size. A Fortune 500 manufacturer with regional operations throughout the Midwest, they were evaluating vendors for a significant multi-year contract. Meridian had made it to the final round after months of groundwork laid by the sales team — relationship building, proposal refinement, competitive positioning. It was the kind of deal that, if it closed, would be the single largest contract in Meridian’s history.
The presentation was scheduled for 9:00 AM sharp. A Zoom call with four Caldwell executives, including their COO — who Xavier had spent two weeks preparing to speak to specifically, COO to COO.
At 7:30 AM, Xavier was in the office early. Conference room reserved. Slide deck loaded. Notes reviewed. Coffee in hand.
At 8:15 AM, Meridian’s VP of Sales, Renata, did a full tech check. Everything worked. Zoom connected. Screen share functional. The demo environment loaded cleanly.
At 8:47 AM, the internet went down.
8:47 AM: The Sequence Begins
It started the way these things always start — ambiguously. A webpage that loaded slowly. A spinning cursor. The kind of minor friction that, on a normal morning, would prompt a mildly irritated browser refresh and nothing more.
On this particular morning, it prompted Renata to walk very quickly to Xavier’s office and say, with the careful composure of someone actively choosing not to panic: “We may have a situation.”
Within four minutes, it was clear the situation was not minor. Meridian’s internet connection — their single ISP line, their one and only path to the outside world — was completely down. No signal. No backup. The ISP’s automated support line confirmed a local outage with an estimated resolution time of two to four hours.
The Caldwell call was in thirteen minutes.
What followed was, by most accounts, one of the more creatively chaotic thirteen minutes in Meridian’s recent history. Personal phones were turned into hotspots. The IT generalist on staff attempted to route the Zoom call through a mobile connection with the bandwidth of a 2009 streaming service. Three people simultaneously Googled “how to run Zoom on hotspot” as if the results would be different for each of them.
Xavier made a decision: they would join the call from personal devices, ask Caldwell for sixty seconds of grace, and present from a laptop tethered to his phone’s hotspot.
They got through the introduction. They got through the agenda slide. They got, mercifully, through the first five minutes of the presentation.
Then Xavier’s phone, running the hotspot while simultaneously running Zoom, running the slide deck, and receiving three text messages from Renata asking if everything was okay, hit its limit.
The call dropped.
The screen went black.
The room went silent in the particular way rooms go silent when something very bad has just happened in front of very important people.
What the Caldwell COO Said
Xavier called back within ninety seconds. To their credit, the Caldwell team was understanding — these things happen, technology is imperfect, no need to apologize. The COO on the other end made a joke about having experienced the same thing on a board call the previous week.
The presentation resumed. It recovered. Meridian did not lose the opportunity on the spot.
But Xavier spent the remainder of that call acutely aware of something: Caldwell’s COO was evaluating Meridian as a potential long-term operational partner. And for approximately four minutes, Meridian had demonstrated, unintentionally but unmistakably, that their operations were dependent on a single point of failure that could drop at any moment.
Not the impression a COO wants to leave with another COO.
After the call ended, Renata exhaled for what felt like the first time in ninety minutes. Xavier sat quietly for a moment, then pulled out his phone and called Xpert.
“I need you to make sure this never happens again,” he said.
It was the most straightforward brief he’d given them yet.
The Root Cause: A Single Thread Holding Everything Together
When the Xpert team assessed Meridian’s connectivity setup, the finding was simple and stark: the company had one internet connection, from one ISP, running into one router, with no redundancy of any kind.
For a 200-person company operating in a cloud-first environment — where virtually every business-critical application, communication tool, file system, and client-facing platform required an active internet connection to function — this was the infrastructure equivalent of building a bridge with a single cable and hoping nobody looked too closely at the engineering.
It wasn’t a design flaw, exactly. It was the default. When Meridian had moved into their current office space years earlier, they’d set up a single ISP connection because that’s what most companies do when they move into an office. It worked fine for a 40-person company with mostly on-premise systems. It had simply never been revisited as the company scaled, went cloud-first, and became entirely dependent on that one connection for every operational function.
The ISP outage that morning was, in the grand scheme of things, routine — a local line disruption resolved within a few hours. Minor for most of the world. Potentially catastrophic for Meridian, depending on what was happening at 9:00 AM.
On this particular morning, a lot was happening at 9:00 AM.
How Xpert Fixed It
The solution Xpert implemented wasn’t exotic. It didn’t require a complete infrastructure overhaul or a lengthy implementation timeline. It was, at its core, a well-designed answer to a simple question: what happens when the primary connection fails?
Redundant ISP connection. Xpert coordinated the installation of a secondary internet connection from a different ISP, routed through separate physical infrastructure. If the primary line went down, the secondary was available — independent of the same local disruption that had taken out the primary.
Automatic failover configuration. The failover wasn’t manual. It didn’t require someone to notice the outage, diagnose the problem, and make a configuration change while thirteen minutes ticked down on a Fortune 500 call. The system was configured to detect primary connection failure and automatically route traffic through the secondary within seconds — seamless, invisible, and requiring nothing from anyone in the building.
Uptime monitoring and alerting. Xpert configured continuous monitoring of all three connections, with immediate alerts to their team if any layer showed instability. Rather than discovering an outage when a Zoom call drops, Meridian would now know about connectivity issues before they impacted anyone in the building.
The next time Meridian’s primary ISP had an outage — which happened, as ISPs tend to do, about six weeks after the Caldwell incident — nobody in the building noticed. The failover activated automatically. Work continued. No one called Xavier. No one turned their phone into a hotspot.
Renata sent him a single message that afternoon: “ISP is down. Nobody cares. It’s great.”
Caldwell Industries, For the Record
Meridian got the contract.
The Caldwell COO mentioned in his follow-up email that he appreciated Xavier’s composure during the technical difficulties and that it actually spoke well of the team’s ability to handle adversity in real time.
Xavier appreciated the sentiment. He also made sure that particular adversity would never repeat itself.
The Question Worth Asking
Business continuity planning tends to conjure images of disaster recovery scenarios — floods, fires, server room catastrophes. The big, dramatic, hopefully-never-happens stuff.
But the more common business continuity failure is quieter than that. It’s an ISP outage on the morning of your biggest presentation of the quarter. It’s a single point of failure that nobody identified because nothing had gone wrong yet.
What in your operation is held together by one thread right now?
For Meridian, it was the internet connection. For your business, it might be something else entirely. The value of a partner who asks that question before the thread breaks — not after — is difficult to overstate.
Xpert asked it. Then they fixed it. Then they moved on to the next thing.
There was always a next thing.
Coming up in the next installment of The Xavier Chronicles: A marketing coordinator starts using a free AI writing tool to help with client content. The terms of service tell a very different story about where that content is going.
Meridian Group is a fictional company. Single points of failure in internet connectivity are one of the most common and most preventable causes of operational disruption for growing businesses. Xpert Technologies helps growing companies in Metro Detroit build technology environments that work for their business — even when the unexpected happens.
One outage at the wrong moment can cost more than a new connection ever would. Is it time to chat with an Xpert?
#BusinessContinuity #NetworkReliability #DisasterRecovery #ManagedServices #ITInfrastructure #MetroDetroit #XpertTechnologies