Why we built the world's first Church Relationship Manager

Every Sunday, pastors across the country open their church management software and see a number. Attendance: 147. Up from last week. Down from last month.

They check giving. They pull up the event calendar. They glance at the volunteer schedule.

And then they wonder: Why did the Hendersons stop coming?

The software can't tell them. It tracked the Hendersons' attendance, their giving, which events they signed up for. But it never tracked the thing that would have told the pastor something was wrong months earlier.

Their relationships.

The thirty-year blind spot

Church management software has been around since the early '90s. In that time, the industry built solid tools for tracking attendance, managing donations, scheduling events, and organizing volunteer teams.

But every one of these products was built around the same assumption: the church's relationship with its members is what matters most.

That assumption produced Church Management Software - ChMS. Tools that track how members relate to the institution:

• Did they attend?
• Did they give?
• Are they in the directory?
• Did they sign up?

These are all vertical relationships. The institution looking down at individual members. Planning Center, Breeze, Church Community Builder, Pushpay -- every product in the category is, at its core, a database of individuals and their transactions with the church.

What nobody built was a tool that tracks the horizontal relationships - the connections between members themselves.

What the research actually says

In 1975, Flavil Yeakley completed a doctoral dissertation at the University of Illinois that changed how church leaders think about retention. His study, published as Why Churches Grow (1979), compared 50 actively involved church members with 50 who had joined but dropped out.

The gap was brutal:

• Active members averaged 7.3 friendships within the congregation. Ninety percent had 6 or more friends.
• Members who left averaged 1.9 friendships. Ninety-eight percent had fewer than 6.

Win and Charles Arn later popularized these findings through the church growth movement. The "7-Friend Threshold" became one of the most cited numbers in church leadership. Gary McIntosh and Charles Arn covered it again in What Every Pastor Should Know (Baker Books, 2013).

The takeaway is uncomfortable in its simplicity: whether someone stays in a church has less to do with preaching or programming than with whether they made friends.

Members with friendships stayed. Members without them left. The pattern was almost universal.

And for thirty years, no church software tracked this.

I think about that a lot. We built tools to count heads and dollars, and we never built a tool to see if people actually knew each other.

The biblical foundation

Peter said it before any researcher did:

"Be shepherds of God's flock that is under your care, watching over them -- not because you must, but because you are willing, as God wants you to be; not pursuing dishonest gain, but eager to serve; not lording it over those entrusted to you, but being examples to the flock."
-- 1 Peter 5:2-3, NIV

The Greek word for "watching over" is episkopountes. It doesn't mean surveillance. It's the kind of attentive care that notices when someone is drifting before they've drifted too far.

And the whole New Testament is built on horizontal relationships. Love one another. Bear one another's burdens. Encourage one another. Confess to one another. These are about the connections between people, not the connection between an institution and its members.

Acts 2:42-47 describes the early church growing not through programs but through koinonia -- shared life, deep fellowship, mutual belonging. People were connected to each other, not just showing up to the same building on Sunday.

Connections keep people. Connected people become disciples. Disciples make new disciples. That's the Great Commission in its simplest form (Matthew 28:18-20).

So why did we spend thirty years building church software that optimizes for attendance and giving while ignoring the relationships that Scripture says actually matter?

What "Church Relationship Management" actually means

We call what FlockConnect does ChRM -- Church Relationship Management -- because it's a different thing from ChMS or Church CRM.

Here's the distinction, as plainly as I can put it:

ChMS (Church Management Software) tracks members' relationships with the institution. Attendance, giving, registrations.

Church CRM is contact management for churches. It tracks when the church last reached out to a member. Still institution-to-member.

ChRM (Church Relationship Management) tracks the relationships between members. Who knows whom. How connected someone is. Who's isolated. Who would naturally click if they met.

FlockConnect is built around connections between members -- not just member records. The connection scoring, the relationship graph, the isolation detection -- these aren't features we added on top of a ChMS. They're the foundation. The whole data model starts with the question: how are these people connected to each other?

