More Than a Contract: IT Support That Shows Up

When a business loses access to its systems, the technical explanation is rarely the first thing its employees need.

They need to know what happens next. Who is working on it? What needs to be done? And does the person on the other end understand what this interruption means for their day?

For Grant Moore, Senior Network Engineer at Stratus Services, that last question matters as much as the troubleshooting.

“If they’re down all day, their people can’t work,” he says.

That perspective shaped his response to two separate disruptions that happened close together: an urgent firewall security update affecting a client in San Diego, followed by an unrelated data center power outage affecting another client.

The technical circumstances were different. His sense of responsibility wasn’t.

An urgent update—and an unexpected complication

The first situation began with a serious vulnerability affecting Fortinet firewalls. A security update needed prompt attention, and Stratus coordinated with affected clients to apply it.

Most systems came back online afterward. One client location in San Diego did not.

According to Grant, troubleshooting pointed to a DNS-related issue involving the location’s internet service provider.

DNS is often described as the internet’s address book. It helps systems translate names into the numerical addresses they use to find one another. When that process doesn’t work correctly, a connection can fail even though the underlying problem isn’t obvious to the people trying to use it.

For the client, the important fact was simpler: their systems weren’t working as expected.

The issue arose overnight. Before most of the client’s employees were awake for their workday, Grant was already on a plane to San Diego. Within nine hours, he had traveled there, addressed the issue on-site, and completed the return trip.

His first consideration wasn’t whether the client’s business sounded especially high-stakes. It was that the client’s team would soon be starting their workday—and the problem needed attention before it disrupted their ability to work.

Different businesses. The same commitment.

Some technology supports medical care. Some help aircraft land safely. Some keep a local construction company’s crews, schedules, and project information moving.

The consequences of an interruption are not identical. But for Grant, the commitment to careful decisions, timely attention, and effective problem-solving should not depend on how impressive a client’s work sounds.

“They all deserve that same proactiveness,” he says, “making sure that they get the same quality of service, networking, and monitoring.”

Then he makes an important distinction about what that really means:

“I always say, not patching, but attention.”

That doesn’t mean every incident receives an identical technical response. Life-safety risks, security threats, and operational interruptions require appropriate prioritization. It means no client should have to prove that their business matters before someone takes their problem seriously.

Grant’s approach is to bring the same care and discipline to understanding the problem and deciding what comes next.

“It wasn’t a matter of, do I need to go out there? Who needs it?” he says. “It doesn’t matter. Okay, when? Let’s get it done.”

A steady perspective when the pressure rises

Grant’s comfort in demanding situations is rooted in his background as a veteran. Making sound decisions in hostile environments gave him a perspective he now brings to technical problems: stay composed, assess the circumstances, and focus on what needs to happen.

“I came from those hostile environments and was at peace in those environments,” he says. “This isn’t as hostile, but the meaning of the client is still significantly the same, if not more.”

The comparison isn’t about minimizing a client’s disruption. It explains why the pressure itself doesn’t overwhelm him.

An unfamiliar problem, an urgent decision, or a room full of frustrated people doesn’t prevent him from thinking clearly. Those are conditions he is comfortable working through.

For the client, that steadiness matters. When the people around a problem are understandably anxious, someone still needs to make careful choices.

Grant keeps his attention on the practical stakes.

“They lose money,” he says. “And if they’re down all day, their people can’t work.”

An instinct to stay ready

As the San Diego visit wrapped up, Grant was already thinking about another client’s environment and upcoming firewall maintenance.

He considered staying in the area in case additional support became necessary.

“I was at the airport like, I should just stay just in case something goes wrong.”

That instinct reflected more than a willingness to respond after an alert. He was looking ahead: weighing the work still to come, the potential disruption, and where his presence might be useful.

He was also careful not to introduce unnecessary interruptions. With a further vendor fix still pending, he chose not to rush into an update that might require the client to stop work twice.

Then, something did go wrong.

The second client’s data center lost power.

It was not the firewall problem he had been considering, and it was not caused by a Stratus update. The planned maintenance had not taken place. This was a separate infrastructure event.

But his instinct to stay alert proved well-founded: another situation requiring close attention was already unfolding.

Grant worked remotely with people on-site, using video calls to coordinate access and rebuild a network switch configuration. The recovery effort extended through the weekend.

“You never expect the unexpected,” he says, “but be ready for it.”

Readiness doesn’t mean predicting the exact failure. It means paying attention before trouble starts, exercising judgment about changes, and being prepared to adapt when the situation takes a different direction.

Supporting the people, not just the equipment

Grant also talks about a part of technical service that rarely appears in a list of capabilities: understanding the room.

Every client environment is different. So are the people in it.

Someone dealing with a brief inconvenience may welcome a little humor. Someone whose team has been unable to work for hours may need a clear explanation and a focused conversation.

“Depending on how long they were down, they might not be in a joking mood,” he says. “So you’ve got to be able to navigate those circumstances.”

That awareness matters because an outage is more than a malfunctioning device. It creates uncertainty for the people responsible for keeping the business moving.

Technical expertise helps resolve the problem. Respectful, practical communication helps people navigate the disruption while that work is underway.

Neither should be treated as an optional extra.

Every incident should make the next response better

Despite his comfort under pressure, Grant doesn’t confuse confidence with having nothing left to learn.

“I would never be comfortable with, and I don’t think anybody should ever be comfortable with, their current knowledge and their current ethics,” he says. “I think everybody always has room to grow.”

Every environment presents a different combination of technology, dependencies, and working relationships. Each experience can reveal something useful for the next response—and something worth sharing with the team.

“I learn something every trip,” he says.

For Grant, the standard is not simply whether he was present or completed a task. It is whether his involvement made things better.

The goal is not to become comfortable handling the same disruption over and over. It is to use what you learn to support the client better going forward.

More than a contract

Asked what drives his approach, Grant comes back to the relationship.

“At the end of the day, it’s a reflection of Stratus,” he says. “And I don’t want this company to feel like it’s just a contract.”

Then he puts it plainly:

“It’s always more than a contract. It’s about a relationship.”

For him, that relationship is not a benefit added after the technical work. It shapes how he approaches the work in the first place: taking the interruption seriously, thinking ahead, adapting to the people involved, and staying focused on the outcome.

It also reflects why he values being part of Stratus.

“I’m blessed to be in a position to represent Stratus and its honor,” he says, “and have a big part in how others get to view us, our work ethics and our services for them.”

A service agreement defines responsibilities. The relationship becomes visible in how those responsibilities are handled.

No IT provider can promise that every security update, internet connection, or data center will operate without disruption.

What matters is how that provider prepares, responds, and learns—and whether the people relying on those systems feel supported throughout the process.

At Stratus Services, that is the responsibility behind the technical work.

If you’re evaluating your IT support, start with more than a list of tools. Let’s talk about how your business operates, what your team depends on, and what you need from the people supporting it.

‍