A 130-attendance church in a New England mill town

A 130-attendance Congregational church in a New England mill town runs Breeze, Vanco, Mailchimp, Google Sheets, One Call Now, and Google Forms. Staff: 1 full-time, 2 part-time. Software is about $75/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 130-attendance Congregational church in a New England mill town. One full-time pastor and two part-time staff. Older buildings, annual meetings that still matter, and members who will answer a phone tree faster than an app notification.

Why does this mix exist?

Breeze is enough membership database without a suite. Vanco respects envelope habits. Mailchimp stays on a free tier. The volunteer sheet hangs on a real deacon board. One Call Now covers storms and funerals when email fails.

How the week actually runs

Sunday ushers mark the Sheet. The office updates Breeze Monday. Vanco and envelopes reconcile before the treasurer leaves. Meeting notices go by Mailchimp and, for urgent closes, One Call Now after the pastor approves. Benevolence forms never land in a shared inbox. After the second service, one usher photographs the attendance Sheet and texts it to the office before lunch. Monday, pledge and plate lines in Vanco are matched to Breeze before any thank-you list is pulled. Building-use requests stay on a separate form that never asks for counseling details.

What breaks if you copy this blindly

Dropping phone notices because “everyone has email.” Letting building-use forms expose pastoral care details. Running annual meeting rolls from a stale spreadsheet instead of Breeze. Skipping One Call Now because the last storm “was not that bad.” Letting the treasurer be the only person who understands pledge mapping. Posting pastoral care updates in the building-use Google Group.

What they would change next

A backup One Call Now operator. Clearer pledge mapping documentation for the next treasurer. A laminated export policy taped inside the office closet. Laminate the export policy by the office printer. Schedule a thirty-minute pledge-mapping walkthrough with the next treasurer before fiscal year end.

How should you use this page?

If your church still runs on annual meetings and phone trees, keep those channels honest and add software only where the paper already fails.

Field note after the annual meeting

The phone tree still reached shut-ins faster than the email blast. Software only helped when it supported that call list instead of replacing it. They kept the tree, put numbers in Breeze, and stopped pretending a newsletter open rate was pastoral care.

Field note after a storm close

A nor’easter canceled Sunday at 6:30am. Email alone left shut-ins waiting for a ride that never came. One Call Now, after pastoral approval, reached the households that still answer a landline. They kept the phone notice as a first channel for weather closes, not a nostalgia project.

Field note after a pledge-map orphan

The only person who understood pledge mapping left mid-year. March statements stalled. They now run a thirty-minute walkthrough with the next treasurer before fiscal year end and keep a laminated map by the printer.

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
• Vanco: Processing fees
• Mailchimp: $0 (free tier)
• Google Sheets: $0
• One Call Now: $25/mo
• 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 New England. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near under-150 attendance (Congregational), 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 in a New England mill town 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, Vanco, Mailchimp, Google Sheets, One Call Now, 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.