A new family that nobody follows up with usually doesn't come back. That, I can automate.
The heart of the work is welcome — but the follow-up after a first visit is where it quietly falls through. A new family comes on Sunday, no one has time to reach out, and they don't come back. Making sure not a single first-time visitor slips through is exactly what I can take off your plate.
01 The pain
Ask anyone leading a Winnipeg congregation or community group where growth stalls and it's rarely the Sunday itself. It's Monday — a new family visited, everyone meant to follow up, and in a busy week nobody did. By the next weekend the moment has passed.
A first-time visitor who hears nothing after their visit usually doesn't come a second time — and there's no IT team or process whose job is to make sure that never happens.
02 Where the software actually leaves you
There's real software for this — Text In Church, Faith Teams, even Planning Center's free People module all offer automated visitor follow-up. So this isn't a missing category of software.
The problem is what happens after setup. Someone configures the workflow, it runs great for a few months, then that volunteer moves on — a new job, a new season of life — and nobody else knows how it works. The messages quietly stop going out, or worse, keep going out unattended. One church sat on 18 months of unfollowed visitor cards before anyone noticed.
And these are rented systems: billed monthly, per message, data on a U.S. server. If the subscription lapses, so does the whole workflow — along with anything you'd learned from it.
The software isn't missing. What's missing is a system that survives staff turnover, and one you actually own.
03 Why a subscription doesn't close the gap
A $30-a-month tool doesn't fail because it's badly built. It fails because nobody owns it. The volunteer who set it up isn't paid to maintain it. When they're gone, so is the institutional memory of why it's configured the way it is.
It's also built for the U.S. market by default — data sitting on American servers, for a system tracking something Canadian privacy law treats as sensitive: religious affiliation. Most churches never think to ask where that data lives, until someone does.
04 The gap I fill
I build the same follow-up layer, but the system is yours when I'm done — not a subscription that stops the moment payments do. Data stays in Canada (AWS ca-central-1), which matters more here than in almost any other industry, since religious affiliation is sensitive personal information under Canadian privacy law.
And I don't hand it off and disappear. I stay involved until whoever's on your welcome team is actually the one running it — so the system outlives whichever volunteer happens to be doing this job this year.
As a safety net underneath all of it: nothing goes out untouched. Every drafted note waits for someone you trust to approve it, and every follow-up links back to the visit it came from — so if something's unclear, a person sees it instead of a mistake going out silently.