A 180-attendance Idaho potato-belt church

A 180-attendance Idaho potato-belt church runs Planning Center People, Services, and Giving with Clearstream, Mailchimp, and Google Sheets. Staff: 2 full-time, 2 part-time. Built for harvest Sundays, not a metro suite.

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 Idaho’s potato belt. Two full-time staff and two part-time roles. Harvest weeks pull members into the fields on Sundays. Ice fog cancels worship a few times each winter. Guests include local farm households and workers who move with the season. Internet thins out outside town.

Why does this mix exist?

They kept Planning Center People as one login an office backup can run when pastors are on hospital runs into the city. Services keeps weekend teams honest when GroupMe fails during dig weeks. Giving covers harvest Sundays when lobby cash dips. Clearstream carries cancels and funeral notices by text and voice because Facebook posts miss households on weak farm signal. Mailchimp stays plain on the free tier. Sheets stay printable when phones lose coverage in the fields.

How the week actually runs

Saturday, staff check harvest schedules and ice-fog notes before anyone posts a cancel. Clearstream goes out early with a reply path to the church number. Sunday cards enter People when the uplink holds; otherwise paper cards wait in a labeled drawer (an idaho potato belt church). Harvest-season tags keep volunteer asks from assuming every family is free on Sunday mornings. Tuesday guest texts use Clearstream so they do not depend on a personal phone that dies in a cold parking lot. Meal-train lists live on the Sheet with a named lead. A printed Services run sheet stays in the green room.

What breaks if you copy this blindly

Buying a heavy suite you cannot staff during harvest. Treating every household as always free on Sundays. Relying on Facebook as the only cancel channel. Leaving seasonal helpers with export rights. Assuming every guest will install an app on weak farm Wi-Fi. Forcing image-heavy email that never loads. Skipping the printed run sheet because “everyone has the app.”

What they would change next

Train a second People admin before the next harvest peak. Print large-type give cards. Put background-check dates on kids tags before summer camp. Name a backup Clearstream sender before first ice-fog week. Add a do-not-contact path for seasonal workers who ask for space after they leave.

How should you use this page?

If your church lives with harvest absences, ice-fog cancels, and thin volunteer weeks, pick tools that survive offline Mondays and voice cancels. Keep human thank-yous. Prefer one paid people database and one cancel channel people answer. If your town has reliable fiber and steady year-round schedules, you may need less Clearstream voice and more steady Mailchimp cadence instead.

Field note after an ice-fog cancel

Fog closed the highway at 6am. Facebook reached town rentals. Clearstream voice reached farm elders who never open email before noon. The lesson was not more apps. It was the channel people answer when the valley disappears.

Field note after a harvest volunteer ask

A volunteer text assumed a free Sunday during dig week. Greeters now mark harvest-season tags on the card, and Monday asks stay honest. Care includes knowing who is in the fields.

Field note after a seasonal-helper export revoke

Seasonal helpers kept export rights after harvest. They now revoke visitor admin the Sunday the crew leaves. Hospitality includes closing doors.

Live quote for elders

Elders only see packets after a morning vendor page check (an idaho potato belt church).

Closed-road comms

Channels people answer matter most when roads close before dawn (an idaho potato belt church).

Keep named tools, ordered steps, real cost, and a last-checked date on every public page you copy.

Cut any foyer step that still needs a desktop login to finish.

Shelfware starts when Tuesday has no owner. Keep ownership written where a substitute can find it.

Prefer one clear weekly owner over three half-owned tools.

Prefer one clear weekly owner over three half-owned tools.

Confirm live pricing the week of the vote, not from last year’s PDF.

Field discipline

Archive read-only exports after a cutover Sunday; two truths are not a plan.

Copy only what a tired volunteer can finish after second service (an idaho potato belt church).

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 (bundled with People on this plan)
• Planning Center Giving: Processing fees on this plan
• Clearstream: $29/mo
• Mailchimp: $0
• Google Sheets: $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: 150-400. Staff shape: 2 full-time, 2 part-time. Region context: US Intermountain West. 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 Idaho potato-belt church 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, Clearstream, Mailchimp, Google Sheets) 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.