That's what makes FlockConnect the first platform purpose-built for horizontal relationships between church members.

"But doesn't [X] already do this?"

We looked. Hard. Here's what we found:

FellowshipOne has a Relationship Manager where admins can manually tag relationship types (counseling, mentoring) and link people. Manual only. No scoring. No isolation detection.

Realm has Relationship Tags. Same idea -- you can manually record that two people are connected. Good for emergency contacts, not for understanding the relational health of 200 people.

Rock RMS has Known Relationships and auto-generated "Implied Relationships" from shared group attendance. Its GitHub page calls it a "Relationship Management System." But in practice, those relationships exist mostly for child check-in authorization (who's allowed to pick up whose kid). Not for detecting isolation or measuring connection health.

TouchPoint has an Engagement Score. It's a number based on attendance, giving, and volunteering. It measures activity, not relationships. You can be a 10/10 on engagement and still not know a single person at church.

None of them answer the question: Does this person have friends here?

We built FlockConnect to answer that.

Every shepherd needs a good sheepdog

We didn't want to add complexity to a pastor's week. The whole point was to make the invisible visible, not to create more work. So we built Collie.

Think of Collie like a sheepdog. You're the shepherd. Collie doesn't replace you. Collie extends your reach.

A shepherd watching 20 sheep can see who's wandering. A shepherd watching 200? That's where the sheepdog earns its keep. It watches the edges of the flock. It notices who's drifting before the shepherd can. And it responds to the shepherd's voice -- it acts on your direction, not its own.

Collie does the same thing for your congregation. It watches the relational edges. It notices when someone's connections are thinning out. It suggests specific introductions -- not vague recommendations, but "Sarah and Maria are both young moms who love hiking and live three miles apart." And you interact with Collie through plain conversation. You ask. Collie answers.

You're the shepherd. Collie just makes sure you can see the whole flock.

What this looks like on a Monday morning

A pastor opens FlockConnect. Collie has three things waiting:

1. Marcus hasn't been contacted in 3 weeks and has only 2 connections in the church. Below the threshold.
2. The Petersons stopped giving last month. First miss in two years.
3. Amy, a new member, comes every Sunday but hasn't connected with anyone outside the service. Collie suggests three people she'd naturally click with based on shared interests and life stage.

The pastor texts Marcus. Schedules coffee with the Petersons. Introduces Amy to a small group member after service.

None of this was possible with traditional ChMS. The attendance numbers looked fine. Giving showed a dip but nothing alarming on its own. And Amy? She was there every week. She just didn't know anyone.

That's the difference between tracking transactions and tracking connections.

The gap is real

We're not building FlockConnect to compete with Planning Center or Breeze. We're building it to fill a gap they were never designed to fill.

Your ChMS handles operations. FlockConnect handles relationships. They work together -- we sync with Planning Center, Breeze, Subsplash, and others, pulling in attendance patterns, giving frequency, and group membership to build the relational picture.

What FlockConnect adds is the layer your ChMS was never designed to provide: Who knows whom. Who's connected. Who's isolated. And what to do about it.

The 7-Friend Threshold isn't just a number from a study. Every member who slips away without being noticed represents a failure of awareness, not a failure of care. Pastors care deeply. They just can't see everything.

FlockConnect helps them see.

FlockConnect is Church Relationship Management software for pastors at churches of 50-300 members. It works alongside Planning Center, Breeze, and other ChMS platforms. Start a free 14-day trial at flockconnect.com -- no credit card required.

Research cited in this article:

• Yeakley, Flavil. Why Churches Grow (1979). Based on Ph.D. dissertation, University of Illinois, 1975.
• Arn, Win & Charles. The Church Growth Ratio Book (1990).
• McIntosh, Gary & Arn, Charles. What Every Pastor Should Know: 101 Indispensable Rules of Thumb for Leading Your Church (Baker Books, 2013).