Every August we get the same email from a church admin. The finance team wants next year's tech line item by mid-September, and nobody in the building can name every tool the church is paying for. The credit card statement has more line items than the ministry staff has fingers.
Before the fall budget conversation starts, thirty minutes with a shared doc will do more than any strategy meeting can. Here is the audit we walk churches through.
Open the last three months of card statements and pull every recurring software charge into one list. Include the free-tier accounts too — the ones that will quietly convert to paid when you cross a user or storage threshold. For each row, write three things: what it does, who on staff uses it weekly, and when it renews.
Then sort by renewal date. Anything renewing before December 31 is the near-term work. Annual plans that lock in for another year are the ones worth looking at first, because a decision made now is a decision. A decision made in January is a receipt.
Three patterns almost always show up. The first is the tool a former staff member set up that nobody has logged into since spring. The second is two tools doing overlapping work — usually a scheduling feature that lives inside your church management software and a separate scheduler somebody preferred. The third is the "free" account that stopped being free at some quiet threshold last quarter.
None of these are failures. They are what happens when a ministry says yes to good tools over a five-year stretch. The audit is not about cutting for cutting's sake — it is about walking into the fall budget meeting with a list you can defend line by line.
A good rule of thumb: if no one on staff can say in one sentence what a tool did for the ministry this year, it does not belong in next year's budget without a conversation.
If you would like a second set of eyes on that list — or a simple template your team can fill in this week — reach out. We help churches enter fall with a tech budget their whole team understands.