A 190-attendance church in a North Dakota oil town

A 190-attendance church in a North Dakota oil town runs Breeze, Tithely, Clearstream, Mailchimp, Google Sheets, and Google Forms. Staff: 2 full-time, 2 part-time. Built for rotation schedules and weather cancels, not for a steady suburban calendar.

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 190-attendance nondenominational church in a North Dakota oil town. Two full-time staff and two part-timers. Sundays swing with rotation weeks. Guests include locals and temporary workers who may leave after a few months. Winter weather cancels are real. Data can thin out after long field shifts.

Why does this mix exist?

They kept Breeze as one database with rotation tags instead of treating every temporary household as permanent. Tithely covers online gifts when lobby cash swings with boom-and-bust weeks. Clearstream carries cancels and Tuesday texts by voice and SMS because email alone misses shift workers. Mailchimp stays plain on the free tier. Sheets and Forms stay printable when building Wi-Fi dies.

How the week actually runs

Saturday, staff check weather before anyone posts a cancel. They fire Clearstream early and keep replies on the church line. Sunday greeters mark rotation status on guest cards. Cards enter Breeze before staff leave when the uplink holds; temporary workers get an expected departure week. Monday, Tithely batches import so giving history stays in one place. Volunteer Sheets key to rotation weeks so Sunday roles do not assume every household is free at 8am.

What breaks if you copy this blindly

Treating every boom-town guest as a year-round stewardship unit. Relying on Facebook as the only weather cancel. Assuming every guest will install an app after a twelve-hour shift. Leaving temporary helpers with export rights. Forcing image-heavy email that never loads on weak mobile data.

What they would change next

Train a second Breeze admin before winter. Print large-type give cards. Put background-check dates on kids tags before VBS. Name a backup Clearstream sender before the first blizzard. Add a do-not-contact path for temporary workers who ask for space after they leave town.

How should you use this page?

If your church lives with rotation schedules and hard winters, keep one people database, honest temporary tags, and a cancel channel people answer. Keep human thank-yous. If your town has steady year-round attendance and reliable fiber, you may need less Clearstream voice and more steady Mailchimp cadence instead.

Field note after a rotation ghost ask

Volunteer texts hit households already out on a two-week rotation. They now mark expected away weeks on Breeze tags and pull the Sheet from those tags. Oil calendars are ministry calendars.

Field note after a Facebook-only blizzard cancel

A blizzard cancel posted only to Facebook. Second-shift households never saw it. Clearstream voice after pastoral approval reached people already in the truck. Weather care needs a channel for people who do not live on email.

Field note after a boom-week stewardship scare

Online gifts spiked during a boom payroll week, then collapsed. Elders almost cut ministries. Finance now tags rotation-bonus gifts so one fat week does not rewrite the budget.

Reality check before you renew

Thank people in a human voice even when receipts are automated. People still need a voice.

Final gate

Name who revokes visitor admin the Sunday short-term help leaves.

Size check for this church

Keep a paper cancel card in the foyer when the uplink fails.

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

Print-day confirmation

Confirm the vendor quote on print day, not from memory (a church in a north dakota oil town).

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

Nobody-maintains stacks lose to quiet ordinary faithfulness (a church in a north dakota oil town).

Knowledge capture

Put the last-checked date in the same paragraph as the Monday owner (a church in a north dakota oil town).

Copy only what a tired volunteer can finish after second service (a church in a north dakota oil town).

Coverage card

The backup admin needs a labeled spare login card in the safe, not in a personal phone (a church in a north dakota oil town).

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):

• Breeze: $60/mo
• Tithely: Processing fees on this plan
• Clearstream: $29/mo
• Mailchimp: $0
• 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, 2 part-time. Region context: US Northern Plains. 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 190-attendance church in a North Dakota oil town 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, 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.