The Question That Started Everything
It started with a simple question. A group of church volunteers sat down to plan their congregation’s future. They needed to answer a basic question that any church administrator would recognize:
“How many people do we actually have in our congregation?”
It sounds simple. It shouldn’t be hard. But it was.
The answer was buried in spreadsheets, scattered across email attachments, written on paper forms stuffed in filing cabinets, and existing only in the memory of people who’d been volunteering for decades. There was no single source of truth. When they tried to count, different people got different numbers. When they needed to follow up, they had no easy way to track who they’d contacted.
The Search
They looked for software to solve the problem. What they found was discouraging.
The options fell into three categories:
Option 1: Prohibitively Expensive
Enterprise church management systems cost thousands of dollars per year. Smaller churches could never afford them.
Option 2: Needlessly Complicated
Generic business software required hiring someone just to maintain it. A church office manager shouldn’t need to be a database administrator.
Option 3: Dangerous to Data Ownership
The “affordable” solutions required congregations to upload their member records to someone else’s cloud. Your data lived on a vendor’s servers, under their terms of service, with no guarantee it would stay accessible or private.
None of these options felt right for a congregation.
The Decision
So the volunteers decided to build their own.
They didn’t start from nothing. They discovered ChurchInfo, an earlier open-source church administration tool that had been built by church volunteers in the 1990s. It had the right DNA — built for churches, by church people — but it was aging. It ran on old technology, had an outdated interface, and wasn’t designed for modern congregations.
Instead of abandoning it, they forked it. They updated it for contemporary ministry needs. They rewrote the interface. They added features that real churches were asking for. They built it on modern, maintainable code. And they kept the original philosophy: software should serve the mission, not the other way around.
That meant:
- Free — No fees, ever. Not because we hate money, but because churches already give so much away that membership fees shouldn’t determine who gets good tools.
- Open — Your data is yours to keep, export, or migrate. You can run ChurchCRM entirely on your own servers. No vendor lock-in. No surprise changes to the terms of service.
- Community-driven — Not built by a company, but by volunteers who understand church ministry because they live it.
From Scratch to a Movement
The first versions were rough. The volunteers started with a basic member directory. They added attendance tracking. Then giving management. Then volunteer coordination. Step by step, they built what churches were actually asking for.
Word spread. A church in one state heard about it. Then another. Then another. Congregations started using it in their own contexts and contributing improvements back to the project.
Then something unexpected happened: people started translating it. Volunteers from other countries saw the project and thought, “My church needs this in Spanish.” Or German. Or Tagalog. Or Swahili. Instead of the software being trapped in English, it began to serve a global Church.
Today, ChurchCRM is available in 49 languages, each translation maintained by volunteer translators who know their communities. A church in Nigeria can use ChurchCRM in Yoruba. A Filipino church can use it in Tagalog. A Chinese congregation can use it in Simplified or Traditional Chinese. The software became a global resource.
How It Works Today
ChurchCRM is maintained by a lean, distributed global community:
- Volunteer developers ranging from professional software engineers to self-taught programmers contribute code
- Church administrators and pastors use the software and report what they need
- Translators bring ChurchCRM to churches in their language
- Testers validate that features work before they reach churches
- Documentation writers help congregations understand and use the system
- Designers improve the interface and user experience
There’s no central headquarters, no CEO, no board of directors (in the traditional sense). Instead, there are people who care about churches having access to great tools, who invest their time because they believe in the mission.
Some contributors are professionals working in the tech industry. Some are pastors or church administrators who wanted to solve a problem and ended up helping churches around the world.
The diversity of perspectives makes ChurchCRM better. It’s built by people who understand church ministry because they live it — because they’re in the pews on Sunday, serving on committees, managing volunteers, tracking giving, and planning events.
Read the founder’s full account: From a Simple Question: The Story of How ChurchCRM Started — the first-hand story of the volunteer meeting where it all began.
Why It Matters
For churches in wealthy denominations with large budgets, expense wasn’t the main concern. But ChurchCRM was built for the 95% of churches worldwide that have to make do with limited resources:
- A church plant with 50 people and no IT budget can get the same tools as a church with 5,000 people and a dedicated tech staff.
- A mission church in a developing country can access professional management software without spending money on licenses.
- A congregation that wants to own its data — to avoid putting sensitive member information on someone else’s cloud — has a real option.
- A church that’s been burned by a vendor changing their terms or raising prices suddenly can switch to ChurchCRM and never face that again.
Over the years, ChurchCRM has served congregations through changes no one could have predicted: churches adapting to an online-only model during lockdowns, rural churches discovering they could run professional software on limited internet, multilingual congregations finding that their language was finally supported.
AI-Assisted Development
In recent years, ChurchCRM has begun using AI-assisted development as part of its workflow. This doesn’t change the project’s mission or philosophy — it accelerates the pace at which volunteers can contribute and respond to church needs. AI tools help with routine coding tasks, documentation, and testing, freeing volunteers to focus on features and improvements that matter most to churches.
The project remains community-driven, with all decisions made by the global volunteer team. AI is a tool that makes it easier for those volunteers to do their best work, not a replacement for human judgment or community values.
Where We Are Now
ChurchCRM has been downloaded more than 25,000 times over the past decade — by small house churches, large multi-campus parishes, rural congregations, urban churches, wealthy denominations, and mission organizations. The software has become an essential tool for churches that value:
- Financial independence — No subscription fees mean more money for ministry
- Data ownership — Complete control over member information
- Flexibility — Open-source code means churches can customize it for their unique needs
- Community — Users helping other users, contributors improving the software for everyone
The project that started as one question — “How many people do we have?” — has become a global resource that helps congregations focus on their mission instead of struggling with administrative tools.
The Bigger Picture
ChurchCRM’s story is ultimately about a principle that matters far beyond one software project:
Free, trustworthy tools should be available to every congregation, regardless of budget.
Not “affordable.” Not “good enough.” Free and trustworthy. The kind of tool a church can rely on without worrying about hidden costs, surprise price increases, or losing access to their own data.
Churches already ask their members to sacrifice time, energy, and money for ministry. The least the world can do is provide them with great software that doesn’t add another financial burden.
That’s ChurchCRM. That’s why it was built. That’s why thousands of people use it.
And that’s why the volunteers keep improving it.
Get Involved
This story isn’t finished. It’s being written right now by people like you. Whether you’re a developer, a translator, a designer, a pastor, or a church administrator, there’s a place for you in this community.