Why we said no to social style timelines on the church feed

The church isn't a social network

I'll be honest. When we started designing Ekklesia, the temptation was there. Social feeds are what users know. Infinite scroll, likes, comments, the whole apparatus. It feels modern. It feels connected. But then we spent time in actual churches - Winners Chapel branches in Ikoyi and Lekki, RCCG parishes in the South, DLCF in Abuja. We watched how pastors and administrators actually move through their week.

A resident pastor's job isn't to engage with a feed. It's to know where people are in their faith journey. It's to catch a visitor who came three weeks ago and never came back. It's to notice that someone who was serving as an usher has gone quiet. It's to approve a purchase request from the children's ministry before Wednesday. A social timeline would bury all of that under photos of last Sunday's baptism and celebration posts.

What we built instead: clarity over noise

Ekklesia's pastor dashboard gives you the signal without the noise. You see your visitor follow-up queue. You see your member journey pipeline. You see which service units need roster updates before the weekend. Everything there has a job to do. Everything moves a decision forward.

The visitor follow-up queue is a good example. When someone visits for the first time, they enter a simple workflow. The pastoral team gets routed a template. They follow up. They log the outcome. The system shows you who's stuck, who's ready for next steps, who should be invited to membership class. That's not social engagement. That's pastoral care with structure.

We also built a 6-stage establishment ladder. First-timer to new convert to baptism class to baptised member to service unit to worker. At each stage, the church can issue a certificate and know where someone stands. A pastor can pull up the dashboard and see instantly where the health gaps are. How many visitors are waiting for follow-up? How many new converts haven't made it to baptism class? These are real questions that change how a pastor spends their time.

The giving feed tells you everything

We did build one feed. It's the giving feed. But it works the opposite way to social media. It's not about broadcast. It's about transparency and gratitude.

Ekklesia runs giving end-to-end. A grandmother in London can give through a public donor page without logging in. She receives a thank you. Your finance pastor can see the gift come through in real time. At the end of the tax year, Ekklesia reclaims Gift Aid with HMRC through Charities Online integration. No missed claims. No paperwork delays. The system handles it.

The giving feed is a record. Not a performance. It's the place where generosity gets documented and stewarded. Not gamified. Not turned into a competition. Just honest numbers that tell you how your members are walking out their faith through giving.

Request to Purchase: when the feed becomes workflow

Here's where the design philosophy really shows itself. When the children's ministry needs supplies, they submit a Request to Purchase. It moves through four stages: unit head, pastor in charge, finance pastor, resident pastor. Each stage is a decision point. Comments can be added. Approvals flow. The system tracks where it sits.

That's not a social feed. That's a conversation that has a beginning and an end. It has stakes. It has clarity. A pastor in charge knows exactly what decision is waiting for them, and why it matters.

A social timeline would hide this under a thousand other things. People posting about prayer meetings. Photos from last week's service. Birthday announcements. All of it valuable perhaps. But none of it urgent in the way that a held purchase request is urgent.

The discipline of saying no

Building Ekklesia for Pentecostal and charismatic churches has meant being opinionated. This is a system for Winners Chapel and RCCG branches, KICC, DLCF, House on the Rock and similar congregations. Usually between 200 and 3,500 members. That specificity matters.

It means we don't try to be everything. We don't chase every trend. We keep the interface tight. We keep the workflows clear. A finance pastor can log in and understand the dashboard in ninety seconds. A resident pastor can pull up the dashboard and see their pastoral priorities without scrolling past celebration posts.

That's harder to design than a social feed. Infinite scroll is easy. People understand it. Our way requires us to really understand what a pastor actually needs in a given moment. It requires us to keep refining the signal, cutting the noise, staying true to what Ekklesia is.

It's also harder to sell. Social feeds are familiar. They feel connected. They feel modern. But a pastor doesn't need to feel connected through an app. They need to be effective in their work. They need to see their people clearly. They need to move decisions forward. That's what Ekklesia does.