Multisite, Church Plant, or Merger: Choosing the Right Expansion Strategy

Three pastors I have talked with in the last six months are working on three different versions of the same church expansion strategy decision: multisite, church plant, or merger.

The first is a lead pastor of a 600-member church in a growing suburb. Their primary service is at 92 percent capacity, the parking lot fills up before the service starts, and the closest comparable church is 18 miles away. They are talking about a second campus.

The second is the lead pastor of a 450-member church whose two largest small groups have started meeting in two different neighborhoods 25 minutes apart. He is 53, his associate is 32, and the associate has been quietly carrying a vision for the southern part of the city for two years. They are talking about a plant.

The third is the lead pastor of a 280-member church whose denominational neighbor, two miles away, has been below 80 attenders for four years and just lost their pastor. The denomination called him last month. They are talking about a merger.

All three pastors typed the same phrase into Google last weekend. Church expansion strategy. And almost everything they read pushed them toward whichever model the publisher happened to sell. The multisite consultant said multisite. The planting network said plant. Almost nobody wrote seriously about the merger.

This post is the comparison they actually needed. Three models, side by side, with honest cost, timeline, survival data, and a decision framework. No advocacy for any one path. The right answer depends entirely on what your church is constrained by, and that is the part most expansion content skips.

If you have already chosen your model and you need the week-by-week build, our church expansion 90-day action plan is the calendar. This post is what you read before that one.

The right question isn't which model. It's what you're constrained by.

Most expansion conversations start with the wrong question. The wrong question is "should we go multisite or plant?" The right question is "what is constraining the next 100 people we are trying to reach?"

If the answer is seats on Sunday at 10 a.m., you may not need expansion at all. You may need a second service, a renovation, or a Saturday night option. Adding a campus to solve a seat problem is the most expensive seat in the world.

If the answer is geography, you have a real expansion question. People in a different part of your city are not going to drive past two other churches to reach yours. The question becomes whether you extend your church into that geography (multisite) or send people to start a new church there (plant).

If the answer is a struggling congregation that already exists in your geography, the question is whether a merger is more kingdom-minded than competition. Two half-empty rooms a mile apart are usually a worse picture than one full room with two committed teams.

If the answer is we just feel like we should grow, slow down. Growth without a constraint is usually a calling problem disguised as a strategy problem. Carey Nieuwhof has written extensively that the churches with the clearest expansion stories are the ones who can name the specific group of people they are not currently reaching. Conviction without a named constraint usually means the right answer is to do the existing thing better, not bigger.

So before you choose between multisite, plant, and merger, write one paragraph: who are we trying to reach in the next 24 months that we cannot currently reach, and why can we not currently reach them? If you cannot finish that sentence, the model question is premature.

If you can finish it, the constraint usually points to the model on its own. The rest of this post is the comparison that helps you confirm.

The three church expansion strategies at a glance

Here is the side-by-side comparison most expansion blogs avoid because their business depends on advocating for one column. We have no advocacy here. The right answer is the one that fits your context.

A few honest notes on this table.

The cost ranges assume the lower end is a smaller, leaner version of the model and the higher end is a city-center launch with paid worship, kids, and production staff. The actual number depends on your region, denomination, and whether you are renting, building, or being given a building.

The survival numbers come from a 2022 joint Lifeway and NAMB report on church plants and multisite campuses. They are the best public data we have, and they should be read as a baseline, not a guarantee. Survival is also not the only measure of success. A plant that lasts ten years and sends out two more plants has a different fruit profile than a campus that quietly absorbs back into the mother church.

The merger row is harder to put a single number on, because mergers come in four different forms and each form has its own success profile. We will get to that.

Multisite: One church in multiple locations

A multisite church is one church that meets in two or more physical locations, with shared leadership, shared finances, and usually shared teaching (live or video). Multisite is the right model when your brand and systems are strong, the constraint is geography, and you have the lay leadership to populate a new campus without gutting the original.

