The short version
- Most IT budgets are last year’s numbers plus a percentage, which is how March surprises happen.
- The costs that break a budget have dates attached: renewals, warranties, support deadlines.
- Security has moved from a discretionary line to a condition of doing business.
- Build the list from what expires, not from what you spent.
Most businesses build next year’s technology budget by taking this year’s and adding a percentage. It is quick, it survives a board meeting, and it is how a company ends up with an unplanned forty thousand dollar hardware refresh in March.
Start with what expires
A technology budget is mostly a calendar. Every licence, warranty, contract and supported product carries a date, and the ones landing next year are knowable today: Microsoft 365 renewal, hardware warranties, line-of-business software cycles, and Windows 10 Extended Security Updates Year 2 at $122 per device through October 2027. Pull those into one list before you put a number against anything. Most unpleasant surprises were visible twelve months earlier to whoever bothered to write them down.
Hardware is where budgets break
Hardware is lumpy, and lumpy wrecks a forecast. A business replacing a third of its machines each year has a boring, predictable cost. One that replaces everything every five years gets four quiet years and one brutal one, and the brutal one reliably lands in the same quarter as something else expensive. A three to five year cycle varied by role, with the cost spread rather than banked, is the usual answer. Machines that failed the Windows 11 compatibility check are the obvious first candidates.
Security is no longer the line you trim
Security used to be the item a business quietly shrank in a thin year. That stopped being true for contractual rather than technical reasons. Cyber insurance renewals now require multi-factor authentication across every account, monitored detection, tested backups and a written incident response plan, and their absence surfaces as a premium increase or an exclusion. Client contracts increasingly carry the same list. So the question is not whether to fund it, but whether you do that deliberately now or expensively later.
Every line should map to a date, a contract, a replacement cycle or a named problem. Anything that maps to “we spent this last year” deserves a second look.
The lines people forget
- Monitoring and response, not just tools. Detection software nobody watches is an audit trail, not a defense.
- Backup, separate from your cloud platforms. Microsoft 365 protects its own infrastructure, not your data from being deleted or encrypted.
- Training. Usually the cheapest item on the list and reliably the first one cut.
- Somebody’s hours. Every project needs time from a real person, and that is a genuine cost even when it is internal.
The value of doing this in October is not precision, because next year’s forecast will be wrong in places regardless. It is that you find out now, while the options are still cheap, rather than in March when the only ones left are not.
Building next year’s technology budget?
PTSI will map what expires in 2027 across your licences, hardware and contracts, and give you the real numbers before you commit them to a spreadsheet.


