A 190-attendance liturgical parish in the Upper Midwest

A 190-attendance Lutheran parish in the Upper Midwest runs Church Community Builder, Vanco, Constant Contact, SignupGenius, Google Sheets, Google Forms, and Planning Center Services for choir. Staff: 1 full-time, 3 part-time. Software is about $88/mo plus giving fees.

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 190-attendance Lutheran parish in the Upper Midwest. One full-time and three part-time staff. Baptism, confirmation, and membership records matter as much as the weekly email. Altar guild and ushers still think in sign-up sheets.

Why does this mix exist?

Church Community Builder holds long-lived membership records. Vanco ties online gifts to envelope numbers older members trust. Constant Contact sends parish email and funeral notices from one office sender. SignupGenius covers altar guild and coffee hosts without forcing those teams into the ChMS. Sheets track attendance.

How the week actually runs

The office manager enters connection cards Monday. Absence lists pull from CCB. Ushers mark a Sheet on Sunday. Seasonal liturgical helpers sign up on SignupGenius; staff calendars stay elsewhere. Funeral notices wait for pastoral wording before Constant Contact sends. Monday, the office manager enters connection cards and runs the CCB absence list before coffee hour leftovers are forgotten. Ushers keep a paper Sheet as the Sunday source of truth when Wi-Fi drops. Seasonal liturgy teams get calendar holds in Services-equivalent planning before Advent and Lent, not the week of.

What breaks if you copy this blindly

Migrating altar guild into a complex module mid-Lent. Letting volunteers blast the all-parish list. Ignoring envelope numbers until stewardship season panics. Treating SignupGenius as the membership record for baptisms and confirmations.

What they would change next

A shared baptism and confirmation checklist with due dates. Name a backup Constant Contact sender before the administrator’s vacation. A clearer paper-to-CCB card handoff when the office is closed Mondays for holidays.

How should you use this page?

If records and seasons drive your parish more than apps, keep the membership database stable and use lightweight sign-ups for rotating liturgical roles.

Field note before Advent

They once moved altar guild into the ChMS the first week of Advent “to get organized.” Half the team stopped signing up. The next year SignupGenius stayed put, Advent dates were locked in September, and CCB kept membership records only. Seasonal teams need a tool they will open. Membership records need a tool that will still be there in ten years.

Field note after a holiday Monday

Memorial Day closed the office, so connection cards sat until Tuesday. Absence lists and guest emails both slipped. They now print a holiday handoff card: who enters cards, who sends Constant Contact, and who covers funerals when the administrator is out. Liturgical calendars already plan Advent. Holiday Mondays need the same care.

Field note after a liturgical calendar clash

A Holy Week volunteer ask ignored Triduum rehearsal dates already on the parish calendar. They now require Services blockouts to match the liturgical calendar before any blast. Feast weeks are not “optional busy.”

Adoption check

Name the weekly job in one sentence, then keep only steps a substitute can finish when the lead is out.

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

Care-first check

A fifteen-minute handoff card belongs in the office binder before vacation week.

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

Rights return

Name the steward who revokes visitor rights after short-term help (a liturgical parish in the upper midwest).

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 liturgical parish in the upper midwest).

Write the substitute phone number on the office whiteboard before you renew (a liturgical parish in the upper midwest).

Cellular reality check

Keep human thank-yous for first gifts even when receipts are automatic.

Hard stop on blasts

Benevolence content in a blast template is an automatic stop (a liturgical parish in the upper midwest).

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):

• Church Community Builder: $49/mo
• Vanco: Processing fees only on this plan
• Constant Contact: $25/mo
• SignupGenius: $0 (free tier)
• Google Sheets: $0
• Google Forms: $0
• Planning Center Services: $14/mo

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: 1 full-time, 3 part-time. Region context: US Upper Midwest. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near 150-400 attendance (Lutheran), 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 190-attendance liturgical parish in the Upper Midwest 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 (Church Community Builder, Vanco, Constant Contact, SignupGenius, 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.