Church technology

Why FlockConnect is a ChRM

By FlockConnect · Directed and edited by Michael Tribett · March 11, 2026 · 13 min read

For thirty years, church software has tracked how members relate to the institution. The care that keeps people, a team noticing who has gone quiet and following through, never had a place of its own. That gap is the reason for a new category.

Key takeaways

A Church Relationship Manager (ChRM) is where a church's whole team keeps up with care for each person: noticing early, following through, and sharing the load, rather than recording each member's 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 care around each person scattered across inboxes and memory.

The retention case is old. In a small study Win and Charles Arn published in 1984, most new Christians still active after six months had made seven or more friends in their church; most who dropped out had made two or fewer, a finding echoed across decades of church-growth literature.

FlockConnect is a ChRM built for pastoral care. It complements the operational system a church already runs; it does not replace it.

The product stays narrow on purpose: a presence reading for each person, follow-ups and a shared care log, an official two-way Planning Center integration, CSV import, and an advisory assistant that can show how a person you are looking at is doing and draft a next step. Nothing it drafts reaches a member or a connected system, and no care record is created, until a person approves it.

Quick answer: What is a Church Relationship Manager (ChRM)?

A Church Relationship Manager (ChRM) is where a church's whole team keeps up with care for each person: noticing early, following through, and sharing the load. Traditional church management systems track institution-to-member data: attendance, giving, directories. FlockConnect complements that operational layer with a presence reading for each person, follow-ups with an owner and a due date, a shared care log, and an advisory assistant. Nothing it drafts reaches a member or a connected system, and no care record is created, until a person approves it.

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 place for the care around each person. Who has gone quiet. Who would be missed. Whether anyone has called. Underneath that care sit the friendships between members, which no software can count, and which church-growth research ties to who stays.

What the research ties to who stays

The link between relationships and who stays is not a marketing line. It comes from the study of how people join and stay in churches.

Win Arn and his son Charles led the Institute for American Church Growth. In a small study they published in 1984, most new Christians still active after six months had made seven or more friends in their church; most who dropped out had made two or fewer. The study compared the friendships of people who stayed with the friendships of people who left, and the Arns carried that comparison to working pastors in their book The Master's Plan for Making Disciples.

The exact number is the least important part; read it as a memory hook, not a magic number. The shape of the finding, that friendship went together with staying, is what has been echoed across decades of church-growth literature.

One honest caution belongs here. The research ties friendship in a new Christian's first months to who stays. It does not say preaching or worship are optional, and it never tested teaching quality as a competing variable. Pastors know a full sanctuary with no friendships is still fragile, and that a church with deep friendships and shallow teaching has its own problem. Healthy churches attend to both. This post's point is narrower: the care around each person is the part most churches cannot keep track of. 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 software where a church's whole team keeps up with care for each person, rather than a 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 care layer. Its native question is pastoral: who needs care, who on the team is following up, and who the church hasn't seen lately. It keeps the care around each person in one place (notes, calls and visits, follow-ups, and who on the team is responsible) beside a presence reading drawn from the attendance a church already records.

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 one shared place to keep up with care. That is the whole proposition.

How FlockConnect builds the category

FlockConnect is a tool built for 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 care layer well and leave the rest to the systems that already do it.

In practice that means a small, honest feature set.

A presence reading for each person. A line like "usually weekly, not seen for 3 weeks," read against that person's own rhythm, from the attendance a church already records. On the Collie plans, connection-health rings add care contact, groups and teams, and giving cadence (never amounts). 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.
Follow-ups and a shared care log. A promised call or visit becomes a follow-up with an owner and a due date, and each call, visit or note is kept where the people caring for that person can find it.
Collie, an advisory assistant. Collie can show how a person you are looking at is doing and draft a note or a next step. Nothing it drafts reaches a member or a connected system, and no care record is created, until a person approves it. 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 care 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 care across a team rather than holding every name 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 help a real person notice who needs care 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. A few people need attention: the presence readings show who the church hasn't seen lately, and the follow-ups show which promised calls are due. On the Collie plans, the pastor can ask Collie to draft a suggested next step for each one.

A longtime member who usually comes weekly has not been seen for three weeks; the church-wide attendance report did not flag it, because one person's dip hides inside a steady total. A new family at four weeks has no care partner yet. A member who used to be at every group meeting has missed the last month of them.

None of this was visible on an attendance report, because attendance counts the room and not each person's own rhythm. 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 keeping up with care, 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 a 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 care layer worth building without the operational records a good ChMS keeps.

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 who in the room is slipping away, and whether anyone on the team has reached out. Friendship is what church-growth research ties to who stays; no software can make a friend, but a team that notices early can make sure no one drifts away alone. That second question 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 editor

Michael Tribett is the founder of FlockConnect, a Church Relationship Manager (ChRM) built for pastoral care. 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 participated in the Missional Labs Faith & AI Accelerator during Winter and Spring of 2026 and is an Official and Authorized Planning Center Integration.

Frequently asked questions

Does a ChRM replace church management software?

FlockConnect is a ChRM built for pastoral care. It complements the operational system a church already runs; it does not replace it.

What does the research say about whether a new member stays in a church?

In a small study Win and Charles Arn published in 1984, most new Christians still active after six months had made seven or more friends in their church; most who dropped out had made two or fewer. A Church Relationship Manager (ChRM) helps a church's team keep up with care for each person, so someone notices early when a new member is drifting. Traditional church management systems track institution-to-member data: attendance, giving, directories. FlockConnect complements that operational layer with a presence reading for each person, follow-ups with an owner and a due date, a shared care log, and an advisory assistant. Nothing it drafts reaches a member or a connected system, and no care record is created, until a person approves it.

What is a Church Relationship Manager (ChRM)?

A ChRM is software where a church's whole team keeps up with care for each person: noticing early, following through, and sharing the load, rather than the vertical record of attendance and giving. FlockConnect coined the term and is built for that 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 care layer: who needs care, who on the team is following up, 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 care 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 one shared place to keep up with care. Churches on other systems import people by CSV.

What is the evidence linking relationships to who stays?

Does the research say preaching does not matter?

No. The research compared the friendships of people who stayed with those of people who left; 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 show how a person you are looking at is doing and draft a note or a next step. Nothing it drafts reaches a member or a connected system, and no care record is created, until a person approves it.

Why call it a 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 care a team gives each person, and FlockConnect is 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.

How this was written: drafted with AI from Michael Tribett's ideas and research, then fact-checked and edited by him. How FlockConnect uses AI