×
churchops.ai
×
churchops.ai
Prepared for Pastor Jerry & The Well team · Geneva, ILA ministry operations engine for The Well, built from what we're running live at Christian World Church. Every connect card caught. Every next step moved. Every Sunday counted. And every sensitive thing kept in human hands.
Here's what came up in one short conversation. We're sure there's more, and finding it is what Discovery is for. But this is where we'd start.
Well Connected, ChurchMetrics and QuickBooks each hold part of the story. Pulling them together for a report is manual work.
Every week, admin staff key connect cards into a Google Sheet before anything can happen.
First-time guests, new givers and baptism steps don't move on their own once someone raises a hand.
Two missed serve check-ins should reach a team leader, so someone checks in before a faithful server drifts away.
When a giving pattern moves noticeably up or down, the right pastor should know, without anyone digging for it.
Kids check-ins, new households, connect cards and decisions in one view, showing what's been done and who did it.
Personal and financial data has to stay safe. We agree completely. It's why security gets its own section below, not a footnote.
Using only public information (your website, app listings and public records), here's the digital footprint we can already see. A Command Center doesn't replace any of these. It reads across all of them so they finally speak one language. Tap any stream.
This card mirrors the one already on your website. Fill it out however you like, choose where it came from, and watch what happens next. No re-typing, nobody forgotten, and the parts that need a pastor still go to a pastor.
Read the moment it's submitted. No inbox, no spreadsheet, no Monday re-typing.
● AutopilotChecked against existing profiles. New household built, or the existing family found. If it might be a duplicate, it pauses for a person to confirm.
◆ Staff confirm possible duplicatesPlaced in the right process queues automatically. The holy and private stuff goes only to people.
A welcome text and email go out using words Pastor Jerry approved once. Then a follow-up rhythm runs for the weeks after.
◆ Words approved once by Pastor JerryYour team gets a plain-English note on what was done, for whom, and what still needs a human.
● Every action leaves a receiptYou asked for two signals: when a faithful server goes quiet, and when generosity shifts. Here's how each one works, and who is allowed to see it.
Mike serves on the Parking Team. Tap a Sunday to mark it missed and see what happens.
sample person, sample Sundays
Church-wide giving trend, read as a pattern, not as dollars on a screen. Switch seats to see who sees what.
illustrative trend, not The Well's numbers
One Command Center with a pulse board for each seat. Everyone sees their own lane, nothing more, and can ask plain-English questions about what's moving and what's stuck. Pick a seat.
Security isn't an add-on. It shapes how the whole thing is built. These are the commitments we'd put in writing for Pastor Jerry and your Elders before any system gets connected.
We start by reading, not writing. Nothing changes in Well Connected until you've approved that exact workflow.
The engine reads trends and totals. Individual-level views are turned on one workflow at a time, each with a named owner.
Allergy and medical notes, children's records, confidential prayer, benevolence and individual gift amounts stay out of AI summaries and shared views.
Lead Pastor, staff, directors and Dream Team leads each see only their own lane. When someone leaves a seat, their access ends.
Well Connected, Pushpay and QuickBooks remain the source of truth. The Command Center keeps only what a dashboard needs.
Each automated step is logged: what happened, for whom, by which workflow, and who approved it.
Pause any workflow at any time, or disconnect completely. Your systems keep running exactly as they did before.
A Privacy & Permissions Charter, reviewed by Pastor Jerry and your Elders, sets the rules before day one.
Tap a seat to highlight it. This is the kind of access map your Charter would lock in. The exact lines are yours to draw.
← swipe the table to see every seat →
Your Well Kids pre-registration page asks for each child's date of birth, grade and allergy notes, plus parent contact details. Website form submissions usually land in an inbox or a spreadsheet, which puts them outside the secure check-in system you already trust.
What we'd do: route pre-registration straight into Well Connected, so children's information sits behind the same permissions as check-in and never sits in an inbox.
cometothewell.org email runs on Google Workspace, but the domain's public sender record (SPF) only authorizes an old web host (HostGator), and its anti-spoofing policy (DMARC) is set to monitor-only. That can quietly send guest follow-up emails to spam, and it makes it easier for scammers to pose as a pastor (the classic church "gift card" email).
What we'd do: a short DNS update so Google is an authorized sender, confirm Google's email signing (DKIM) is on, then step DMARC up to enforcement over a few weeks.
Both were found using public information only: your published web pages and your domain's public DNS records. No logins, no access to any Well system.
No. We only run The Well's data through business-grade AI services that are set up not to train on it, and we'll show your team exactly where that's configured.
Where it lives today: Well Connected, Pushpay, QuickBooks and ChurchMetrics. The Command Center reads what a dashboard needs. Sensitive fields (allergy and medical notes, children's records, confidential prayer, individual gift amounts) are never copied into it.
Only the people named in your Charter, only during the build, and only for the work it describes. After launch, any access is by your request and logged.
Access belongs to the seat, not the person. Remove them from the seat and their access ends that day. Connection keys get rotated on a schedule and whenever staff changes.
Anytime. Pause a single workflow, or switch off the connection inside Well Connected and everything stops. Your systems keep working exactly as they do today.
Children's records stay in your check-in system. The Command Center sees Well Kids attendance as counts only, never individual children's details.
We'd also walk your Elders through our full security brief in person. Some of it describes how our engine works under the hood, so we share it in conversation rather than on a web page.
Every task gets one of three gates. Filter the table to see where each line falls, who holds the gate, and why. This is the list your Charter would make official.
Logistics. Counting, routing, reminders and receipts. If a volunteer would do it with a clipboard, the system can do it, and it reports back every time.
Anything in a pastor's voice, or anything uncertain. The system drafts or suggests, and a named person approves before it counts.
Holy ground and private matters: salvation decisions, confidential prayer, money conversations, children and care. The system can tell someone to look, but a person does the work.
← swipe the table for who and why →
One of your core values is "Love is a behavior we choose to walk in." That's why the choices stay with people. The system handles the logistics so your team has time to love people well.
Three ways to begin. Each one builds on the last, so nothing gets thrown away when you're ready to grow. Pick one, and the timeline below updates to match.
Tools only change a church when people use them. These programs make sure it sticks, and they fit with the work Philip and Jeremy are already doing with you.
Pick a start date and a build. Dates, phases and statuses update as you change them. We'd suggest a January start: Christmas is sacred ground, and Discovery can happen quietly in December.
We've spent the better part of two years building, breaking and rebuilding this at Christian World Church, learning what works in a real church week and what doesn't. You get the version that works, adapted to Well Connected, without repeating our mistakes.
Everything on this page, and what Philip saw on our call, is churchops.ai v2. To be honest, our public website is already a little behind what's running today. You'd be building on the newest version, not the brochure.
No commitment and no pressure. Just a clear picture of what's possible at The Well and where it would help most.
About an hour with Pastor Jerry, Pastor Isaiah, Pastor Shannon and Jill. We map how a person really moves from first visit to Growth Track to Dream Team at The Well.
With your permission, a view-only connection to Well Connected that you control and can switch off. We map your data. Nothing is changed.
A draft Privacy & Permissions Charter for Elder review, plus a build plan around the problems that matter most to you.