The Church Software Market Is Broken

The first time I opened a data export from a legacy church management system and tried to understand what I was looking at, I had a very specific thought: how did it get this bad?

Fifteen years of contact records, duplicated because someone didn't know to search before adding. Giving data in a format that predated the current giving platform. Attendance records for ministries that no longer existed. Family relationships that were either missing or wrong. Merge conflicts from when two people at different times imported the same donor list from a paper form.

This is not an unusual situation. It's the situation at almost every church we work with that has been on a legacy platform for more than five years. It's what happens when software is designed for a moment in time and then simply continues to exist — accumulating data and complexity without a coherent way to manage either.

The church software market has real problems. Some of them are structural, some of them are cultural, and some of them are just the natural result of an industry that didn't invest in technology the way other sectors did. This is my honest take on all of it.

The market, briefly

The church management software (CHMS) market has a handful of legacy players that have been around for twenty-plus years — ACS, Shelby, Church Community Builder — and a generation of newer platforms that emerged in the 2010s. Planning Center is the one Threefold specializes in, and it's genuinely one of the best-designed platforms in the space. Pushpay, Rock RMS (open-source), Breeze, ChurchTrac, and a few others round out the field.

The legacy platforms serve a large number of churches, many of which have been on them for so long that the idea of migrating is genuinely terrifying. These platforms are deeply embedded in operational processes, staff workflows, and institutional memory. And they're hard to leave — not because they're great, but because the cost and complexity of migrating away is high enough to justify staying even when the software itself is suboptimal.

function evaluateCHMS(platform) {
  return {
    modernUX: platform.designedAfter(2015),
    mobileFirst: platform.mobileExperience === 'native',
    openAPI: platform.apiAccess === 'full',
    onboardingSupport: platform.migrationSupport.exists,
    dataPortability: platform.dataExport === 'full-fidelity',
    workflowAutomation: platform.automationCapability === 'robust',
    score: Object.values(this).filter(Boolean).length,
    verdict:
      this.score >= 5
        ? 'Modern platform, worth considering'
        : this.score >= 3
          ? 'Mixed — strong in some areas, weak in others'
          : 'Legacy platform — may be functional but not built for the current moment',
  }
}

Why churches stay on bad software

The most important thing to understand about church software purchasing decisions is that the person who feels the pain most acutely is rarely the person who makes the final call.

The administrator or database coordinator who spends forty hours a week in the system knows exactly what's broken. They've built workarounds on top of workarounds. They know which reports they can trust and which ones require manual correction before they're safe to share with leadership. They have been asking for a better system for years.

But the person who decides whether the church buys new software is usually the executive or lead pastor. They don't live in the system. They see reports and make decisions based on them. To them, the software works — they get their numbers, everything seems fine. The operational pain is invisible.

This dynamic is why the church software market moves slowly. The people with buying authority don't feel the problem, and the people who feel the problem don't have the budget authority. By the time it becomes bad enough for leadership to notice, the organization has typically been on a broken platform for two or three years longer than it should have.

What good church software looks like

After working with churches across a range of platforms, here's what I think separates the tools that genuinely help from the ones that just hold data:

It meets people where they are. If using the software requires significant training to do basic tasks, the software has failed. The best platforms are designed so that a new volunteer or part-time admin can get productive quickly without a multi-day onboarding.

It automates the repetitive. Follow-up tasks, communication triggers, attendance tracking, report generation — these should be handled by the system, not by staff remembering to do them manually. If a church is relying on individuals to run the same workflow every Monday morning, that workflow will fail when that person is sick, on vacation, or simply overwhelmed.

It surfaces what matters. A good platform doesn't just store data — it helps you understand it. Which ministries are growing? Which people have been attending but haven't connected to a community? Where are people falling off between first visit and membership? These questions should have answers that are easy to access, not require custom reports that only one person knows how to build.

It gets out of the way. The best technology is the kind you stop noticing because it just works. If the staff is spending more time managing the platform than using it to serve people, something is wrong.

Where the market is going

AI is starting to touch the CHMS space, mostly in predictable ways: chatbot integrations, automated reporting, some early experiments with predictive analytics for giving and attendance. The honest take is that most of these are features bolted onto existing platforms, not fundamental rethinks.

The deeper change AI will drive is in data entry and data quality. A huge percentage of the operational pain we see at Threefold is the result of inconsistent, manual data entry — people added twice, relationships wrong, giving records misattributed. AI has a real role to play in catching these issues in real time, suggesting corrections, and reducing the accumulated debt that makes migrations so painful.

What AI won't change is the human dimension of church management software. The reason these platforms matter is that they help organizations care for people. No amount of automation replaces pastoral judgment about when someone needs a phone call versus an email. No algorithm replaces the volunteer coordinator who knows which volunteer will thrive in which ministry. The software is infrastructure. The ministry is still fundamentally human.

What Threefold is trying to do

We started Threefold because we believed churches deserved better than what most of them were getting. Not better software necessarily — Planning Center is excellent — but better implementation. Better process design. Better use of tools they were already paying for.

Five years in, that belief hasn't changed. The gap between what these platforms can do and what most churches actually use them for is still significant. Every engagement we take on is an attempt to close some of that gap — not just by moving data from one system to another, but by helping churches understand what they now have the capability to do.

The market is broken in some structural ways I've described. But the underlying problem — organizations that care deeply about people, struggling with systems that don't serve that mission — is solvable. One church at a time, if that's what it takes.

That's a long game. We're playing it.