Why we built Ekklesia instead of adopting Church Center

The template problem

Church Center is genuinely well-built software. It does what it promises: flexible, approachable, works for dozens of church contexts. That flexibility is also its ceiling.

Most church operating systems start from a blank canvas. You decide what a member journey looks like. You configure your giving flow. You build your roster structure from first principles. This sounds empowering until you're six months in and realising your 500-member branch in Accra spends 30 minutes every Sunday manually routing visitor data because the system wasn't designed for rapid check-in scale.

Pentecostal and charismatic churches in Nigeria, Kenya, and the UK operate with distinct patterns. Winners Chapel runs 8 service units per branch. RCCG has a hierarchical pastoral approval chain that generic tools treat as a quirk rather than a feature. DLCF and House on the Rock track member maturity through an established establishment ladder. These aren't edge cases. They're the operating logic.

When Church Center launched, it optimised for flexibility. Ekklesia optimised for fit. We built a 6-stage visitor to worker pipeline because that's what RCCG, Living Faith, KICC and DLCF actually use. We built the Request to Purchase with four approval gates because that's how finance pastors need oversight. We built service unit rosters because without them, your 8 units can't coordinate swaps and substitutions.

Giving, Gift Aid, and the financial leak nobody mentions

Here's what nobody tells you about generic giving tools: they leak money invisibly.

A grandmother in Birmingham wants to give £50 to her church. Generic systems ask her to sign up, create a password, remember it next month. She gives once and forgets. Church Center handles this well enough, but it's still friction.

Ekklesia removes the login entirely. Public donor page. She gives once. Next month, you email her a link. She gives again. No account. No friction.

The bigger leak is Gift Aid. A charismatic church with 1,500 members runs roughly £4,000 to £9,000 per month in unclaimed Gift Aid if they're not systematic about it. We integrated HMRC Charities Online submission directly into the platform. Your finance pastor doesn't batch entries in a spreadsheet. The system reclaims automatically, every quarter. One customer recovered £18,000 in the first year because we made it frictionless.

Then there's the native iOS app. Pay by Bank, Monthly, Card, Pay using Xcel. Most church giving tools offer web forms. We built native because members in Lagos aren't using desktop browsers on a Sunday morning. They're on phones. The app works offline. It syncs when connectivity returns. Our Fee Savings Calculator shows you exactly how much you recover in the first three years by switching.

Church Center offers giving. Ekklesia treats it as a revenue engine that should pay for itself and fund growth.

The visitor follow-up queue that actually works

Two weeks after launch, a pastor in Nairobi sent us a voice note. Her visitor follow-up sheet was in Excel. She had 40 names. Three of them had been waiting three weeks for a pastoral call because nobody owned the queue.

That's the problem Church Center doesn't solve. It gives you contact management. It doesn't solve the routing problem.

Ekklesia routes visitors through a follow-up queue. Check-in triggers a notification to the assigned member care unit. Templates guide the conversation. But here's the bit that matters: the pastor's dashboard shows which visitors are stuck. How many are past the 3-day touch point. Which ones should have graduated to the next stage but haven't. It's visibility, not nagging.

By the time someone moves from first-timer to baby Christian to committed member to worker, Ekklesia has issued certificates at each stage. The visitor feels progression. The pastor sees momentum. The system becomes a coaching tool, not a form.

The approval chain that respects hierarchy

A finance pastor in Ibadan explained why spreadsheets and WhatsApp messages had become their budget process. No generic tool understood the flow they needed.

Unit head requests something. It goes to the pastor in charge. Then the finance pastor. Then the resident pastor. Four gates. At each step, someone can say yes, no, or ask for clarification. The request sits in the system until it's resolved.

Church Center has workflow features. They're general purpose. Ekklesia built the Request to Purchase chain because that's how these churches actually govern spending. It's not flexibility. It's respect for how they operate.

That matters more than it sounds. When your finance pastor doesn't have to chase approvals via voice note, they spend 6 hours a month doing actual work instead of administration. Scale that across a 3,500-member branch with 8 service units, and you're recovering serious capacity.

The conversation we keep having

Someone always asks: why not just use Church Center and configure it?

Because configuration is work. It's also fragile. A new admin comes in and doesn't understand why the system is structured the way it is. They reconfigure. Six months later, the pastor is confused about whether a visitor is at stage two or three because the definitions drifted.

Ekklesia's 6-stage ladder is doctrine, not decoration. Same with the approval chain. Same with the service units. They exist because Pentecostal and charismatic churches think about growth, membership, and governance this way. We didn't invent it. We formalised it.

Church Center works well for churches that haven't yet decided how they operate. Ekklesia works for churches that know exactly how they operate and want software that fits, not software to fit into.