Why your generic CMS can't run a Pentecostal church
Last October, a finance pastor from a 900-member Winners Chapel wrote to us: 'Your giving page let my 78-year-old mother donate without logging in. She's given more in three months than the previous year.' That sentence changed how I understood what churches actually need.
The generic tool problem is a real one
Most church software is designed for traditional evangelical or Catholic structures. They assume a straightforward Sunday service, a giving form that looks like every other giving form, and members who are comfortable with passwords and logins. Nothing wrong with that, except it's not how charismatic churches operate.
Pentecostal congregations like RCCG, Living Faith, DLCF, KICC, and House on the Rock move faster. Service units run in parallel (sometimes more than eight happening at once). Visitors aren't passive; they're in a journey, and whether they return for baptism class depends on whether someone followed up within 48 hours. Giving isn't just an online form; it's rooted in family structures where grandmother wants to sow a seed but doesn't own a smartphone. Gift Aid matters, but claiming it manually burns time that should be spent on ministry.
When we started building Ekklesia, we stopped asking 'What would a church software company do?' and started asking 'What does our resident pastor actually do on a Tuesday morning?'
The visitor funnel was the first real win
Early users told us their biggest leak happened between someone's first visit and the follow-up. A new convert would attend service, leave feeling moved, and then... nothing. No one knew their name. No one knew if they'd come back. By the time the pastor remembered, it was six weeks later.
We built a 6-stage establishment ladder: first-timer, prospect, believer, member, server, worker. Every visitor lands on stage one. The follow-up queue shows pastors and unit heads exactly who needs a call, a visit, or an invite to next week's workers' meeting. Templates are there (so you're not starting from scratch at 11 pm), but the real magic is role scoping. The altar worker can't bump someone to 'member' status; only the finance pastor can. The unit head flags people ready for baptism class, but the resident pastor closes the loop with a certificate.
One church went from baptising 8 people a quarter to 12 a month. Not because they preached better. Because no one fell through the cracks anymore.
Giving that your grandmother can actually use
Public donor pages with no login aren't a nice-to-have. They're essential. Our giving page lets someone text a link, tap it, and give without remembering a password. We added Pay by Bank, monthly standing orders, card, and integration with Xcel for churches already using it.
But the real insight came from Gift Aid. UK charities can reclaim 25% on every qualifying donation, which for a 500-member church might be £3,000 to £8,000 a year. The problem: claiming it involves spreadsheets, HMRC Charities Online logins, and enough manual data entry that most churches either don't claim or claim late. We built a Gift Aid Reclaim Panel that sits inside Ekklesia. Mark a donation as Gift Aid-eligible, answer the statutory declaration once, and the system prepares everything for HMRC submission. No spreadsheet. No memory.
We also built a Fee Savings Calculator because we needed to show pastors the math honestly. You can model three migration scenarios (staying where you are, moving to us, moving elsewhere) and see a 3-year projection. Some churches save £400 a year. Some save £6,000. The calculator shows your real number, not a marketing promise.
Service units and rosters that actually work
Charismatic churches don't have one service. They have praise and worship, intercession, ushering, children's church, youth, security, media, follow-up. Each unit has a head. Each unit has a roster. Each unit needs to swap people week to week without the resident pastor's phone blowing up.
We built eight service units into Ekklesia with duty rosters, check-in tracking, and swap requests that route to the unit head. On Sunday morning, the altar worker checks in using their phone. If three ushers are scheduled but only two check in, the system flags it. The media unit can see who's rostered for next week and swap offline if the current sound engineer is sick.
The pastor dashboard then shows a pipeline view: how many visitors are stuck in prospect stage, how many workers are ready for commissioning, where bottlenecks are. It's not a vanity metric. It's operational health.
The approval chain nobody likes until they need it
Request to Purchase sounds bureaucratic. In a charismatic church with 200 to 3,500 members, it's survival.
Unit head wants to buy new audio cables. They submit. The pastor in charge approves (is it aligned with our direction?). Finance pastor approves (do we have the money?). Resident pastor approves (is the priority right?). No back-and-forth emails. No 'Did you see my message?' frustration. The request lives in one place until it's done or rejected with a reason. Transparency. Accountability. A paper trail if questions come up later.
We've had pastors tell us this single feature stopped duplicated purchasing and £2,000+ in wasted spend per year. Not because the feature is clever. Because it makes what was invisible (decision-making) visible.
Built for you, not retrofitted to you
Every feature in Ekklesia was built because a Pentecostal or charismatic pastor asked for it, or because we watched their Sunday morning and saw where software could save them an hour. We didn't take a generic CMS and slap 'Church Edition' on it. We started with your structure: the 6-stage ladder, the service units, the approval chain, the visitor follow-up queue. Then we built around it.
This means Ekklesia won't work perfectly for a liturgical Catholic church or a traditional Protestant denomination. We're opinionated. That opinion is rooted in how you actually run things.
When you're evaluating software for your branch, ask yourself: Does this tool understand why we do what we do? Or is it asking us to reshape our church to fit its template? The honest answer usually determines whether you spend six months fighting the software or six months saving time and money.
If you're spending Sunday evening manually copying visitor names into a spreadsheet or watching Gift Aid claims slip past because the paperwork feels impossible, we'd like to show you what happens when software is built for your rhythm, not borrowed from someone else's. What's the one thing your current system makes harder than it should be?
Ready to try Ekklesia by MRVL?
One tap to download. No sign-up wall.