The Nonprofit Stack Audit Worksheet

Most nonprofits do not have a software problem so much as an inventory problem. Tools get added one at a time, each solving a real need in the moment, and a few years later nobody on staff can say with confidence exactly what the organization pays for, when each contract renews, or who actually uses each seat.

Before any consolidation conversation is worth having, do the audit first. It takes an afternoon and it changes every conversation that follows.

What to list for every tool

• The tool name and what it is actually used for, in plain language.
• Annual cost, including any per-seat or per-transaction fees that scale with usage.
• Renewal date and notice period — many contracts auto-renew unless you cancel 60–90 days out.
• Who on staff owns the relationship, and who would notice if it disappeared tomorrow.
• What data lives only in that tool, and nowhere else.

Questions worth asking every vendor

Once the list exists, a short round of vendor questions usually surfaces the real cost of staying put: what does the next tier of seats cost, what is not included in the base price, and what would it take to export everything you own if you left.

The point of the audit is not to justify switching. It is to know, in writing, what staying costs.

What the audit usually reveals

Two patterns show up again and again once organizations do this exercise: a handful of tools nobody remembers approving, and two or three systems quietly doing the same job for different teams. Neither is a surprise once you see it in one place — it is only invisible when it is spread across seven different invoices.

Key takeaways

• Inventory every tool with its real annual cost, renewal date and owner.
• Note contract auto-renewal windows before they sneak up on you.
• Ask every vendor what a real export of your own data looks like.
• Look for tools quietly duplicating each other across teams.