Information Technology Budget Guide

The Size-Right Goal Ladder matches the budget goal to four realities: continuity, control, coordination, and resilience. Each level adds management responsibility. Do not move to a higher level because a department requests more software. Move up when the organization’s size, locations, data, or obligations require stronger control.

1. Small organizations: protect continuity. Set a goal that keeps essential work running. Identify the few systems the organization cannot operate without, such as email, point-of-sale software, payroll, scheduling, or customer records. Fund reliable devices, backups, updates, and support before adding optional tools. The goal is not to build a large technology department. The goal is to prevent one failed laptop, lost password, or damaged file from stopping the business.

2. Medium organizations: build control. Set a goal that makes technology predictable across teams. Create a complete equipment list, assign system owners, standardize devices, and document how staff receive access. Fund replacement planning instead of waiting for equipment to fail. A medium organization often has enough staff and systems to create confusion, but not enough resources to absorb repeated mistakes. Clear ownership reduces that waste.

3. Large organizations: coordinate departments. Set a goal that connects separate technology budgets to shared standards. Establish rules for security, purchasing, data storage, vendor review, and support. Departments may still choose tools for specialized work, but they should follow common requirements. A large organization gains value when it reduces duplicate systems, negotiates purchases consistently, and gives leadership a reliable view of technology risks.

4. Enterprise organizations: fund resilience and governance. Set a goal that protects operations across locations, business units, and legal environments. Include disaster recovery, independent security testing, supplier oversight, identity controls, and tested plans for major outages. Enterprise budgeting must account for the cost of failure across the whole organization. A short outage in one office differs from a system failure that affects every location, customer, or public service.

To use the ladder, separate the budget into four practical groups: run, protect, improve, and replace. “Run” covers normal operation, such as internet service, software subscriptions, and technical support. “Protect” covers backups, security tools, access controls, and recovery work. “Improve” covers projects that make service faster or easier. “Replace” covers planned equipment and system renewal. This structure shows whether the organization funds basic reliability or spends heavily on new features while neglecting existing systems.

Set a one-year goal and a three-year direction. The one-year goal should name the specific condition you will reach, such as “every employee uses a supported device and every critical file has a tested backup.” The three-year direction should describe the capability the organization needs, such as “all departments follow one access process and recover essential services after a major outage.” These statements give the budget a test that anyone can understand.

A simple planning table can keep the goal proportional to the organization:

| Organization size | Main budget goal | First evidence of progress | |---|---|---| | Small | Keep essential work running | Critical systems, devices, and backups have named owners | | Medium | Make technology predictable | Equipment, access, renewals, and support follow written procedures | | Large | Coordinate departments | Shared standards reduce duplicate tools and uneven protection | | Enterprise | Maintain resilience at scale | Recovery plans, supplier controls, and security tests work across locations |

The budget should follow the goal. If a small organization cannot restore its accounting files, buying another productivity application does not solve the main problem. If an enterprise cannot identify who controls access to a major system, adding another security product may create more complexity instead of protection.

Putting the Ladder Into Practice

Nia, 34, serves as operations lead for a nonprofit with 28 employees, two offices, grant-funded programs, and a small administrative team. The nonprofit relies on email, cloud document storage, donor records, payroll, a case-management system, and laptops used by field staff. Its current budget lists subscriptions and occasional equipment purchases, but it does not show replacement dates, backup tests, or ownership for each system.

Nia uses the Size-Right Goal Ladder rather than copying the budget from a much larger charity. The nonprofit fits the medium organization level because multiple teams and locations need consistent control. She follows these steps:

1. Name the one-year goal. Nia writes: “By the end of the budget year, every critical system will have an owner, every employee will use a supported device, and the nonprofit will complete two documented file-restoration tests.” The goal gives the board a clear result instead of a vague request for “more IT funding.”

