Church Planting
How to build and organize a launch team for a church plant
You build a launch team for a church plant by making a clear ask, recruiting people relationally into a short list of roles you actually need, separating the committed from the merely interested, and keeping one living list of who said yes to what. A committed core covering setup, kids, hospitality, and worship matters more than a big number, and you can launch without burning anyone out if you build around the roles instead of the headcount.
When we were planting, I made the mistake of treating the launch team like a headcount. I wanted a big number to feel safe, so I collected names of everyone who said they were excited. Three weeks before our first Sunday, I realized half of that list had never agreed to do anything specific, and the other half didn't know what I was expecting. The fix was not more people. It was clarity about who was doing what, and a list I could trust.
What is a church launch team and what is it actually for?
A church launch team is the core group of committed people who help you hold the first public services together: setting up the room, running kids and check-in, welcoming guests, and leading worship. It exists to make Sunday repeatable and survivable while the church is still tiny, not to fill seats or look impressive on a vision night.
The launch team is your first real test of whether the plant can function as a body and not a one-person show. If everything depends on you, the launch team is where that becomes obvious. A good launch team carries the operational weight so you can pastor, preach, and pay attention to the guests walking in for the first time. That handoff of responsibility is the whole point, and it starts months before anyone sets up a chair.
How many people do you need on a launch team?
There's no single right number, and the people who coach planters don't agree on one. Some networks and longtime church-growth voices point toward 40 to 50 committed adults for a healthy, sustainable Sunday launch with room to grow. Others make the case that a smaller, fully committed core of roughly 15 to 30 launches better than a big crowd of the merely curious. What both camps agree on is that commitment matters more than the raw count.
For us, the number that mattered was not how many people were excited about the church. It was how many people would show up at 7am on a Sunday to do a specific job. I'd rather launch with 18 people I can count on than 50 names where I'm guessing who'll actually be there. Smaller core teams also stay closer relationally, which matters when launch season gets hard and you need people who will keep showing up after the novelty wears off. Whatever target you land on, build the team around the roles, then recruit to fill them, instead of recruiting a crowd and hoping the roles sort themselves out.
What roles do you actually need on a church plant launch team?
You need five roles to run a launch Sunday: setup and teardown, kids and check-in, hospitality and first impressions, worship and tech, and a coordinator who holds the whole operation. Anything beyond these five can wait until after launch. Keep the org chart small enough that you can picture a real face in every slot.
Here are the roles, in the order I'd fill them:
- Coordinator. One person who owns the master list, the Sunday timeline, and the group text. This is often the planter's spouse or a trusted friend, and it is the single most important hire on the team.
- Setup and teardown. The crew that loads in, puts out signage and chairs, and tears it all down. In a portable church this is your largest and least glamorous group, so recruit for reliability over enthusiasm.
- Kids and check-in. The people who run a safe, welcoming kids' environment and handle check-in. Parents decide whether to come back based largely on this, so screen and train these volunteers carefully.
- Hospitality and first impressions. Greeters, the welcome table, coffee, and the follow-up with guests. This role is the difference between a visitor feeling noticed and feeling processed.
- Worship and tech. The band, the sound, the slides, and whatever streaming or audio you run. Small is fine. Consistent and unflustered matters more than polished.
If you want a fuller picture of how these roles fit into everything else a plant has to run, the church planter operating system walks through the whole setup. And once your roles are defined, the harder work is filling them, which is its own skill set covered in recruiting volunteers for a church plant.
How do you tell committed launch team members from interested ones?
You tell them apart by giving someone a real responsibility with a date attached and watching what they do. Interested people affirm the vision and show up when it's convenient. Committed people take a named role, hold a recurring time, and rearrange their week to be there. The follow-through is the whole signal.
Early on, everybody sounds committed. The way to find out is to ask for something specific and small, then something specific and larger. "Can you come to the setup walk-through Saturday at 9?" tells you far more than "Are you excited about the church?" ever will. The people who keep their small yeses are the ones you build around. The table below is roughly how I learned to read the difference once I stopped trusting enthusiasm alone.
| Signal | Interested | Committed |
|---|---|---|
| Response to the vision | Excited, talks about it | Excited, asks how to help |
| When you ask for a specific role | "Let me think about it" | Says yes and asks for the date |
| Recurring time | Comes when convenient | Reorganizes the week to be there |
| Follow-through on small asks | Spotty | Reliable |
| What they need from you | Inspiration | A clear job and a list |
None of this is a judgment on someone's heart. Plenty of warm, godly people are in an interested season because of work, kids, or capacity, and that's fine. Your job is to read the behavior honestly so you build the team on people who can actually carry the load, and so you don't resent someone for not doing a job they never agreed to.
How do you keep track of who is doing what?
Keep one living list of every launch team member, the role they said yes to, and their contact info, and update it the moment something changes. A shared spreadsheet works fine to start. The rule that matters is that there is exactly one list, everyone knows where it lives, and you trust it enough to plan from it.
The trap I fell into was scattering commitments across texts, a notebook, and my memory. By launch week I couldn't tell you who had actually agreed to run check-in. Whatever tool you use, capture three things for each person: name and contact, the role they own, and whether they've completed any training or screening the role requires. Review the list weekly in the run-up to launch, and stop treating "I think so-and-so is covering that" as a plan.
This is the one place I'll mention what we build. The reason to keep your launch list as real people records, not a throwaway spreadsheet, is that those same people become your founding members on day one. In Scout, the launch team you recruit is already in the system as people with serving roles attached, so on your first Sunday nobody gets re-keyed from a spreadsheet into a new tool. The list you built to survive launch becomes the foundation of how you'll notice and care for your congregation afterward. Scout reads serving, giving, and groups to show you who's leaning in and who's pulling back, which is the question you'll be asking the week after launch.
Frequently asked questions
How do you build a launch team for a church plant? Start with a clear ask and a short list of the roles you actually need: setup and teardown, kids, hospitality, worship, and a coordinator. Recruit relationally, give each person one job and a name, and keep a single living list of who said yes so it carries straight into launch.
How many people do you need on a church launch team? There's no single right number. Some networks point planters toward 40 to 50 committed adults for a sustainable launch; others argue a smaller, fully committed core of 15 to 30 launches better than a big curious crowd. Either way, you need enough to cover setup, kids, hospitality, and worship on a Sunday without burning anyone out, and depth in a few roles beats a long roster of occasional names.
What is the difference between committed and interested launch team members? Interested people like the vision and show up when it's convenient. Committed people take a named role, hold a recurring time, and reorganize their week around it. The test is simple: give someone a real responsibility with a date attached and watch whether they follow through.
What roles do you need on a church plant launch team? At minimum you need setup and teardown, kids and check-in, hospitality and first impressions, worship and tech, and one coordinator who holds the whole list. Everything else can wait. Keep the org chart small enough that you can name every person in each role from memory.
Nic Moore is a pastor who planted a church and still has the messy first spreadsheet where he learned the hard way that a launch team is built on who shows up, not who's excited.