← All Articles
Vendor Management

How to Stop Overpaying for Software: A Nonprofit Technology Audit

By Adam Broidy  ·  8 min read

In nearly every technology audit I conduct at a nonprofit, I find the same thing: the organization is spending significantly more on software than it should be. Not because anyone made bad decisions — but because nobody was looking.

Software spending tends to accumulate quietly. A tool gets adopted for one project and the subscription never gets cancelled. A vendor auto-renews at a higher rate than last year and nobody notices. A department buys a license for a tool that another department has been using for two years. The CFO knows the total line item; nobody knows what's actually inside it.

The result, across dozens of engagements, is consistent: 20–30% of technology spend is either redundant, underutilized, or negotiable downward. For a $10M nonprofit spending $200,000 a year on technology, that's $40,000–$60,000 in recoverable budget.

Here's how to find it.

Step 1: Build a Complete Software Inventory

You cannot audit what you cannot see. The first step is building a complete picture of every software tool your organization is paying for — not just the ones IT manages, but everything, including tools departments bought independently, personal subscriptions people expense, and tools that live in a single person's credit card.

Where to look:

  • Credit card statements: Pull 12 months of statements for any card used for organizational purchases. Software subscriptions show up as small recurring charges that are easy to overlook individually but add up quickly.
  • Vendor invoices: Request a list of all technology-related vendor payments from accounts payable for the past 12 months.
  • Your IT team or vendor: Ask for a list of all software licenses, cloud services, and subscriptions under IT management.
  • Staff survey: Ask department heads to list every tool their team uses, whether or not it's organizationally procured.

Consolidate everything into a spreadsheet. For each tool, capture: vendor name, cost (monthly or annual), number of seats or licenses, contract renewal date, and who the internal owner is.

Step 2: Evaluate Utilization

A license you're paying for but nobody uses is money you're giving away. Once you have your inventory, the next question for each tool is: is anyone actually using this?

Many software tools — particularly SaaS products — provide usage analytics in the admin console. Log in as an administrator and look at active users over the last 90 days. You'll often find that you're paying for 50 seats and 12 people are active users. Or that a tool purchased during COVID for a specific purpose hasn't been opened since.

For tools that don't provide usage data, ask the internal owner directly: when did you last use this? Who on your team uses it regularly? What would you lose if it went away?

The most expensive software is the software nobody uses. The second most expensive is the software everyone uses differently with no one governing the overlap.

Pay particular attention to category overlap — places where you're paying for two or more tools that do the same thing. Project management is a common offender (one department uses Asana, another uses Monday.com, another uses a shared spreadsheet). Document collaboration is another. Often the overlap happens organically and nobody noticed until a budget lens reveals it.

Step 3: Review Every Contract Before It Renews

Auto-renewal is the software vendor's best friend and the nonprofit's worst enemy. Most software contracts automatically renew unless you give 30, 60, or even 90 days' notice before the renewal date. Many organizations miss these windows and are locked in for another year at a price they never consciously agreed to pay.

In your inventory spreadsheet, add a column for renewal date and sort by it. For any contract renewing in the next 120 days, take the following steps:

  • Confirm you actually want to renew before the deadline passes
  • Request a pricing discussion with the vendor — particularly if you're on auto-renewal pricing, which is often not the best available rate
  • Evaluate whether the current seat count matches current usage; right-sizing a contract is often a simple conversation
  • Ask about multi-year pricing if you're committed to the tool — vendors often discount 10–15% for a two- or three-year commitment

Negotiation is not adversarial. Software vendors — especially those serving the nonprofit market — expect to negotiate. They'd rather retain you at a lower price than lose you to a competitor. The key is initiating the conversation before you're inside the auto-renewal window, when you still have leverage.

Step 4: Maximize Nonprofit Discounts

Many of the largest software vendors have dedicated nonprofit programs offering substantial discounts — sometimes 50–80% off commercial pricing. These programs are often not prominently advertised and require an application through a nonprofit technology intermediary like TechSoup.

Major programs worth knowing:

  • Microsoft 365: Eligible nonprofits pay dramatically reduced rates through the Microsoft Nonprofit program. Many nonprofits are paying commercial pricing when they qualify for 75%+ discounts.
  • Google Workspace for Nonprofits: Free for eligible 501(c)(3) organizations.
  • Salesforce Nonprofit Success Pack: Deeply discounted or free access to Salesforce through their Power of Us program.
  • Zoom: Discounted rates through TechSoup.
  • Adobe Creative Cloud: Significant nonprofit pricing through TechSoup.

If your organization is not actively managing nonprofit discount eligibility for your major software vendors, you're likely paying more than you need to. This is particularly common when software decisions were made by someone who didn't know to look for these programs.

Step 5: Build a Governance Process

Finding savings through an audit is a one-time win. Keeping them requires putting a process in place so the same problems don't reaccumulate.

At minimum, you need:

  • A single owner for software procurement. Purchases above a certain threshold (typically $500–$1,000/year) require approval from IT or a designated technology decision-maker. This prevents the quiet accumulation of tools that nobody is coordinating.
  • A renewal calendar. Every contract renewal date lives in a shared calendar with a 90-day advance reminder. Someone is assigned to review each renewal before it occurs.
  • An annual technology audit. Once a year, revisit your inventory, check utilization, and make active decisions about what to keep, right-size, or cancel. Don't let the default answer be "keep everything."

Governance doesn't require bureaucracy. It requires intention — treating software spend with the same rigor you'd apply to any other significant budget category.

The Bigger Picture

A technology audit is almost always worth doing. The savings are real, often substantial, and recoverable within a single budget cycle. But the deeper value isn't the savings — it's the visibility.

When you know exactly what technology you're using, why you're using it, what it costs, and who owns it, you're in a position to make strategic decisions rather than reactive ones. You can align technology investment to program priorities. You can approach the board with a defensible technology budget instead of a line item nobody can explain. You can make the case for new investment because you can demonstrate you've already optimized what you have.

That's what technology leadership looks like. And it starts with something as straightforward as knowing what you're paying for.