What churches actually spend on software by attendance

Budget church software by the jobs you will staff, not by envy of a larger campus. Count processing fees, hosting, and admin hours beside every monthly sticker.

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.

stewardshiphonest

Start with the jobs, not the envy

Church software budgets go wrong when elders compare logos instead of Monday jobs. A 90-person plant does not need the stack of a 2,100-attendance hospitality metro. A 280-person suburban church does not prove faithfulness by staying on sticky notes forever. Stewardship here is closer to counting the cost before you build (Luke 14:28) than to collecting apps because a conference booth was friendly.

The useful question is plain: what must happen every week for people to be known, scheduled, thanked, and reached when weather or absence interrupts the plan? Price those jobs. Ignore the feature matrix until the jobs have names and owners.

What small churches often spend

Under about 150 in weekly attendance, many faithful churches run on one people database, one giving path, and free or nearly free email. In our field notes, that often lands near $50-75/month for a simple ChMS (church management system), plus card processing fees on gifts, plus optional texting near $29/month if guest follow-up or cancels leave personal phones. ChurchTrac and similar all-in-one tools can sit lower on the software line when name counts stay honest. Spreadsheets still appear for volunteer grids. That can be wise if one admin keeps the Sheet true every week and a backup exists.

What small churches should not do is stack four free tools 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.

What midsize churches often spend

Between roughly 150 and 400, the bill usually grows because the jobs grow. Planning Center People in our stacks often shows near $14-35/month before Services, Check-Ins, or Giving modules. Clearstream or Text In Church adds another $29-67/month for light pastoral SMS. Processing fees remain the quiet giant on the giving line. A church in this band can stay under a few hundred dollars a month in software and still run honest guest follow-up, weekend scheduling, and online gifts.

Rock RMS enters the conversation for some midsize churches that want one serious household database. The license can look free. Hosting, care plans, and admin hours are not. A Midwest heritage pattern in our library keeps Rock for people and money, then leaves weekend teams in Planning Center Services so worship leads are not blocked by global admin rights. That split can be wise. It is still not cheap if nobody can finish an upgrade weekend.

What large churches actually pay

Over 1,000 in attendance, software is infrastructure. One Southwest hospitality-metro stack in our library runs Rock with a suggested donation near $9,100/year, partner hosting, a full-time systems admin, Clearstream on a larger texting plan, Pushpay on contract pricing, and Planning Center Services for worship teams. The lesson for smaller churches is not “copy that.” The lesson is that serious databases require serious ownership. If your board wants Rock features with volunteer-only care, you are buying a future outage, not a bargain.

Processing fees are ministry money

Elders often approve a $29 texting tool and ignore a few percent of every online gift. December card volume can dwarf the SaaS stickers. Put processing estimates beside software lines on every board note. Compare Pushpay, Tithely, or Planning Center Giving on your real average gift size, not on a vendor’s happy path. Recurring giving helps planning. It does not erase fees. A $5 test gift that clears into the church account still matters more than the color of the give button.

Admin hours belong on the packet

A cheap tool with ten unpaid hours a week is not cheap. Beside every line item, write monthly fee, hours per week to keep it honest, and the owner’s name. If the owner cell is blank, the tool 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.

This is where attendance brackets mislead. A 120-person church with a gifted admin can run a cleaner stack than a 350-person church with no Monday owner. Budget for the human capacity you actually have, then choose tools that fit that capacity. Do not buy a platform that needs a systems pastor you have not hired.

A sober bracket guide

Use this as a starting conversation, not a law:

1. Under 150: One database, one give path, paper where setup time is short. Texting only if personal phones are already failing you. Total software often tens of dollars per month before processing.
2. 150-400: People lists, volunteer scheduling, kids check-in as needed, church texting for guests and cancels. Expect a few hundred dollars per month possible once modules and SMS stack, still far below enterprise hosting.
3. 400-1000: More automation, clearer permissions, likely a part-time ops owner. Dual databases during “transition” become expensive fast.
4. Over 1000: Fund admin labor in the open. Open-source or enterprise, someone still owns upgrades, exports, and quiet-hour rules.

Confirm vendor pricing the week you vote. Screenshots from last year lie.

What faithfulness looks like here

Faithfulness is not the cheapest stack. Faithfulness is not the most impressive stack. Faithfulness is paying for the tools that help you keep promises to guests, volunteers, givers, and families, then refusing the rest. It is telling the congregation the truth about processing fees. It is declining a free trial that creates a second people list you will not close.

If you need product-level help after the budget talk, read the ChurchTrac and Rock reviews for size fit, the Clearstream versus Text In Church comparison for SMS, and the Planning Center versus Breeze comparison for database shape. For the giving launch path, use the online and recurring giving workflows. Those pages are for the how. This page is for the boardroom honesty that should come first.

Count the cost. Name the owner. Buy less than your envy wants and more than your sticky notes can carry. Bring the truth to the next finance meeting while there is still time to choose.

Common questions

Should we budget software as a percent of the whole church budget?

Use jobs and ownership first, not a fixed percent copied from another church. A small plant and a midsize congregation can need different tools at the same percentage. Price the Monday work you will staff, then compare that total to giving capacity with clear eyes.

Where should processing fees appear in the packet?

Beside the giving tool and the online gift totals, not buried in miscellaneous. December card volume can dwarf SaaS stickers. Elders cannot steward what they cannot see on one page.

When is it wise to spend more than our attendance bracket suggests?

When a cheaper path creates unpaid heroics, privacy risk, or a single point of failure you can already name. Spend for capacity you will actually use. Do not spend to look like a larger campus.