CapEx vs OpEx: An IT Budgeting Guide for MSPs and In-House Teams

Updated: November 2026

CapEx is money spent buying or upgrading an asset the business owns and depreciates over time, while OpEx is the recurring cost of running the business, deducted in the year it's spent. For an in-house IT team, the split decides which approval track a request takes, and for an MSP, it decides how fast a proposal moves through a client's finance team. This guide covers what each column holds in an IT budget, how managed services and client onboarding shift the mix, and the 2025 tax and accounting changes that reset the math.

TL;DR

• CapEx. Money spent to buy or upgrade an asset the business owns, deducted over its useful life through depreciation.
• OpEx. The recurring cost of running the business, deducted in full in the year it is spent.
• The MSP shift. A managed contract moves servers, licenses and labor out of the capital budget into one flat monthly line.
• For IT teams. Hardware sits in the capital plan, while subscriptions, cloud, staff and outsourced services run through the operating budget, which approves faster.
• The 2026 twist. 100% bonus depreciation is permanent again, so CapEx carries no automatic tax penalty.

What CapEx and OpEx Mean in an IT Budget

Capital expenditure is money spent acquiring or improving something the business will own and use for years. A rack server, a firewall appliance, twenty new laptops, the cabling run through a new office. The cost lands on the balance sheet as an asset and gets written down over time.

Operating expenditure is what it costs to keep the lights on this month. Microsoft 365 licences, the MSP's monthly fee, cloud hosting, the security subscription riding on the firewall. It hits the income statement in the period it's incurred and it's gone.

The difference between CapEx and OpEx matters because the two live in different approval processes. Capital requests usually go through an annual budget cycle, need a business case, and often need someone above the IT manager to sign. Operating spend fits inside a department budget that's already approved. That's why the same $48,000 can be easy or hard to get depending on which column it lands in.

Depreciation is the mechanism that connects them. The IRS treats computers and peripheral equipment as five-year property, so without bonus depreciation or Section 179, a $50,000 server is deducted across six tax years under MACRS, starting with $10,000 in the first, rather than as a single $50,000 write-off. Cash leaves on day one. The tax benefit arrives in slices.

How CapEx and OpEx Lines Show Up in an IT Team's Budget

An internal IT budget runs to a handful of lines, and only one of them is mostly capital. Capital budgets were 13.0% of IT spending in Avasant's 2025/2026 study, down from 21% in 2016, with cloud and SaaS pulling spend into the operating column.

How a line is priced decides how it moves. Per-seat lines such as Microsoft 365 and identity licenses track headcount, per-device lines such as RMM, patching and endpoint security track the fleet, and cloud tracks usage. A team planning a hiring push should model the per-seat lines first, and a team adding servers, kiosks or shared devices should model the per-device ones.

Cloud deserves its own line rather than sitting inside software. It's operating spend, but a one- or three-year reserved instance or savings plan commitment locks the cost in the way a capital purchase does, so plan it with the same care. Our IT budget planning template has the full column set and a sample budget for a 75-person business.

CapEx vs OpEx: The Side by Side

The pattern that follows from that table: CapEx buys control and ties up cash, OpEx buys flexibility and spreads the cost. Neither is free. A business that runs everything as OpEx has no assets to show a lender. A business that capitalizes everything has a five-year-old estate it can't afford to refresh.

How to Classify a Real SMB IT Stack

Textbook examples stop at buildings for CapEx and salaries for OpEx. IT budgets raise harder calls, such as whether the firewall subscription counts, so here's how a typical 30-person office breaks down.

Two answers worth having ready, because finance teams ask them early. Is software CapEx or OpEx? A perpetual licence the client owns is capital; a subscription is operating. Is SaaS CapEx or OpEx? The subscription itself is OpEx, but the setup work around it may not be, which is its own section below.

The line that trips people up most often is the firewall. The box is an asset with a five-year life. The threat-prevention and content-filtering licence renewing on it every year is operating spend. Same device, two budget columns, and a client who has only ever been quoted one bundled number will not know that until the renewal invoice arrives without the hardware attached. Splitting it in the original quote prevents an awkward conversation two years later.

Capitalization thresholds matter here too. A company's policy sets a floor below which items get expensed regardless of useful life, and the IRS de minimis safe harbor allows up to $2,500 per invoice or item, or $5,000 for a business with an applicable financial statement such as audited financials. A $1,400 laptop falls under a $2,500 floor and gets expensed, while a $6,000 server above it gets capitalized. Ask the controller what the threshold is, and whether a bulk purchase counts as one project, before writing the proposal, because it changes how the same purchase gets coded.

