Church Planting
The church planter's operating system: what to set up before launch day
You set up a church plant's operating system by getting six pieces working before launch day: a people record, a way to receive giving, a way to communicate with the room, a kids check-in process, a guest follow-up rhythm, and a way to organize volunteers. Get those standing and you can run a launch without dropping anyone in the gaps.
When we were planting, I had a beautiful logo and a launch-team text thread before I had any way of remembering who walked in the door on a preview Sunday. That was backwards. The operational pieces are not the glamorous part of planting, but they are the part that decides whether a first-time guest gets a second conversation or disappears into a folder of good intentions. This page is the map. Each section is short on purpose, with a link to the deep dive for when you're ready to build that piece.
What systems does a church plant actually need before launch?
A plant needs six operational systems before launch: a people record, giving, communication, check-in, follow-up, and volunteers. You don't need all of them polished. You need each of them present in some form. The table below is the whole map in one place, with what each system does and when you realistically need it working.
The honest version is that most planters over-build the website and under-build the parts nobody sees. Here is the order I'd stand them up if I were doing it again.
| System | What it does | When you need it by |
|---|---|---|
| People record | Remembers who is in your world: names, contact info, who came when | First preview gathering |
| Giving | Lets people give online and in person, and tracks it cleanly | Before your first public service |
| Communication | Gets a message to your launch team and your room | Launch-team formation |
| Kids check-in | Safely signs children in and out, matches them to a guardian | First Sunday with kids present |
| Guest follow-up | Turns a first-time guest into a second conversation | First guest you don't already know |
| Volunteers | Organizes who serves where, and asks people in a way they can say yes to | A few weeks before launch |
If you want the broader version of this same question, with specific tool categories named, start with what software a church plant actually needs. It's the companion to this page.
What's the first system to set up when planting a church?
Set up your people record first, before giving, before the website, before the launch graphics. A people record is the one thing every other system depends on, because giving, follow-up, and volunteer scheduling all hang off knowing who is actually in your world and what they've done so far. Get this one wrong and everything downstream wobbles.
For a launch team of a dozen, a shared spreadsheet is a legitimate people record. Columns for name, contact, how they found you, and the date they first showed up will carry you further than you'd think. The trouble starts when the spreadsheet can't answer a pastoral question, like who came twice and then went quiet. For the full walkthrough of keeping names from slipping, see how to keep track of everyone at a new plant. And if you're weighing whether to graduate from the spreadsheet now or later, do you need church management software before launch lays out the trade honestly.
How should a church plant handle giving before launch?
Get the financial plumbing in place before your first public service: an EIN, a bank account in the church's name, and a giving processor that charges only standard transaction fees. Test it with a real one-dollar gift to yourself before launch day so you're not debugging at the back table while someone waits to give.
One thing worth saying plainly: be careful with anyone promising "free" giving. Every gift still costs the payment processor's standard fees. Stripe's discounted nonprofit card rate runs around 2.2% plus thirty cents per transaction, and bank-transfer (ACH) giving is cheaper still. A good setup means no platform takes an extra cut on top of that, not that giving costs you nothing. The step-by-step is in setting up online giving for church plants.
What's the cheapest way to run a plant's systems?
The cheapest stack is built from tools you already know: a spreadsheet for people, a free group-messaging app for communication, and a giving processor that only charges standard transaction fees. You can run a plant's first season for close to nothing if you're willing to do a little manual stitching between tools.
The hidden cost isn't the monthly fee. It's the time you spend copying a name from your giving tool into your spreadsheet into your text thread. That juggling is fine at fifteen people and miserable at a hundred. When the stitching starts eating your Monday mornings, it's time to consolidate. I broke down the actual dollar figures in the cheapest way to run a plant's systems.
How do you handle people, follow-up, and volunteers with almost no team?
You handle it by building the launch team first, then using that team to cover follow-up and serving roles while the room is still small. Your launch team is your people system, your volunteer base, and your first guest-follow-up crew all at once. Treat building it as the central planting task rather than a side errand you get to after the logo is done.
Three of the spokes live under this one section because they're so tied together in practice:
- Build the team. Recruit a launch team that can carry the weight of a first season, and organize them so they know what they own. The how is in building a church launch team.
- Recruit volunteers. When you barely have people, asking well matters more than asking often. Recruiting volunteers for a church plant covers how to make a real ask.
- Follow up with guests. A guest who came once and heard nothing back has been told something. Set up a guest follow-up process for a plant with no system yet before you have your first guest, not after.
A note on kids check-in, since it doesn't get its own spoke yet: even with five kids, have a process that safely matches each child to a guardian on the way in and out. It can be a clipboard and matching tags for a season. Just don't improvise it on launch morning with strangers in the room.
How should a church plant use AI without losing the plot?
Use AI for the labor that drains a small team, drafting follow-up notes, summarizing what happened on a Sunday, sorting your week, and keep human judgment on anything pastoral. AI can help you notice that someone has gone quiet. It should never be the one deciding what that means for that person's walk with God.
I'm cautious here, and I think planters should be too. The practical and ethical version of this is in how a church plant should use AI, and a concrete tool list is in the best AI tools for church planters in 2026. The line I hold is simple: AI surfaces the observation, a person carries the care.
How do you choose church software as a planter?
Choose software the way you'd choose anything for a young plant: by whether it reduces the number of disconnected tools you're juggling, fits a planting budget, and matches the size you actually are right now, not the size you hope to be. The best fit is usually the one system that holds people, giving, and serving together so a name only lives in one place.
This is where Scout fits, honestly and lightly. It's one place where serving, giving, groups, and check-ins land on the same person record, so the system can tell you when someone who used to show up has pulled back. Scout takes no cut of your giving; you still pay the processor's standard fees. If you're comparing options, how to choose church software as a planter walks the decision, and the best church management software for church plants in 2026 names specific tools. Pick the one that lets you spend Sunday afternoon thinking about people instead of reconciling spreadsheets.
Frequently asked questions
What systems does a church plant need before launch day? A plant needs six things working before launch: a people record so names don't vanish, a way to receive giving, a way to communicate with the room, a kids check-in process, a guest follow-up rhythm, and a way to organize volunteers. Everything else can wait until you have actual people and actual problems.
Do I need church management software before I launch a church? Not necessarily on day one. A shared spreadsheet covers a launch team of fifteen. You'll want real church management software once names are slipping through the cracks, usually within the first couple of months, because the cost of re-finding people is higher than the cost of the tool.
What's the cheapest way to run a church plant's systems? Start with free or near-free tools you already know: a spreadsheet for people, a free group-messaging app for communication, and a giving processor that charges only standard transaction fees. Consolidate into one church management system once juggling separate tools costs you more time than money.
What should a church planter set up first? Set up your people record first. Every other system, giving, follow-up, check-in, volunteers, hangs off knowing who is actually in your world. If you can't answer "who came last week and did anyone reach out to them," nothing else you build will hold.
Nic Moore is a pastor who planted a church and learned the hard way that the systems nobody claps for are the ones that decide whether a first-time guest ever gets a second conversation.