A 130-attendance church on the Navajo Nation

A 130-attendance church on the Navajo Nation runs Breeze, Tithely, Clearstream, Mailchimp, Google Sheets, and Google Forms. Staff: 1 full-time, 2 part-time. Built for road weather, weak signal, and multi-household care, not for 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 130-attendance nondenominational church on the Navajo Nation. One full-time pastor and two part-time staff. Road weather and long distances shape Sundays. Guests include local households and visitors from border towns. Multi-home family patterns are normal. Internet can thin out on bad weather days.

Why does this mix exist?

They kept Breeze as one login a part-time admin can run when the pastor is on hospital runs to town. Tithely covers gifts when members work off-Nation and lobby cash dips. Clearstream carries cancels and funeral notices by text and voice because Facebook posts miss households without reliable data (a church on the navajo nation). Mailchimp stays plain on the free tier. Sheets and Forms stay printable when the uplink dies.

How the week actually runs

Saturday, staff check road and weather notes before anyone posts a cancel (a church on the navajo nation). The church number catches replies when Clearstream goes out before Sunday. Offline Sundays still capture cards on paper in a labeled drawer for later Breeze entry. Household tags note multi-home patterns so volunteer asks do not assume one address. Parking-lot cold killed a personal phone once; Tuesday guests now leave via Clearstream. Transport lists for town medical trips live on the Sheet with a named driver.

What breaks if you copy this blindly

Buying a heavy suite you cannot staff during travel weeks. Treating every household as a single suburban address. Relying on Facebook as the only cancel channel. Leaving short-term mission helpers with export rights. Assuming every guest will install an app with weak signal. Forcing image-heavy email that never loads.

What they would change next

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

How should you use this page?

If your church lives with long roads, weak signal, and multi-home families, pick tools that survive offline Mondays and voice cancels. Keep human thank-yous. Pay for one people database; pick one cancel channel households answer. If your town has reliable fiber and one-address households, you may need less Clearstream voice and more steady Mailchimp cadence instead.

Field note after a road-closure Sunday

A storm closed the main road at 6am. Facebook reached border-town rentals. Clearstream voice reached local elders who never open email before noon. The lesson was not more apps. It was the channel people answer when the road is closed.

Field note after a multi-home volunteer ask

A volunteer text hit the wrong household address for a multi-home family. Greeters now mark home patterns on the card, and Monday tags keep asks honest. Care includes knowing how people actually live.

Field note after a mission-week export revoke

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

What to verify this week

Time the path on a phone in the foyer. Desktop-only steps get rewritten or removed.

Final gate

Write the substitute phone number on the office whiteboard before you renew.

Ministry proof line

Time the guest text on a real phone in the parking lot, not only on office Wi-Fi.

Keep the public checklist honest: named tools, ordered steps, real cost, last-checked date.

Refuse tools whose normal week requires heroics from regular people on a church on the navajo nation.

Offline cancel card

Keep a paper cancel card for storm weeks without uplink (a church on the navajo nation).

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

Skip the impressive ghost stack; keep ordinary faithfulness (a church on the navajo nation).

If elders cannot say the weekly job in one breath, wait thirty days (a church on the navajo nation).

Budget honesty

Reject add-ons that need a staff role you will not hire this budget year.

Hero-free holidays

Aim for Christmas weeks that run without heroes by cutting earlier (a church on the navajo nation).

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 Southwest Indigenous. 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 130-attendance church on the Navajo Nation 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.