IT Budget Planning Template for MSPs and In-House Teams (2026)

Updated: November 2026

Finance asks for next year's IT number, and what comes back is a list of renewal dates, a hardware wishlist, and a managed services invoice nobody has itemized in two years. An IT budget planning template turns that into something a CFO can approve line by line, whether an in-house IT team builds it or an MSP builds it with a client. This guide covers the six core categories, the 2026 structure benchmarks to check them against, and a sample budget you can copy into Excel or Google Sheets.

TL;DR

• What it is. A worksheet that splits annual IT spend into separate categories so every line can be defended on its own.
• How big. Published ratios run from 2.9% of revenue (Avasant median, 2025) to 5.49% (Deloitte average, 2022 data), so build from seats first and use the ratio as a check.
• How it splits. Personnel takes 30.8% of the average IT budget, cloud and data center 14.6%, security 5.4% and AI 1.9% (Avasant, 2025/2026).
• Where plans fail. Managed services fees, hardware refresh, and security land as single unexplained rows.
• The fix. Break those three out, attach a benchmark to each, and accrue hardware annually.

What Goes Into an IT Budget Planning Template

Six categories carry almost all IT spend at a small or mid-sized business. Get these rows right and the rest is arithmetic. The sizing column says where each number comes from, which is the first question finance asks.

Two more lines sit across the top of those six rather than beside them. Security and compliance spend hides inside cloud, software, and outsourced IT. Project spend hides inside hardware and outsourced IT. Both need their own tracking rows even though the money is already counted elsewhere, because those are the two numbers finance will ask you to justify first.

That double-counting trips people up, so label the rows clearly. Six spend categories add to 100% of the budget. Security and projects are overlays that report a slice of that same total.

IT Budget Template Columns for Excel or Google Sheets

The template is a column layout, so it works the same in Excel, Google Sheets, or the workbook your finance team already uses. Make one row per budget line under the six categories, then add these columns:

Keep the formulas visible. A forecast cell that reads seats times rate is easy to defend, while an annual IT budget template in Excel with hard-coded totals has to be rebuilt every time a seat count moves.

Sample IT Budget for a 75-Person Business

Here's the template filled in for a 75-person business with one in-house systems administrator and a co-managed MSP. Every unit cost comes from a public figure or a stated assumption, so you can swap in your own. Cloud and telecom vary too much by business to estimate from outside, so those two come from your invoices.

The pay figure is the May 2025 median for network and computer systems administrators from the Bureau of Labor Statistics, and the 43% reflects benefits making up 30% of total private-industry compensation in the BLS employer cost survey for June 2026. Microsoft 365 Business Premium stayed at $22 per user a month in Microsoft's July 2026 US price update.

The $90 rate sits inside the $75 to $110 co-managed range in our outsourced IT support breakdown. A fully managed agreement at $165 per user would take the place of both the staff and co-managed lines at $148,500 a year, which is the comparison worth running before either contract renews.

Size the Budget Before You Fill In the Lines

IT budgeting is the yearly work of forecasting technology spend, splitting it into categories, and checking each line against a benchmark before finance sees it. The template is the output. The budgeting is the sizing that happens first.

A blank template invites wishful thinking. Check the total against a published ratio before you distribute it. Every figure below is public and citable, which matters when someone in finance asks where the number came from.

Two of those numbers deserve a caution. Avasant's respondents have at least $50 million in revenue or $1 million in IT spending, and its ratio counts operational IT spending, so a smaller business should treat 2.9% as context rather than a target. And Gartner's 14.2% growth forecast is driven heavily by data center and AI infrastructure at the top of the market, so it's a signal about vendor pricing pressure rather than a rate you should apply to your own budget.

For a business under $50 million in revenue, the faster sanity check is the sample budget above: build the total from seats, contracts, and the hardware accrual, then divide by revenue. If the result lands far from the published ratios, look for a missing line or a padded one before the number goes to finance.

Average IT Budget as a Percentage of Revenue

