On this page
What belongs in a client IT budget?
A useful IT budget covers everything the client will spend on technology in the year, not just the MSP's invoice. Typical categories:
| Category | Examples | Billing pattern |
|---|---|---|
| Managed services | The MSP's monthly agreement, backup, security services | Monthly |
| Licences and subscriptions | Microsoft 365 seats, line-of-business software, domain renewals | Monthly or annual |
| Hardware lifecycle | Laptops, servers, firewalls and switches due for replacement | One-time, in a specific month |
| Projects | A new office fit-out, a migration, a security improvement | One-time or spread over the project |
| Labour outside the agreement | Project hours, after-hours work | As incurred |
| Contingency | Unplanned replacements or growth | Reserved, not scheduled |
The recurring categories are usually the largest and the easiest to forecast. The one-time items are where clients get surprised, which is why they should come from an agreed roadmap rather than being added when the quote arrives.
How to build the budget step by step
- Start from last year's recurring costs. Copy the services and subscriptions that continue, then adjust quantities for headcount changes and known price changes.
- Count licences properly. Use current seat counts from the licensing portal or tenant rather than last year's guess, and note renewal dates.
- Add lifecycle replacements. Use device age, warranty dates and vendor end-of-support dates (for example from Microsoft's product lifecycle pages) to decide which hardware and software must be replaced this year.
- Add projects from the roadmap. Every approved or likely roadmap item with a cost belongs in the budget. See How do MSPs build a technology roadmap with clients?
- Schedule by month. Place each cost in the month it will be invoiced. A budget that is right for the year but wrong by month still causes cash-flow surprises.
- Review and approve with the client. Walk through it with the person who signs off, explain each line in business terms, and record which lines were approved, rejected or deferred.
Why a monthly view matters
Annual totals hide timing. A client that budgets for twenty laptops in the year but receives the invoice in a single month needs to know that in advance. A month-by-month breakdown shows when each cost lands, separates recurring from one-time spend, and helps the client's finance team plan cash rather than react to it.
How to track the budget during the year
Approval is not the end of the job. Once a budget is approved, treat it as a fixed baseline and compare it with what was actually invoiced:
- Match invoices to budget lines, so the client can see which costs came in as planned.
- Show the variance, over or under, by line and in total.
- Flag spend that does not match any line, so it can be explained rather than ignored.
- If the plan changes, revise it as a new version instead of quietly editing the approved one.
Reviewing budget against actual at each business review keeps the conversation factual. See What should an MSP QBR include?
Planning beyond this year
A multi-year forecast helps clients see the recurring cycles ahead: a full laptop refresh every few years, a server replacement, licence growth as the business hires. It does not need line-level precision. Projecting each category forward with an expected growth rate, and overriding years where a big project lands, is usually enough for leadership planning.
How MSPortal handles client IT budgets
MSPortal's Budgets live inside the client's branded portal, next to their tickets and roadmap:
- Built from the roadmap. Add Planner items and goals to a budget, carrying their costs, categories and dates. Each line keeps a link to the work it pays for.
- Imports. Bring in lines from Excel, last year's budget, your product catalog or Microsoft 365 licensing, then review them before saving.
- Client approval. Approvers are client users with budget approval permission. They approve or reject each line, or approve all pending lines, and sign with their typed name. Approval locks the budget and gives each line a reference for invoice matching. To revise an approved budget, duplicate it.
- Monthly breakdown and exports. The monthly view applies each line's billing schedule across the year, and the budget can be exported to PDF or Excel.
- Budget against actual. The Actuals tab compares an approved budget with customer invoices synced from ConnectWise Manage, Autotask or HaloPSA. It needs invoice sync and the right permissions, and unmatched spend stays in Unallocated for your team to assign. The budget actuals guide explains what counts as actual spend.
- Five-year forecast. Project each category up to five years ahead with growth rates and overrides, starting from budget totals or Planner costs.
Clients see the budgets their role allows, and the Actuals tab only with invoice access. To see a sample client budget, book a demo.
Related questions
Who should approve a client's IT budget?
The person at the client who controls spending, usually the owner, a finance director or an operations lead. The MSP prepares and explains the budget, but approval is the client's decision and should be recorded line by line.
How do you compare an IT budget with actual spending?
Lock the approved budget as a baseline, then match each invoice to the budget line it relates to. Show the variance by line and in total, and list any spend that does not match a line so it can be explained.
What is the difference between an IT budget and an IT roadmap?
The roadmap says which initiatives happen when and why; the budget says what everything will cost and when it will be billed, including recurring services. A good budget is built from the roadmap so both describe the same plan. See How do MSPs build a technology roadmap with clients?
How far ahead should an MSP forecast a client's IT spend?
One detailed year plus a rougher multi-year forecast works for most clients. Three to five years is long enough to show hardware refresh cycles and licence growth without pretending to know exact prices.