The 2028 IT Plan You Should Start Writing This Year

December 15th, 2027

Team reviewing data dashboards on laptops in an office

December is the wrong month to plan next year's IT budget. By then the calendar is full, the finance team is closing the books, and the only decisions left are the ones that cannot wait. The businesses that start planning in the fall make better choices because they have time to review, prioritize, and compare options.

A good IT plan is not a wish list of technology. It is a short document that connects business goals to specific projects, costs, and risks. It tells leadership what the business needs to operate, grow, and protect itself in the coming year.

Start With an Honest Review

Before planning 2028, review 2027. What worked? What was delayed? Which projects delivered the expected result, and which did not? What broke, and what did it cost?

Look beyond the project list. Review incidents, help desk trends, security events, and employee feedback. A pattern of repeat issues may reveal a foundation problem that should be fixed before new projects begin.

Write down the lessons. A plan that ignores last year's problems will repeat them.

Inventory the Environment

You cannot plan what you have not documented. Update the asset inventory with hardware, software, licenses, and support dates. Include network gear, servers, endpoints, phones, and cloud services.

Flag everything that is past end of support or approaching it. These items become the mandatory part of the budget, the work that has to happen regardless of new initiatives.

Review contracts and renewals too. A software renewal that is not on the calendar becomes a surprise expense.

Cover the Mandatory Work

Lifecycle Replacements

Servers, switches, firewalls, access points, and endpoints all have a useful life. Replace them before failure, not after. The plan should show what is due in 2028 and what can wait.

Security Improvements

Review the security baseline: patching, MFA, endpoint protection, backup, monitoring, and incident response. Identify the gaps and the projects that close them. Security work is easier to fund when it is tied to a specific risk rather than a general concern.

Backup and Recovery

Test the restore process and document the results. If the recovery time is longer than the business can tolerate, the backup plan needs work. Include the cost of any changes in the budget.

Compliance and Insurance

Check the requirements that apply to the business: industry regulations, customer contracts, and cyber insurance questionnaires. Note the deadlines and the evidence the business needs to provide.

Connect Technology to Business Goals

Ask leadership what the business is trying to do in 2028. Open a new location? Hire more people? Improve customer service? Reduce manual work? Each goal has technology implications.

A new location needs network, phones, and security. Hiring needs onboarding and endpoint capacity. Customer service improvements may need CRM integration, call routing, or AI assistance. Manual work reduction may need automation or better data.

Put each goal next to the technology work it requires. That connection makes the budget conversation easier and keeps IT from being seen as a separate cost.

Evaluate AI With Discipline

AI will be part of the 2028 plan for most businesses, but not every AI project deserves funding. Start with the problem, not the tool. Rank candidates by business impact, data readiness, risk, and time to value.

Include the full cost: licensing, integration, training, review time, and security review. Plan a pilot with clear success measures before committing to a company-wide rollout.

A small, measurable AI project is a better first step than a broad initiative with no defined outcome.

Plan the Staffing and Skills

Technology plans fail when no one has time to implement them. Review the team's capacity and skills. Identify the work that will be handled internally and the work that needs a partner.

Include training in the budget. A new platform that the team cannot administer is a liability. Plan for documentation and cross-training so the business is not dependent on one person.

Build the Budget

Separate the budget into categories: mandatory lifecycle, security, business initiatives, and contingency. A contingency line is not pessimism. It is recognition that something will break or change.

Estimate costs with ranges where the scope is uncertain. Label assumptions clearly. Finance teams prefer an honest range to a precise number that is wrong.

Show the cost of doing nothing where it is relevant. An unsupported firewall or an aging phone system has a risk cost that belongs in the comparison.

Set a Quarterly Roadmap

Break the plan into quarters. Put the mandatory work first, then the projects that support the highest-priority business goals. Leave room for unplanned work.

Review the roadmap every quarter. Priorities change, and a plan that cannot adapt becomes obsolete. The quarterly review is also a chance to confirm that completed work delivered the expected result.

Write It Down and Share It

The plan should be short enough to read and specific enough to act on. Share it with leadership, finance, and the people who will do the work. A plan that lives only in the IT provider's folder is not a business plan.

ATS helps businesses build IT strategy and planning that connects technology to business goals. If 2028 is approaching without a plan, contact our team to start the review.

Posted in: IT Support