Choosing an IT Partner

Why Every Client Had My Cell Number — and What I’d Tell 2009 Me Now

Originally written in April 2009 for the blog of eMonarch, the managed IT company I ran before founding NSN Management. I have left the 2009 promise intact below, then added what seventeen more years of running an IT company taught me about it — because the second half is the part worth reading.

2009: every client should be able to reach me

After a rough Monday, I came to a realization I should have had years earlier: my customers should be able to get hold of me on my cell — even at home — if they have a critical issue. Period.

In the early days the company was built around my technical skills, so almost every customer talked to me to get things fixed, from designing their Active Directory to helping with an Outlook problem. That did not scale, and it did not leave me any time to grow the business. So I spent years building systems and processes so my team could handle everything without me. But that is not always right for the customer who is paying my company to take care of them. I am the one who sits across from the owner when they sign the agreement and says “we will take care of you.” So when we drop the ball, that owner should be able to reach me, no matter what.

That week I also put words to why the company existed at all: to transform lives through excellence and innovation. People struggled with how a managed IT company “transforms lives,” so I explained it like this. Our customers are small businesses. Those businesses are owned by men and women with families, who are building the business to provide a better life for those families and to spend more time with them. Our job is to make that real through technology — to make the tools work for the owner instead of against them, with excellent service and innovative solutions. Do that, and you have changed that owner’s life a little.

How many customers of a McDonald’s know who owns the store? But I bet they know the owner of their law firm, their CPA firm, their main supplier. So my customers got my cell number and my home number.

2026: I was right about the promise and wrong about the mechanism

The instinct in that post was correct, and it is still the standard I hold NSN Management to: the owner is accountable for the promise made across the table. What I got wrong was thinking the way to honor it was for the owner to personally answer the phone.

Here is what I have learned since. If the founder’s cell is the safety net, then the safety net is one person — who is also in a sales meeting, or on a plane, or asleep. It feels like accountability; in practice it is a single point of failure dressed up as a personal touch. Worse, it quietly tells the team that the real escalation path goes around them. And it does not scale past the first few dozen clients — which is roughly when I wrote it.

I do not solve tickets anymore. I am the captain of the ship, not the engine room, and a captain who spends the day in the engine room is not steering. What a client actually needs from the owner is not my hands on their problem; it is that the system I built takes care of them every time, and that when it doesn’t, the failure reaches me — quickly, and without them having to know my number.

What accountability looks like when it scales

  • A written response standard, agreed up front. Not “call Sean if it’s bad” — priorities and targets we agree with you before you sign, so “critical” means the same thing to both of us.
  • An escalation path that is a process, not a person. A critical ticket that is not moving is escalated automatically to the team lead and then to leadership. You should never have to go around the help desk to get attention; the help desk should be where attention lives.
  • Reporting you can see. Every month, tickets, response times against the standard, backups, patching, security events. If a promise is not being kept, it shows up in a report you receive — not in a phone call you have to make.
  • A planning review with someone senior. This is where I — and the rest of leadership — actually belong: looking ahead with you about budget, risk, and where the business is going. That is the owner’s job on your account, and it is where the “transform lives” purpose gets done.
  • The WOW standard. Every ticket, project, and meeting is a chance to make someone’s day better than they expected. That is a habit for the whole team, not a heroic act by the founder.
Every ticket, project, meeting

Something happens for you.

We handle it

Fast, clear, owned to resolution.

We ask the question

Was that service worth talking about — would you tell someone?

We raise the bar

What made it a yes becomes the standard.

So can you still reach me?

Yes — and if the system fails you badly enough that you feel you need to, I want to hear it, because that means something is broken in the process and not just in your server. But you should not need to, and if you ever do, that is on me to fix at the system level, not just for that afternoon. That is the difference between 2009 and now: the promise is the same, and the way we keep it is what grew up.

The purpose stayed too. NSN Management still exists to make technology work for the owners of Tulsa businesses so they can build the life they started the business for. If you would like to see how that works in practice — the standard, the reporting, the reviews — here is how we work, or book a Discovery Call.

Questions Tulsa businesses ask about this

Can I reach the owner of NSN Management directly?

Yes — and if the system has failed you badly enough that you feel you need to, Sean wants to hear it, because that means a process is broken. But you should not need to: critical tickets escalate automatically to the team lead and then to leadership, and every promise is reported against monthly.

Why isn’t the owner’s cell number a good escalation path?

Because it makes the safety net one person — who is also in a meeting, traveling, or asleep — and it teaches the team that the real path goes around them. Accountability that scales is a written response standard, automatic escalation, and reporting the client can see.

What does an escalation path look like at a managed IT company?

A ticket’s priority is set against an agreed standard; if it is not moving, it is escalated automatically to the team lead and then to leadership without the client having to ask. The client sees the outcome in the monthly report.

What is NSN Management’s purpose?

To make technology work for the owners of Tulsa-area businesses so they can build the life they started the business for — first put into words in 2009 as “transform lives through excellence and innovation,” and carried today through the WOW standard on every ticket, project, and meeting.

What does the owner of an IT company actually do for my account?

The planning: looking ahead with you about budget, risk, replacement cycles, and where the business is going in the scheduled review — and owning the system that handles the day-to-day so you never have to go around it.

· Founder, NSN Management

Sean founded NSN Management in Tulsa in 2012 after running eMonarch, the managed IT company he started in 1999, and still leads the team. He co-wrote Special Edition Using Microsoft Active Directory (Que, 2001), was named to the Tulsa Business Journal’s 40 Under 40, and led NSN Management to Kaseya/Datto MSP of the Year 2025.

Published · Updated

Choosing an IT PartnerManaged IT Strategy