Choosing Software
How to Choose Church Management Software: A Pastor's 9-Question Framework
Choosing church management software comes down to nine questions you can answer before you ever sit through a demo. The most important one is who actually uses the tool day to day, which is usually your operations or volunteer coordinator and not the lead pastor. Close behind it: whether serving, giving, and groups live on one record for each person, or in separate silos you cross-reference by hand.
I've sat on both sides of this. I've been the pastor who signed off on a tool nobody used, and I've been the one building one. A 2020 Christian Standard survey found that 91% of the churches it surveyed already run some kind of management system, and just over half (51%) use Planning Center. Most churches aren't deciding whether to use software. They're deciding whether the one they pick fits how their church already works.
Below are the nine questions, then a checklist you can paste into a doc and bring to your team.
What questions should I ask before committing to a ChMS?
Ask who uses it daily, whether the domains connect on one record, whether you can export your own data, how pricing scales, whether volunteers will adopt it, and whether it surfaces who needs care. Those questions sort the tools you'll keep from the ones that become an expensive address book within a year. Each one below has a one-line note on why it matters, because the why is what slips your mind mid-demo when the salesperson is showing you a dashboard.
I've ordered them roughly by how often I've watched them get skipped.
- Who is the daily user, and have they tested it? The lead pastor signs the bill, but the volunteer coordinator lives in the tool every week. If they can't run check-in or build a schedule comfortably, adoption dies.
- Do serving, giving, and groups sit on one record per person? When a regular volunteer also stops giving, you want both on one screen, not two reports and a coincidence you happen to catch.
- Can you export all of your own data, anytime, without asking? Your people's names, contact info, and giving history are yours. A tool that makes export hard is a tool you can never really leave.
- Is pricing flat, or does it stack per module and per person? A low headline price can triple once you add giving, check-in, and groups as separate line items.
- Will your volunteers actually open it? A greeter or small-group leader who needs three logins and a manual will go back to a paper list, and your record goes stale.
- Does it surface who needs care, or only store records? A database tells you who exists. A good tool helps you notice the regular attender who has been showing up less or has come off the serving rotation.
- How does child check-in handle security? Security codes, authorized pickup, and allergy or medical flags are the difference between a system parents trust and one they route around.
- What does switching in and switching out actually cost? Ask how import works from your current tool and how export works if you leave. Both answers tell you how confident the vendor is in keeping you.
- Does the pricing model fit a church, or a startup? Contracts, per-seat fees, and features locked behind higher tiers are built for companies. Flat, no-contract, full-product pricing fits a church budget that answers to a board.
What features should church management software have?
The non-negotiables are a unified profile per person, child check-in with real security, low-fee giving, and clean import and export. Reporting, a member app, and forms are useful but secondary. When the core record is fragmented, no amount of extra features fixes the day-to-day friction.
The way I think about it, features fall into three layers. The bottom layer is the record itself: one profile per person carrying their household, giving, serving, groups, and check-ins. The middle layer is the weekly work that touches that record, like scheduling volunteers, running check-in, receiving gifts, and collecting prayer requests. The top layer is what the tool notices for you, such as a volunteer who has served every single week for two months and may be heading toward burnout. Most tools handle the bottom and middle layers fine. The top layer is where they differ, and it's the layer that changes how you pastor.
How do I match church software to my church's size?
Match the tool to your size by what breaks first as you grow. Under roughly 150 people, simplicity and volunteer adoption matter more than anything else. From about 150 to 800, the cross-referencing problem appears and you need serving, giving, and groups connected. Above 800, multi-campus support, permissions, and how cost scales become the deciding factors.
| Church size | What matters most | Common tradeoff to watch |
|---|---|---|
| Under 150 | Simplest tool your volunteers will use; low or flat cost | A "records" tool can be plenty; don't overbuy |
| 150–800 | Serving, giving, and groups on one connected record | Per-module pricing starts to stack here |
| 800+ | Multi-campus, role permissions, how price scales by people | Silos and manual cross-referencing get expensive fast |
A note on the small end. If you're under 150 and mostly need a clean directory and giving, a records-focused tool like Tithely Church Management (which is what Breeze became in 2025) may be all you need, and that's a fine answer. Buying for the church you wish you were is how tools end up unused.
Who in our church should actually choose the software?
The person who uses it daily should choose it, with veto power, usually your operations or volunteer coordinator rather than the lead pastor alone. The pastor sets the vision and owns the budget, but whoever schedules volunteers and runs check-in every Sunday knows within ten minutes of a demo whether it fits. Buy the tool that person will defend.
I learned this the slow way. I picked something once because it demoed beautifully to me, and our coordinator kept her own spreadsheet for another year because the tool didn't fit her actual workflow. The decision belongs to the people who live in the workflow. Give them the demo logins, let them try to build a real schedule and run a real check-in, and listen to what they say afterward.
The copy-paste due-diligence checklist
CHURCH SOFTWARE DUE DILIGENCE
Daily user
[ ] Who runs this every week? Have they tested it?
[ ] Did they build a real volunteer schedule in the trial?
[ ] Did they run a real check-in in the trial?
The record
[ ] Giving, serving, groups, check-ins on ONE profile per person?
[ ] Household context on the profile?
[ ] Does it flag who's pulling back / over-serving, or just store data?
Money
[ ] Flat price, or per-module / per-seat?
[ ] Total cost with EVERYTHING we need turned on?
[ ] Contract length? Can we cancel anytime?
[ ] Giving fees (platform fee + processor)?
Data ownership
[ ] Can we export all our data ourselves, anytime?
[ ] How does import from our current tool work?
Safety
[ ] Check-in security codes + authorized pickup?
[ ] Allergy / medical flags on kids?
Adoption
[ ] Would a non-technical volunteer open this willingly?
[ ] Is there a member-facing app or portal?
Bring that to your team meeting and let the coordinator drive it.
One honest note about where I land, since I built a tool in this space. Scout is the one I'd put against question two: giving, serving, groups, check-ins, prayer requests, and pastoral notes sit on a single profile per person, and a nightly pass flags who needs attention. Pricing is flat and banded by size ($69 to $199 a month, $35 for church plants), with no per-seat fees, and Scout takes no cut of your giving beyond the payment processor's standard fees. If you're under 150 and mostly need records, Tithely Church Management is probably simpler. If you want Sunday execution and don't mind silos and per-module cost, Planning Center is the strongest option going. Run all three through the nine questions and trust your coordinator's read.
Frequently asked questions
What questions should I ask before committing to a ChMS? Ask who the daily user will be, whether serving, giving, and groups live on one record, whether you can export your own data, whether pricing is flat or stacks per module, and whether it surfaces who needs care or only stores records. Those five separate the tools you'll keep from the ones you'll abandon.
What features should church management software have? At minimum: one profile per person that carries giving, serving, groups, and check-ins together; child check-in with security codes and pickup verification; giving with low fees; and a clean way to import and export your own data. Reporting and a member app are common but secondary to the unified record.
How do I match church software to my church's size? Under about 150 people, prioritize the simplest tool your volunteers will actually use. From roughly 150 to 800, you need serving, giving, and groups connected on one record. Above that, weigh multi-campus support, role-based permissions, and how pricing scales as you add people.
Who in our church should actually choose the software? The person who lives in it daily, usually your operations or volunteer coordinator, not only the lead pastor. The pastor sets the vision and signs the bill, but whoever schedules volunteers and runs check-in every week should test it and have veto power.
Is Planning Center a good church management system? Planning Center is excellent at Sunday execution and worship planning, and it's the most widely used ChMS. Its tradeoffs are that it's priced per module, so cost stacks as you add People, Check-Ins, Giving, and Groups, and those areas stay in separate silos rather than one connected record.
I'm Nic, a pastor who got tired of cross-referencing rosters by hand. Bring the nine questions to your team and pick the tool your coordinator will defend.