A 140-attendance multigenerational church on the Plains

This 140-attendance Plains church runs Planning Center People and Services, Pushpay for giving, Gmail for the weekly email, Google Sheets for attendance, and Facebook for urgent notices. Software is about $14/mo plus giving fees.

By Caleb Brooks · Published February 2026· Editorial standards · Conflict of interest

Field guide page: steps and costs from hands-on church-tech work, written under a pen name. Church names stay private. See how we write and verify.

What kind of church is this?

A 140-attendance multigenerational Baptist church on the Plains. One full-time pastor and two part-time staff. Harvest weeks thin the volunteer roster. Snow Sundays need a cancel notice older members will actually see.

Why does this mix exist?

They already paid for Planning Center People. Pushpay stayed because older givers knew it from a sister church. Gmail, Sheets, and Facebook cover the rest so software stays near $14/month plus giving fees.

How the week actually runs

Greeters mark attendance on a Google Sheet before they leave. The secretary updates Planning Center on Monday and pulls a quiet absence list for care calls. Envelope and online gifts batch together Monday morning. Weather cancellations post on Facebook only after the pastor approves the wording. Greeters finish the Google Sheet before they leave the foyer. Monday, the secretary updates Planning Center and prints a short absence list for elders who still prefer paper. Harvest and winter storm weeks get Services blockouts a month ahead so nursery and greeter slots are not empty the same Sunday.

What breaks if you copy this blindly

Facebook-only cancels miss people who left the platform. A Sheet without a named Sunday enterer goes blank on vacation weeks. Pushpay without a Monday batch owner delays first-gift thank-yous. Cancelling church only on Facebook. Leaving the Sheet with no named Sunday enterer during vacation. Recruiting harvest-season greeters the same morning you need them.

What they would change next

A simple texting tool for snow days. Nursery and greeter blockouts locked before harvest, not during it. A printed booth copy of the volunteer grid when rural Wi-Fi drops. Add a simple SMS cancel path for members who left Facebook. Lock nursery and greeter blockouts before harvest, not during it.

How should you use this page?

If you are under 150 with seasonal work rhythms, keep one paid people database and refuse marketing platforms until a person owns them every week.

Field note after harvest season

Attendance dipped for six weeks and the CRM looked like a crisis. It was harvest. They added a seasonal work tag and a September care plan instead of buying a retention suite. Rural calendars are not suburban funnels.

Field note after a youth-leader handoff

The youth leader left for college with group chats still on a personal phone. Parents lost the thread for two weeks. Moving texts to a church Clearstream inbox before graduation kept continuity without another software purchase.

Field note after a harvest-supper double book

The fellowship hall was promised to two families on the same Saturday because the Sheet and the verbal calendar disagreed. They now require building-use requests on one Form that writes to the Sheet before anyone says yes. Plains hospitality still needs one source of truth.

Board-ready proof

Time the path on a phone in the foyer. Desktop-only steps get rewritten or removed.

Who owns admin

On a team sized like 1 full-time, 2 part-time, one named staff lead should hold master admin for the people database and any tool that can export households or send church-wide texts. Ministry directors get limited views for their rosters. Greeters and foyer volunteers should search and check in, not download the full list.

Write a backup admin before vacation weeks. Role changes get a five-minute access checklist the same week: remove logins, remove export rights, confirm the backup still works. Leftover volunteer IT access is how old Sheets and pastoral notes leak into personal inboxes.

If engineers or “techy” members help, they still need a staff owner. Unpaid IT without an owner becomes a single point of failure when that member moves.

What this stack costs

Software lines from this page (confirm the week you brief elders):

• Planning Center People: $14/mo
• Pushpay: processing fees only on this plan
• Planning Center Services: $0 (included)
• Gmail + Google Groups: $0
• Google Sheets: $0
• Facebook Page: $0

Add card processing fees beside any giving tool. December volume can dwarf the SaaS stickers. Put weekly admin hours beside each line on the board packet. A cheap tool with unpaid heroics is not cheap.

Attendance bracket on this page: under-150. Staff shape: 1 full-time, 2 part-time. Region context: US Great Plains. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near under-150 attendance (Baptist), you can staff the Monday jobs these tools assume, and you will name owners for guest follow-up, scheduling, and giving reconcile. Steal the weekly rhythm and the permission habits first. Steal the logo list second.

Good signs you are ready: cards leave the building with a named enterer, texts leave a church-owned number or watched inbox, and one person can explain each tool in one sentence.

What breaks first

What usually breaks first when churches copy A 140-attendance multigenerational church on the Plains without the staffing: guest cards sit until Wednesday, personal phones become the cancel channel again, dual databases appear “for transition,” or export rights stay with former volunteers. The tools (Planning Center People, Pushpay, Planning Center Services, Gmail + Google Groups, Google Sheets, Facebook Page) only work when the Monday owners are real.

Refuse a second people list. Refuse automations nobody watches. Refuse measuring success by open rates while replies sit unread. If your staff hours are thinner than 1 full-time, 2 part-time, shrink the stack before you expand it.

Board packet checklist

1. Name master admin and backup for the ChMS (church management system).
2. List monthly software fees and estimated processing fees on one page.
3. Write the weekly job each tool serves in one sentence.
4. Schedule a ninety-day pre-renewal review with actual hours beside each fee.
5. Confirm vendor quotes the same week elders vote.

Keep churchRef and slug stable when you link workflows to this stack. This page is a field pattern, not a mandate to buy everything at once.