A 120-attendance church in an Appalachian small town

A 120-attendance church in an Appalachian small town runs Breeze, Tithely, Google Sheets, and 3 more. Staff: 1 full-time, 2 part-time. Compare this under-150 mix before you buy another subscription.

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 120-attendance independent Christian church in a small Appalachian town. One full-time pastor, a part-time office admin, and a part-time kids lead. Broadband is uneven. Funeral weeks and weather cancels are common. Software has to work when the building Wi-Fi does not.

Why does this mix exist?

Breeze keeps people, giving history, and volunteer tags in one login two part-timers can share. Tithely covers online gifts without a second database. A Google Sheet stays the Sunday grid because it prints. GroupMe covers one Saturday reminder. Clearstream reaches people who will not see a Facebook post during a snow day. Google Forms catch benevolence and volunteer interest without another paid suite.

How the week actually runs

Monday, Tithely batches import into Breeze. The office admin updates the Sheet from Breeze tags before Wednesday. Saturday at 9am, one GroupMe reminder goes out. If schools close for ice, Clearstream sends a cancel text by 7am with a reply path to the church number. First-time guests get a personal Clearstream text on Tuesday, not a blast. Benevolence forms never land in the volunteer GroupMe. A printed Sheet hangs in the foyer as the fallback when the projector network dies.

What breaks if you copy this blindly

Making Facebook the cancel channel for a town that still listens for phone trees. Letting benevolence forms sit in a shared Drive folder. Skipping the printed Sheet because “everyone has phones.” Giving every deacon Breeze export rights. Running a second give page “for the fair booth” with no sunset date.

What they would change next

Put background-check dates on Breeze kids tags before the next VBS. Train a second Clearstream sender before the pastor’s study week. Keep one laminated give URL card for the county fair booth. Archive seasonal fair volunteers within two weeks so the roster stays honest.

How should you use this page?

If you are under 150 with thin staff and uneven Wi-Fi, prefer one ChMS, one give tool, a printable schedule, and a text channel that works when social media does not. Do not buy a suite you cannot staff on a funeral week.

Field note after a flood Sunday

A creek rose overnight. Facebook reached half the room. The office used Clearstream voice for the cancel and kept a printed give card in the foyer for the next dry Sunday. In a hollow town, the channel people answer on a bad morning matters more than the prettiest app.

Field note after a flood-week export leftover

A temporary cleanup helper kept Breeze export rights after the water receded. They now revoke flood-helper access the same week the sandbags come down. Disaster hospitality includes closing doors.

Field note after a benevolence form in email

A hardship request sat in a shared inbox everyone could read. They moved benevolence to a pastoral form with two-person review. Flood season does not excuse privacy shortcuts.

Reality check before you renew

Name the weekly job in one sentence, then keep only steps a substitute can finish when the lead is out.

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.

Weekly heroics from ordinary staff are a stop sign for that seat on an appalachian small town church.

Paths that need more than fifteen minutes to train a backup are overweight.

Print-day confirmation

Confirm the vendor quote on print day, not from memory (an appalachian small town church).

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

Thank-you discipline

Put the last-checked date in the same paragraph as the Monday owner.

Copy only what a tired volunteer can finish after second service (an appalachian small town church).

Access spare

Put a labeled backup-admin login card in the office safe before vacation week (an appalachian small town church).

Who owns admin

On a team sized like 1 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: $50/mo
• Tithely: 2.9% + $0.30 per gift
• Google Sheets: $0
• GroupMe: $0
• Clearstream: $29/mo
• 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, 2 part-time. Region context: US Appalachia. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near under-150 attendance (Independent Christian), 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 120-attendance church in an Appalachian small 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, Google Sheets, GroupMe, Clearstream, 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, 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.