A 120-attendance Maine coastal fishing-town church

A 120-attendance Maine coastal fishing-town church runs Breeze, Tithely, Clearstream, Mailchimp, Google Sheets, and Google Forms. Staff: 1 full-time, 1 part-time. Built for fog Sundays and boat season, 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 120-attendance Congregational church in a Maine coastal fishing town. One full-time pastor and one part-time admin. Fog and nor’easters cancel worship a few times a year. Boat season pulls members offshore on Sundays. Summer brings tourist guests who may never return. Internet thins out when storms hit the peninsula.

Why does this mix exist?

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

How the week actually runs

Saturday, staff check marine weather before anyone posts a cancel. Clearstream goes out early with a reply path to the church number. Offline Sundays still capture cards on paper in a labeled drawer for later Breeze entry. Boat-season tags keep volunteer asks from assuming every family is ashore. Tuesday guest texts use Clearstream so summer visitors get a human path without a personal staff phone. Harbor-ride lists live on the Sheet with a named lead.

What breaks if you copy this blindly

Buying a heavy suite you cannot staff during tourist weeks. Treating every household as always ashore. Relying on Facebook as the only cancel channel. Leaving seasonal helpers with export rights. Assuming every summer guest will install an app on weak dock Wi-Fi. Forcing image-heavy email that never loads.

What they would change next

Train a second Breeze admin before the pastor’s next hospital week (a maine coastal fishing town church). Print large-type give cards. Put background-check dates on kids tags before Vacation Bible School. Name a backup Clearstream sender before first nor’easter week. Add a do-not-contact path for tourists who ask for space after they leave.

How should you use this page?

If your church lives with marine weather cancels, boat-season absences, and summer guest spikes, 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 year-round attendance, you may need less Clearstream voice and more steady Mailchimp cadence instead.

Field note after a fog-bound Sunday

Fog closed the harbor road at 7am. Facebook reached inland relatives. Clearstream voice reached dockside elders who never open email before noon. The lesson was not more apps. It was the channel people answer when the coast disappears.

Field note after a boat-season volunteer ask

A volunteer text assumed an ashore family could cover nursery during a late haul. Greeters now mark boat-season tags on the card, and Monday asks stay honest. Care includes knowing who is on the water.

Field note after a tourist-week export revoke

Seasonal helpers kept export rights after August. They now revoke visitor admin the Sunday Labor Day weekend ends. Hospitality includes closing doors.

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 New England Coast. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near under-150 attendance (Congregational), 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 Maine coastal fishing-town 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.