Why FlockConnect is the world's first ChRM

For thirty years, church software has tracked how members relate to the institution. The relationships that actually keep people, the ones between members, were never on the screen. That gap is the reason for a new category.

Key takeaways

• A Church Relationship Manager (ChRM) is a tool built around the horizontal relationships between members, the connections that predict who stays, rather than the vertical record of attendance and giving.
• For three decades, the church management system (ChMS) category tracked the institution-to-member relationship: who attended, who gave, who is in the directory, who signed up. That work is genuine and necessary, and it leaves the relational layer unseen.
• The retention case is old and well-attested. Flavil Yeakley's assimilation research and the popularizing work of Win and Charles Arn point to relational integration as the clearer signal for who stays, a finding echoed across decades of church-growth literature.
• FlockConnect names and builds the first tool in the ChRM category. It complements the operational system a church already runs; it does not replace it.
• The product stays narrow on purpose: a per-person connection view, an advisory assistant that drafts but never acts on its own, an official two-way Planning Center integration, and CSV import. A person reviews and approves every action.

The thirty-year blind spot

Church management software has been around since the early 1990s. In that time the category built dependable tools for the work a church has to do: take attendance, record giving, run a calendar, schedule volunteers, keep a directory current. None of that is wasted. A church that loses track of its operations is a church in trouble.

But the whole category was built on one quiet assumption. The relationship that matters most is the one between the institution and each member. So the questions the software learned to answer all run in a single direction. Did this person attend? Did they give? Are they in the directory? Did they sign up for the retreat?

Those are vertical relationships. The institution looking down at an individual and recording what that individual did. Useful, countable, and incomplete.

What the category never set out to build was a tool for the horizontal relationships, the connections between members themselves. Who knows whom. Who has friends in the room and who walks in and out alone. Who would be missed. That layer is harder to count, which is exactly why nobody built around it, and it is also the layer that decides who is still here in two years.

Why the horizontal layer is the one that holds people

The case that relationships predict retention is not a marketing line. It is one of the more durable findings in the study of how people join and stay in churches.

Flavil Yeakley, a communication researcher who studied church growth in the 1970s, tracked new members over time and asked a pointed question: who in this congregation do you actually know, and when did you come to know them? Then he watched who was still active a year or two later. The strongest predictor of retention in his data was relational integration during the early months, not how often a person attended at first. People who had been folded into the relational life of a congregation stayed. People who were processed through events but never joined anyone left, often without a complaint and without a goodbye. Yeakley wrote it up for pastors in Why Churches Grow.

Win Arn and his son Charles carried that work into the pastorate. Through their church-growth training in the 1980s and 1990s, they took findings like Yeakley's out of the journals and put them in front of working pastors, and the shorthand that stuck was that a new member needs to form several real friendships, often cited as about seven, inside the first six months. New people who formed those friendships tended to stay; those who formed almost none tended to leave inside the first year or two. The exact number is the least durable part. The shape of the finding is what has been echoed across decades of church-growth literature.

One honest caution belongs here. The research points to relational integration as the clearer signal for who stays. It does not say preaching or worship are optional, and it never tested teaching quality as a competing variable. A full sanctuary with no friendships is still fragile, and a church with deep friendships and shallow teaching has its own problem. Healthy churches attend to both. The point is narrower than it sometimes gets quoted: the relational layer is the part most churches cannot see, and it is the part that most often decides who drifts. For the working definition of the relationship itself, the companion piece what is a church connection is the place to start, and the friendship threshold research goes deeper into where the finding comes from.

What "Church Relationship Manager" means

A Church Relationship Manager is a tool built around the relationships between members rather than the record of each member's transactions with the institution. The category name is FlockConnect's own. The thing it points at is older than the name: the church has always described itself as a body whose parts are joined to one another, not an audience that happens to face the same direction for an hour.

The distinction is easiest to see side by side.

What a ChMS tracks

A church management system keeps records and runs operations. Attendance, giving, registrations, the directory, the volunteer schedule. Its native question is institution-to-member: what did this person do with the church. A respected example is Planning Center, which many churches run well as their operational backbone.

What a ChRM tracks

A Church Relationship Manager works on the relational layer. Its native question is member-to-member: who is connected, who looks isolated, and who has quietly slipped from the first group toward the second. It reads the signals a church already produces (attendance patterns, group rosters, care history) into a per-person view of how rooted someone actually is.

The two are not rivals. A ChRM rides on top of the operational system a church already runs and adds the layer that system was never designed to provide. The church keeps its ChMS for operations and gains a way to see relationships. That is the whole proposition.

