A 140-attendance church on a Hawaii neighbor island

A 140-attendance church on a Hawaii neighbor island runs Breeze, Tithely, Clearstream, Mailchimp, Google Sheets, and Google Forms. Staff: 1 full-time, 3 part-time. Built for visitor churn, ferry weeks, and weather cancels, not for a mainland megachurch 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 140-attendance nondenominational church on a Hawaii neighbor island. One full-time pastor and three part-time staff. Sundays mix local households with mainland visitors who may stay two weeks. Weather, road closures, and rare tsunami-siren Sundays are real. Internet near the harbor can thin out on busy ferry days.

Why does this mix exist?

They kept Breeze as one login the part-time office volunteer can run when the pastor flies to the mainland for family care. Tithely covers gifts when members travel and lobby cash dips. Clearstream carries cancels by text and voice because Facebook posts miss kupuna without reliable data. Mailchimp stays plain on the free tier so visiting families can open the note on hotel Wi-Fi. Sheets and Forms stay light and printable.

How the week actually runs

Saturday, staff check road and weather notes before anyone posts a cancel (a church on a hawaii neighbor island). If schools close for a storm watch, They send Clearstream early and route replies to the church number. Sunday cards enter Breeze before staff leave when the uplink holds; visitor cards get a “short stay” tag with an expected departure week. Giving batches close when connectivity returns. Tuesday guest texts use Clearstream so they do not depend on a personal phone that dies near the harbor. Ferry-day hospital visits are logged on the Sheet so care does not vanish when the pastor is on the water.

What breaks if you copy this blindly

Buying a heavy Planning Center suite you cannot staff during mainland trips. Treating every visitor as a permanent member for stewardship goals. Relying on Facebook as the only cancel channel. Assuming every guest will install an app with weak harbor data. Leaving short-stay tags unmarked so summer lists stay dishonest.

What they would change next

Train a second Breeze admin before the pastor’s next mainland 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 hurricane season. Add a do-not-contact path for visitors who ask for space after they fly home.

How should you use this page?

If your church lives with visitor churn and weather alerts, pick tools that survive offline Mondays and voice cancels. Keep human thank-yous. Choose one paid people record and one cancel channel with real reach. If your town never hears a tsunami siren and fiber is reliable, you may need less Clearstream voice and more Mailchimp cadence instead.

Field note after a siren Sunday

A tsunami siren emptied the coastline mid-morning. The Facebook post reached vacation rentals. Clearstream voice reached local kupuna who never open email before noon. The lesson was not “add more apps.” The lesson was “pick the channel people will answer when the siren sounds, and name a backup sender before hurricane season.”

Field note after a two-week visitor wave

Twelve mainland households visited during a school break. Without short-stay tags, they stayed on the volunteer ask list for months. Now greeters mark expected departure on the card, and Monday cleanup archives the tag when the week ends. Hospitality includes an honest goodbye.

Field note before you copy the invoice

Boards that copy A 140-attendance church on a Hawaii neighbor island without naming a Monday owner usually renew shelfware. Write the weekly jobs first. Subtract anything that dies when the lead travels.

Tuesday proof test

Ask finance how fees appear beside the subscription line. Hidden costs create Monday surprises.

Prefer one clear weekly owner over three half-owned tools.

Who owns admin

On a team sized like 1 full-time, 3 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, 3 part-time. Region context: US Hawaii. 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 140-attendance church on a Hawaii neighbor island 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, 3 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.