The reason multisite has dominated the conversation for the last decade is that it works. The same Lifeway and NAMB data shows roughly 80 percent of multisite campuses still operating at year five, which is materially higher than plant survival. The reason is structural. A campus inherits the sending church's brand, donor base, leadership pipeline, and systems on day one. The campus pastor is not building an organization from scratch. They are running a known playbook in a new location.

That structural advantage is also the failure pattern. Multisite campuses tend to underperform when the sending church's systems are not actually as strong as the leadership thought. If your member database has duplicate records, your volunteer rotation lives in three spreadsheets, and your follow-up process depends on the same exhausted person who has been carrying it for five years, expansion will multiply that mess across both locations. The campus does not fix the operational gaps. It exposes them.

The other failure pattern is brand thinning. The first campus is usually a stretch but doable because the sending church gives it a disproportionate share of senior staff attention. The second campus is harder. The third is where most multisite churches discover they have built a confederation of underfunded campuses instead of one strong multi-location church. Carey Nieuwhof's writing on multisite consistently flags this: the structural pressure to keep launching campuses can drift into a numbers game that the underlying ministry capacity cannot support.

Multisite fits best when:

• Your primary service is consistently above 80 percent capacity
• You have a working visitor follow-up system that returns more than 20 percent of guests
• You have at least eight lay leaders who could carry a ministry area at a new location
• The geography you want to reach is more than 15 minutes from your current building
• Your member, giving, and volunteer systems can carry a second context without doubling your admin work

When I was designing Flowbudd, I kept coming back to that last point. I have watched two multisite teams I love spend the first 90 days of their second campus reconciling spreadsheets between databases. The campus pastor's first quarter went to data hygiene instead of pastoral care. That is the operational tax most multisite content does not warn you about. If your systems are the bottleneck, the model is going to amplify the bottleneck.

Church plant: Sending, not extending

A church plant is a new, autonomous congregation that the sending church helps launch but does not run long term. Plant when your call is to send, not to extend, and when the new congregation needs its own leadership, name, and identity rather than a campus relationship to your church.

The plant survival rate (about 68 percent past year four, per Lifeway and NAMB) is lower than multisite, but the framing matters. A plant is not a smaller version of multisite. It is a different ministry vehicle with a different goal. The point of a plant is not the survival of the new congregation. It is the multiplication of churches in places that need a new church.

Christianity Today's research on church planting costs found a strong correlation between adequate funding at launch and long-term survival. The plants that survive are not the ones with the most charismatic planters. They are the ones with three years of runway, a launch team of 50 or more committed adults, and a sending church that does not pull back the support after year one.

The most common failure pattern in church plants is loneliness. The planter goes from a staff team of six to a staff team of one. The launch team is excited for six months and then life gets in the way. By month nine, the planter is preaching, doing pastoral care, running the kids' check-in, and handling the giving statements. Burnout in church plants is not primarily a money problem. It is an isolation problem.

The second failure pattern is misaligned timeline expectations. A plant that has not broken 75 attenders by year two often gets quietly written off as "not working" when in fact most healthy plants do not stabilize until year three. Sending churches that pull funding at month 18 because the numbers are not there yet are killing plants that would have made it.

A church plant fits best when:

• You have a clear sense of "send" rather than "extend" (the new congregation needs its own identity)
• Your sending church has at least 24 months of operating reserves AND a 36-month commitment to fund the plant
• The planter is genuinely visionary and entrepreneurial (this is a different skill set than running a campus)
• You can recruit a launch team of at least 25 to 50 committed adults, ideally drawn from people who already live in the target area
• You are willing to accept that the plant may eventually look very different from the sending church (different style, different demographics, different theology emphasis within the same family)

If your conviction is "we want to make a copy of our church somewhere else," that is multisite. If your conviction is "we want to release a different expression of the gospel into a context we cannot fully reach," that is a plant. The honest pre-question is which one you actually mean.

Merger: Two churches becoming one

A church merger is the combination of two existing congregations into one. Mergers are the most underrated expansion strategy because they look defensive ("we are absorbing a struggling church") when in fact most healthy mergers are offensive: two churches do more kingdom work together than apart.

