What a retainer actually buys you

The reasonable objection to a monthly plan is that you might not use it. Some months nothing breaks. You pay anyway, and it feels like insurance you didn't need.

That's a fair way to look at it, so let me answer it honestly rather than sell around it.

What you're actually paying for

A retainer is not a block of hours. If it were, you'd be right to resent the quiet months, and I'd be incentivized to make the work look bigger than it is.

What it buys is continuity — someone who already knows how your systems are put together. Your VLAN layout, which switch port the point-of-sale runs on, why the firewall has that one exception in it, what your DNS looks like and who your mail actually goes through. That knowledge is the expensive part of any IT problem, and it doesn't live in a ticket system. It lives in whoever built the thing.

And it buys attention — monitoring that notices a failing disk or an expiring certificate before it becomes your Monday morning. Most of what a plan does, you never see, because it happened at 2am and got fixed before you woke up.

Why break-fix costs more over a year

Look at the one-time rates. Business remote support runs $150/hr, and after hours or emergency is $225/hr. Those numbers aren't a penalty for not having a plan; they're what unscheduled work genuinely costs.

But the hourly rate isn't the real expense. The real expense is that every break-fix call starts from zero. Before anyone can fix anything, someone has to work out how your network is laid out, get access, find the documentation that doesn't exist, and reconstruct what changed. You pay for that rediscovery every single time, at emergency rates, while you're down.

An engineer who already has the diagram in his head skips that entirely. Same problem, a fraction of the time, and usually before you noticed it.

There's a second cost that's harder to see: the small things nobody calls about. Backups that stopped running four months ago. Firmware that never got updated. A certificate quietly counting down. Break-fix, by definition, only ever addresses what has already gone wrong.

What a retainer does not include

This is where most managed-services pitches go vague, so:

New projects are quoted separately. A network redesign, a new site build, an automation install, a migration — those are scoped in writing, with a price, before anything starts. A plan doesn't turn them free.
Hardware is hardware. Replacement switches, access points, and cameras are quoted at cost plus a flat handling margin, itemized by model.
It isn't 24/7 unless the plan says so. Business plans get same-business-day priority. Genuine round-the-clock response is a different agreement with a different number attached.
It won't fix a decision you haven't made. If the actual problem is that nobody has decided who owns the domain or which platform you're standardizing on, no amount of monitoring resolves that.

If a one-time fix would have been covered by a plan, I'll say so before I bill you. That runs both directions — if a plan wouldn't help you, I'd rather tell you that than take $80 a month for nothing.

Who it's genuinely for

If you're one laptop and a printer, buy support incidents as you need them. A plan is overkill and I'll say so.

It earns its keep the moment being down costs you money — a shop that can't take payments, a clinic that can't reach records, an office where email going dark stops the day. At that point you are not buying hours. You are buying the fact that somebody already knows your setup and is already watching it.

Every plan and every one-time rate is published, with no "call for a quote" on the everyday work — the numbers are all here.