Church Ops
How to run a church with a small staff
Run a church with a small staff by deciding clearly what to systematize and what to keep human. Put the repetitive admin (giving records, statements, check-in, rosters, follow-up reminders) on one connected system, and reserve your people's hours for the conversations only a person can have. Let the tools carry the admin so your staff can carry the people.
I pastor, and for years our "system" was a database, a giving platform, a check-in app, a serving spreadsheet, and a group text, none of which talked to each other. The thing that finally clicked for me was noticing how much of our week went to moving the same names between those tools. That is the problem a small staff can actually solve, and solving it gives you your week back.
Where do small-staff churches lose the most time?
Small-staff churches lose the most time to double entry and manual reporting: typing the same person into the giving tool, the database, and the check-in app, then rebuilding the same "who hasn't been around" or "who gave this year" report by hand whenever someone asks. It happens every week, and it adds up fast.
When I watched where our hours actually went, almost none of the loss was in the work that needed a pastor. It was in the seams between tools. A new family fills out a connection card. Someone types them into the database, someone else adds them to the giving platform when they give, and a third person adds the kids to check-in. That is the same family entered three times by three people, and if any one of those steps gets skipped, that family slips out of view. Lifeway Research found that people often fall away during ordinary life transitions without ever making an intentional decision to leave, and the early signs of that are exactly what gets lost in the gaps between disconnected tools.
What should a small church staff systematize versus keep human?
Systematize anything repetitive with no judgment in it: giving records, year-end statements, check-in, rosters, and the reminders that tell you who to reach out to. Keep human anything that involves a relationship, like the follow-up call, the hard pastoral conversation, the decision about who needs care this week. The system surfaces the prompt; a person does the caring.
The line is cleaner than it sounds. A computer is good at noticing that a regular giver who gave every month for two years hasn't given in ten weeks, and that she has been showing up to her group less. It has no idea whether that means she lost a job, lost a parent, or is on a long vacation. So let the system carry the noticing, which it does without forgetting, and let your people carry the conversation, which is the part that was always the point. If you are wondering who actually merits a personal reach-out in a given week, I wrote about that in who needs a pastoral check-in.
Here is how I would sort a typical small-church workload:
| Task | Systematize | Keep human |
|---|---|---|
| Recording gifts and issuing year-end statements | Yes | |
| Kids check-in and printed name labels | Yes | |
| Tracking who served and how often | Yes | |
| Flagging a guest who visited twice | Yes | |
| The follow-up message to that guest | Yes | |
| Noticing a giver stopped | Yes | |
| The call that follows | Yes | |
| Deciding who is ready to lead a group | Yes |
How do you consolidate church tools without losing the personal touch?
Consolidate by mapping every tool you pay for to the job it does, then collapse the ones doing the same job onto one connected record. You keep the personal touch because consolidation removes the admin between you and people, not the people. Fewer tools means fewer places for someone to fall out of view.
Here is the process I would run, and did:
- List every tool and what it costs. Database, giving, check-in, the serving spreadsheet, email, texting. Write down the monthly price and who maintains it. Most small churches are surprised by the total.
- Map each tool to its job. People records, money, participation, scheduling, communication. You will usually find two or three tools fighting over the same job, and a person re-typing data to keep them in sync.
- Find the double entry. Anywhere the same name lives in two systems, that is a seam where someone slips through. These seams cost you more than the subscriptions do.
- Pick the one system that covers the most jobs. The goal is one record per person that holds their giving, their serving, their group, and their check-in history together, so you stop re-typing.
- Migrate instead of rebuilding. Export your people and your giving history and bring them into the new system rather than re-entering by hand. If a vendor's team will run the import for you, take that.
- Keep the human steps human on purpose. Write down which reminders the system will raise and which conversations a person owns. Put names next to the conversations.
The personal touch does not come from your software being friendly. It comes from your staff having the hours to make the call, and from the right person getting noticed before they have been gone three months. If you want a fuller framework for choosing the system in step four, I laid out the questions I would ask in how to choose church management software.
What does a small church actually need from its software?
A small church needs one place that holds each person whole: their giving, their serving, their group, their household, their check-ins, and the notes a pastor keeps. That is the difference between software that creates work and software that removes it. Feature count matters far less than whether everything connects to one record.
The trap for a small staff is buying the biggest system and discovering nobody has time to maintain it. A system that needs a full-time administrator is the wrong system for a church with two or three staff. What helps a small team is a record that updates itself from the things people already do: they give, they serve, they check their kid in, and the picture fills in on its own. When your giving and your participation live on the same person, you can see that the family who used to serve and give every month has pulled back on both, without running a single report. For more on reading participation honestly across serving, giving, and groups instead of leaning on a Sunday headcount, see participation vs. attendance.
This is the one place I will mention what I am building. Scout is the church platform I made because I was tired of being the seam between five tools. It puts giving, serving, groups, check-ins, and pastoral notes on one person record, then tells you in plain language who has pulled back and who is carrying too much, so your small staff spends its hours on people instead of data entry. On giving, Scout takes no cut of donations and makes no money on it; you still pay the payment processor's standard fees (Stripe's nonprofit rate runs 2.2% plus 30 cents per card gift), because the point is to get as much of every gift into the church's hands. The manual method above stands on its own. Scout is the version that does the noticing for you.
Frequently asked questions
What should a small church staff systematize first?
Start with the recurring admin that has no judgment in it: giving records, year-end statements, check-in, group rosters, and first-time-guest follow-up reminders. These eat hours every week and run fine on a system. Keep the actual pastoral conversation human. Systematize the prompt, not the relationship.
How many tools does a small church actually need?
Fewer than most run. A common small-church stack is five or six disconnected tools: one for giving, one for the database, one for check-in, a spreadsheet for serving, email, and a texting app. Each one re-types the same people. One connected system covering people, giving, groups, and check-in removes most of that double entry.
What should a small church never automate?
The conversation. Automate the reminder that a regular giver hasn't given in two months, or that a guest visited twice; do not automate the message that follows. A real pastor or volunteer should make that contact. The system's job is to make sure the right person gets noticed in time, not to do the caring for you.
How do I free up staff time at a small church?
Track where the hours go for two weeks, then cut the double entry first. Most small-staff time loss is re-typing the same people into separate tools and rebuilding the same reports by hand. Consolidate those tools and turn manual reports into standing ones. That usually returns several hours a week before you touch anything pastoral.
Is church management software worth it for a church with two or three staff?
Usually yes, if it replaces tools you already pay for instead of adding to them. The test is whether it removes double entry and manual reporting, not whether it has the most features. A small staff benefits more from one connected record than from a large system nobody has time to maintain.
Nic Moore is a pastor and the founder of Scout. I built it the year I finally added up how many hours my small staff spent re-typing the same families into tools that would not talk to each other.