A 180-attendance church in a Great Lakes mill city

A 180-attendance church in a Great Lakes mill city runs Planning Center People, Planning Center Services, Planning Center Giving, and 3 more. Staff: 2 full-time, 2 part-time. Compare this 150–400 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 180-attendance nondenominational church in a Great Lakes mill city. Two full-time and two part-time staff. One Sunday service. Winter weather cancels are normal. Many households work shift schedules, so Monday follow-up has to survive late replies. The building Wi-Fi is fine; the bigger constraint is people who cannot answer email until after second shift.

Why does this mix exist?

They standardized on Planning Center for People, Services, Giving, and Check-Ins so weekend tools stay in one login. Mailchimp carries the weekly email. Clearstream handles snow cancels and Tuesday guest texts when email sits unread during factory shifts. They tried Facebook cancels for one winter and missed half the second-shift households.

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 before leaving the office. Services plans lock midweek with blockouts for winter travel. Check-Ins prints allergy notes at classroom doors. When schools close for snow, Clearstream goes out by 7am with a reply path to the church number. Shift workers who miss Sunday still get the Tuesday guest text if they visited the week before. The youth midweek plan uses the same Services account with a separate calendar so Sunday greeters are not recruited for Wednesday by accident.

What breaks if you copy this blindly

Using Facebook as the only cancel channel for shift workers who do not scroll midday. Letting automations send the thank-you. Wide export rights for volunteer leaders. Buying every Planning Center module “for later” without a Monday owner. Counting snow-day absences as pastoral follow-up targets until the absence list becomes noise.

What they would change next

Name a backup Clearstream sender before the next lake-effect week. Put background-check dates on kids tags before VBS. Lock the Monday noon batch time in writing. Train a second People admin before vacation season. Add a printed foyer card with the give URL for guests who will not install another app in a cold parking lot.

How should you use this page?

If you are 150–400 in a winter city with shift workers, unify the Sunday suite and keep a text channel that works when email is slow. Keep human thank-yous. Compare your invoice module by module before you copy the whole suite. If your town does not cancel for weather and most people answer email by 9am, you may need less Clearstream and more Mailchimp cadence instead.

Field note after a shift-change cancel miss

A snow cancel hit email at 6am. Second-shift households never saw it before leaving for work. Clearstream voice after pastoral approval reached people who do not open email before noon. Mill-city calendars need a channel for people already in the car.

Field note after a second-shift welcome miss

A Tuesday text went out at 9am to second-shift households still asleep. They moved guest texts to mid-afternoon and kept voice cancels for snow mornings.

Field note for the Monday owner

The person who owns A 180-attendance church in a Great Lakes mill city should finish guest follow-up, cancels, and giving questions without a vendor call. A second monthly miss is a shrink signal, not an upgrade signal.

Who owns admin

On a team sized like 2 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: $0 (included)
• Planning Center Giving: $0 (included with People) plus processing
• Planning Center Check-Ins: $0 (included)
• Mailchimp: $20/mo
• Clearstream: $29/mo

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: 2 full-time, 2 part-time. Region context: US Great Lakes. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near 150-400 attendance (Nondenominational), 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 180-attendance church in a Great Lakes mill city 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, 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 2 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.