Guest follow-up, live in 14 days.
Every guest assigned to a staffer, every overdue follow-up surfaced, a weekly completion report, and nothing reaching a guest until a named staffer approves it. Built for executive pastors and operations directors at multi-staff churches.
It runs on the church management system and giving tools you already pay for. We do not ask you to move platforms. David Horton runs this kind of stack for a multi-campus church.
What it does
You already have a church management system. You already have a giving platform. Guests are still getting lost in the space between them.
A card gets filled in on Sunday. By Wednesday, nobody can say whose job it was to call.
Not because anyone stopped caring. The card went into a pile, the pile went into a spreadsheet, and the spreadsheet has no owner. This offer puts a name on every guest and keeps that name visible until the follow-up is done.
- Every guest assignedEach new guest is given to a named staffer or team the same week, using assignment rules you set.
- Overdue follow-ups surfacedA short list of guests still waiting, shown to the person who owns them and to whoever oversees follow-up.
- A weekly completion reportWho was contacted, who is late and who has each guest. It goes to the person you name, every week.
- A named staffer approves every messageWelcome notes and follow-ups are drafted for review. That person approves, edits or rejects each one. Nothing is sent until they do.
It is a church-specific packaging of our automation sprint: one workflow, fixed scope, a finish line.
The 14 days
The clock starts once we have the access and the approver listed below. If those arrive late, the 14 days start late, and we will say so rather than quietly run over.
- Days 1 to 3: mapWe walk through how guests arrive today, who follows up, and what counts as overdue for your church. We agree the assignment rules and who approves.
- Days 4 to 9: buildWe connect the church management system and giving tools, set up assignment, the overdue list, the approval queue and the weekly report, all in a test setup.
- Days 10 to 12: testYour staff run sample guest records through it. We fix what they find and tighten the wording of the drafts.
- Days 13 and 14: go liveIt starts on real guests with approval on from the first message. You get a runbook, a staff walkthrough and the first weekly report the week after.
What the church provides
This is the whole list. If you can put these five things in place, we can hold the 14 days.
- Admin access to your church management system, or a person who can grant it.
- A named staffer who approves messages, and a backup for weeks they are away.
- Read access to your giving tools, if you want first-time givers followed up too.
- Your current follow-up steps, even if they live in one person’s head.
- A scoping call at the start and a staff walkthrough at the end.
Out of scope, on purpose
Said now, so you do not find it out in week two.
People stay in charge of the pastoral parts.
This offer does not handle pastoral counseling, and it does not read or act on the content of prayer requests. It does not collect or process data about minors: children’s and youth records stay out of it.
It is one workflow, not a rebuild of your systems. We do not migrate your church management system, clean up your historic member data, or replace your giving platform.
Every message to a guest is approved by the named staffer before it goes. That is a condition of the offer, and we will not switch it off.
Terms
Boards agree budgets in advance, so the price is fixed before we start and there is no open-ended bill at the end.
- Timeline
- 14 days
- Price
- $4,000
- Founding price
- $2,400, first 3 clients only
- Terms
- Fixed price, paid upfront
Founding rates are open to our first three clients, in exchange for a published case study. Three clients, then the standard price is the only price. If you take a founding slot, the trade is plain: a lower price in exchange for letting us write up what we built for you.
Built and running
The same pattern runs every week at a multi-campus church. The case study has the detail.
-
WhenSomeone fills in a connect card on a Sunday
ThenThey get a personal welcome, and the right pastor or team gets a follow-up task instead of a spreadsheet row.
-
WhenA gift comes in through the giving platform
ThenRecords are updated and the people who need to know are told, with no one re-keying it.
-
WhenA form comes in: a volunteer sign-up, a question
ThenIt lands with the person responsible, not in a shared inbox where everyone assumes someone else has it.
After guest follow-up
Most churches stop at the first step for a season. These are the next ones, when you want them.
- NextAI assistant setupA staff assistant on your handbook and policies, so the office stops answering the same questions. Added to a sprint, not bought on its own.
- NextAnother sprintEvent registration follow-up, volunteer rota reminders, or donor thank-you letters drafted for a person to approve.
- SummitAI operations teamFor churches with several campuses or ministries, where the weekly coordination is the real workload. Guest follow-up is a good first workflow for it.
We work with nonprofits on the same terms. Tell us the process on the call.
Who is meant to call that guest?
Twenty minutes, no pitch deck. Tell us how guests are followed up today, and we will say whether 14 days is realistic for your church and what should stay with a person.