The two revenue ratios measure different things. Avasant reports the median operational IT spend across its sample, and Deloitte's study reports the average tech budget, which it tracked rising from 4.25% of revenue in 2020 to 5.49% in 2022. Deloitte also found that companies selling data or tech-enabled services spend 8.54% of revenue on technology, against 3.66% for the rest, and Avasant notes that sector drives the ratio more than company size.

So compare against your own sector before you compare against an all-industry figure, and put the source and year beside every ratio in the template. A ratio without a date invites the question of which survey it came from.

IT Department Budget Structure Benchmarks for 2026

The revenue ratio sizes the total. Structure benchmarks check how that total splits, and the 2025 survey cycle gives a usable set for the lines finance asks about first.

Read those as structure checks, not targets. A business that works with an MSP moves spend out of personnel and into the outsourced IT row, because the provider's staff sit inside the managed services fee, so a low personnel share there is a design choice rather than a gap.

Budget Structure for In-House IT Teams

An in-house team gets the most from the personnel and capital lines. A staff share far above 30.8% points to work that better tooling or a co-managed agreement could take off the team's plate, and a capital share well above 13% points to hardware still being bought in spikes rather than accrued.

Budget Structure for MSP Client Budgets

For an MSP, the client's IT budget is a planning deliverable in its own right, and budget planning fits naturally into the quarterly business review. Bring the five managed services sub-lines from the next section, the hardware accrual for the client's fleet, and the security overlay, so the client sees where the fee goes and which lines they control.

Where Managed Services Fees Belong in the Plan

A single row and a single number is the quick way to enter outsourced IT. It's also the row finance queries hardest, because a lump sum with no breakdown reads like a subscription nobody has reviewed.

Per-user pricing spreads wide, so check your rate against a survey rather than a headline. In Kaseya's 2023 benchmark of MSPs, 22% of providers charged $50 to $100 per user a month, 17% charged $101 to $150, 11% charged $151 to $200, and 28% didn't price per user at all. Scope explains the spread, and the ranges we use across our cost guides are $130 to $200 per user a month for fully managed, $75 to $110 for co-managed, and $35 to $60 for help desk only. Out-of-scope work is the line that drifts, so budget last year's actual spend for it rather than the contract rate.

Split the retainer into five sub-lines instead:

• Covered seats. Contracted per-user or per-device rate times your seat count, at the rate on the current agreement rather than last year's.
• Pass-through tooling. EDR, backup, email security, and RMM agent licenses your provider bills through, listed separately because they scale with seats and renew on their own dates.
• Out-of-scope and after-hours. Last year's actual spend on work outside the agreement, not zero.
• Project work. Migrations, refreshes, and office moves booked against a rate card.
• Onboarding and remediation. One-off spend if you're changing providers or cleaning up a backlog.

Do that and the conversation changes from "why is IT support $180,000" to a set of five numbers with different owners and different levers. It also surfaces overlap, since pass-through tooling frequently duplicates something already sitting in the software licenses row. Our breakdown of MSP pricing models covers how providers build these rates, which helps when you're checking whether your quote is competitive.

Budgeting Hardware Refresh Without the Every-Fourth-Year Spike

Hardware is the least evenly distributed line in the template. Buy 60 laptops in one year and the budget looks broken, then buy none for three years and it looks padded. Neither version survives a finance review.

Accrue instead. Divide each asset class by its useful life and book the annual figure, whether or not you spend it that year. The useful lives below are planning choices rather than standards: four years for laptops, five for desktops and servers, and seven for network gear. Here's the arithmetic on a 75-person business:

That $29,614 goes into the template every year. Actual purchases vary, the accrual doesn't, and the variance between them is a number you can explain in one sentence.

Your refresh plan and your tax schedule can differ. IRS Publication 946 treats computers and peripheral equipment as 5-year property for depreciation, so finance may book a laptop over five years while the budget plans a four-year refresh, and both are correct for their purpose.

Two things are pushing 2026 refresh costs up. Microsoft ended support for Windows 10 on October 14, 2025, so a machine still running it needs either Extended Security Updates, priced at $61 per device for the first year and doubling each year after, or a replacement. And Gartner's July 2026 forecast points to rising hardware and memory costs, so price the refresh from current quotes, including any tariff changes your supplier has passed through, rather than last year's unit cost.

