IT budget template for mid-sized companies, with a system and archive count

An IT budget template for a mid-sized company should give every system and contract its own line, grouped into applications, finance systems, collaboration, infrastructure, devices, security, managed services, archives and projects. Each line needs an owner, a renewal date, the records it holds and a planned fate, so the budget doubles as a system count before anything is cut.

When to use this IT budget template

Use it whenever technology spend is set or trimmed: the annual budget, a mid-year reforecast, the integration after an acquisition, a cost-reduction program or a managed service contract renewal. It is built for mid-sized companies where the CFO, not a CIO, often owns the IT budget.

It differs from a generic spreadsheet in one way. Every line names a system, an archive or a legacy license, so building the budget also produces a count of the company's systems and a list of archives that a cut could delete.

IT budget categories

Category	Typical lines	Main cost driver	Archive question
Business applications	CRM, help desk, project management, HR and payroll	Seats and tiers	Does cancelling end access to the history?
Finance systems	ERP or accounting platform, payables automation, consolidation	Users and modules	Is older history in this system or somewhere else?
Collaboration	Email, Slack or Teams, video, file sharing	Seats	How far back do mailboxes and channels go?
Infrastructure and hosting	Cloud accounts, servers, networking, colocation	Usage and hardware refresh	What do retiring servers hold?
End-user devices	Laptops, phones, peripherals	Headcount and refresh cycle	Are departed staff devices preserved or wiped?
Security and compliance	Endpoint protection, identity, backup, assessments	Users and requirements	Do backups cover systems that are no longer live?
Managed services and support	MSP retainer, vendor support contracts	Scope and response levels	Does the MSP hold archives for the company?
Data and archives	Backup storage, mail archive, read-only legacy licenses	Volume and retention	Is this the only copy?
Projects	Migrations, implementations, upgrades	Scope	Does the plan include a history export?

The template

Use one row per system or contract. The columns below work in any spreadsheet.

Line ID	Category	System or contract	Business owner	Annual cost	Renewal date	Records held	History from	Fate
{line_id}	{category}	{system_name}	{owner_name}	{annual_cost}	{renewal_date}	{records_description}	{first_year}	Keep, reduce, or retire after export

Add a line note to any row marked reduce or retire, and keep it in the budget file beside the row.

Before an archive line is cut, send the owner a short note.

How to count systems while you build the budget

Pull the accounts payable vendor list for the last 24 months and flag every software, hosting and IT services vendor.
Add company card statements, where many SaaS subscriptions hide.
Export the app list from the identity or single sign-on provider, if the company has one.
Ask the MSP for its asset and license inventory.
Ask each department head two questions: what do you log into every week, and what did you use before it?
Merge and deduplicate, then mark each line as a system of record (holds history) or a utility (does not).

The count of systems of record is the number that matters. Companies with strong records commonly run 10-15+ systems; if your count comes in well below that, look again at card statements and department tools.

How to personalize the template

Client situation	What to adjust	Why
PE-backed with an add-on	Add an entity column and a combined view	Overlapping systems are the first consolidation target
Heavy MSP outsourcing	Split the MSP retainer into the systems it covers	One retainer line can hide ten systems
Financial services firm	Add the security program lines below	Some requirements are mandatory, not discretionary
Recent ERP migration	Keep a legacy access line until the export is verified	Cancelling early can cut off history
Multi-site or remote team	Add device refresh by location	Devices and data drift between sites

Security lines for covered financial institutions

If the client is a financial institution under the FTC's jurisdiction, part of the security budget is required rather than optional. The FTC Safeguards Rule calls for a written information security program, a designated Qualified Individual to oversee it, encryption of customer information in transit over external networks and at rest, and a written incident response plan (16 CFR Part 314). Give each its own budget line so it is never trimmed in a savings round. Whether a client is covered depends on its activities, so confirm coverage before building these lines. This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

When to revisit the budget

At each quarter end, review renewals due in the next two quarters.
Before any cancellation, check the export status in the line note.
After an acquisition, rebuild the system count for the combined company.
At year end, roll the template forward and keep the prior version with its line notes.

What never goes in the budget file

Passwords, API keys or admin credentials.
Exported records, customer lists or any confidential contents of the systems.
Personal data about employees or customers beyond the names of budget owners.
In any summary shared outside the company, including with a referral partner: system names and approximate years only, with no records, no promises of payment and no typed reward amounts.

What the system count says about licensing fit

A long list of systems of record with deep history is one sign that a company could license data through SourceX. The other tests concern the company rather than its tools: a US operating business, 50+ full-time employees at peak (contractors excluded), a documented history measured in years rather than months, records it has the right to license, and a decision-maker at the top who will sponsor the process. The data inventory builder helps turn the budget's system list into an inventory, and who qualifies sets out the criteria in full.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, and rewards become payable only after the buyer pays and SourceX receives its fee. You make the introduction; the company handles everything after it with SourceX. Check any professional rules on referral fees that apply to you; the fractional CFO partner page has more. For the hardware side of the same exercise, see the fixed asset register cleanup guide, and log archives at risk in the risk register template.

Next step

Build next year's budget with the records columns filled in. If the count and history look strong, register as a partner and introduce the company, or send the owner your referral link so they can apply at sourcex.si/apply.

Step 1Share your linkSend your personal link to a company you know.
Step 2Company appliesThe company applies itself at /apply.
Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

What share of revenue should a mid-sized company spend on IT?

There is no single right figure. Published benchmarks vary widely by industry, business model and survey method, and a software company and a distributor will look nothing alike. Compare against a benchmark from your own industry, track your own trend over several years, and judge spend by what each system supports rather than by a ratio alone.

Should SaaS subscriptions sit in the IT budget or in department budgets?

Either works if every subscription appears somewhere with a named owner. Many mid-sized companies keep shared platforms such as email, identity and the ERP in IT, and charge department tools such as marketing automation to the department. The owner column makes the split visible either way, and the system count should include both.

How should read-only legacy systems be budgeted?

Give each one its own line with the records it holds, the years covered and an end date tied to a verified export. Read-only licenses are easy targets in a savings round because nobody uses them daily, which is exactly why they need an owner decision before cancellation. Once the history is exported and verified, the line can be retired.

What is the difference between an IT budget and an IT asset inventory?

The budget covers what the company will spend and why. The asset inventory lists what the company owns or subscribes to, often with serial numbers, license counts and assignments. They overlap on systems and contracts, and building the budget one system per line, with records held and history dates, makes it a usable bridge between the two.

Who should approve cancelling an archive or legacy subscription?

The business owner of the records should approve, with finance confirming the saving and IT or the managed service provider confirming the export is complete and readable. Where an archive carries legal, tax or contractual retention requirements, counsel or the tax adviser should confirm first. The owner or CEO should sign off when the archive is the only copy of years of history.

Free resources

Business exit readiness assessment — A preliminary exit readiness score and checklist for advisors.
SDE vs EBITDA calculator — Seller's discretionary earnings next to market-rate EBITDA.
IRR calculator — Internal rate of return on annual cash flows.
All free tools · MCP resource center

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment