A 110-attendance Montana ranch-distance church

A 110-attendance Montana ranch-distance church runs Breeze, Tithely, Clearstream, Mailchimp, Google Sheets, and Google Forms. Staff: 1 full-time, 1 part-time. Built for blizzard roads and long drives, not for 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 110-attendance nondenominational church in Montana ranch country. One full-time pastor and one part-time admin. Some families drive forty minutes on gravel. Winter cancels are normal. Guests include ranch households and travelers stopping between towns. Internet thins out when weather hits the valley uplink.

Why does this mix exist?

They kept Breeze as one login a part-time admin can run when the pastor is on hospital runs two towns over. Tithely covers gifts when snow keeps envelopes out of the lobby. Clearstream carries cancels and funeral notices by text and voice because Facebook posts miss households without reliable data (a montana ranch distance church). Mailchimp stays plain on the free tier. Sheets and Forms stay printable when the uplink dies.

How the week actually runs

Saturday, staff check road and weather notes before anyone posts a cancel (a montana ranch distance church). Reply-to stays on the church number when Clearstream goes out early. Sunday card flow: Breeze if online, labeled drawer if the uplink dies. Ranch-route tags keep volunteer asks from assuming every family lives in town. Tuesday guests get Clearstream texts; personal phones stay out of the weather failure path. Snow-route driver lists live on the Sheet with a named lead.

What breaks if you copy this blindly

Buying a heavy suite you cannot staff during winter travel weeks. Treating every household as a single in-town address. Relying on Facebook as the only cancel channel. Leaving short-term helpers with export rights. Assuming every guest will install an app with weak ranch signal. Forcing image-heavy email that never loads on slow Wi-Fi.

What they would change next

Train a second Breeze admin before the pastor’s next hospital week (a montana ranch distance church). Print large-type give cards. Put background-check dates on kids tags before summer camp. Name a backup Clearstream sender before first snow. Add a do-not-contact path for travelers who ask for space after they leave.

How should you use this page?

If your church lives with long gravel drives, blizzard cancels, and thin volunteer weeks, pick tools that survive offline Mondays and voice cancels. Keep human thank-yous. Pay for one people database; pick one cancel channel households answer. If your town has reliable fiber and short drives, you may need less Clearstream voice and more steady Mailchimp cadence instead.

Field note after a blizzard cancel

A storm closed the county road at 5am. Facebook reached town rentals. Clearstream voice reached ranch elders who never open email before noon. The lesson was not more apps. It was the channel people answer when the road is closed.

Field note after a forty-minute volunteer ask

A volunteer text assumed an in-town family could cover nursery after a late Saturday chore. Greeters now mark ranch-route tags on the card, and Monday asks stay honest. Care includes knowing how far people actually drive.

Field note after a visiting-helper export revoke

Short-term helpers kept export rights after a summer work week. They now revoke visitor admin the Sunday the team leaves. Hospitality includes closing doors.

What to verify this week

Time the path on a phone in the foyer. Desktop-only steps get rewritten or removed.

Final gate

Write the substitute phone number on the office whiteboard before you renew.

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.

Print before the storm

Have paper cancels ready before the uplink dies (a montana ranch distance church).

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

Choose ordinary faithfulness over shelfware that looked impressive (a montana ranch distance church).

If elders cannot say the weekly job in one breath, wait thirty days (a montana ranch distance church).

Budget honesty

Reject add-ons that need a staff role you will not hire this budget year.

Copy only what a tired volunteer can finish after second service (a montana ranch distance church).

Tools serve people. People still make the hospital calls (a montana ranch distance church).

Prevent December panic

October step cuts prevent Christmas-week heroics (a montana ranch distance church).

Who owns admin

On a team sized like 1 full-time, 1 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: $50/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: under-150. Staff shape: 1 full-time, 1 part-time. Region context: US Northern Rockies. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near under-150 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 110-attendance Montana ranch-distance 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 (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 1 full-time, 1 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.