Follow up every newcomer.Without the spreadsheet.
Pave runs the weeks after a connect card — who to call, who’s been called, and who’s still waiting. Then it hands them to your church database and gets out of the way.
Free while we’re in trial with our first churches.
A visitor fills in a connect card. It goes in a pile.
By Wednesday, nobody’s quite sure who called them.
By next Sunday, the moment has passed.
It’s almost never that a church doesn’t care.
It’s that nobody can see it — who’s been contacted, who’s carrying whom, and whether it’s actually working.
Sunday is the denominator.
Follow-up only means something as a ratio of the room. Pave measures the whole journey against the Sunday it started on — three numbers, every week, worked out for you.
How much of the room you actually met. Every connect card, against every person who came.
Of the ten people currently being carried, how many were reached inside 48 hours — while they still remember the service.
Of the seven who've come through a full follow-up cycle, how many are still here. The only one that finally counts.
Growth stops being a feeling and starts being three numbers you can move.
Figures shown are from our demo church — illustrative, not a result.
How Pave works
One loop, running every week of the year.
Enter Sunday
Connect cards and attendance, a couple of minutes at the welcome desk.
Delegate
Every newcomer on one board, with who’s carrying them. Assign by capacity so nobody quietly ends up with fifteen people.
Follow up from a phone
Leads see only their own people. Tap to call or text, log it in a tap.
Hand them on
Mark them done. Their details export to your church database, and Pave lets go of them.
Nobody sees more than their role needs
Four jobs, four different apps — same church, same data. A volunteer on the welcome desk never sees a pastoral note; a small-group leader only ever sees their own people.
Who's carrying whom?
Every newcomer from the moment their card lands to the day they're settled. Assign by capacity, see who hasn't been picked up and who's overdue a call. No settings, no billing — the coordinator runs people, not the account.
Assign by capacity, move people through the weeks, archive with a reason.
Growth and health, week against month against last year. Read-only on the board.
Their people, nobody else’s — this is the screen they live in, on their own phone.
Cards in, numbers in, done. No access to anybody’s details afterwards.
Pave doesn’t replace your church database
It’s the welcome desk, not the filing cabinet. Pave carries a newcomer through their first six weeks, then hands them — and their history — back to whatever you already run.
CSV export today. Direct integrations as churches ask for them.
We’re building this with a handful of churches first
Pave is in trial with a small group of New Zealand and Australian churches. It’s free while we’re in trial — what we want back is a fortnightly conversation about what’s working and what isn’t.
- Your whole team — welcome desk, coordinator, every follow-up lead
- Set up with you, on a call, in under an hour
- A say in what gets built next
- Export everything and walk away whenever you like
A combined twenty years helping multi-campus churches operate — the welcome desk, the database, the Sunday numbers. Pave is the tool we wanted and couldn’t buy.
in trial
We haven’t set a price yet — we’re setting it with the churches using it. Trial churches get told well before anything changes.
Look around a demo churchTalk to us about a trialSee it with demo data first — just your email, no account.
Pave holds newcomers briefly, hands them back to your database, then anonymises them. Built for the NZ and Australian Privacy Acts. Privacy policy →
Four Sundays from now, you could know every name
Set your church up in a few minutes and start with the people who came this weekend. By the end of the month you’ll have a connection rate, a response time, and nobody sitting in a pile.
Free while we’re in trial with our first churches.