Do You Need an IT Company or Someone to Call?

The short version

Most small businesses assume hiring IT help means signing a monthly managed contract, priced per machine, whether or not anything breaks. For a business with a handful of computers and occasional problems, that's usually overkill — what they need is one person who knows their setup and picks up the phone. A managed contract genuinely is the right answer once you have compliance obligations, a lot of machines, or need someone reachable at three in the morning. The tell is whether you'd use what you're paying for.

When a small business decides it needs IT help, the first quote is almost always the same shape: a monthly contract, priced per machine or per person, covering monitoring, patching and a helpdesk number.

That's a real service and some businesses genuinely need it. Plenty don't, and nobody selling it has much reason to say so.

The two arrangements

Strip away the branding and there are two things you can buy.

A managed contract is ongoing coverage. You pay every month whether or not anything breaks. In exchange, someone is watching the machines, patching them, and contractually obliged to respond within a set time.

Someone to call is a person who knows your setup and is available when you need them. You pay for work when there's work.

Managed contract Someone on call
Monthly cost Always Only when used
Response SLA-backed Depends on availability
Who turns up Whoever is assigned The same person each time
Suits Many machines, compliance Few machines, occasional issues

Neither is better. They suit different businesses, and most small ones are quoted the first without being asked whether they need it.

When a contract is genuinely the right answer

I'd tell you to sign one if any of these are true:

  • You have compliance obligations. Regulated work often requires documented, monitored, centrally reported endpoint management. That paperwork is a real deliverable and it's what a managed provider is built to produce.
  • You have a lot of machines. Past roughly twenty, tracking what's patched and what isn't stops being something anyone does by eye.
  • You need guaranteed response. If an hour of downtime costs you real money, a contractual response time is worth paying for, and "he's on another job" isn't an acceptable answer.
  • You have multiple locations, or staff who need help outside business hours.

If none of those describe you, keep reading.

When it's overkill

The mismatch shows up in what you use versus what you're billed for.

You're paying per device for machines that never break. Ten computers on a per-device plan, and eight of them are a browser and a printer driver. Those eight are pure margin.

You call twice a year. Some businesses genuinely have that few problems. Paying monthly for a helpdesk you contact twice is renting insurance against a risk you don't have.

You use a fraction of what's covered. Read what's actually in the contract. Server monitoring, when you have no server. Mobile device management, when everyone uses their own phone anyway.

The person who shows up is different every time. With a larger firm, the account manager who impressed you often isn't the technician who arrives, and you re-explain your setup on every visit. That's a real cost even though it isn't billed.

What "someone to call" looks like in practice

One person who has seen your setup, knows why that switch is in that cupboard, and can be reached without a ticket number.

For most small businesses that means occasional visits when something needs hands on it, remote help for everything else, and a handful of things kept current in the background — updates, backups, and knowing the wifi will hold up. Billed per visit, or monthly if you'd genuinely rather it stayed handled without you thinking about it.

The honest limitation: one person is not a 24/7 operation. If your business stops when the network stops, you need coverage I can't promise, and I'll say so rather than take the work.

What to ask, whoever you're talking to

Useful for comparing me against an MSP, or two MSPs against each other:

  • What's specifically not included, and what does it cost when it happens?
  • Who actually turns up — the person I'm talking to now, or someone else?
  • What's the response time, and is it a contractual commitment or a hope?
  • If I leave, what do I take with me? Credentials, documentation, and configuration should be yours.
  • What am I paying for that I'm not currently using?

A provider who answers those plainly is worth more than one who's cheaper and vague. If any of them makes somebody defensive, that told you something.

Working out which you are

Count two things — how many machines actually matter, and how many times in the last year you genuinely needed help. If those numbers are small, you're probably being quoted for a service built for a company several times your size.

I do this work for small businesses around Princeton, Hopewell, Flemington and Lawrenceville, on site when it needs hands and remotely when it doesn't. More on what that covers, and how IT work is priced if you're comparing quotes.

Get in touch and I'll tell you honestly which one you need — including when the answer is a managed contract I'm not the right person to provide.

← Back to Insights