A 540-attendance nondenominational church in the suburbs

A 540-attendance nondenominational church in the suburbs runs Planning Center People, Planning Center Services, Planning Center Giving, and 5 more. Staff: 5 full-time, 3 part-time. Compare this 400–1,000 attendance mix before you buy another subscription.

By Caleb Brooks · Published September 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 540-attendance nondenominational church in Southwest suburbs. Five full-time and three part-time staff. Two Sunday services. First gifts used to disappear into a receipt with no pastor voice.

Why does this mix exist?

They standardized on Planning Center for People, Services, Giving, Check-Ins, Forms, and Automations so staff were not hopping suites mid-Sunday. Mailchimp sends the weekly email. Flocknote-style pastoral care notes (FlockConnect in their writeup) stay separate from the public email list.

How the week actually runs

Sunday gifts close Monday noon. Automations only apply a first-gift tag. A person writes a no-amount thank-you card the same afternoon. Services runs both services with required blockouts. Check-Ins prints allergy notes. Ministry directors get limited People permissions; exports stay with the executive pastor. Friday, the Services coordinator checks open positions for both services and texts only the people who can actually cover, not the whole team list. Kids Check-Ins opens fifteen minutes before the first service so allergy labels print before the rush. Mailchimp’s weekly send is locked Thursday so Monday thank-you work is not competing with newsletter edits.

What breaks if you copy this blindly

Letting automations send the thank-you. Buying every Planning Center module “for later.” Wide export rights for volunteer leaders. Copying the FlockConnect care notes into the all-staff Slack. Running a second giving tool “during the transition” for a year. Letting student ministry keep a shadow spreadsheet of teens that never syncs to People.

What they would change next

Lock the Monday noon batch time in writing. Forbid automation sends on first gift, not only “for now.” Quarterly permission reviews. Name a backup Monday thank-you writer before the next staff vacation. Put the Mailchimp audience sync failure alert on a watched inbox, not a personal Gmail.

How should you use this page?

Growing suburban churches should unify the Sunday suite and keep human thank-yous. Compare your invoice module by module before you copy the whole suite.

Field note after a second service launch

They launched a second service before guest follow-up had a Monday owner. Attendance rose. Follow-up debt rose faster. They froze new programming for six weeks, named one connections owner, and only then restaffed greeters. Growth without a Monday owner is just a taller unread pile.

Field note after an automation thank-you

An automation sent a first-gift email with the dollar amount in the subject line. A giver replied asking who else could see it. They killed amount-in-subject sends the same day and returned to handwritten no-amount cards on Monday afternoon. Speed without dignity is not stewardship.

Field note after a Check-Ins printer jam

Allergy labels jammed during the first-service rush. They now run a test print fifteen minutes early and keep a paper backup clipboard. Heat and dust are ministry conditions too.

Board-ready proof

Ask finance how fees appear beside the subscription line (a growing suburban church in the southwest). Hidden costs create Monday surprises.

Who owns admin

On a team sized like 5 full-time, 3 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: $35/mo
• Planning Center Services: $0 (included)
• Planning Center Giving: $0 (included with People) plus processing
• Planning Center Check-Ins: confirm current pricing (no monthly figure on this stack page)
• Mailchimp: $20/mo
• Planning Center Automations: $0
• Planning Center 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: 400-1000. Staff shape: 5 full-time, 3 part-time. Region context: US Southwest. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near 400-1000 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 540-attendance nondenominational 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 Giving, Planning Center Check-Ins, Mailchimp, Planning Center Automations…) 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 5 full-time, 3 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.