What's inside
The workbook separates the annual budget, device-level refresh plan, and assumptions that make the numbers understandable.
- Sheet 1 — Budget: one line per item across licenses and SaaS, hardware, security, projects, managed services, cloud, and connectivity, tagged opex or capex and phased Q1–Q4.
- Sheet 2 — Hardware refresh: one row per device with type, age, replacement quarter, and estimated cost.
- Sheet 3 — Assumptions: editable refresh-cycle defaults, opex and capex definitions, and quarterly-phasing guidance.
How to use it
The sequence matters: classify the spend, phase it when invoices land, build refresh from the asset list, then use later years for direction.
- 1. Tag every line opex or capex so recurring costs and one-time capital purchases can be discussed separately.
- 2. Phase by quarter rather than dividing annual spend evenly.
- 3. Build the hardware refresh sheet from devices approaching or past their refresh cycle.
- 4. Sketch years two and three loosely and revise them annually.
The line this template can't fill in for you
Everything on the budget sheet is knowable from invoices except hardware refresh. That line needs an accurate asset list with ages and warranty dates. QBR Studio can compute that refresh budget from synced PSA and RMM asset data and place it in each client's QBR and zero-login page.
Keep recommendations reviewed and evidence explicit
QBR Studio computes service metrics and drafts client-facing summaries from connected data. Your MSP reviews the evidence, chooses every recommendation, and approves the final report before a client sees it.
What MSP teams usually ask
Is the download really ungated?
Yes. The link above is a direct file download — no form, no email address, no follow-up sequence. If the template is useful, you'll remember where it came from; that's the whole exchange.
Does it work in Google Sheets?
Yes — upload the .xlsx to Google Drive and open it in Sheets. The totals and subtotals use plain SUM and SUMIF formulas, which Sheets handles identically.
Why aren't there pre-filled dollar amounts?
Because they'd be made up, and made-up numbers in a budget template do more harm than blank cells. The structure — categories, opex/capex split, quarterly phasing, refresh cycles — is the part worth templating. The amounts are your data.
What's the difference between this and a technology roadmap?
A budget is the money view; a roadmap is the initiative view. This template deliberately stays on the money side — quarterly spend, refresh planning, three-year direction. Pair it with your roadmap document rather than trying to make one file do both jobs.