Most of the owners we work with have a budget for payroll, a budget for rent, and a budget for insurance. Technology gets handled differently. It gets handled when a server dies, when a laptop will not boot on a Tuesday morning, or when a renewal notice arrives for software nobody remembers buying. That is not a budget. That is a sequence of emergencies with invoices attached.
The good news is that a working IT budget is not complicated. It is a one page document with a handful of recurring lines, a contingency line, and a short list of projects with quarters attached. It takes a few hours to build and about an hour a year to maintain. Here is the template we use with small and mid-sized businesses across Denton County, including the lines almost everyone forgets.
Start With an Inventory, Not a Number
The most common mistake is starting with a dollar figure. Someone says “let’s keep technology under thirty thousand this year” before anyone has written down what the business runs on. You cannot budget for what you have not listed, and you cannot defend a number you built by feel.
The National Institute of Standards and Technology puts inventory first for a reason. In its Cybersecurity Framework 2.0 Small Business Quick-Start Guide, published in 2024, the guidance is to understand what assets your business relies upon by creating and maintaining an inventory of hardware, software, systems, and services. That inventory is also the foundation of the budget. Four columns are enough.
- Hardware. Every computer, server, firewall, switch, access point, printer, and phone, with the purchase year and warranty end date next to each one.
- Software and subscriptions. Every recurring charge, the cost, the seat count, and who owns the renewal. If you have never done this, expect surprises. We covered what those look like in our post on the cost of neglecting subscriptions.
- Services. Internet circuits, phone service, backup, hosting, and support agreements.
- Data. Where the important files live, and who can reach them.
The Recurring Buckets
Six buckets cover almost every business under a few hundred employees. Build them as annual totals, then divide by twelve if your accounting runs monthly.
- Hardware replacement on a rolling schedule. Pick a replacement age for computers, commonly four or five years, then replace a fifth or a quarter of the fleet each year rather than the whole fleet at once. That turns a frightening capital event into a predictable line. Servers, firewalls, and switches get a longer cycle and a planned replacement year in the inventory.
- Software and per seat licenses. Productivity suites, accounting, and the industry specific application your team lives in all day. Budget per seat and per year, using the headcount you expect at year end rather than today’s.
- Security tooling. Endpoint protection, email filtering, multifactor authentication, backup, and monitoring. Give this its own bucket rather than burying it inside software, because a buried line is the one that gets cut by accident.
- Connectivity. Primary internet, any backup circuit, phone service, and cellular failover if uptime genuinely matters to how you make money.
- Support. An internal person, a managed services agreement, or hourly help. Put a real number here even if the arrangement is informal. Informal support still costs money, just unpredictably.
- Training. Security awareness, application training when you roll something out, and the onboarding time nobody logs. This bucket is most often set to zero, and it is usually the cheapest one on the page.
The Contingency Line and the Per Hire Line
Two lines get left off almost every first draft, and both are why budgets get blown. The first is contingency. Something will break that you did not plan for. A drive fails, a circuit goes down for three days, a vendor raises a renewal price sharply, a laptop goes swimming. Our own rule of thumb is a contingency line worth roughly five to ten percent of total annual technology spend. Using it keeps one unplanned expense from becoming a referendum on whether technology spending is out of control.
The second is the per new hire cost. Owners plan salary and benefits and then forget that a new person also needs a working desk on day one. Price it once and reuse the number.
- The device. Laptop or desktop, plus dock, monitor, keyboard, and mouse.
- The license stack. Email and productivity seat, plus every application that role touches.
- The security seat. Endpoint protection, multifactor, and backup coverage for the new device and the new account.
- Phone or extension. Desk phone, softphone license, or a mobile stipend.
- Setup labor. Imaging the machine, creating accounts, assigning permissions, and the first day of questions.
Add those together and you get one number, per person, to multiply by your hiring plan. It is the fastest way to connect a technology budget to the business plan instead of running it in parallel.
Phasing the Big Projects Across Quarters
Most businesses have two or three real projects in a given year: a server replacement, a move to hosted phones, a network refresh, a migration to a new application. Running all of them at once is how projects fail.
So phase them. Assign each project a quarter, using a simple test for the order: what is closest to failing, what is blocking something else, and what has a hard deadline attached. Equipment the manufacturer no longer supports moves up on its own merit, because once a vendor stops issuing security updates, the risk grows every month whether anyone touches it or not.
Then write each project with four fields: the quarter, the rough cost, who is affected, and the business reason. Leave one quarter lighter on purpose, because something always slips.
How to Present It to a Partner or a Board
Technology budgets get rejected for one reason more than any other. They are presented as a shopping list. Nobody approves a shopping list.
- Lead with cost per employee per month. A large annual total sounds abstract and alarming. The same number divided by headcount and then by twelve sounds like what it is, a line item sitting next to other operating costs. Give both figures.
- Tie each bucket to a business consequence. Hardware replacement means people stop losing twenty minutes a day to a slow machine. Security tooling means an email impersonating a vendor does not become a wire transfer. Connectivity means the office keeps taking orders when the circuit drops.
- Show last year next to this year. Three columns: what we budgeted, what we spent, what we propose. Explaining a variance you already found beats being asked about one you did not.
- Name what you are choosing not to do. A budget that only says yes looks undisciplined. Listing the two projects you deferred, and why, makes everything else more credible.
- Quantify time, not only dollars. Hours recovered are real money and usually the easiest part of the case to make, an argument we made at length in our piece on why saving time takes priority over saving money.
The Bottom Line
An IT budget is not an act of prediction. It is an act of sequencing. You will not guess every number correctly, and you do not need to. What you need is a written list of what you own, six recurring buckets, a contingency line, a per hire number, and two or three projects with quarters next to them. That page turns technology from an unpredictable interruption into a planned expense.
If you want help building the first version, this is work we do with clients regularly, and we are happy to start from whatever you have. We will build the inventory, price the buckets honestly, and order the projects to match how your business runs. Contact us today.
Sources:
Comments are closed