A 320-attendance bilingual church in a Texas border city

This 320-attendance bilingual church runs Breeze for people records, Tithely for giving, Text In Church for texts, Mailchimp for email, and Planning Center for services and kids check-in. Software runs about $155/mo plus card fees.

By Caleb Brooks · Published March 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 320-attendance bilingual church in a Texas border city. Two full-time and three part-time staff. English and Spanish services share one database. Language preference is a required field, not a note someone might forget.

Why does this mix exist?

Breeze keeps one household record with language tags. Tithely covers online and text giving with bilingual prompts. Text In Church and Mailchimp run separate lists by language so nobody gets the wrong follow-up. Planning Center Services schedules bilingual worship teams.

How the week actually runs

Greeters ask language preference once and tag it the same day. Monday guest texts go from the matching language list. The weekly email uses one template with two audiences. Volunteer schedules show who can serve in which language room. Greeters ask language preference once and tag it the same day. Monday guest texts leave from the matching language list, not a blended blast. Thursday rehearsal plans and Sunday slides are checked in both languages before print deadlines, so one language is not always late.

What breaks if you copy this blindly

One English-only automations stream trains Spanish-speaking guests to ignore you. Two databases (one per language) duplicate families and break giving history. Untranslated give-page errors stop first gifts cold. One English-only automation stream. Separate databases per language that double-count households. Translating the thank-you text in a browser five minutes before send.

What they would change next

A bilingual paper backup card for guests who will not scan QR codes. A second Breeze admin who is fluent in both languages. Shorter SMS copy reviewed by a native speaker, not only machine translation. Bilingual paper backup card for guests who will not scan QR codes. Train a second Breeze admin fluent in both languages before the next leadership transition.

How should you use this page?

Require language fields and matched follow-up lists before you add another tool. Keep one database even if services meet at different hours.

Field note after an English-only blast

A Spanish connection card received an English welcome email. The guest did not reply. Greeters now mark language preference on the card, and Monday email matches it. Translation is not a polish step. It is the first proof you listened.

Field note after a mixed-language QR fail

A foyer QR opened an English-only give page. A Spanish-speaking guest stopped mid-gift and left cash unsigned. They printed bilingual give cards beside the QR and fixed the Spanish error text on the live page the same week. First gifts die on untranslated errors, not on theology.

Field note after a late Spanish slide deck

Spanish slides arrived after English print deadlines three weeks running. They now lock both language decks on the same Thursday checklist. Translation is a schedule, not a favor.

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

If two people cannot name the weekly job, wait before you renew.

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 bilingual church in a texas border city.

No slides needed

Hold renewal until the weekly job is obvious without a deck (a bilingual church in a texas border city).

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

Budget honesty

Ask finance to show SaaS and processing on one line before the elder vote.

Copy only what a tired volunteer can finish after second service (a bilingual church in a texas border city).

Explain-to-guest

Have a greeter teach the give path in one sentence before you renew anything (a bilingual church in a texas border city).

Who owns admin

On a team sized like 2 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 ChMS: $72/mo
• Tithely: 2.9% + $0.30 per card gift
• Text In Church: $49/mo
• Mailchimp: $20/mo
• Planning Center Services: $14/mo
• Planning Center Check-Ins: $0 (included)

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: 150-400. Staff shape: 2 full-time, 3 part-time. Region context: US South Texas. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near 150-400 attendance (Non-denominational), 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 320-attendance bilingual church in a Texas border city 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 ChMS, Tithely, Text In Church, Mailchimp, Planning Center Services, Planning Center Check-Ins) 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 2 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.