Nobody Hired You to Be the IT Person

You have your own job

If you run operations, finance or the front office, there’s a good chance you’re also the IT person. Nobody asked you. It just landed on your desk.

You reset passwords between budget meetings. You chase the vendor about the printer, the laptop for the new hire, the license that quietly expired. You’re the one people come to when Zoom breaks five minutes before a client call.

We hear some version of this in almost every first conversation we have. The words change, but the feeling doesn’t: I’m exhausted, and this isn’t what I was hired to do.

This post is for you. It isn’t a pitch. It’s what we’ve learned from listening to people in exactly your seat, and what we’d want you to know before you hand IT to anyone, including us.

How it usually happens

Almost nobody wakes up and decides to shop for an IT provider. Something pushes them. In our experience, it’s usually one of these:

• The IT person leaves. Overnight, all that knowledge walks out the door, and IT falls to whoever is closest: often operations or finance.
• The provider goes quiet. Tickets sit. Calls go unanswered. Often it starts after the provider gets acquired or cuts staff.
• Something scary happens. A breach, a near miss, or a license that lapsed without anyone noticing.
• Someone asks for proof. A client, investor or auditor wants to see your security. Suddenly it’s SOC 2 and due diligence questionnaires.
• You grow. A new office, a move, a hiring spurt. What worked for 10 people stops working at 30.

If one of these just happened to you, you’re not behind. You’re right on schedule.

The real cost isn’t on the invoice

You’d expect price to be the big worry. It rarely is. When people tell us what’s wrong with their current setup, money almost never leads. Here’s what does.

Chasing. If you don’t follow up, nothing happens. Your request disappears into a black hole until tomorrow, or next week. You end up managing your IT provider, which is the job you were paying them to take off your plate.

Re-explaining. Every call reaches someone new. You walk them through your setup, your people, last month’s fix. Again. Nobody seems to know your business.

Patching, not fixing. The same problem comes back every few weeks, and each time it’s treated like a one-off. No one asks why it keeps happening.

Looking bad. When the video call drops in front of a client, it’s not the provider who’s embarrassed. It’s you.

Not knowing what you don’t know. This is the one that keeps people up at night. You’re not an IT expert, so you can’t see the gaps. You just hope someone else is watching.

When price does come up, it’s usually standing in for something else: I can’t tell what’s included. I got a surprise bill. I don’t want to be locked in. Those are trust problems, not budget problems.

Six questions to ask before you hand over the keys

Whoever you talk to, these questions will tell you more than any brochure. A good provider will be glad you asked.

1. “When I call, who picks up?” A person who can fix it, or someone who logs a ticket and promises a callback? Ask how many issues get solved on that first call.
2. “What’s covered, and what counts as a project?” Everyone defines “project” differently. Ask to see it in writing before you sign, and ask how new work gets quoted and approved.
3. “Will you know us, or just our ticket number?” Ask how they document your users, devices and setup, so you never re-explain anything to a new face.
4. “Are you reactive or proactive?” Ask what they’ll tell you without being asked: upcoming renewals, aging hardware, security gaps, a budget for next year.
5. “Could I show your security to an auditor?” Not “are we secure,” but “could we prove it to a client or investor tomorrow?”
6. “What happens if the switch goes wrong?” Ask about overlap with your current provider, who holds the logins, and whether you’re locked into a long contract or seat minimums.

If the answers are vague, that tells you something too.

You’ll probably have to sell this inside

Here’s something that surprised us. The person who feels the pain is usually not the person who signs. You’re the champion; a boss, a set of partners or a board makes the call.

That’s a hard spot. You know the problem in your bones, but you have to explain it to people who don’t live it every day. A few things help:

• Lead with time, not tech. How many hours a week go to IT that should go to your real job? That number lands with any leadership team.
• Name the risk plainly. A lapsed license, an unanswered breach alert, a client asking for proof of security. Leaders understand exposure.
• Show the cost of the status quo. Chasing, downtime and embarrassment are real costs, even if they never show up on an invoice.
• Ask the provider to help. A good partner should hand you a short, plain summary you can share, and be willing to explain it to your leadership directly.

How we try to answer those questions

We’ve spent 24 years building Red Key around the answers we’d want to hear. When you call, an engineer picks up, and about 91% of issues get fixed on that call. Every user and device is documented, so nobody re-explains anything. You see what’s covered before anything is billed, and new projects are quoted and approved first.

We’re about 20 people serving nearly 100 clients. Big enough to cover you around the clock, small enough that you’re never just an account. And when you switch, we run a 30-day overlap with your current provider and don’t bill until we’re ready.

The questions above matter more than who you pick. Ask them of everyone. If you’d like to ask them of us, we’re happy to talk, with no pressure and no pitch.

You have your own job. IT shouldn’t be it.