Recurring giving setup for a small church

This 175-attendance West Coast plant launched recurring giving on Pushpay after bank verification, a $5 test, a Sunday script, and a named first-gift thank-you owner. Monday batch review catches failed gifts the same week.

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.

Before you start

Church bank account details, elder or finance approval in writing, admin access to Pushpay and Planning Center People, and one weekend blocked for the $5 tests. Do not announce recurring giving until the one-time and recurring tests clear into the church account. Write the Sunday script before you pick button colors on the give page.

Why they built it

Cash-only weeks left renters and students out. A split-processor experiment left finance with two Monday exports. They chose one tool (Pushpay), one announcement, and a named thank-you owner. Recurring gifts helped the plant plan rent and salaries without pretending every household must pledge on paper. The Monday noon batch review made failed gifts a care call, not a quarterly surprise.

What they’d do differently

They would print the large-type give URL card on day one. QR-only launches miss people who refuse phone cameras in the lobby. They would also put processing fee estimates on the elder launch page beside the SaaS line. December card volume taught them the sticker price is not the gift cost. They would keep text-to-give off until online recurring had six quiet weeks.

Before you copy the clicks

Recurring giving setup for a small church only works when a tired Monday reader can finish it without inventing owners. Read the frontmatter tools (Pushpay, Planning Center People, Monday finance checklist) and confirm those logins already exist in an-urban-church-plant-on-the-west-coast. If a tool is missing, buy or borrow it on purpose. Do not invent a parallel Sheet “just for this week.”

Setup difficulty on this page: a-weekend. Plan about one focused weekend for first setup, plus a quieter second pass after the first real Sunday. Incremental cost range: Processing fees only (often a few percent + per-gift fee; confirm current rates). Confirm vendor pricing the week you brief elders.

Who owns each handoff

Name a primary owner and a vacation backup before the first live run. Write those names on a card near the desk that finishes Sunday entry. Greeters, finance helpers, and volunteer coordinators should know who to ping when a step stalls.

Keep exports and pastoral notes on the tightest permissions the job allows. A workflow that moves guest or benevolence data through a shared inbox needs an explicit watch schedule, including holiday weekends.

What the week looks like when it works

• Pick one giving tool and finish bank verification: keep the owner and timing in the detail as written; do not skip the human handoff.
• Turn on recurring gifts and write the Sunday script: keep the owner and timing in the detail as written; do not skip the human handoff.
• Name the first-gift thank-you owner before launch: keep the owner and timing in the detail as written; do not skip the human handoff.
• Test a $5 gift and a $5 recurring schedule end to end: keep the owner and timing in the detail as written; do not skip the human handoff.
• Announce once, then review batches every Monday: keep the owner and timing in the detail as written; do not skip the human handoff.

When the week works, nobody needs a hallway rewrite. Cards or forms land in the right list the same day. Messages leave a church-owned channel when personal phones would hide replies. Exceptions get a note, not a new secret process.

What breaks first

The first break is usually ownership, not software: a card left in a basket, an unwatched reply-to, a schedule published without a backup, or a giving test that never clears into the church account. Automations without watchers create polite silence. Dual systems create double Monday reconcile.

If your staff hours are thinner than the churchRef stack assumes, shrink the promise. Keep the moral core (a person follows through) and cut optional channels until the core is reliable for four Sundays.

Pricing and time honesty

Budget Processing fees only (often a few percent + per-gift fee; confirm current rates) plus the weekly minutes to keep the path honest. A $0 path that burns three volunteer evenings is not free. Put hours beside fees on the board note. Train the backup on a quiet weekday before vacation season.

Re-verify this workflow when tools change owners or when the churchRef stack updates. lastVerified dates are stewardship tools. Treat an unverified page as a starting draft until someone runs the path again.

Copy-only-if checklist

1. Tools in frontmatter match logins you actually have.
2. Primary and backup owners are named in writing.
3. One full path timed end to end on a phone if foyer work is involved.
4. No second database or second inbox “for transition.”
5. Elder or staff note includes cost range Processing fees only (often a few percent + per-gift fee; confirm current rates) and setup time one focused weekend.

Steal the promise and the ownership pattern. Adapt the branding later.

After the first four Sundays

Review what actually happened: missed steps, reply delays, and any hallway workarounds. Keep the parts people used. Cut the parts that required heroics. A workflow that only works when one specific person is healthy is not finished yet. Write the backup path before you call the process done.

You can give online at {short URL}, including a recurring gift that helps us plan. Cards are at the welcome table if you prefer not to use an app. Thank you for supporting the work here.

1) Open yesterday's batch. 2) Note failed cards and ACH returns. 3) Call those households this week. 4) Tag first gifts and assign thank-you owner. 5) Record fee total for the monthly elder report.