A 180-attendance church in California's Central Valley

A 180-attendance church in California Central Valley runs Breeze, Tithely, Clearstream, Mailchimp, Google Sheets, and Google Forms. Staff: 2 full-time, 3 part-time. Built for harvest-season attendance swings and bilingual follow-up, not for a coastal tech-suburb 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 California’s Central Valley. Two full-time staff and three part-timers. Sundays swing with harvest weeks. Guests include year-round households and seasonal workers who may leave after a few months. Fog mornings and extreme heat both cancel plans. Spanish and English sit in the same foyer.

Why does this mix exist?

They kept Breeze as one database with language tags instead of two tools that double-count families. Tithely covers online gifts when lobby cash thins between harvests. Clearstream carries cancels and Tuesday texts on separate language lists because a blended blast trains half the room to ignore you. Mailchimp stays plain on the free tier with two audiences. Sheets and Forms stay printable when building Wi-Fi dies in a heat wave.

How the week actually runs

Saturday, staff check fog and heat notes before anyone posts a cancel. Clearstream goes out early on the matching language lists with a reply path to the church number. Sunday greeters ask language preference once and tag it the same day. Guest cards enter Breeze before staff leave; harvest workers get a seasonal tag with an expected departure month. Monday, Tithely batches import so giving history stays in one place. Tuesday guest texts leave from the matching language list, not a blended send. Volunteer Sheets key to harvest weeks so Sunday roles do not assume every farm family is free at 8am.

What breaks if you copy this blindly

One English-only automation stream. Separate databases per language that double-count households. Treating every harvest worker as a year-round stewardship unit. Relying on Facebook as the only fog cancel. Assuming every guest will scan a QR after a twelve-hour shift. Forcing image-heavy email that never loads on weak home data.

What they would change next

Train a second bilingual Breeze admin before peak harvest. Print bilingual give cards with large type. Put background-check dates on kids tags before VBS. Name a backup Clearstream sender before fog season. Add a do-not-contact path for harvest workers who ask for space after the season ends.

How should you use this page?

If your church lives with harvest swings and two languages in one foyer, keep one people database, matched follow-up lists, and a cancel channel people answer. Keep human thank-yous. If your town is monolingual with steady year-round attendance, you may need less seasonal tagging and more steady Mailchimp cadence instead.

Field note after an English-only fog cancel

A tule-fog Sunday cancel went out in English only. Spanish-speaking households arrived to a locked lot. They now send Clearstream cancels on both language lists after pastoral approval. Weather care is not optional translation.

Field note after harvest ghosting

August volunteer asks hit families still in the fields at 7am. The Sheet now marks harvest blackout weeks the same way it marks vacation. Agricultural calendars are ministry calendars. If the grid ignores them, Sunday invents resentment.

Field note for the Monday owner

The person who owns A 180-attendance church in California’s Central Valley should finish guest follow-up, cancels, and giving questions without a vendor call. If it breaks the same way twice in thirty days, simplify.

What to verify this week

Ask finance how fees appear beside the subscription line (a church in californias central valley). Hidden costs create Monday surprises.

Ministry proof line

Time the guest text on a real phone in the parking lot, not only on office Wi-Fi.

Keep the public checklist honest: named tools, ordered steps, real cost, last-checked date.

Bad-weather backup

When storms kill the uplink, paper cancels still have to work (a church in californias central valley).

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

Ordinary care finished beats impressive software abandoned (a church in californias central valley).

Who owns admin

On a team sized like 2 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):

• Breeze: $60/mo
• Tithely: Processing fees on this plan
• Clearstream: $29/mo
• Mailchimp: $0 (free tier)
• Google Sheets: $0
• Google Forms: $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, 3 part-time. Region context: US California Central Valley. 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 California’s Central Valley 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 (Breeze, Tithely, Clearstream, Mailchimp, Google Sheets, Google Forms) 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, 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.