It is the most reasonable question an owner can ask, and the most common answer — a percentage of revenue — is close to useless on its own. The same percentage is too much for one business and nowhere near enough for another, depending on what the money is buying and what breaks if it stops.
Here is a better way to think about it.

What an IT Budget Is Actually Paying For
Most IT spending falls into four buckets, and the trouble usually starts when a business only funds the first one.
Keeping the lights on. Licences, internet and phones, the machines people work on, file storage, and backups that actually run. Unglamorous, non-negotiable.
Security and compliance. MFA, endpoint protection, patching, email filtering, staff training, and whatever your insurer or a client contract now requires you to demonstrate. This bucket has been growing for everyone.
Projects and improvement. The migration, the new line-of-business system, the workflow that saves a person two hours a week.
The reserve. Money set aside for the thing you did not plan for — a failed server, a ransomware response, a laptop stolen from a car.
A budget that covers only the first bucket is not a budget, it is a countdown.
The Traps That Blow the Number Up
Deferred hardware refresh. Machines are kept four years past sensible, then twelve fail in the same quarter and the replacement bill lands in one month instead of being smoothed over three years.
Licence creep. Seats bought for staff who have left, three tools that do the same job, an enterprise tier for a feature nobody uses. This is the most common quiet overspend in small businesses.
Funding projects but not support. The new system gets budgeted because it is visible. The ongoing administration it needs does not, so it degrades.
No allowance for an incident. Recovery is expensive and urgent, which is the worst possible combination to be paying for out of cash flow.
Spending to pass a questionnaire, then stopping. Controls that exist only for an audit tend to lapse, and you pay twice.
Building Your Own Number
Rather than starting from a percentage, start from what you actually spend and work up. It takes an afternoon and produces something you can defend.
- Pull twelve months of invoices. Everything IT: software subscriptions, internet, phones, hardware, support, hosting, backups. Owners are consistently surprised by this total, in both directions.
- Divide hardware by lifespan. Add up the machines and servers, assume a realistic refresh cycle, divide. That is your true annual hardware cost, whether or not you spent it this year.
- Price your security baseline. Whatever is now expected — MFA, endpoint, backup, filtering, training — as an annual figure.
- Add a project line. Even if the specific project is not decided, the line should exist.
- Add the reserve. Pick a number you could survive, and treat it as untouchable.
Now compare the total to revenue. Not as a target to hit, but as a sanity check: if you are far below what similar businesses spend, you are probably deferring something that will bill you later. If you are far above, it is worth asking what you are getting for it — the in-house versus managed IT cost comparison is a useful lens there.
Signs You Are Spending Too Little
Not "spending less than you could" — spending too little, which is a different thing. The symptoms are specific: work is reactive, and the same problems recur. Backups exist but nobody has tested a restore. The owner is the escalation path for everything technical. Questions on an insurance or client security questionnaire are answered "no" or with a guess.
Every one of those is a cost that has been moved, not removed. It will be paid in downtime, in lost data, or in the premium increase after an incident.
Signs You Are Spending Badly
Overspending rarely looks like overspending. It looks like paying for three overlapping tools, or buying a licence tier for one feature, or calling a break-fix engineer to the same failing machine for the third time because the machine is the cheaper conversation.
It also looks like paying for advice that never gets implemented. A report is not an outcome.
Buy Outcomes, Not Hours
The most useful change an owner can make is to stop comparing hourly rates and start comparing what is included and what is guaranteed.
Two providers can quote the same monthly figure while one covers monitoring, patching, backup verification and helpdesk, and the other covers a phone number. The number that matters is not the cost of an hour; it is the cost of the outcomes you need, minus the cost of the outages you no longer have.
At Virtue Technology Solutions we work with Southern California SMBs on managed IT and IT professional services, and we would rather help you size a budget you can sustain than sell you the largest one you will accept.
Want a second opinion on what you should be spending? Contact Virtue Technology Solutions for a no-pressure consultation.