Annual software spend
The direct budget impact, reported in terms the board understands.
Nonprofit software stacks grow one grant, one staff member and one free trial at a time. A peer-to-peer fundraising platform for one campaign, a second email tool the events team prefers, a volunteer system nobody updates, an auction platform used once a year and a project management tool that half the staff ignore. Renewals land on a corporate card and nobody reviews them together.
We would inventory every system, map who uses it and for what, check which nonprofit discounts and grants you are and are not using, and recommend what to keep, connect or cancel. Sometimes the best outcome is fewer tools. Sometimes it is connecting two that already work well.
Use bank and card statements, invoices and staff interviews to list every tool, its cost, renewal date, owner, users and the data it holds.
Draw how donors, gifts, volunteers and contacts move between systems, and where staff export and import spreadsheets by hand each week.
Confirm eligibility for nonprofit pricing from Microsoft, Google, Salesforce, Canva and others, and whether your current plans and invoices actually reflect it.
Give a recommendation for each tool with cost, effort and risk, timed to renewal dates and your campaign calendar so nothing changes mid-campaign.
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
The direct budget impact, reported in terms the board understands.
Shows hidden staff time spent moving data between tools.
Ownership is what keeps the stack from sprawling again.
Fewer places means less privacy risk and simpler consent management.
For example, an illustrative animal rescue with twelve staff finds it pays for Mailchimp, Constant Contact and a CRM with built-in email, plus two volunteer platforms and an auction tool used once a year. The audit recommends keeping the CRM's email, moving the events team onto it before the summer renewal, retiring one volunteer platform, and keeping the auction tool on a seasonal plan. It also finds the organization missed eligible nonprofit pricing on its Microsoft licenses.
In the first 30 days we would collect card statements and invoices, interview each team about the tools they use, build the inventory and data-flow map, and check nonprofit discount eligibility. You would see the full list and early savings before any recommendations are final.
No. InTheory does not resell software or take referral fees from vendors. We would base recommendations on how your team works, what you already own and the cost of switching. Often the advice is to keep your current CRM and configure it better, because migrations are expensive for small teams.
We would prepare a short summary covering current spend, recommended changes, savings, risks and timing, written for board members who are not technical. Boards tend to respond well to clear numbers and a phased plan rather than a list of software names.
Often yes. Many capacity-building grants ask what you will change and how you will measure it. An audit gives you a documented current state, a costed plan and clear measures, which makes a stronger application. Whether a particular funder will cover the work is their decision.
Illustrative defaults for a nonprofit. Replace them with your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
Software stack audit: full guide
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.