The resident pastor who emptied the spreadsheet drawer on day three
It was a Tuesday morning when Pastor Tunde messaged us. He'd been running Ekklesia for exactly three days across his 2,100-member branch, and he'd just done something he hadn't done in seven years: he'd taken every single spreadsheet out of the filing drawer and put it in the recycling bin. Not filed away. Not archived. Deleted.
Seven years of giving records, suddenly visible
Before that Tuesday, giving at Tunde's branch moved through three separate systems: a legacy spreadsheet tracked cash and online transfers; a second one recorded which families were up to date; a third sat with the finance pastor and never quite matched the first two. When a visitor asked, "How much has my family given this year?" there was no quick answer. The actual flow of generosity through the church was invisible.
What changed wasn't magic. Ekklesia brought every transaction into one space. Visitors could see their own giving history through the native iOS app. The finance team could see patterns instead of loose numbers. Gift Aid reclaim stopped being a manual nightmare; the HMRC Charities Online integration pulled exactly what was needed. Three days in, Tunde realised those spreadsheets weren't protecting anything. They were just making noise.
The public donor page nobody expected to use
Most church finance pastors worry about one thing: people giving anonymously because the old system felt clunky. Ekklesia's donor page requires zero login. Your grandmother can open a link, give once, or set up a monthly gift in three taps. No account creation. No friction.
Tunde's branch saw something unexpected happen. Not only did giving increase in the first month, but the giving actually stabilised. People who used to give sporadically started setting monthly amounts through the iOS app or the web page. The finance team stopped chasing down "missing" givers because they could see the exact pattern and follow up with kindness instead of spreadsheet anxiety. That stability meant the building fund they'd been discussing for two years suddenly had real momentum.
When a Request to Purchase becomes a conversation, not a bottleneck
The old Request to Purchase process was email chains. Unit heads emailed pastors-in-charge. Finance pastors printed forms. Everything sat on someone's desk for weeks. Tunde's branch had forty-two open purchase requests from the previous quarter. Forty-two.
Ekklesia's four-stage approval chain routes requests through the system in sequence: unit head submits, pastor-in-charge reviews, finance pastor flags concerns, and resident pastor signs off. It's not faster because the steps are fewer; it's faster because everyone knows exactly where things are and what decision is theirs to make. Within two weeks of implementation, the backlog was gone. More importantly, people stopped treating purchase requests as something to hide because the process felt collaborative instead of bureaucratic.
The visitor who became a worker
Ekklesia tracks what the church calls "establishment" across six stages. A first-time visitor moves through that journey only as the relationships around them move them. Tunde's team uses the follow-up queue to ensure no one gets lost in the system. When someone completes a stage (moves from visitor to member, member to team, team to worker), Ekklesia generates a certificate. Not as a trophy, but as a moment of acknowledgement.
Three weeks after launch, Tunde noticed something on his dashboard. A man named Chisom, who'd first visited in March, had just been routed as "ready for worker tier." The pastoral follow-up queue had flagged him; the template had gone out; the conversations had happened. Tunde's team hadn't missed him because they weren't relying on memory. The system wasn't replacing pastoral care; it was making pastoral care systematic. That matters when you're managing 2,100 people. You can't remember everyone. But the system can help you remember to care.
The drawer stays empty because the work stays visible
What made Tunde bin those spreadsheets wasn't that Ekklesia is new or shiny. It's that the old system was hiding things from him. A spreadsheet in a drawer can't alert the team when giving dips. It can't route a visitor to follow-up. It can't show a pastor which members are stuck or which service units are running short on rosters. It's just a record. A static thing.
Ekklesia made the church's actual life visible. The flow of giving, the journey of people, the load on service units, the pipeline of growth. Once you've seen that, you can't go back to a filing drawer. You don't want to. Because now when someone asks, "How is the church actually doing?" you don't have to guess. You know.
If your branch is still managing giving across multiple spreadsheets and building relationships on memory alone, what would it look like to know exactly what's happening in your church?
Ready to try Ekklesia by MRVL?
One tap to download. No sign-up wall.