Church planting and the relational lens

A planting team's hardest season is rarely the first convert. It comes after the fruit arrives, when the web of relationships grows faster than any one person can hold in their head, and people start slipping out of view.

Key takeaways

• Multiplication runs on relationships, and relationships are exactly what memory cannot hold. As a planting team bears fruit, the people in its care outgrow memory long before they outgrow the mission.
• Momentum dies where people get forgotten. A new believer who goes a month with no contact does not file a complaint. They simply drift, and the line of disciples that might have come through them never forms.
• The early church treated systematic care as part of the mission. Acts 6 shows the apostles building a structure so that no one in their care would be overlooked.
• 2 Timothy 2:2 describes a chain of relationships. Entrusting the gospel to faithful people who will teach others requires knowing who those faithful people are and where each one stands.
• A tool's honest job here is to help a human team not forget anyone and coordinate who has whom. FlockConnect reads scattered signals into a per-person view, shares care across a team, and lets Collie surface and draft, while a person reviews and approves every step.

Where multiplication actually breaks

Ask a church planter what nearly ended the work, and the answer is rarely the obvious enemy. It is rarely opposition, and it is rarely a dry season. It is the season right after the fruit comes.

For the first stretch, a planting team can hold everything in its head. There are a handful of contacts, two or three people studying Scripture, one person who has just believed. The team knows each name, each next step, each unanswered question. Care is effortless because the whole picture fits in one mind.

Then the gospel does what it is supposed to do. The one who believed brings two friends. A study becomes a small gathering. Someone the team barely met is suddenly leading others. The work has not slowed. It has succeeded. And success is what overwhelms the system, because the relational web now grows faster than any single person can track it. The people are no longer the bottleneck. Holding them in view is.

This is the point where most efforts plateau, and they plateau quietly. No one decides to stop caring. A team simply runs out of room to remember, and the people who fall out of view are, by definition, the ones nobody notices are gone.

Why momentum dies in the forgotten

The math of multiplication is encouraging right up until it is frightening. One disciple becomes three. Three become a small gathering. A leader emerges and starts something new in a network the team has never visited. Each layer is good news. Stacked together, they are more relationships than memory can carry.

The first person to get lost is usually the ordinary one: the new believer who had two real conversations and then went three weeks without a third. Nobody meant to drop them. The team was busy with the people in front of it, and this person was not in front of anyone. They drift, and the line of disciples that might have come through them never forms. A movement does not usually die from a single failure. It thins out, one forgotten person at a time, until the multiplication that depended on each link in the chain has too many broken links to spread.

So the hard truth underneath the encouraging math is this. Multiplication depends on no one falling through the cracks, and keeping people from falling through the cracks takes intentional attention to relationships. A notebook and a hope that you will remember will not carry it.

What 100 house churches really required

The clearest picture of healthy multiplication is a story rather than a chart.

KC Underground, a network in Kansas City, has reported roughly 100 microchurches forming over about five years. Its leaders describe much of that growth coming through new disciples rather than transfer from existing congregations, which is the kind of fruit a planting team prays for. It is worth looking closely at what made it possible.

By their own account, the order in the multiplication came from care rather than from a single charismatic leader carrying everyone. It grew through intentional relational shepherding, repeated and handed off: ordinary believers discipling the next person, who discipled the next, with someone paying deliberate attention to each relationship so the chain did not break.

Two cautions about reading a story like this. First, it shows what intentional relational care can support. It is not an outcome any tool can promise. Software does not plant churches; people obeying Jesus do. Second, the lesson is not "track more metrics." The lesson is that attention to people, sustained as the numbers grow, is the thing that lets fruit become more fruit. A planting team does not need a movement-analytics dashboard. It needs to not forget anyone.

The early church already knew this

The instinct to build structure so that no one gets overlooked goes back to the New Testament. It is there from the beginning.

In Acts 6, the early church is growing fast, and a real failure of care surfaces: some widows are being overlooked in the daily distribution. The apostles do not treat this as a distraction from the spiritual work. They treat it as part of it, and they build a structure so that the overlooked get seen. The point translates directly to the field. A growing body of people in your care will produce people who slip through, unless someone is responsible for making sure they do not.

Paul gives the planting logic its most quoted form. In 2 Timothy 2:2 he tells Timothy to entrust what he has heard to faithful people who will be able to teach others. Read it slowly and it is a chain of relationships across at least four links: Paul, Timothy, faithful people, others also. That chain only holds if someone knows who the faithful people are, where each one is, and who is being entrusted to whom. Multiplication, in Paul's own framing, is relational bookkeeping done out of love.

The companion piece on the early church model and authentic community sits alongside this point: the structures the first Christians built existed to protect relationships rather than replace them.

What the disciple-makers keep saying

Mission writers who have watched real multiplication tend to land in the same place from different angles.

David Platt, in Radical, presses the church not to soften the cost of the Great Commission into something comfortable. Going and making disciples is costly, hands-on work, and teaching people to obey everything Christ commanded assumes you actually know the people you are teaching well enough to walk with them. That is a paraphrase rather than a quotation, but the thrust is clear: real obedience to the command is personal, and it cannot be done at a distance.

