FellowshipOne for churches

FellowshipOne is only-if for most churches under 400. Keep it if you already live there with a named admin. Do not pick it as your first people database.

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.

Should a small church buy FellowshipOne?

Only if you already run FellowshipOne, or you are merging into a congregation that does and cannot abandon the history. Skip it as a first buy if you are under about 400 and need a people list a volunteer administrator can learn without a consultant.

Who is FellowshipOne for?

Staffed churches with complex permissions, long contribution history, and a person who can own exports, ministry views, and vendor tickets. Think multi-ministry campuses that already budget for database administration, not a two-elder plant choosing software from a booth map.

Who should skip it?

Any church shopping for its first shared contacts list. Implementation and training hours usually dwarf the license line. If you cannot name a database owner before the contract, you are buying a graveyard of half-used modules.

What does ownership look like week to week?

One named administrator documents who can see giving, who can edit membership, and how Sunday guest cards become records. Ministry leaders get views, not full admin. Once a quarter you rehearse a cancel-and-export path so renewal is a choice, not a trap. Without that rhythm, FellowshipOne becomes tribal knowledge that leaves with one staff member.

Common mistakes

• Choosing FellowshipOne from a conference booth without a migration budget or timeline.
• Turning on every module the first month because the demo looked complete.
• Skipping a cancel/export rehearsal before the renewal window.
• Handing full admin to a rotating volunteer with no written export rule.

How does this show up in real ministry work?

Ministry leaders should open filtered views without full admin. Guest cards should become records on a documented path. Quarterly export rehearsal should prove you can leave if you must. If only one staff member understands the database, you do not own FellowshipOne; that person does.

Greenfield churches under 400 should compare lighter tools against Monday jobs before signing an enterprise CHMS.

Field notes before you buy

Ask for current packaging, implementation fees, and training hours in one written quote. If the quote assumes a full-time-adjacent owner you do not have, do not sign. For a greenfield church under 400, compare Breeze and Planning Center People against your real Monday jobs first.

Field note after a migration pause

A church nearly left FellowshipOne mid-stewardship season. They paused, finished pledge season, then planned a quiet winter cutover with dual exports for one month only. Timing the switch around money season mattered more than the vendor brochure.

Field note after a legacy login maze

Two volunteer admins still signed into an old FellowshipOne bookmark after the church moved people data. Guest cards went to the wrong system for a month. They revoked legacy logins the week of cutover and printed the new URL by the office computer. Migrations fail on leftover doors.

Adoption check

Receipts track money; humans still say thank you. People still need a voice.

Care-first check

Ask who revokes export rights the Sunday a short-term helper leaves.

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

Cut seats that only work with weekly heroics from the team on fellowshipone review.

Elders get last-checked and Monday owner on the same printed line.

Substitute readiness

The steward check: one fifteen-minute handoff, then solo completion (fellowshipone review).

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

Cost line for elders

Name the person who tests STOP/opt-out on a spare phone before holiday volume.

Copy only what a tired volunteer can finish after second service (fellowshipone review).

Tools serve people. People still make the hospital calls (fellowshipone review).

Tools serve people. People still make the hospital calls (fellowshipone review).

Keep the Monday owner visible beside the last-checked date.

Start with the pile

Before tools, name who handles guest cards when the foyer clears (fellowshipone review).

Day to day for a non-tech staffer

FellowshipOne should feel boring in a good way on a normal Tuesday. A volunteer or part-time admin should finish the weekly job without calling a consultant. Write the clicks in one short card: who opens it, what they check, and where replies go. If the path only works on a desktop in the office while greeters need a phone in the foyer, rewrite the path before you renew.

Keep permissions narrow. Full export rights belong to one primary admin and one backup, not to every ministry lead. When roles change, run a five-minute access checklist the same week. Leftover logins are how directories sheets and people lists leak into personal inboxes.

Name quiet hours and STOP handling out loud if FellowshipOne sends messages to households. Counseling and benevolence detail stay off blast tools. Logistics and short hospitality can share an inbox. Hard conversations still need a call.

Pricing for a 150–400 attendance church

Field pricing note: Confirm current pricing and implementation fees in writing.

Put sticker price beside processing fees, SMS overages, and weekly admin hours on the same board page. A low monthly fee with ten unpaid hours is not cheap. A higher fee that removes heroics can be faithful stewardship. Confirm the vendor quote the week elders vote. Screenshots from last year lie.

Ask who holds the card on file and where cancel lives. Multi-year contracts need two signatures when the tool can export the full people list or hold giving history. Write the cancel path in the church Drive before you need it.

Versus alternatives

• Breeze or Planning Center People: Lighter weekly ownership for churches under 400 starting fresh.
• Stay on what you have until merger paperwork is done: Do not migrate mid-stewardship season just to

Choose by the Monday job you will staff this quarter, not by the longer feature list. If two tools both fit, pick the one with a clearer owner and a simpler foyer path. Dual systems during a “transition” with no cutover Sunday usually mean two truths and double Monday reconcile.

What breaks first without an owner

Without a named weekly owner, FellowshipOne fails in predictable ways: guest cards sit, cancels leave personal phones, volunteer slots double-book, or giving reports drift from the bank deposit. The product label (only-if) does not rescue an unowned seat. Put the owner and vacation backup on the invoice note before the annual renew.

Train the backup on a quiet weekday. Time one full path end to end (guest text, schedule confirm, or deposit reconcile). If that timing feels impossible, shrink the promise before you expand the stack.

Setup habits that keep the verdict honest

1. Write the weekly job in one sentence on the board note.
2. Name primary and backup admins before go-live.
3. Test export permissions and delete-by habits in week one.
4. Refuse a second people list or second inbox “just for now.”
5. Review the tool ninety days before renewal with actual hours beside the fee.

FellowshipOne is a fit when those habits are real. It is shelfware when they are not. Keep draft facts honest: last verified dates and pricing notes are stewardship tools, not decoration.