Okay, so you may already know the five systems that matter: guest follow-up, discipleship pathway, leadership pipeline, volunteer development, and sending culture. You don’t need me to convince you they matter. You need a way to actually build them without adding six hours to your week you don’t have.
So let’s just build them. One at a time. Here’s how.
1. Guest Follow-Up
The goal here is simple: nobody who visits your church falls through the cracks, and it doesn’t depend on you remembering.
Build it like this:
- Grab contact info every time.
A connect card, a text-to-join, whatever — but make it the same ask every single week, not something you remember to do on good weeks.
- Assign the follow-up before Sunday ends.
Don’t let it sit in a pile until Tuesday. Whoever’s on the hospitality team texts or calls every first-time guest before Monday morning. That’s the whole rule.
- Keep the message dead simple.
“Hey, it’s [name] from [church]. So glad you came out yesterday — would love to grab coffee or just chat sometime this week if you’re open to it.” That’s it. Not a sales pitch. A human being noticing another human being.
- Put someone’s name on it — not a role.
“Our team” doesn’t build relationship. “Sarah from the church” does.
- Track it somewhere dumb-simple.
A shared spreadsheet with name, date, who followed up, and whether they responded. You don’t need church management software to start. You need a system that survives you being tired on a Monday.
You’ll know it’s working when you stop having to ask, “Did anyone follow up with the Johnsons?” — because the answer is already logged.
2. Discipleship Pathway
The goal: every person in your church can answer, “What’s next for me spiritually?” without guessing.
Build it like this:
- Draw the pathway on one page.
Seriously — one page, in plain language. Something like: New Here → Connect Group → Serve Team → Leadership Track. Doesn’t need to be fancy. Needs to be clear enough that a new believer could explain it back to you.
- Give every step a next action, not just a next stage.
“Join a group” isn’t actionable. “Text this number to get placed in a group this week” is.
- Announce the pathway constantly, not occasionally.
You will get sick of saying it long before your church gets sick of hearing it. Say it from the stage, put it in the bulletin, mention it in every new members’ conversation.
- Assign an owner.
Somebody other than you needs to know who’s stuck at each stage and nudge them forward. If it’s only in your head, it’s not a pathway — it’s a to-do list nobody else can see.
- Build in a personal layer, not just a program layer.
A one-page flowchart moves people through stages. It doesn’t replace an actual mentor or small group leader checking in on someone’s life. Make sure both exist.
You’ll know it’s working when new people can describe their own next step without you telling them.
3. Leadership Pipeline
The goal: your church doesn’t stop functioning if you disappear for six weeks.
Build it like this:
- Make a list of every role only you can currently do.
Preaching backup, leading a team meeting, making a pastoral care call — write down every single one. That list is your risk map.
- Pick one role a month to hand off.
Not all five. One. Identify someone with the character and capacity, apprentice them for a few weeks doing it alongside you, then let them run it while you watch, then let them run it while you’re not even there.
- Build an actual apprenticeship step, not just a title.
“You’re now the small groups leader” without any training is setting someone up to fail quietly. Shadow, then co-lead, then lead solo, then they train the next person. That last step is the one almost everyone skips — and it’s the one that makes the pipeline self-sustaining instead of something you have to manually restart every time.
- Have a real conversation about calling, not just capacity.
Ask potential leaders where they sense God might be leading them long term — not just whether they’re free on Sundays. You’re not just filling slots. You’re identifying people you’ll eventually train and release.
- Review your risk map every quarter.
As you hand things off, that original list should get shorter. If it’s not shrinking, you’re not actually developing leaders — you’re just delegating tasks and taking them back.
You’ll know it’s working when you can take a real week off and come back to find things ran fine without you.
4. Volunteer Development
The goal: people who want to serve have an obvious way in, and nobody who’s already serving is quietly drowning.
Build it like this:
- Create one low-barrier entry point.
A single Sunday, a single team, a single “come try it for a month, no commitment” on-ramp. Make it embarrassingly easy to say yes to.
- Stop recruiting only when you’re desperate.
If the only time you ask people to serve is during a scramble, you’ll always end up asking the same five tired people. Make the ask a normal, regular rhythm — not a fire alarm.
- Match capacity to role on purpose.
Not everyone wants to lead a team, and that’s fine. Have both light-lift roles and high-capacity roles clearly defined, so people can self-select instead of getting talked into more than they can sustain.
- Check in quarterly, not just when someone quits.
A short conversation — “How’s this role feeling? Want to keep going, shift, or step back?” — normalizes stepping back before burnout forces it. People who know there’s an exit ramp actually stay longer.
- Have every volunteer train a shadow before they rotate out.
Even informally. This is the single biggest thing that turns “a volunteer” into “a volunteer pipeline.”
You’ll know it’s working when a volunteer stepping back is a smooth handoff instead of a five-alarm fire.
5. Sending Culture
The goal: your systems make it easy to release your best people, not just easy to keep them.
Build it like this:
- Talk about calling out loud, regularly. Not just “serve here forever,” but “where is God calling you, even if that’s eventually somewhere else.” Say it from the stage. Model it in how you talk about your own future.
- Create a real pathway for planters and senders, not just servers. If someone on your team says, “I think I’m supposed to plant a church,” do you have any next step for them — coaching, resources, a network — or does that conversation just end?
- Celebrate people leaving to go start something, publicly. If the only public celebrations are people staying and serving, you’re training your church that staying is the only win. Make sending a visible value, not a private exception.
- Give financially or practically to something outside your walls at least once a year. Support a plant, send a team, fund a leader. Sending as a value has to show up in the budget, not just the sermon.
- Ask this once a year at a leadership level: “Who on our team is ready to be sent, and are we actually preparing them, or just hoping they stay?” Uncomfortable question. Ask it anyway.
You’ll know it’s working when releasing someone feels like a win instead of a loss.
Where to Start
Don’t try to build all five this month. Pick the one that’s weakest right now — you already know which one it is — and build just the first bullet point under it this week. Not the whole system. One step.
Systems get built one repeatable action at a time, not in a single strategic planning session. Start small, stay consistent, and check back in a month on what’s actually sticking.
Want the “Why” Behind These Steps?
This post is all “how.” If you want the “why” — the research, the stakes, and a couple of angles we didn’t get into here — that’s what the podcast episode is for. A few things you’ll only get there:
- The number that kicked this whole thing off.
- “Bus factor” — a term borrowed straight from software engineering.
- The theological guardrail underneath all of this.
🎙️ Listen to the full episode here: Church Planting 2.0 Podcast
