Why Growth and Connection Are Opposite Problems

This piece first ran on ChurchTechToday.

Churches aim for getting more people in the room. The more people in the room, the healthier the church must be, right? But when a group of pastors was asked "what is making your church grow right now?", the answer isn't usually about successful paid ads or a back to school event that went well. Everyone answers with a common thread, their growth is directly correlated to their level of connection. Growth measures who's arriving, but connection measures who's staying. It's easy to fall into the trap of only building systems for the first one.

If you're a church leader, you could likely tell me what your attendance was last Sunday, what your giving trajectory is for this quarter, and your first-time guest count. But when asked a question like "how many people who were regularly attending six months ago have quietly stopped coming," you may have to give me a guess, not a concrete answer. Why is this? I will tell you that it is certainly not because pastoral care matters less than outreach. It's because outreach comes with a dashboard and care does not.

A marketing budget gets justified with a report. A staff hire gets justified with a metric. Nobody's building a presentation slide for "we noticed Karen wasn't here for a month and someone checked in."

So when a church has limited time, limited staff, and limited software budget (and it almost always does) the money and attention flow toward what's easy to measure and report up the chain.

Growth gets systems because growth is visible. Connection stays dependent on whoever happens to notice, which usually means it depends on how well-staffed and well-rested the connections person is in any given season. Churches (and most orgs, honestly) tend to build infrastructure around what they can already see.

Until noticing someone fade out is treated as a number worth tracking rather than a hope that someone catches it, connection will keep losing the budget argument to growth, every single time. What will that do for the people that are looking for belonging in your church?

What "quietly stops showing up" actually looks like

Let's paint this picture with a fairly typical member. Shelby and her family have been attending for two years. She sings in the worship rotation twice a month and she used to lead a youth group, but the students all grew up. So week one, she misses because of a work trip. Nobody thinks twice, people travel.

Then the leadership of the worship team changes and she isn't requested again. Week three and four, she's gone again, this time no reason given. Still nothing unusual, attendance dips and swells constantly. By week six, she's down to once a month and volunteering has stopped completely.

By week ten, she hasn't been seen or asked to volunteer in two months, and by week fourteen, she and her family are not coming back, though nobody quite knows when that became true. At no point in that stretch did anything happen that would trigger a phone call. No single absence looked wrong. No one event marked the moment she left. That's precisely what makes this pattern so hard to catch, and precisely why almost nothing catches it.

And no ChMS flags it because no single absence looks unusual.

The frustrating part is when we compare that to how a business would treat the same data. A dip in usage frequency over ten to fourteen weeks would flag as a churn risk almost immediately, and it would trigger some kind of outreach before the customer canceled entirely. Yet churches, for all our focus on hospitality, mostly don't have the equivalent. Attendance gets counted, but it rarely gets read as a pattern. One missed Sunday and fourteen missed Sundays look the same in most systems. Just an absence, logged and forgotten.

However, unlike business, where if you are forgotten you probably just get a few less emails, getting forgotten by your church strikes deep.

This is also the part of the story that's hardest to talk about because it isn't really about data at all. It's about the particular ache of realizing, sometimes months later, that you drifted out of a community and nobody asked why. The truth is it's not because they didn't care, but rather that nothing in the room was built to notice.

The good news

The good news is we can typically piece together the same data points that we have to measure growth to thread together a picture of who is starting to quietly slip away. Right now, these reports live in silos, but when pieced together, you can see the signs that someone is moving away from your church and step in before it's too late.

Here are 5 signs to look out for. Because, when in concert, these are the signals that it's time for you to step in.

• Serving: Their serving rhythm breaks. They skip one rotation, then two. Serving is usually the first thread to snap.
• Giving: Giving pauses without a conversation. Not necessarily the amount, but the rhythm.
• Group drift: Their group goes quiet on them and vice versa. They're still on the roster, but stopped showing up. Group leaders notice but rarely report it.
• Digitally unengaged: They've stopped interacting. Emails unopened, texts unanswered, forms unfilled. Digital silence usually precedes physical absence.
• Inconsistency: They're around but not in rhythm anywhere. Attending sometimes, connected to nothing. The hardest one to see and the most common.

Why the signals live in silos

You're probably closer to solving this problem than you think, because someone likely already notices most of these things. The volunteer coordinator sees the missed serving shifts. Finance sees the giving pause. A small group leader notices when someone goes quiet in the group chat. Whoever runs your church app can see, if they think to look, who hasn't opened an email in six weeks. The information exists. It's just scattered across five different people doing five different jobs, and connecting the dots isn't part of any of those jobs.

It's the same problem from earlier, just showing up smaller. Nobody built a report for "3 of these signals fired on the same person this month," because building that report isn't anybody's assignment. The volunteer coordinator isn't checking giving records. Finance isn't sitting in on every small group. And even when everyone involved genuinely cares, which they usually do, there's no shared place for what they've noticed to land. No one whose job is to look across all five and ask what it means when a few of them show up together under the same name.

Right here is where most churches stop, and it makes sense that they do. Cross-referencing five data sources by hand, every week, for every person in the church, isn't a task. It's a full-time job nobody budgeted for. So the signals stay exactly where they are. Technically visible. Never actually seen.

What actually closes the gap

Closing the gap doesn't mean throwing out what you already have and starting over. It means deciding, on purpose, that these five signals are worth looking at together instead of five times separately.

In practice, that's a few decisions, not a new department:

• Set a threshold. Agree ahead of time what counts as worth a check-in. I suggest "two or more signals inside a rolling two months" as a reasonable place to start.
• Assign ownership before you need it. This doesn't have to be a pastor. A care team, a volunteer, anyone works, as long as someone actually owns the follow-up instead of it being everyone's job and therefore no one's. Bonus: try making calls or follow up in person if you can. This is about connection, after all.
• Separate this from new guest follow-up. Most churches already do first-time guest care well. Quietly-drifting members need a different playbook, because by the time someone's down to once a month, "welcome" isn't the right conversation anymore.

None of this requires new software, or a big budget line. It requires treating the noticing itself as a job, not a hope.

That said, this is exactly why we built Bellwether. It connects to the tools you already use, your ChMS, your giving platform, your small group software, and watches for these five signals so nobody has to remember to check. When two or three of them line up on the same person, someone on your team gets a heads up with a name attached, instead of five dashboards nobody has time to cross-reference. See how Bellwether tracks this.

Closing the loop

Growth will always be easier to see than connection, but new visitors are much harder to gain than connecting with those already within your walls.

If you're only building systems for growth, you're optimizing for the half of the story that's easiest to measure, not the half that's hardest to get back.

Attendance can tell you who walked through the door last Sunday. It can't tell you who's deciding if this is their last month. Growth and connection were never really opposite problems, just unevenly resourced ones. Closing that gap starts small. It starts by treating the quiet signals as data worth watching, not as a hope that someone happens to notice in time. No, go on and grow.

If you'd rather not build that report yourself, see how Bellwether does it.