Most church management software is not built for you. It is built for the five-campus church with a paid data manager, a giving-operations person, and a volunteer coordinator who does that job and nothing else. The features, the pricing, and the sales calls all assume that church. If your congregation runs 60 to 200 people with one bivocational pastor and a part-time secretary, that shortlist is wrong for you before you have even opened the first demo.
This is not a case against software. It is a case for a different shortlist — one built around what a small congregation actually does every week, not around what a large one needs to keep five departments talking to each other.
Why the big-church shortlist does not fit
The largest church management platforms grew up solving a coordination problem: how does a staff of twelve, spread across three services and two campuses, stay on the same page about who is a member, who gave what, and who is scheduled where. That is a real problem, and their answer to it — staff roles, permission tiers, campus-level reporting, approval workflows — is a real answer. It is also completely unnecessary for a congregation where the same two people touch the system every week and already trust each other.
When a small church buys that software anyway, it does not get a smaller version of the same thing. It gets the whole thing, priced for the whole thing, with most of it sitting unused. A volunteer treasurer does not need an approval chain for a contribution she entered herself. A part-time secretary does not need a permission system to keep herself out of a screen she already has every right to see. Every unused feature is still a menu to click past, a setting to configure, and often a line item on the invoice.
There is also a quieter cost: the sales process itself. Software built for a multi-campus budget is usually sold through a multi-campus process — a discovery call, a needs assessment, a custom quote, an implementation specialist. None of that is wrong, exactly. It is simply built for a buyer with a committee and a line item, not a bivocational pastor squeezing the decision into a Tuesday afternoon. If getting a straight answer to “what does this cost, all in, for us” takes three phone calls, that alone tells you who the product was built for.
What a congregation this size actually does every week
Strip the job down to what genuinely repeats. A guest visits and someone needs to notice, follow up, and not let it depend on memory. Attendance gets counted and, eventually, someone wants to see whether it is trending up or down. Giving gets recorded, tracked toward a goal, and turned into a statement come January. A handful of volunteers get scheduled for the jobs that need covering — greeting, nursery, sound. A few small groups meet and need a leader and a roster. None of that requires a staff directory or a campus filter. It requires a record that a part-time person can keep current in under an hour a week.
Our guide to choosing church management software walks through building that job list before you look at a single product. It is worth doing first, because the list itself is the real filter — a vendor's feature grid is not.
It is worth naming what is not on that list, too. A congregation of ninety does not usually run its own accounting department, does not have a communications team separate from whoever writes the bulletin, and is not managing five weekend services across three time zones. The job list for a church this size is shorter than a vendor's pitch deck implies, and that is not a limitation — it is just an accurate description of the work in front of you.
The shortlist that actually applies to you
Once you have your job list, judge every candidate against it, not against everything the vendor shows you. A few things to weigh heavily for a congregation under 200:
One login, not a permission system. If it is you and one other person keeping the church's records, a tool built around restricting what different staff members can see is solving a problem you do not have. It is also a problem you would have to set up and maintain.
A directory a volunteer will actually trust. The record only works if the person entering data believes it is accurate and the person reading it believes the same. That is a smaller ask than it sounds — see our guide on building a directory your team trusts for what that takes in practice.
A flat, predictable price. Per-member pricing punishes the exact growth you are hoping for. Per-feature add-ons turn a simple decision into a running negotiation. A single price you can put in next year's budget without a footnote is worth more than it looks on paper.
Follow-up that has an owner and a date. A guest who visited on Sunday and is still “someone should reach out” two weeks later is the most common way small churches lose people. The tool should make that specific failure visible — our guide to the guest-to-member path covers what that looks like day to day.
What you can skip entirely
Be comfortable saying no to things that sound impressive. A congregation of 90 rarely needs:
- Multi-campus reporting, or any feature whose name includes the word “campus.”
- Staff role hierarchies and approval workflows — these exist to manage disagreement between paid staff, not trust between volunteers.
- A messaging or email platform bundled into the church tool. You likely already have one you trust, and bundling rarely makes either half better.
- Online giving processing bundled at a markup over what your bank or a dedicated processor already charges you.
- A child check-in kiosk you will use for one hour a week, priced like it runs your whole operation.
None of these are bad ideas in the abstract. They are simply not the load-bearing work of a congregation this size, and paying for them — in dollars or in setup time — is a cost with no matching benefit for you.
It helps to say this plainly to a vendor during a demo: “we are not going to use this feature, ever — can you tell me what we are paying for it anyway.” Some will adjust the quote. Some will explain that the feature is bundled and cannot be unbundled. Either answer is useful information, and neither costs you anything to ask for.
What one part-time person can actually keep up with
The honest test of any tool for a small congregation is whether one person, working an hour or two a week around a job or a family, can keep the record current. That means: entering a new guest takes under a minute. Recording a Sunday's giving does not require a second login. Checking who has not been contacted in two weeks does not require building a custom report. If a demo makes you hunt for the answer to any of those, imagine that hunt repeated every week for a year, by someone busier than you are right now.
This is also where the weekly rhythm matters more than any single feature. Our guide to the weekly church admin rhythm lays out what a sustainable Monday-morning routine looks like at this size — and it is short on purpose. If the tool cannot fit inside that routine, the tool is wrong, however many features it has.
A shortlist you can actually run
Put three or four candidates through the same test: your real job list, your real weekly hour, and your real one or two people. Sit down and try to do the work, not watch someone else do it in a sales call. Can you find a person in ten seconds? Record a gift in under a minute? See, at a glance, who visited last Sunday and whether anyone has followed up? A congregation under 200 does not need the tool built for the church five times its size. It needs the smaller, plainer version of the same job — done well, priced flat, and small enough that one tired, competent person can keep it current.
SundayBridge was built around that exact list — people, follow-up, giving, serving, groups, one flat $19 a month, one login — and skips the rest on purpose. The public demo is a fully populated sample church you can walk through before you decide anything, which is the same test this guide has been describing all along.