A 110-attendance church on the Alaska road system

A 110-attendance church on the Alaska road system runs Breeze, Tithely, Clearstream, Mailchimp, Google Sheets, and Google Forms. Staff: 1 full-time, 2 part-time. Built for winter cancels and weak internet, not for a big-city 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 on the Alaska road system. One full-time pastor and two part-time staff. Winter road closures are normal. Internet can drop to a thin satellite link on bad weather days. Guests include seasonal workers who may leave after a few months.

Why does this mix exist?

They kept Breeze as one login the part-time admin can manage when the pastor is on the road for hospital visits. Tithely covers online gifts when lobby cash thins in deep winter. Clearstream carries cancels by text and voice because Facebook posts miss households without reliable data. Mailchimp stays plain on the free tier so the weekly note still opens on a weak uplink. Sheets and Forms stay light and printable.

How the week actually runs

Saturday, elders check the road-status sheet before anyone posts a cancel. If schools close for ice fog, Clearstream goes out by 7am with a reply path to the church number. Sunday cards enter Breeze before staff leave when the uplink holds; otherwise paper cards wait in a labeled drawer for Monday. Giving batches close when the satellite link holds again, not on a rigid noon clock that ignores whiteouts. Tuesday guest texts use Clearstream so they do not depend on a personal phone that dies in the cold parking lot. Seasonal workers get a tag with an expected departure month so summer care lists stay honest.

What breaks if you copy this blindly

Buying a heavy Planning Center suite you cannot staff when the pastor is traveling. Relying on Facebook as the only cancel channel. Assuming every guest will install an app in a cold parking lot. Leaving seasonal workers marked as year-round members. Forcing Mailchimp templates full of images that never load on a thin satellite link.

What they would change next

Train a second Breeze admin before the pastor’s next Lower 48 trip. Print a large-type give card for the foyer. Put background-check dates on kids tags before VBS. Name a backup Clearstream sender before the first winter storm. Add a do-not-contact path for seasonal workers who ask for space after they leave the road system.

How should you use this page?

If your church lives with road weather and weak internet, pick tools that survive offline Mondays and voice cancels. Keep human thank-yous. A single CHMS and one reliable cancel channel is enough for most weeks. If your town never closes for ice fog and fiber is reliable, you may need less Clearstream voice and more Mailchimp cadence instead.

Field note after a whiteout Sunday

A whiteout closed the highway at 6am. The Facebook post reached about a third of the room. Clearstream voice hit the rest, including older members who never open email before noon. The lesson was not “add more apps.” The lesson was “pick the channel people will answer when the road is closed, and name a backup sender before the storm.”

Field note after a winter-backup drill

They practiced a Clearstream cancel with the backup sender in October. The first ice storm was not the training day.

Field note after a substitute week

A substitute ran A 110-attendance church on the Alaska road system for ten days. They refused Slack archaeology; steps were written or gone. Substitute friction is the real scorecard.

Board-ready proof

Confirm the vendor page the same week you write the board note. Stale PDFs lie.

Final gate

Cut any step that needs a desktop login to finish a foyer job.

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: 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, 2 part-time. Region context: US Alaska. 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 church on the Alaska road system 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, 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.