Hardware as a service moves the whole question to the MSP's side of the table. The MSP owns the gear, carries the capital cost and recovers it through the monthly fee, so the client books OpEx. MSPs pricing those agreements compare how fast they earn the outlay back:

The Tax Story Changed in 2025, and So Should the Pitch

For a decade the CapEx to OpEx pitch had a tax kicker attached: buy the server and you wait five years for your deduction, sign the managed contract and you deduct it all this year. That argument is now much weaker, so it's worth checking the proposal deck, or the capital request, before the next finance meeting.

The One Big Beautiful Bill Act, signed July 4, 2025, restored 100% bonus depreciation for qualified property acquired after January 19, 2025, and made it permanent rather than letting it phase down, which the IRS confirmed in Notice 2026-11. Section 179 expensing for 2026 sits at $2.56 million under IRS Rev. Proc. 2025-32, reduced dollar for dollar once purchases pass $4.09 million. Off-the-shelf software qualifies alongside hardware.

Read that against an SMB budget. A client buying $80,000 of servers and workstations in 2026 can generally deduct the entire $80,000 that year through bonus depreciation or Section 179. The five-year drag is gone for anyone under the phase-out threshold, which covers effectively every SMB an MSP serves.

So the tax case for OpEx is no longer automatic. What survives is the cash case, and it's the stronger argument anyway. At the 21% federal corporate rate, a full deduction on $80,000 is worth $16,800 before state tax. The client still had to find $80,000 in cash first. Say that out loud in the meeting and the finance lead will trust the rest of the proposal more, because they already know the tax rules changed.

Your SaaS Rollout Is Not 100% OpEx

Here's a nuance that comes up on every cloud migration.

Under ASC 350-40, when a client signs a hosting arrangement that's a service contract rather than a licence, the subscription fees are OpEx, but qualifying implementation costs get capitalized as a prepaid asset and amortized across the contract term. Configuration and testing work can land in that bucket. FASB's ASU 2025-06, issued in September 2025, removes the project-stage model from Subtopic 350-40, so capitalization starts once management has authorized and committed to funding a project and it's probable that the project will be completed. It takes effect for annual periods beginning after December 15, 2027, with early adoption permitted.

What that means practically: a $60,000 Microsoft 365 and Azure migration is not one clean OpEx number. Part of it may sit on the balance sheet and unwind over three years. If an MSP or an IT manager tells a controller the whole project is operating expense and the auditor disagrees, the rest of the plan loses credibility.

The safe framing is to flag it rather than rule on it. Present the project with the hardware, the recurring subscriptions, and the professional services separated as three lines, then let the client's accountant place them. That takes thirty seconds and buys a lot of credibility.

Is Software Development CapEx or OpEx?

On the books, internal-use software development costs are capitalized only once the project meets the Subtopic 350-40 criteria, while planning, training and maintenance are expensed, so a custom integration or internal tool can land in both columns. For tax, the same 2025 law added Section 174A, which lets a business deduct domestic research and experimental costs, including software development, in the year they're paid or incurred, for tax years beginning after December 31, 2024, as IRS Rev. Proc. 2025-28 sets out. Book and tax treatment can differ, so check both with an accountant.

What Managed Services Do to the Shape of a Budget

The macro numbers explain why this keeps coming up. Gartner's July 2026 forecast puts worldwide IT spending at $6.37 trillion for the year, up 14.2%. Software reaches $1.47 trillion, up 15.5%. Infrastructure-as-a-service grows 29.3% to $287 billion. For an SMB or an internal IT team, both arrive as subscriptions, so that growth lands in the operating column. In a separate Gartner survey of 303 CFOs, run in September and October 2025, three-quarters expected technology budgets to rise in 2026.

For a client, moving to a managed contract does four things to the budget shape. The capital request disappears or shrinks to endpoints only. The monthly number goes up and becomes predictable. Labour cost converts from headcount to service fee. And the refresh cycle stops being a lumpy every-fourth-year crisis.

The pricing reality behind that: managed plans run $100 to $250 per user per month in our breakdown of what IT support costs a small business, so a 20-person business at $200 per user lands at $4,000 monthly, about $48,000 a year. That's the figure a finance lead checks the proposal against, so it belongs in the proposal rather than in the follow-up email.