2. List the systems that keep work moving. She records email, cloud storage, donor records, payroll, case management, internet service, and staff laptops. For each system, she notes the owner, renewal date, monthly or annual cost, and consequence of failure. This exercise reveals that the case-management system has no backup export and that three laptops will reach the end of their support period during the year.

3. Divide the needs into the four budget groups. The nonprofit assigns $18,000 to run: software subscriptions, internet service, and technical support. It assigns $6,000 to protect: backup service, multi-factor sign-in, and an annual security review. It assigns $4,000 to improve: a better intake workflow for field staff. It assigns $9,000 to replace: three laptops, two network devices, and one office printer. The total proposed IT budget reaches $37,000.

4. Test the goal against available cash. The nonprofit can fund $31,000 without reducing direct services. Nia does not remove backup testing or supported devices. Instead, she delays the intake workflow to the next budget cycle, negotiates a support renewal, and replaces one laptop immediately while scheduling the other two for the next quarter. The revised first-year budget becomes $32,500, leaving a small gap for the board to approve or remove through another specific cut.

5. Set measures that show whether the goal worked. Nia tracks four results: all systems have named owners, no staff member uses an unsupported device, two restoration tests succeed, and every renewal appears on a calendar at least 60 days before payment. These measures connect spending to operating conditions. They also give the board a reason to continue funding the work next year.

The expected outcome is not a larger technology program. It is fewer urgent purchases, clearer responsibility, and a better chance of restoring work after a mistake or outage. Nia’s budget also gives leadership a useful choice: approve the remaining gap, reduce a named improvement, or accept a defined risk. That is stronger than presenting one unexplained total.

Quick checklist

• Identify whether the organization fits the small, medium, large, or enterprise level. - Write one measurable IT goal for the next budget year. - List essential systems, devices, locations, and data. - Assign an owner and renewal date to each critical system. - Divide costs into run, protect, improve, and replace. - Fund continuity and protection before optional improvements. - Check the one-year goal against available cash. - Record delayed work and the risk it creates. - Set three or four measures that show whether the budget worked. - Review the goal every quarter as staffing, locations, or obligations change.

Mistakes That Distort Size-Right Goals

Using employee count as the only size test

A 15-person financial services firm may require stronger controls than a 40-person retail shop because it handles sensitive records and faces stricter contractual duties. A 20-person nonprofit with two offices may need more coordination than a single-location business with the same headcount.

Do this: judge size by employees, locations, critical systems, sensitive data, service obligations, and recovery needs.

Not this: choose a budget goal from headcount alone.

Funding improvements before continuity

New software can look productive while old devices fail, backups remain untested, and staff lose access to essential records. This mistake creates a polished surface around a fragile operation.

Do this: confirm that essential systems run, protected data restores, supported devices remain available, and access has clear owners before funding optional improvements.

Not this: approve new tools because they offer attractive features while ignoring known failures.

Treating enterprise governance as a small-organization expense

A large or enterprise organization may resist shared rules because departments want speed and independence. Yet separate purchasing, inconsistent access, and unreviewed suppliers create costs that no single department can see.

Do this: require shared standards for identity, security, vendor review, data storage, and recovery. Let departments document a business reason when they need an exception.

Not this: allow every department to select and manage critical systems without a common record.

Setting a goal without a replacement path

A budget may cover this year’s subscriptions while ignoring when laptops, network equipment, servers, or major software platforms need renewal. That approach turns predictable costs into emergencies.

Do this: record purchase dates, expected replacement windows, support expiration dates, and estimated future costs. Reserve money gradually when the organization can afford it.

Not this: wait for equipment to fail and then call the emergency purchase unexpected.

A size-right goal gives technology spending a clear job. Small organizations protect continuity. Medium organizations build control. Large organizations coordinate decisions. Enterprises fund resilience across a wide operating system. When the goal matches the organization’s real obligations, each budget request becomes easier to defend, schedule, and measure - and the organization gains a stronger foundation for every financial decision that follows.

End of chapter one. 39 more chapters and about 71,326 words in the full book.