A congregation of seventy has a lot in common with one of seven hundred: people to know, guests to follow up with, a serving schedule, giving to record, a Sunday to run. What it does not have is staff. There is no finance department, no volunteer coordinator with a full calendar, no one whose whole job is the database. Whatever keeps the records has to be simple enough that the same three or four tired, competent people can run it alongside their actual jobs.
That single fact — no staff, not just fewer people — explains almost everything a church this size should and shouldn't buy. Here is what actually gets used, and where the bigger platforms start working against you instead of for you.
The list is shorter than it looks
Strip away the sales copy and a church under 100 people is really trying to do a handful of things reliably: know who is part of the church and how to reach them, notice when a guest shows up and make sure someone follows up, keep track of who is serving where, record giving accurately enough to trust it and to hand a giver a statement in January, and see, roughly, whether Sunday attendance is holding steady. That is the whole job. It fits on an index card.
Everything else — multi-site scheduling, donor segmentation, workflow builders, custom permission tiers — is solving a problem this church doesn't have yet. It might have it in five years. It does not have it now, and paying to configure a feature you don't need is not free just because the checkbox was already there.
Why the big platforms overshoot
Most of the well-known church management systems were built for, or have grown to serve, churches with paid staff and real complexity: multiple campuses, ministry directors who each need their own view, finance teams that reconcile against a general ledger, volunteer programs numbering in the hundreds. None of that is a criticism of those tools — a church that size needs it. But the same depth that serves a large staff becomes a wall for a volunteer treasurer who logs in twice a month.
The tell is usually the setup itself. If getting started means picking from a dozen modules, defining custom fields before you've entered a single person, or sitting through an onboarding call to understand what you even turned on, the tool was not sized for you. A small church shouldn't need a configuration decision before its first Sunday with the software.
There is also a cost problem hiding inside the complexity. A lot of these platforms price by the number of active people in your database, or charge separately for modules that a bigger church would license as a bundle but a small one has to buy piecemeal. A congregation of seventy people, three staff-equivalent volunteers, and a Tuesday-night budget meeting is a bad customer for pricing built around growth. It ends up paying enterprise-shaped money for a fraction of an enterprise-shaped tool.
None of this means the small church is somehow lesser for not needing the depth. It means the shopping list is different. A congregation under 100 people should be comparing tools on how quickly a tired volunteer can do the one thing they came to do — not on how many modules light up green on a comparison chart.
What actually matters: people and households, not org charts
The center of any church record should be the person and the household, not a department. One profile per person — their groups, their serving, their giving, their care history, a timeline of how they've engaged — is worth more to a small church than any dashboard. It is the difference between remembering a family and having to ask someone who remembers.
If your directory is still scattered across a phone, a binder, and someone's memory, that is the actual starting point, not a feature list. Our guide on moving off spreadsheets walks through making that move without losing anything, and households vs. individuals covers a decision that trips up a lot of churches early: whether to track people as a family unit or one by one.
Following up on a guest is the whole game
Ask any small-church pastor what actually causes people to stick and the honest answer is rarely the sermon or the songs. It is whether someone followed up with the visitor who came alone, sat in the back, and left before anyone said hello. A church under 100 people can do this well precisely because it is small — but only if someone is assigned to the follow-up and a date is attached to it. Without an owner and a date, a good intention quietly becomes nothing.
This is worth more configuration attention than almost anything else on this list. See the guest-to-member path for what that actually looks like week to week.
Giving records that hold up in January
A church this size still has real giving to track, and the requirements don't shrink just because the numbers do. You need contributions recorded accurately, a way to correct a mistake, and a statement you can hand a giver at year end that they can trust with their taxes. None of that requires the church to also process payments — recording giving and taking giving are two different jobs, and a small church can use a payment processor it already trusts for the second while keeping the record of the first somewhere built for records.
Tracking giving that respects the giver and getting year-end statements right cover the mechanics. SundayBridge records and edits contributions and generates those year-end statements; it does not take the payment itself.
A schedule your volunteers can actually see
At this size, the same eight or ten people are usually rotating through nursery, greeting, sound, and setup. The software's job is small: show who is scheduled, flag a background-check alert if one is needed, and make it obvious who is carrying too much of the load. It does not need a shift-bidding marketplace. It needs to be honest about who is burning out. Serving team without burnout and scheduling volunteers at a small church go into how to spot that before it costs you a volunteer.
What to skip for now, and what to leave read-only
A church under 100 people rarely needs a child check-in kiosk, CSV import from six other systems, staff-only permission tiers, or built-in messaging. Buying those before you feel the actual gap just adds screens nobody opens. Attendance and a Sunday school roster, on the other hand, are worth tracking even at this size — but they are fine as something you read and chart, not something that needs its own data-entry workflow beyond what your greeter already does at the door.
SundayBridge is built around exactly this shape: one flat plan, the modules above, and nothing to configure before your first Sunday with it. It does not send email, does not process payments, and does not import your old spreadsheet for you — we offer to load it by hand instead, for free, which turns out to matter more than another integration would have.
The one meeting a month it should survive
A useful test for any tool at this size: could the person who runs it be out sick for two weeks without anything breaking? At a church with no staff, the software has to be legible enough that a second person — a spouse, an elder, next year's volunteer — can open it cold and find what they need. That is a harder bar than it sounds. It rules out anything that depends on tribal knowledge: a custom report only one person remembers how to build, a field nobody explained, a workaround that lives in someone's head instead of the system.
It also argues for fewer screens rather than more. A monthly finance meeting at this size usually just needs three numbers: what came in, what the trend looks like against a goal, and whether anything looks off. If getting those three numbers means exporting a spreadsheet, pivoting it by hand, and cross-checking it against last month's printout, the tool has failed the test even if it is technically capable of showing the number somewhere.
Buy for the church you are, not the one you might become
It is tempting to buy ahead — to pick the platform built for a church of a thousand so you never have to switch if you grow into it. In practice, most churches under 100 people stay in that range, or grow slowly enough that switching later, once the need is real, is far cheaper than carrying complexity you don't use for years. Buy for the Tuesday you actually have.