In Better Together: Making Church Mergers Work (Leadership Network, 2012), Jim Tomberlin and Warren Bird estimate that about 2 percent of US churches enter a merger conversation each year, which is several thousand churches annually. The book identifies four practical merger types, and the type matters more than almost any other variable.

Rebirth is when a struggling church is relaunched under healthy leadership. The struggling church donates its building, brand, or congregation to a new vision, often with the existing pastor stepping down or transitioning to a non-lead role. Rebirths tend to do well because the model has a clear "before and after" and the leadership transition is decided up front.

Adoption is when a small church joins a larger one as a campus. The adopting church absorbs the people, building, and ministry obligations of the smaller church. Adoptions are structurally similar to multisite from the larger church's perspective and structurally similar to a campus launch from the smaller church's perspective. They tend to do well when the smaller church genuinely wants the change.

Marriage is two healthy peer churches combining. This is the romantic version of mergers and the one that most often stalls. Two equal partners means two existing pastors, two leadership cultures, two sets of expectations, and two grieving congregations who each thought their identity would survive the merger. Most peer-to-peer marriages take longer than expected and require a clearer leadership plan than the parties initially want to make.

ICU is the emergency version. One church is days or weeks from closing, and another church steps in to keep the building open and the people pastored. ICU mergers are kingdom work but operationally difficult, and they generally only work when the receiving church has the bandwidth to carry the weight of a quick transition.

The biggest predictor of merger success is naming the type honestly before the announcement. A "marriage of equals" that is actually an adoption (one side has the leadership and money, the other has the building and the grief) almost always blows up at month nine when the equal partnership turns out not to be equal.

A merger fits best when:

• There is a partner church near you whose strengths and weaknesses are genuinely complementary to yours
• Both leaderships can name the merger type honestly (rebirth, adoption, marriage, or ICU) and agree on it
• The leadership transition plan is decided up front, in writing, before any congregational announcement
• The cost of not merging (one or both churches declining toward closure) is honest and shared
• Theological alignment is real, not negotiated to make the merger work

Mergers are usually faster and cheaper than multisite or plants because the people, building, and giving base already exist. They are also more emotionally complicated than the spreadsheet suggests, because you are not just combining organizations. You are asking two congregations to grieve who they used to be in order to become someone new.

A decision flowchart you can actually use

Here is the prose version of the decision tree. Walk through it with your leadership team. Honest answers only.

Start here. Is your primary service consistently above 80 percent capacity for the last six months, AND is your visitor return rate above 20 percent, AND do you have at least three lay leaders ready to step up this year?

If the answer to any of those three is no, the right move for the next 12 months is not expansion. It is fixing the prerequisite. Use the next year to strengthen assimilation, build leadership depth, and consolidate operations. Come back to the expansion question once the foundation is solid. Our guides on church leadership structures that work and managing a large church with a small team are where most under-prepared churches start.

If the answer to all three is yes, continue.

Question 2. What constrains the people you are trying to reach? Is it geography (they live too far away), context (they need a different style or expression), or proximity (there is already a struggling church near them that needs help)?

If the constraint is geography, you are choosing between multisite and plant. Continue to question 3.

If the constraint is context (they need a Spanish-speaking service, a Gen Z-focused service, a contemplative liturgical service that your current church does not offer), plant is almost always the right answer. A campus that tries to be a different church than the mother church usually breaks the multisite model.

If the constraint is a specific nearby church that is healthier together with you than apart, jump to question 5.

Question 3. Do you want the new location to be a copy of your church (same teaching, same style, same brand) or a new expression that is sent from your church but free to become its own thing?

If you want a copy, multisite is the model. Continue to question 4.

If you want a new expression, plant is the model. Skip to question 6.

Question 4 (multisite path). Do your member, giving, and volunteer systems run cleanly across one location today? If you are already managing five disconnected tools at the original church, expansion will double the integration debt. Either consolidate first or build the consolidation into the launch plan. Then continue to the 90-day expansion action plan.

