A 95-attendance college-town church plant in the Midwest

This 95-attendance college-town plant runs Planning Center People and Services, Stripe for giving, WhatsApp for student texts, Substack for email, and Tally for forms. Software is about $14/mo plus Stripe fees.

By Caleb Brooks · Published April 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 95-attendance college-town plant in the Midwest with 2 full-time staff. Students fill most seats from August to May. Summers shrink. Guests turn over every semester, so the database must mark “graduated and moved” without erasing pastoral notes.

Why does this mix exist?

Planning Center People and Services came from the sending church, so early volunteers already knew the screens. Stripe is one give link with no lobby kiosk yet. WhatsApp and Substack match student habits. Tally covers guest cards without another paid form product.

How the week actually runs

Sunday guests complete a short Tally form. A leader sends a same-day WhatsApp or email, then enters the household in Planning Center before Monday classwork swallows the week. Services blockouts cover exam weeks. The treasurer exports Stripe weekly into a simple sheet and checks for failed gifts. Student leaders get Services roles that expire at semester end so summer does not inherit ghost accounts.

What breaks if you copy this blindly

WhatsApp-only follow-up that misses grandparents who visit once a month. Using Substack as if it were a membership database. Stripe without a named Monday reconciler creates quiet giving gaps. Leaving student admins active after graduation.

What they would change next

A cheap SMS channel for non-student guests. A second People admin trained before the next leadership handoff. A summer “local core” tag so care lists do not assume campus rhythms year-round. A summer archive checklist for graduated leaders.

How should you use this page?

Steal the turnover tags and same-day guest handoff first. Keep the lean giving link if you have no finance office. Skip WhatsApp if your people do not already live there.

Field note from May graduation week

One plant kept student Services admins active “until fall.” By July, three graduated leaders still got plan reminders and one still had export rights. The fix was a graduation Sunday checklist: expire student roles, move pastoral notes to a local-core tag, and confirm the Stripe export owner before summer travel. Campus churches fail on calendar edges more than on Sunday morning tools.

Field note after May move-out

Graduation Sunday looked full. Two weeks later the guest list still pinged students who had already left town. They now run a May archive pass: expire student Services roles, tag local-core households, and pause nurture emails for “graduated and moved.” Campus churches fail on calendar edges more than on Sunday tools.

Field note after finals-week ghosting

Half the greeter team vanished during finals with no blockout. Guests met empty doors. They now require exam-week blockouts the same way they require spring break travel. Academic calendars are ministry calendars.

Small-church proof gate

A substitute should finish the core path after one fifteen-minute handoff. If not, cut steps first.

Final gate

Name who revokes visitor admin the Sunday short-term help leaves.

Size check for this church

Prefer voice or SMS cancels when email open rates collapse in bad weather.

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

Closed-road comms

Channels people answer matter most when roads close before dawn (a college town church plant in the midwest).

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

Impressive tools without maintainers lose to ordinary faithfulness (a college town church plant in the midwest).

Who owns admin

On a team sized like 2 full-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):

• Planning Center People: $14/mo
• Stripe checkout link: Stripe fees only
• WhatsApp Community: $0
• Substack: $0
• Planning Center Services: $0 (included)
• Tally: $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: 2 full-time. Region context: US Midwest. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near under-150 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 95-attendance college-town church plant in the 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 (Planning Center People, Stripe checkout link, WhatsApp Community, Substack, Planning Center Services, Tally) 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, 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.