A 2,100-attendance church in a Southwest hospitality metro

A 2,100-attendance church in a Southwest hospitality metro runs Rock RMS (~$9,100/yr suggested donation, plus hosting and a full-time admin), Clearstream for texts (~$200/mo), Pushpay for giving, and Planning Center Services for worship, with a Saturday service for a city that works weekends.

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?

This church averages about 2,100 across four weekend services: Saturday 5:30 pm, then 9, 10:45, and noon on Sunday, plus a Spanish congregation of about 250 meeting at 1:30 in the chapel. The Saturday service exists because half the metro works weekends in hospitality, and that shape shows up everywhere in how they operate. Staff is eighteen full-time and about fourteen part-time, including a full-time systems admin who lives in Rock RMS (the church’s main people database).

Guests arrive from night shifts as often as from desk jobs. Paper connect cards still account for roughly 40% of first-time guest info. Follow-up that assumes Monday morning is a quiet office hour will wake the wrong people and miss the right ones.

Why does this mix exist?

Rock is the center of gravity because volunteer assignment, guest workflows, and reporting all need one source of truth at this size. Planning Center Services covers worship and production and syncs with Rock. The two-systems split works because the sync does. Clearstream (a church texting tool) carries guest thank-you texts on a larger plan. Pushpay handles giving under contract pricing. The online connect card on the website feeds Rock directly so digital guests do not wait on office hours.

The stack is not “best of breed for its own sake.” It is what survived four services, bilingual ministry, and a city that does not keep banker hours.

Who owns admin

The full-time systems admin holds master admin in Rock. The connections lead owns guest workflows and the Monday unassigned list. Worship and production leads get Services admin for their teams only. Deacons currently see more of Rock than the ops director likes; a written data-access policy is on the fix list. Greeters enter cards. They do not export lists.

The Spanish congregation’s volunteer scheduling still lives in WhatsApp. The plan is Planning Center Services by spring, but only when a bilingual leader owns the move. Tooling without an owner recreates the WhatsApp problem inside a nicer login.

What this costs monthly

Budget in layers. Rock’s suggested donation is about $4.45 per average weekly attendee per year: a little over $9,100 annually at this size, plus partner hosting. Clearstream runs about $200/month. Pushpay is contract pricing with processing fees that deserve a re-bid before auto-renewal. Planning Center Services is a separate line for worship teams. The largest line is not software. It is the systems admin salary people forget when they hear Rock is “free and open-source.”

Confirm every number the week you brief elders. Contracts and donations change.

How the week actually runs

Saturday 5:30 and Sunday services collect paper cards into a locked box. A volunteer enters them into Rock Sunday afternoon. Online cards create workflow steps automatically. Monday by noon, Rock assigns new guests to connection-team volunteers by zip code. The connection lead clears unassigned records before lunch. Clearstream sends a thank-you text Tuesday at 2 pm, not Monday at 9 am. Assigned volunteers make one personal call or text by Friday, with escalation if the step stalls. Return guests get a next-steps lunch invite in week three.

Copy this if

Copy this if you already have (or will fund) a dedicated Rock admin, you run multiple weekend services, and your city includes large night-shift or hospitality populations. Copy the Tuesday afternoon text timing even if you use a lighter database. Copy the rule that paper cards enter the same day, not Monday.

What breaks first

Rock without a dedicated admin. Dual check-in systems during a migration (they ran two for a year and called it miserable). Giving contracts that auto-renew without a calendar reminder. Deacon access that is wider than pastoral care requires. Spanish-ministry scheduling stuck in WhatsApp with no bilingual owner. Monday-morning guest texts in a night-shift metro.

What they would change next

Write the deacon data-access policy. Calendar the Pushpay renewal and re-bid processing rates. Move Spanish volunteer scheduling into Services only when ownership is real. Stop any habit of measuring hospitality by texts sent while escalations sit open.

Field note after Monday 9 am texts

Cheerful Monday-morning thank-yous hit people asleep after casino and hospital shifts. Angry replies followed. Tuesday at 2 pm fixed the tone and improved replies. Schedule is part of care when the city’s clock is not yours.

Field note after twin check-in systems

Running old and new check-in together for a year trained nobody. Lines slowed. Kids volunteers improvised. Hard cutovers hurt for a weekend. Soft dual systems hurt for months.

Local reality check

A 2,100-attendance church in a Southwest hospitality metro still has to finish ordinary Sundays with the people they have. If a tool in this mix demands a role you will not fund, cut that tool or fund the role before go-live. Faithfulness here is a kept promise to guests, volunteers, and givers, not a complete feature matrix.

When you adapt this page, keep the lastVerified habit. Re-check pricing and admin names when staff changes. A stack page older than your last admin handoff is a rumor until someone verifies it again.