A nonprofit technology budget should show more than subscription totals. It should make clear which services are essential, who depends on them, what risk they carry, and what would happen if funding changed.
1. Build an inventory around responsibility
List software, hosting, domains, devices, support contracts, implementation partners, and material cloud services. For each item, record the owner, renewal date, term, cost, number of paid and active users, data held, integrations, and exit requirements.
Usage frequency is useful, but it is not a deletion rule. An emergency-notification system, annual reporting tool, backup service, or donor-data export may be used rarely and still be essential. Classify each item by mission value, operational dependency, security or compliance need, and recoverability before looking for cuts.
2. Review the expensive boundaries
Unused seats are an easy place to start, but the larger costs often sit between systems: duplicate data entry, fragile integrations, consultant-only knowledge, and exports that cannot be reused. Ask whether two products overlap, whether the higher tier is needed, and whether the organization could move its data if the vendor relationship ended.
Nonprofit offers can help, but discount percentages and eligibility change. Check current terms with the vendor or a maintained catalog such as TechSoup instead of building a budget around a general claim. Include administration fees, implementation, training, support, migration, and future renewal pricing. Open-source software removes a license fee, not the need for hosting, security, maintenance, and capable support.
Annual billing may cost less than monthly billing, but it also reduces flexibility. Use it for established tools with a named owner and a clear renewal decision—not simply because the checkout page advertises a percentage.
3. Decide what to protect, change, and stop
Put each material system into one of four groups:
- Protect: essential and appropriately sized; fund maintenance, security, and recovery.
- Improve: necessary, but ownership, configuration, training, or integration needs work.
- Replace: the capability is needed, but the current cost or constraint is no longer acceptable.
- Retire: no longer needed, duplicated, or safely replaced by an existing service.
For replacement and retirement decisions, plan data export, retention, account closure, integration changes, and staff communication. A canceled invoice is not a completed exit.
Review the inventory before budget planning and again ahead of major renewals. Track total cost, active use where meaningful, upcoming commitments, unresolved risks, and savings actually realized. The goal is not the lowest technology spend. It is a budget that protects the mission and leaves leadership with fewer surprises.