If a role needs newer hardware sooner, shorten its useful life in the table rather than adding a one-off project row, because that keeps the accrual accurate in future years too. Our guide to IT asset lifecycle management covers how to track those dates so the refresh never arrives as a surprise.

In this r/ITManagers thread, an IT lead whose CFO wants a hardware budget and forecast gets a top reply that builds it from two inputs: an end-of-life replacement line and new-hire devices from the HR headcount plan.

Carving Out Security and Compliance Spend

Security is the overlay line that's easiest to leave implicit, and it's the one with the clearest external benchmark. The IANS and Artico benchmark, a survey of 587 CISOs, found security averaged 10.9% of IT spending in 2025 and 0.69% of company revenue. Avasant puts the security line at 5.4% of the average IT budget. The two count differently, since IANS asks CISOs for their whole security budget with staff included, so pick one benchmark and cite it consistently.

There's a useful counter-signal in the same research. Security's share of IT spend fell from 11.9% to 10.9%, the first decline in five years, and average security budget growth slowed to 4% from 8% in 2024, which means the budget you're defending is competing against a trend of security budgets flattening. Gartner's February 2026 forecast meanwhile put worldwide information security spending at about $244 billion for 2026. Falling share, rising absolute spend. Both facts belong in the memo.

What sits in the line: endpoint detection and response, managed detection or SOC coverage, email security, immutable backup, awareness training, cyber insurance premiums, and audit or assessment fees. That last one surprises people. A SOC 2 or CMMC assessment is a real five-figure cost with a fixed date, and it belongs in the budget the year before you need the certificate, not the quarter a client asks for it.

CapEx or OpEx: Where Each Line Lands

The template's last column decides who approves each row and how it hits the P&L. Hardware bought outright is capital spend, depreciated over its useful life. Everything subscription-based is operating spend, hitting the current year in full.

That split has been moving one direction for years. Capital budgets made up 13.0% of IT spending in Avasant's 2025/2026 study, down from 21% in 2016, as cloud and SaaS moved spend into operating budgets. Hardware-as-a-service and device leasing push the hardware row across too. The result is a budget with less capital flexibility and more contractual commitment, which is easier to forecast and harder to pause when revenue dips. Worth deciding deliberately rather than by default. We wrote a full piece on CapEx vs OpEx for IT budgeting if you're weighing which model fits your business.

The Line Nobody Sizes: Tool Count

Software licenses rarely get line-by-line scrutiny, because each subscription looks small on its own. The cost that hurts sits next to it. Every tool carries an integration, an admin, a renewal date, and a seat count that drifts upward, and the labor of running eight overlapping tools shows up in the internal staff row instead, where nobody attributes it correctly.

Before finalizing the template, count the tools rather than the dollars. If ticketing, remote access, monitoring, documentation, and reporting each come from a different vendor with a different renewal month, the consolidation question is worth asking during budget season while contracts are visible. A software license audit in the same window finds the seats nobody uses.

This is the problem OpenFrame is built for. OpenFrame, from Flamingo, the publisher of this guide, is open, AI-native infrastructure for IT and security. It covers large areas of the stack in one platform, including RMM, remote access, patching, PSA, MDM, documentation, and SIEM, with AI agents inline: Fae resolves support requests and Mingo runs IT operations. It costs $1 per device a month with 10M AI tokens included, or $0.80 on annual billing, with a 14-day free trial, so MSPs and in-house teams budget one per-device line instead of several per-tool renewals and the same team covers more devices. No vendor lock-in, so the consolidation decision stays reversible. Whether it fits depends on how much of your stack overlaps today, and that's a question the tool count answers before the budget does.

Add a Row for AI Tooling

Templates written before 2025 have nowhere to put AI spend, so it gets scattered. A Copilot license lands in software, an AI ticket triage add-on lands in outsourced IT, and GPU-backed inference lands in cloud. Three rows, no total, and no way to answer the one question leadership will ask, which is what the business spent on AI last year and what it got back.

Give it a tracking overlay like security. Same mechanism: the money is already counted inside cloud, software, and outsourced IT, and the overlay reports the slice. Then the answer to "what's our AI spend" is a number rather than an afternoon of reconciliation.

