Budget for admin time not just software fees

Price church software with admin hours included. Free is not free if it burns people out.

By Caleb Brooks · Published September 2026· Editorial standards · Conflict of interest

Field guide page: steps and costs from hands-on church-tech work, written under a pen name. Church names stay private. See how we write and verify.

stewardship

What looks cheap on paper?

A $0 spreadsheet can cost ten hours a week. A $49 tool can save those hours if one named person actually runs it. Elders often compare sticker prices and miss the quiet labor line: who enters the data, who fixes bad exports, who answers the Tuesday reply.

Luke 14:28 asks whether a builder counts the cost before the tower goes up. Church software budgets often count the sticker and ignore the tower’s weekly maintenance. That is how “free” becomes the most expensive line in the packet.

Cheap also looks like four free tools stacked to avoid a $50 database. Duplicate households and lost guest cards cost more than the invoice in pastor hours. Free is not free when Tuesday reconcile burns the only part-timer.

How do you count the real cost?

Write three numbers beside every tool on the invoice: monthly fee, hours per week to keep it honest, and the name of the owner. If the owner cell is blank, the tool is not cheap. It is unfinished work waiting to land on the pastor’s phone.

A volunteer-built system with no backup is also expensive. When that volunteer moves, you pay in crisis mode. Processing fees belong on the same page. A giving tool with a friendly monthly sticker can still move serious money in December fees.

When you price a tool, write the weekly minutes beside the monthly fee before anyone says yes. Bring that note to the elder meeting without a sales slide.

A board packet example

The third row is the expensive one. Free software with no owner is a deferred staff crisis. Put the owner column in every technology request before you vote.

Ask which tool you would drop if staff time got cut by five hours a week. Prefer one maintained list over three neglected apps. Pay for help when the alternative is burning out the only person who knows the login.

Field patterns worth learning from

A church called a ChMS (church management system) switch a one-weekend project. It consumed twelve volunteer evenings and still left envelope numbers wrong. The next budget included a line for admin hours beside every software fee. Tools are cheap until you count the Mondays.

Another church stacked four free tools to avoid a $50 ChMS. The office spent six hours a week reconciling duplicates. They cut three free tools, paid for one database, and recovered the hours for guest follow-up. Free is expensive when nobody owns the merge.

A “free” roster sheet cost a volunteer six hours a week until she quit. The next budget put her hours beside the $0 line and bought a simple database. Admin time is a budget line even when the vendor invoice is blank.

What should change in the next budget meeting?

Add an “admin hours” column to the software page of the budget packet. Show SaaS and processing on one view before the vote. Require a Monday owner and vacation backup on every renewal. Time foyer paths on a phone; desktop-only steps for lobby work get rewritten or removed.

If two people cannot name the weekly job a tool serves, wait before you renew. Hold renewal until the weekly job is obvious without a deck. Sunset a second system within a month when it doubles Monday reconcile.

How to talk about this without shaming volunteers

Counting hours is not an accusation against faithful people who gave evenings for free. It is how the church stops using their love as an invisible subsidy. When you put hours on the packet, you can thank people accurately, budget relief where needed, and stop calling burnout “commitment.”

Some volunteers want the hours. That is fine when the work is bounded, backed up, and truly voluntary. It is not fine when the church’s only path to a clean roster is one person’s unpaid second job. Elders should ask: if this person moved next month, what would we pay to replace the labor?

One practice for this month

When a vendor demo starts, open a blank note and write the weekly minutes beside the monthly fee before anyone says yes. Add the owner name before the meeting ends. If the owner cell stays blank, the answer is not yes yet. Bring last month’s actual hours for your messiest tool, even if the estimate is rough.

Price church software with admin hours included. Free is not free if it burns people out.

Migrations need hours too

The most expensive admin hours often hide in switches: new ChMS (church management system), new giving processor, new texting tool. A weekend cutover promise rarely survives first contact with envelope numbers and duplicate households. Budget migration hours as their own line. If you cannot fund the cutover labor, you are not ready to switch, no matter how friendly the demo felt.

Prefer fewer tools with owners

Every additional login multiplies reconcile time. Before you add a specialty app, ask whether your current database or Sheet can hold the job for another quarter. Fewer tools with named owners usually beat a shelf of niche logins that each need a Tuesday patch. Complexity is an admin-hours decision, not only a features decision.

Common questions

Is a free church tool actually free?

Only if you count staff and volunteer hours. Ten unpaid hours a week can cost more than a paid plan that finishes the job in one. Count total cost of ownership, not sticker price alone.

How should elders compare two tools?

Put sticker price, processing fees, and weekly admin hours on the same board note. Pick the lower total cost of ownership for the jobs you will actually staff.

What if we cannot hire admin help?

Shrink the stack to the jobs one person can keep honest. Document the steps. Name a backup. Do not buy a platform that assumes a systems hire you do not have.