Question 5 (merger path). What type of merger is this honestly? Rebirth, adoption, marriage, or ICU? Get both leaderships to agree on the type in writing before any congregational announcement. If the two leaderships cannot agree on the type, the merger is not ready. Continue to the 90-day plan once the type is named.

Question 6 (plant path). Do you have a planter (a person, not a job description), a 36-month funding commitment, and 25 to 50 launch team members willing to commit a year? If yes, you are ready. If no, slow down. Plants without a planter are wishes, plants without funding are nonprofits that do not survive year three, and plants without a launch team are pastors preaching to empty chairs.

A short quiz: which path fits your context?

Score one point for each statement you can honestly say "yes" to. Tally each column at the end. The highest column is the model your context most likely supports right now.

Multisite (one point each yes):

1. Our brand and culture are strong enough that people would recognize us as the same church in a new location
2. We have at least eight lay leaders who could carry a ministry area at a new campus
3. The geography we want to reach is more than 15 minutes from our current building
4. We have 150,000 to 500,000 dollars in startup capital we can deploy without putting the existing church at risk
5. Our member, giving, and volunteer systems already run cleanly at one location
6. We are willing to share teaching (live or video) and not let the campus become a different church

Church plant (one point each yes):

1. We have a specific person we believe is called to plant, not just a campus pastor we want to give a step up to
2. We can commit to funding the plant for at least 36 months, not 12
3. We can recruit a launch team of 25 to 50 committed adults, ideally living in the target area
4. We are willing to release the plant to develop its own identity, leadership, and theology emphasis within the same family
5. The constraint we are solving is more about context (style, demographic, language) than just seats
6. Our planter can build a community from scratch, not just run an existing playbook

Merger (one point each yes):

1. There is a real partner church near us whose strengths and weaknesses complement ours
2. Both leaderships can name the merger type honestly (rebirth, adoption, marriage, or ICU)
3. We can write down the leadership transition plan up front, before any announcement
4. Theological and cultural alignment between the two churches is real, not aspirational
5. Both congregations are willing to grieve who they used to be in order to become someone new
6. The cost of not merging (one or both churches declining toward closure) is honest and shared

If your highest-scoring column is at 5 or 6, you have strong directional clarity. If your highest column is at 3 or below, you are not ready for that model yet. If two columns are tied, you have a real conversation to have with your leadership team. The quiz is a discussion starter, not a verdict.

When the honest answer is "none of these yet"

Sometimes the most pastoral answer is to wait a year.

If your primary service is at 60 percent capacity, your visitor return rate is below 15 percent, your lay leadership pipeline is two people deep, or your finance reserves are under three months, expansion will expose every weakness rather than solve it. The Hartford Institute's Faith Communities Today data shows that 85 percent of North American churches have fewer than 200 weekly attenders, and the bottleneck for most of them is structural, not numerical.

Doing nothing this year is not failure. Strengthening the assimilation system, deepening the leadership bench, consolidating the tool stack, and getting the operations clean is what separates churches that expand well from churches that expand and then quietly contract.

If that is where you are, our posts on church leadership structures that work and managing a large church with a small team are where to start. Build the foundation. Come back to this post when the foundation is real.

What to do once you've chosen

The model is the start of the conversation, not the end. Once your leadership team has named the constraint and chosen the path, the next 12 weeks are about audit, build, and launch.

Our church expansion 90-day action plan is the week-by-week calendar. Weeks 1 to 4 are the audit phase (numbers, model confirmation, financial stress test, alignment). Weeks 5 to 8 are the build phase (launch team, assimilation, systems, vision casting). Weeks 9 to 12 are the launch phase (soft launch, public launch, retention, review).

The plan is the same shape for all three models. The work inside each week looks different depending on whether you are launching a campus, planting a church, or merging two congregations. But the rhythm of audit-build-launch is universal.

Pick the model. Then pick the calendar. Then run the play.

About the author

Daniel Olaleye is the founder of Flowbudd, the all-in-one church management platform that brings giving, communications, volunteers, and member management into one place. He grew up in a church family and builds software to give pastors their week back. Reach him at founder@flowbudd.com.