A 90-attendance West Virginia coal-hollow church

A 90-attendance West Virginia coal-hollow church runs Breeze, Tithely, Clearstream, Mailchimp, Google Sheets, and Google Forms. Staff: 1 full-time, 1 part-time. Built for night shifts and flood roads, 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 90-attendance Methodist church in a West Virginia coal hollow. One full-time pastor and one part-time admin. Night shifts pull members off Sunday mornings. Flood weeks close creek roads. Guests include local households and relatives visiting from the county seat. Internet thins out when storms hit the ridge.

Why does this mix exist?

They kept Breeze as one login a lay leader can run when the pastor is on hospital runs into town. Tithely covers gifts when shift weeks keep envelopes out of the lobby. Clearstream carries cancels and funeral notices by text and voice because Facebook posts miss households without reliable data. Mailchimp stays plain on the free tier. Sheets and Forms stay printable when the uplink dies.

How the week actually runs

Saturday, staff check creek and ice notes before anyone posts a cancel. Clearstream goes out early with a reply path to the church number. Sunday cards enter Breeze when the uplink holds; otherwise paper cards wait in a labeled drawer. Shift-work tags keep volunteer asks from assuming every family is free Sunday morning. Tuesday guest texts use Clearstream so they do not depend on a personal phone that dies in a cold parking lot. Pantry 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 outage weeks. Treating every household as a day-shift schedule. Relying on Facebook as the only cancel channel. Leaving visiting helpers with export rights. Assuming every guest will install an app with weak hollow signal. Forcing image-heavy email that never loads.

What they would change next

Train a second Breeze admin before the pastor’s next hospital week. Print large-type give cards. Put background-check dates on kids tags before VBS. Name a backup Clearstream sender before flood season. Add a do-not-contact path for visitors who ask for space after they leave.

How should you use this page?

If your church lives with shift work, flood roads, 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 day schedules, you may need less Clearstream voice and more steady Mailchimp cadence instead.

Field note after a creek-flood Sunday

Water covered the low bridge at 6am. Facebook reached county-seat relatives. Clearstream voice reached hollow elders who never open email before noon. The lesson was not more apps. It was the channel people answer when the creek rises.

Field note after a night-shift volunteer ask

A volunteer text assumed a day-shift family could cover nursery after a late Saturday. Greeters now mark shift-work tags on the card, and Monday asks stay honest. Care includes knowing who worked overnight.

Field note after a mission-week export revoke

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

Backup login card

Store a labeled spare login card in the office safe for the backup admin.

One-sentence give path

Can the foyer greeter explain how to give in one sentence?

Restricted care notes

Benevolence notes stay in a restricted view, never in blast templates.

Storm-season drill

Run a full cancel path on a spare phone before storm season starts.

October cuts

Heroic Christmas weeks mean you should have cut steps in October.

Keep named tools, ordered steps, real cost, and a last-checked date near the top (west virginia coal hollow church).

Prefer one clear weekly owner over three half-owned tools (west virginia coal hollow church). Confirm live pricing the week of the vote, not from last year’s PDF (west virginia coal hollow church).

Foyer stewardship

A named steward for the guest card pile comes before tool decisions (west virginia coal hollow church).

Aid privacy rule

If it is benevolence, it is restricted, not broadcast (west virginia coal hollow church).

Coverage gate

Substitute name is required on every renewal packet (west virginia coal hollow church).

Keep cancel messages on a channel people answer when roads close (west virginia coal hollow 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 Appalachian Coalfields. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near under-150 attendance (Methodist), 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 90-attendance West Virginia coal-hollow 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.