Most churches that stall out moving off a spreadsheet do not stall because the software is hard. They stall because someone tried to design the perfect record before typing in a single name — every field a denomination survey might ask for, every custom category a well-meaning committee member suggested, every column “just in case.” A congregation of 100 does not need that. It needs a database that is true on day one, even if it is thin.
The minimum viable church database is smaller than most people expect: one record per person, one household to group them for mail, and one serving role for whoever is actually doing something this month. That is not a permanent ceiling — giving, groups, and pastoral care all layer on top later without touching what you already built. It is a floor. Get these three right and a church of 100 can already answer the questions that matter most on a Tuesday afternoon: who is here, who is family with whom, and who is carrying a role right now.
Why “minimum viable” beats “complete”
A complete database is a moving target. There is always one more field a spreadsheet had — anniversary date, spiritual gifts assessment, T-shirt size from a retreat three years ago — and chasing completeness before you have entered a single real person is how a launch turns into a six-month planning project that never finishes. A minimum viable database asks a narrower question: what is the smallest set of facts that lets someone in your church make a real decision this week?
That question has a short answer. A follow-up coordinator needs to know who a guest is and who owns the next step with them. A treasurer needs to know who gave what. A ministry leader needs to know who is serving where and whether anyone is close to burning out. None of those decisions require forty custom fields. They require three records that are actually true, kept up to date, rather than sixty fields that were accurate the week someone typed them in and stale ever since.
Record one: a person, not a household, not a family unit
The person is the atomic record. Every adult and every child gets their own profile — not a shared entry for “the Andersons,” not a household record standing in for four people. At minimum that profile needs a name, a way to reach them, and a place to note who they are relative to the church: visitor, regular attender, member. Everything else — groups, serving, giving, care, an engagement timeline — attaches to this same profile as it becomes relevant, which is the whole point of starting with the person instead of a spreadsheet row that tries to be several people at once.
If you are still untangling whether a family should be one entry or several, our guide on households versus individuals goes into the reasoning in more depth. The short version for this article: the person is where the facts live, and nothing that matters — a gift, a role, a care note — should ever be recorded against anyone but the specific person it happened to.
Record two: a household, because someone has to get the mail
The household is not a second person record. It is a grouping — the equivalent of an envelope with one address on it, holding whichever people share that address. For a church of 100, that usually works out to something like 35 to 45 households once singles, couples, and families are all counted, and building it is mostly a matter of deciding one rule and applying it consistently: whoever shares a mailing address gets grouped together, full stop.
The household record earns its place in the minimum set for one reason: it is the difference between a directory that looks like a spreadsheet dump and one your team actually trusts enough to use for a Sunday morning lookup. Without it, a greeter searching for “the family that just walked in” gets four unrelated names instead of one family grouped together. Our guide to building a directory your team trusts covers what that grouping needs to look like once you are past the first week.
Record three: one serving role, kept honest
The third essential record is not a full volunteer scheduling system. It is a single, honest fact: who is serving in what role, right now. For a church of 100, that might be eight or ten people — a couple of greeters, a nursery volunteer, someone running sound, a small group leader. The record only needs a role name and the person attached to it. What it must not be is aspirational. Listing someone as “on the greeting team” because they served twice last spring is worse than leaving the field blank, because the first time someone checks who is covering the door this Sunday, a stale record sends them looking for a person who is not coming.
This is the record most churches are tempted to skip in the first week, on the theory that the people serving already know who they are. That is true right up until someone new joins the rotation, or a background-check requirement comes up, or a volunteer quietly burns out because nobody was tracking that they had been covering three roles for four months straight. Our guide on keeping a serving team from burning out goes further into what to watch for once this record exists.
What to leave out on purpose, at least for now
The discipline of a minimum viable database is as much about what you refuse to enter in the first week as what you do. A few categories that feel urgent but usually are not, for a launch:
- Full giving history: giving matters, but reconstructing three years of contributions from a checkbook register is a project of its own. Start recording new gifts going forward; backfill history later, deliberately, when you have time to do it carefully rather than during launch week.
- Every small group: if a group has not met in six months or exists only on paper, it does not need a record yet. Add the groups that are actually meeting this month.
- Pastoral care history predating the system: start new care cases as they arise. Do not try to migrate years of sensitive notes from memory or old files in the first sitting.
- Custom fields nobody has asked for yet: a field you add speculatively is a field nobody keeps updated. Add it when someone actually needs it, not before.
None of this is permanent absence. It is sequencing. A church that enters person, household, and one honest serving role in week one, and adds giving and groups in week three, ends up in a better position than a church that tried to enter everything at once and quit halfway through the member list.
What this minimum set already lets you do
It is worth being concrete about what three thin records buy you, because it is more than it sounds like. With people, households, and one serving role entered honestly, a church of 100 can already run a real directory, mail one envelope per family instead of one per person, see at a glance who is carrying a serving role and who is not, and start a follow-up note the moment a guest gives their name — because the guest already has a person record to attach that follow-up to. None of that requires giving totals, group rosters, or a care history. It requires the three records being true.
If your church is coming off a shared spreadsheet rather than starting from paper, the sequencing question is the same one covered in our guide on moving a church off spreadsheets, which walks through what to migrate first when the temptation is to copy every tab over at once.
A one-afternoon plan for entering the minimum set
If you are staring at a blank system and an old spreadsheet, here is an order that tends to work for a congregation this size. First, enter households from your active attender list, one family at a time, address by address. Second, add each person into their household with a name and a way to reach them — phone or email, whichever you actually have. Third, go through your current list of volunteers — the real one, not the wish list — and record exactly who is serving in exactly what role today. Stop there. Resist the pull to keep going into giving history or group rosters in the same sitting. A church of 100 entered correctly across three record types in one afternoon is further along than a church of 100 entered halfway across six record types over three exhausting weekends.
You do not need forty fields to run a church of 100. You need three that are actually true: a person, a household, and one honest serving role. Everything else can wait for the week it is actually needed.