Somewhere past a hundred people, the job changes shape. It is not that a church of 150 is simply a bigger version of a church of 60 — it is that the informal systems holding everything together stop working at the same time nobody notices they have stopped. The pastor who used to know every face by name is now meeting people for the third time and pretending it is the first. The volunteer coordinator who used to text five people about Sunday now has forty names to track across six teams.
None of this shows up as one dramatic failure. It shows up as a slow accumulation of small ones: a guest who never got a follow-up call, a volunteer scheduled twice on the same weekend, a giver who asks in February why their statement never arrived. Church software at this size is not about adding features for their own sake. It is about giving the church a shared memory that does not depend on one person's head.
Why 100 people is where things start to strain
A congregation of 60 to 90 can often run on a spreadsheet, a shared calendar, and a few group texts, because the number of relationships any one person needs to track stays inside what a person can actually hold. Somewhere in the hundreds that number grows past what memory can carry. A church of 200 does not have twice the complexity of a church of 100 — it has something closer to four times the number of relationships to track, because complexity tends to grow with the connections between people, not the head count itself.
That is why the pain at this size rarely looks like “we need more features.” It looks like specific, nameable breakdowns: the serving schedule, the giving record, and the follow-up list all start to slip at once, because they were all being held together by the same overworked volunteer or part-time staff member.
It is also the size where a church usually gains its first real staff, or its first paid part-time administrator, and loses the one advantage a purely volunteer-run church had: nobody was ever quite in charge of the whole record, so nobody was ever quite responsible for its gaps either. Once someone is being paid, even part time, to keep the church running, they need a record that holds still under them — one that does not depend on tribal knowledge from three volunteers who have since moved on.
Volunteer scheduling stops being a group text
At 40 people, one person can hold the greeter rotation, the nursery schedule, and the tech booth in a notebook and it mostly works. At 150 people running six or eight serving teams, the same approach produces double-bookings, no-shows nobody catches until the team is short on Sunday morning, and a background-check requirement that quietly lapses because no one is tracking expiration dates across forty volunteers.
This is the point where scheduling volunteers needs to become a real system rather than a running list in someone's head — roles, assignments, and a place that flags when a background check needs attention, instead of a coordinator trying to remember it. It is also the point where running a serving team without burning people out starts to matter, because a church this size usually has enough people to rotate fairly — if anyone can see who has served three weekends running and who has not been asked in months.
The failure mode is rarely dramatic. It is a volunteer who gets asked to serve four Sundays in a row because the scheduler forgot they had already served last week, and who quietly stops answering the phone after that. A church of this size cannot afford to lose volunteers to avoidable scheduling mistakes, because there are not yet so many people that a few quiet departures go unnoticed.
Giving statements go from a favor to an obligation
A church of 50 might produce giving statements by hand once a year without much strain. A church of 200, with two hundred giving histories to compile, cannot afford for that to be a manual, error-prone January project. Givers expect an accurate statement for tax purposes, and a wrong number or a missing gift is the kind of mistake that erodes trust quietly and permanently.
This is also where tracking giving in a way that respects the giver starts to require real discipline — who can see what, how contributions get recorded consistently across multiple counters, and how the church produces year-end giving statements that are correct the first time, not a scramble in the first week of January. A church this size usually has more than one person touching the giving record — a treasurer, a counting team, maybe a bookkeeper — which means the record needs to be a shared, trusted source, not a personal spreadsheet someone updates when they remember.
None of this requires the church to take payments online or change how it collects gifts. Plenty of churches this size are entirely comfortable continuing to collect through the offering plate or by mail. What changes is what happens to the gift after it is received: whether it is recorded once, in one trusted place, or copied by hand between a notebook, a spreadsheet, and whatever the bookkeeper keeps separately.
The directory stops being one person's contact list
At 60 people, the directory can live in a phone. At 200, it needs to be something the whole team can open, trust, and update without stepping on each other. Households need to be represented correctly, people who have moved on need to be marked rather than silently forgotten, and whoever is following up with a guest needs to see the same information the person running the nursery sees.
A directory your team actually trusts is not a luxury at this size — it is the thing every other job depends on. Follow-up, scheduling, and giving records are all only as good as the person and household data underneath them.
It is also where the difference between a household and an individual starts to matter in ways it did not at 40 people. A family of five that gives as one household, serves on three different teams, and has one child in the nursery needs its record to reflect all of that without duplicating the same address five times or losing track of who belongs to whom. A directory that gets this wrong quietly makes every other job — attendance, giving, follow-up — a little less trustworthy.
What to actually look for in a tool
Given all of that, the shopping list for a 100-to-250-person church is fairly specific:
- A directory that holds households, not just individuals, and that a volunteer can search and trust without asking someone else to confirm it.
- Volunteer scheduling with roles and assignments, plus a way to see who is due for a background check before it lapses.
- Giving records that produce accurate, print-ready year-end statements without a manual January project.
- A follow-up system with a clear owner and date on each next step, so a guest does not depend on one person's memory.
- A price that does not punish the church for growing. Per-member pricing tends to bite hardest exactly in this range, as a church crosses from “small enough to ignore” to “big enough to bill for.”
Notice what is not on that list: staff roles and permissions, a large automation builder, or a dozen integrations. Most churches in this range are still run by one or two trusted admins, not a large staff that needs to be walled off from each other's work. A tool built for a much bigger organization tends to bury this size of church in settings it will never use.
What good enough looks like day to day
The test is not whether the software has an impressive list of features. It is whether the volunteer running check-in on Sunday can find a family in ten seconds, whether the person building next month's serving schedule can see everyone's history at a glance, and whether the treasurer can generate a giving statement in minutes instead of days. SundayBridge was built around that exact size and that exact list — households, serving teams with background-check alerts, and giving records that produce real year-end statements — at one flat price that does not change as the directory grows.
If your church is still deciding whether it has actually crossed the line where a spreadsheet stops being enough, watch for the signs above and make the move before the gaps turn into a crisis rather than after.