How FlockConnect builds the category

FlockConnect is the first tool in the ChRM category, and it stays deliberately narrow. The temptation with a new category is to bolt on everything. The discipline is to do the relational layer well and leave the rest to the systems that already do it.

In practice that means a small, honest feature set.

• A per-person connection view. FlockConnect reads the signals a church already produces into a clear picture of who is connected, who looks isolated, and who is drifting from one toward the other. It is pastor-facing, so members do not have logins. The point is to put the right person in front of a pastor at the right moment.
• Collie, an advisory assistant. Collie can surface who looks isolated and draft a note or a 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 pastor decides; the tool prepares.
• An official, two-way Planning Center integration. This is the one native connection. A church running Planning Center can keep it and add the relational layer on top without leaving the system it already trusts.
• CSV import for everyone else. A church on another system brings its people in by file. FlockConnect does not pretend to natively plug into systems it does not, and it does not ask a church to abandon the operational tool it already runs.
• Care-partner and team distribution. The work of noticing absence at scale is shared. FlockConnect lets a pastor distribute relational care across a team rather than holding the whole map in one person's head.

The deeper reason for the discipline is theological as much as practical. Tim Keller argues in Center Church that a gospel-shaped community forms people through relationships of mutual care, not through programs alone. A program can gather a crowd. Only connection keeps it. A tool that wants to serve that formation should make the relationships visible to a real person and then get out of the way, not try to automate the care that only a human can give.

What this looks like on a Monday

A pastor opens FlockConnect at the start of the week. The per-person view has surfaced a few people worth attention, and Collie has drafted, not sent, a suggested next step for each.

A longtime member has gone quiet. The attendance report did not flag it because the dip is recent, but the connection view shows the relationships around that person thinning out. A new family at four weeks shows up faithfully and has not yet connected with anyone outside the service. A member who was central to a group a year ago has slipped to the edge of it.

None of this was visible on an attendance report, because attendance counts the room and not who in the room is actually known. The pastor reads the suggestions, edits the ones that need editing, and reaches out as themselves. The tool made the absence visible. The pastor did the pastoring.

That is the difference between tracking transactions and tracking relationships, and it is the whole reason for a separate category.

Where the category goes from here

Naming a category is the easy part. Earning it is slower. The claim that FlockConnect is the first ChRM is a claim about what the tool is built around, not a verdict on any other product. The ChMS category does its job, and FlockConnect needs it to: there is no relational layer to read without the operational signals a good ChMS produces.

The bet underneath the category is simple. For thirty years the question church software answered best was how many came and how much they gave. The question it never answered was whether the people in the room actually know one another. That second question is the one the research keeps pointing to, and it is the one a Church Relationship Manager exists to put in front of a pastor. The aim is not a prettier dashboard. The aim is that fewer people leave 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

What is a Church Relationship Manager (ChRM)? A ChRM is software built around the relationships between members, the horizontal connections that predict who stays, rather than the vertical record of attendance and giving. FlockConnect coined the term and built the first tool in the category.

How is a ChRM different from a ChMS? A church management system keeps records and runs operations: attendance, giving, registrations, the directory. A Church Relationship Manager works on the relational layer: who is connected, who is isolated, and what the next caring step is. They are complementary, and a ChRM is designed to run on top of the operational system a church already uses.

Does FlockConnect replace our church management system? No. FlockConnect adds the relational layer on top of the operational system a church already runs. A church running Planning Center keeps it, connects through the official two-way integration, and gains a way to see relationships. Churches on other systems import people by CSV.

What is the evidence that relationships predict retention? Flavil Yeakley's assimilation research in the 1970s and the later popularizing work of Win and Charles Arn point to relational integration during a new member's first months as the clearer signal for who stays. The finding has been echoed across decades of church-growth literature.

Does the research say preaching does not matter? No. The research points to relational integration as the clearer predictor of retention; it did not test teaching quality as a competing variable, and it never claims preaching is optional. A full sanctuary with no friendships is still fragile. Healthy churches attend to both.

Does Collie message or update records on its own? No. Collie is advisory. It can surface who looks isolated and draft a note or a next step, but it never sends messages, writes to records, or changes anyone's care on its own. A person reviews and approves every action.

Why call it the world's first ChRM instead of just better software? Because the difference is a category, not a feature. Existing software is built around the institution-to-member relationship and does that well. A ChRM is built around the member-to-member relationships underneath, and FlockConnect is the first tool designed from the ground up for that layer.

How much does FlockConnect cost? FlockConnect is priced by church size, not by staff or volunteer seats, with a free trial, so the people who serve your church are never the line item.