The four conversations that happen before a church buys anything

The problem money creates when no one's watching

Churches move fast. Pastors plant vision. Volunteers see a need and act. Finance teams scramble to keep up. But unlike a corporate office with an expense policy laminated on the wall, most churches we've talked to have approval processes that live only in someone's head. Or worse, nowhere at all.

That Lagos pastor's six-week chase wasn't an outlier. It's the norm. A unit head wants new chairs for the youth department. They ask the pastor-in-charge verbally. The pastor-in-charge mentions it to the resident pastor over coffee. The finance pastor hears about it in passing. Three different people think three different things are happening, and the chairs never arrive.

Money in that state breeds two kinds of trouble. First, friction. People feel unheard, slow, undervalued. Second, opacity. No one can account for what was approved, when, or why. That's not just messy. It's a governance risk. It matters to church councils, to donors, and to the people who sign off on accounts.

What we learned by talking to finance pastors

When we built Ekklesia, we spent months with finance teams from Winners Chapel branches, RCCG stations, DLCF parishes, and others. They told us the same story in different accents. The churches with the clearest money flow had one thing in common: they followed a chain. Not a bureaucratic gauntlet. A conversation.

The chain looked like this. A unit head says 'we need X'. The pastor-in-charge sees the request first and asks 'is this aligned with our vision this quarter?' The finance pastor asks 'can we afford it, and what's the best way to pay for it?' The resident pastor asks 'does this serve the whole church or just one unit?' Four questions. Four different perspectives. One answer.

No single person was being ignored. Every role had a reason to exist in that chain. The unit head felt heard because their request didn't disappear into silence. The pastor-in-charge kept ministry aligned. The finance pastor stopped churches from spending money they didn't have. The resident pastor saw the whole picture.

Why we hardcoded four stages into the system

We could have built a generic approval tool that any church could configure however they wanted. Flexible. Configurable. Blank slate. But that wasn't what the data told us. Churches without a pre-set approval structure didn't get one. They stayed chaotic. Churches that adopted a four-stage model reported lower spend delays, clearer budgets, and less tension between departments.

So in Ekklesia, the Request to Purchase approval chain moves through four gates: unit head, pastor-in-charge, finance pastor, resident pastor. Each stage has a clear role. Each person gets a notification. The request can't move forward until it's been seen and approved. The whole thing lives in the system, not in email threads or voice memos.

A unit head submits a request. It goes into a queue. The pastor-in-charge reviews it within 48 hours (or it flags). They approve or ask for more detail. Once that's done, the finance pastor sees it with all the context and approves or raises a budget concern. Finally, the resident pastor sees the full picture before it's authorised.

This isn't theoretical. A 900-member branch in Ibadan told us their approval cycle dropped from 21 days to 4 days once this was live. They weren't being less careful. They were being clearer. Everyone knew where the request was. No chasing. No ambiguity.

What changes when money moves in daylight

The secondary effect surprised us. Once approvals were visible, giving followed. Donors want to know their money is handled with care. They want to see decisions made thoughtfully, by named people, for reasons they can understand. When a church can say 'our finance pastor reviewed this' or 'the resident pastor approved it', donors trust differently.

It also changed conversations inside the church. The finance pastor stopped being 'the person who blocks things'. They became 'the person who makes sure we have what we need'. The pastor-in-charge could see which ministry units were asking for most, and that informed bigger conversations about resourcing. The resident pastor had real data about what the church was building, not just quarterly reports.

One more thing happened. Training became easier. New finance volunteers could see how decisions were made in the system. They could read the approvals and understand the reasoning. They didn't have to learn an invisible process from a retiring treasurer who carried everything in their head.

The point of structure is freedom

I know that sounds backwards. A four-stage approval chain sounds like bureaucracy. But churches with clear processes approve faster, spend more confidently, and actually say yes more often. The unit head who waits four days instead of wandering the building asking questions for three weeks is moving faster, not slower.

The other reason we built it this way: it works for churches our size. We built Ekklesia for 200 to 3,500-member branches. That's a scale where you have a finance pastor, a pastor-in-charge, and a resident pastor as distinct roles. You have enough units that someone needs to think about interdependency. You're big enough that 'let's just ask everyone' doesn't work, but small enough that everyone still knows each other.

It's opinionated by design. We're not trying to be a generic church software that fits anyone. We're trying to be the operating system that actually works if you're leading a Pentecostal or charismatic congregation and you want to move money with clarity and speed.