Per-user pricing is one model of several, and the MSP pricing models guide covers how per-user, per-device, and tiered structures change that math.

One thing to be straight about: converting CapEx to OpEx does not reduce total cost on its own. Over five years a managed contract can cost more in absolute dollars than buying the gear and hiring a part-time admin. What it buys is predictability, coverage, and the ability to scale headcount without a capital event. A client sold a cost reduction who gets a cash-flow change instead is a renewal risk.

Where Client Onboarding Lands in the Budget

Client onboarding is where the shift first shows up on paper, and it produces three different lines. The onboarding project fee is one-off professional services, usually expensed in the period. Hardware the discovery phase flags for replacement is a capital purchase, unless it moves into a hardware-as-a-service bundle. The first monthly invoice starts the recurring operating line.

Quoting those three separately lets the controller code each one on day one, and the same split applies when an in-house team brings in an MSP for co-managed support. Our MSP onboarding checklist covers the 30-day plan behind the project fee.

When CapEx Is the Right Recommendation

An MSP that always recommends OpEx is a vendor. One that sometimes recommends capital is an advisor, and the second one keeps the account.

Capital wins when the workload is steady and predictable. Cloud repatriation data makes the point: in Barclays' 2024 CIO survey, 83% of enterprise CIOs planned to move at least some workloads from public cloud back to private cloud or on-premises infrastructure. For steady, always-on compute, owning the hardware can cost less than renting it.

Capital also wins when the client is profitable this year and wants the deduction now, when data residency or compliance rules make owned infrastructure simpler to evidence, when a lender wants assets on the balance sheet, and when the client has cash sitting idle earning less than the effective cost of the subscription alternative.

Operating spend wins when growth is unpredictable, when the client can't or won't tie up cash, when the technology changes faster than a depreciation schedule, and when the client has no internal capacity to run the asset once it's bought. A business can land here for compute and on capital for endpoints, which is why hybrid budgets are normal rather than a compromise.

How to Run the Conversation With a Client's Finance Team

Technicians pitch capability. Finance leads buy predictability and defensibility. The gap between those two is where good proposals die.

Three moves that change the outcome:

1. Open with the five-year total, not the monthly rate. Finance will build that number anyway. Present it first with the assumptions visible, including the refresh cycle you're removing from their capital plan.
2. Split the proposal into capital, recurring, and one-off professional services. Three clean lines let the controller route each one without asking you to re-quote.
3. Name what gets worse. Higher absolute spend over five years, no asset at the end, a notice period. A finance lead who hears the downside from you stops looking for the one you hid.

Then hand over the decision rather than pushing it. The phrasing that works is close to this: the recurring model costs more over five years and removes a $60,000 capital request plus the refresh in year four; the purchase model is cheaper in total and needs the cash now plus someone to run it. Both are defensible. Which fits the way you're planning cash next year?

That's a conversation between peers about a budget, and the same script works for an IT manager taking a capital request to their own CFO. For clients already looking to bring the total number down before they decide, the tactics in our guide on how to reduce IT costs are a useful pre-step.

A Decision Framework You Can Reuse

Run each client through the same six questions and the recommendation writes itself.

Four or more answers on one side is a clear call. A split usually means the right answer is hybrid: own the endpoints and the network edge, rent the compute, the software, and the labour.

Where the Platform Choice Fits

The tool stack an MSP or IT team runs shows up in the operating line whether anyone names it or not. Every separate vendor is a separate per-endpoint fee, and the stack that gets rebuilt after a price hike costs migration time nobody budgeted. For an MSP, the same tools raise a bookkeeping question too, whether they count as cost of goods sold or operating expense, and peers in r/msp compare their charts of accounts here:

OpenFrame, from Flamingo, the publisher of this guide, is open, AI-native infrastructure for IT and security. Gen1 covers large areas of RMM, remote access, patching, PSA, SIEM, SOC, MDM and documentation in one platform, 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 a month on annual billing with 25M tokens, with a 14-day free trial. For a budgeting conversation that matters in one specific way: it collapses several recurring vendor lines into one per-device number, which is the shape a finance team, the client's or your own, is trying to get to. Flamingo isn't the right fit for everyone, and an MSP or IT team happy with its current stack economics has no reason to move.

CapEx or OpEx comes down to cash timing as much as accounting, and the MSP or IT lead who can walk a controller through both columns with confidence gets the budget approved.