Size it conservatively for a first year. AI already took 1.9% of the average IT budget in Avasant's 2025/2026 study, the first year it was tracked as its own line, and per-seat assistants are priced per user per month, so deployment scope moves the number more than the sticker price. Budget the seats you'll roll out rather than the full headcount, and put the difference in projects where it can be released if a pilot works.

The reason to bother is pricing pressure. Gartner's 14.2% growth forecast for 2026 is driven largely by AI infrastructure, and that cost reaches small businesses as vendor price increases on tools they already run rather than as new purchases they chose. An AI overlay row makes those increases visible as a category instead of as unexplained drift across six others.

A Planning Calendar That Keeps the Template Current

A budget built once in November is stale by March. Four checkpoints keep the template usable across the year:

1. August and September. Pull last year's actuals, count seats, list every renewal date in the next 18 months, and log which contracts have uplift clauses.
2. October and November. Draft the six categories, apply the benchmarks, build the hardware accrual, and get the security overlay agreed before the number goes to finance.
3. January. Reconcile the approved budget against signed contracts. Renewal quotes that arrived after the draft are the most common source of first-quarter variance.
4. April and July. Check actuals against accrual, especially hardware. If you're under-spending the accrual two quarters running, the useful lives in your table are too short.

The August start matters. Renewal dates are the constraint that shapes everything else, and finding a three-year agreement that auto-renews in December is a very different problem in August than it is in November.

IT Budget Forecast Template

A forecast is the same template with time added. Keep the annual forecast column, add one column per quarter, and reforecast each quarter from three drivers: seat counts, renewal uplifts, and the hardware accrual. For a growth assumption on everything else, Avasant found IT spending rising between 2.8% and 3.1% at the median in seven of the last nine years, so a forecast far above that range needs a named reason, such as a migration or a new site.

Who Owns Each Step: In-House Teams and MSPs

What Breaks a Budget After It's Approved

Three things, mostly. Seat counts grow without anyone updating the per-user lines, so a business that hires 12 people mid-year quietly adds five figures to managed services and licensing without a single new contract. Renewal uplifts land as surprises because the increase was in the agreement all along but never modeled. And project work gets funded out of the contingency row until the contingency is gone by August.

None of those need a better template. They need the template revisited quarterly with actuals beside the forecast, which is the entire purpose of the April and July checkpoints above.

One more thing worth building in from the start: write a one-line justification next to every row. Not a paragraph. One line naming the benchmark, the contract, or the headcount the number is derived from. When the budget gets questioned in six months, and it will, that column is the difference between a five-minute conversation and a rebuild.

Cutting an IT Budget Without Adding Risk

When finance asks for IT budget cuts, start with the lines that cost money without doing work. Reclaim unused license seats, consolidate overlapping tools at their renewal dates, and negotiate uplift clauses before they trigger. Extending a useful life works for supported hardware and costs more for anything that needs paid security updates to stay patched.

Keep backup and security for last, because their cost shows up after an incident rather than on the invoice. Verizon's 2025 report found ransomware in 88% of breaches at small and medium-sized businesses.

In this r/ITManagers thread on balancing cuts with security, the top replies land on the same habit: write down the trade-off behind each cut and get the decision on record.

Use-It-or-Lose-It Budgets

A use-it-or-lose-it budget returns unspent money at year end, which rewards rushed purchases in the last quarter. The hardware accrual is the fix: ask finance to hold unspent accrual in a reserve that carries forward, so a quiet refresh year funds the busy one instead of disappearing.

Take It to Finance

A template's job is to make each number arguable on its own terms. Six categories built from seats and contracts, then checked against a dated benchmark. Managed services split five ways instead of one. Hardware accrued annually rather than spiked. Security carved out with the IANS and Avasant ratios behind it. Every row carrying the sentence that explains it.

IT Budget Proposal and Presentation Template

The proposal finance reads is shorter than the template. One page in this order covers both the IT budget proposal and the presentation that goes with it:

Fill it in with your own numbers, then delete any row you can't justify in one line. Whatever survives is the budget.