A 280-attendance non-denominational church in the suburbs

A 280-attendance non-denominational church in the suburbs runs Planning Center People, Planning Center Services, Planning Center Check-Ins, and 5 more. Staff: 3 full-time, 2 part-time. Compare this 150–400 attendance mix before you buy another subscription.

By Caleb Brooks · Published August 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 280-attendance non-denominational church in Midwest suburbs. Three full-time and two part-time staff. First-time guests were falling through the cracks between warm greeters and a quiet Monday office.

Why does this mix exist?

Planning Center People holds the first-time guest list. Mailchimp sends a plain Monday welcome email. Clearstream carries the Tuesday personal text off the pastor’s phone. Services schedules weekend teams. Giving already lived in Planning Center, so they refused a second giving login.

How the week actually runs

Sunday cards enter People before staff leave. Monday 9am email goes out with a real reply-to. Tuesday, the connections pastor writes short Clearstream texts for about 15 minutes. Second-time guests move to a week-two checklist with named owners. Overdue steps show on the Monday report. Connection cards are typed before staff leave the building Sunday. The Monday 9am email uses a monitored reply-to, not a no-reply address. Tuesday texts only go to households that have not already replied. Week-two follow-up is a checklist on paper near the admin desk, not a forgotten automation.

What breaks if you copy this blindly

Fancy HTML welcome emails that look like marketing. Leaving paper cards in a basket until Wednesday. Automating Tuesday texts with no human name in the signature. Measuring success by open rate while nobody answers replies.

What they would change next

Set the week-two checklist on day one. Print the reply-to on the physical card so guests who ignore email still know who to call. Train a second text owner before spring break week.

How should you use this page?

If guest follow-up is your hole, copy the 48-hour rule and the human Tuesday text before you buy another funnel product.

Field note after a pretty welcome email

They spent two weeks designing a branded welcome. Opens stayed flat. Replies rose when they switched to three plain sentences, a real reply-to, and a Tuesday text with a pastor’s first name. Guests were not waiting for better design. They were testing whether a person was real.

Field note after a no-reply month

Monday welcome emails went out on time to a monitored address that nobody checked during VBS week. Guests who replied felt ignored. They added the reply inbox to the closing checklist with a name beside it. A real reply-to is not enough. Someone still has to open it before lunch.

Field note after a youth GroupMe leak

A counseling update hit the hospitality GroupMe “so people could pray.” The family found out from a friend. Crisis notes moved back to pastoral-only fields. Midwestern friendliness is not a privacy policy.

Who owns admin

On a team sized like 3 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
• Planning Center Services: confirm current pricing (no monthly figure on this stack page)
• Planning Center Check-Ins: confirm current pricing (no monthly figure on this stack page)
• Planning Center Giving: $0 (included with People subscription)
• Mailchimp: $0 (free tier)
• Clearstream: $29/mo
• Google Forms: confirm current pricing (no monthly figure on this stack page)
• FlockConnect: Confirm current plan

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: 150-400. Staff shape: 3 full-time, 2 part-time. Region context: US Midwest. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near 150-400 attendance (Non-denominational), 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 280-attendance non-denominational church in the suburbs 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, Planning Center Services, Planning Center Check-Ins, Planning Center Giving, Mailchimp, Clearstream…) 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 3 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.