Francis Chan, in Multiply and again in Letters to the Church, argues that the New Testament church was a family before it was a program, and that reproducible discipleship depends on relationships dense enough to pass faith from one person to the next. You cannot entrust responsibility to a faithful person you have lost track of. The friendships are the mechanism, not an accessory to the mission.

Neither writer is describing a feature set. They are describing a way of paying attention. The question for a planting team is simply whether its attention can keep up with its fruit.

What a tool can honestly do here

So where does software fit, and where does it overreach?

It overreaches the moment it claims to run the movement. A tool cannot assess "movement health," map spiritual genealogies, or tell a team who is ready to lead. Those are discernment, and discernment belongs to people who know the person and are praying for them. Any product that promises to do that work for you is selling a fantasy that will quietly replace the very relationships it claims to serve.

What a tool can honestly do is narrower and more useful. It can help a human team not forget anyone, and coordinate who is responsible for whom. That is the same job FlockConnect does for a church, applied to the field.

FlockConnect is a Church Relationship Manager, a ChRM, that complements the systems a team already uses rather than replacing them. It is people-facing for the team, while the contacts have no logins, and a few principles govern how it helps a planting team specifically.

• A per-person view, so nobody is invisible. It reads the signals a team already produces into one clear picture of who is connected and who is being forgotten, so the person nobody has spoken to in a month becomes visible to someone who can reach out.
• Care shared across a team, so responsibility is coordinated. When several people are shepherding, it keeps clear who has whom, which closes the two classic failures: two people calling the same contact, and everyone assuming someone else has the one who slipped.
• Collie, the assistant, is advisory. It can surface who looks isolated or has gone quiet and draft a suggested next step, but it does not send messages, write to records, or change anyone's care on its own. A person reviews and approves every action. The team decides; the tool prepares.

It works with what a team already has, offering an official two-way Planning Center integration as its one native connection and CSV import for everyone else. The aim is not a richer report. The aim is that fewer people get forgotten as the fruit multiplies.

Start before the system gets big

A planting team does not need a platform to start caring well. The discipline comes first, and it scales whether you have ten people in your care or two hundred.

1. List everyone you are walking with right now, at any stage. Be honest: most teams have more relationships than they realized, scattered across notebooks, group chats, and memory.
2. For each person, ask one question: who on the team would notice if this person went quiet for a month? If the answer is "no one," that is the gap to close first.
3. Decide who is responsible for whom, in writing, so care is assigned instead of assumed.

That practice is the whole game, and it works on paper until the paper outgrows you. When holding the relationships in your head stops being possible, that is the moment a ChRM earns its place. FlockConnect is priced by church size, with a free trial, so the team carrying the work is never penalized for the fruit. The deeper principle behind it is the one simple discipleship systems for small churches returns to as well: the goal is never the system. The goal is that no one entrusted to your care leaves unknown.

About the author

Michael Tribett is the founder of FlockConnect, a Church Relationship Manager built to help pastors see who is connected and who is drifting. He holds a Master of Divinity in Christian Ministry from Southeastern Baptist Theological Seminary, where he focused on missions and discipleship, and he serves as a small group leader at his church in the Raleigh, North Carolina area. FlockConnect is an official Planning Center partner.

Frequently asked questions

Why do church planting movements stall after the first few churches? Usually not for lack of calling or effort. As a team bears fruit, the web of relationships outgrows what any one person can hold in their head, people get forgotten, and the lines of disciples that would have come through them never form. Multiplication depends on no one falling through the cracks, which takes intentional attention rather than memory.

Is it biblical to track the people you are discipling? Yes. Acts 6 shows the early church building a structure so that no one in its care was overlooked, and 2 Timothy 2:2 describes a chain of people entrusting the gospel to faithful people who teach others. Both assume you know who your people are and where each one stands. The structure exists to protect relationships, not replace them.

Can a tool measure the health of a disciple-making movement? No, and you should be wary of any tool that says it can. Assessing spiritual readiness or movement health is discernment that belongs to people who know the person. What a tool can honestly do is help a team not forget anyone and coordinate who is responsible for whom.

What is the KC Underground example, and is it a FlockConnect outcome? KC Underground is a Kansas City network that has reported roughly 100 microchurches forming over about five years, with its leaders describing much of the growth coming through new disciples rather than transfer. It is a real example of multiplication through intentional relational shepherding, and it is not a result any tool can guarantee. People obeying Jesus plant churches; software only helps a team keep its people in view.

How does FlockConnect actually help a planting team? It gives a per-person view so the team can see who is being forgotten, it shares care across the team so responsibility is coordinated, and Collie can surface who looks isolated or has gone quiet and draft a next step. A person reviews and approves every action; Collie never sends, writes, or changes care on its own.

Does Collie contact people or update records on its own? No. Collie is advisory. It surfaces who looks isolated and drafts a suggested step, and then a human on the team reviews, approves, and acts. It does not send messages, write to records, or change anyone's care without a person.

Do we have to leave the systems we already use? No. FlockConnect offers an official two-way Planning Center integration as its one native connection and CSV import for everyone else, so a team can keep its current tools and still get one clear per-person view of the people in its care.