Why we built cross-society discovery, not another group chat

The problem wasn't connection, it was discovery

When we first sketched Campus Fellowship, our assumption was straightforward: Christian students on campus were struggling to stay in touch. They needed a chat space, a place to coordinate, a digital version of the group texts that were already happening. We built that first, because it felt obvious.

But once we started talking to chaplains, student leaders, and the societies themselves, the real friction emerged. The problem wasn't that groups couldn't message each other. WhatsApp and Telegram were already doing that. The problem was that large portions of each campus's Christian community had no idea what else existed five buildings away.

A student from one prayer group might never know there was a Bible study they'd prefer. Someone new to faith might assume the one society they found was the only option. Across a typical UK university campus, we found students duplicating effort without knowing it, or missing communities that were genuinely aligned with what they were looking for.

Generic doesn't work when students have very specific needs

We could have built something that worked for any student group anywhere. A generic platform with message channels, file storage, event calendars that would fit everything from the football society to the philology club. Those platforms exist. They're polished and well-funded.

But a Christian student looking for a prayer group on Monday morning doesn't want to wade through a platform built for everyone. They want to see which prayer groups meet this week, what times suit them, who else is going. They want to know if there's a Bible study focused on a specific book. They want the member directory to tell them something real about their community.

So we built something narrow instead. We built for the exact shape of what a campus Christian community actually looks like: events (really matters on a university calendar), prayer requests (people share things there they won't say in a group chat), Bible studies (the structure matters; groups need to track where they are in Scripture), a member directory (trust is built on knowing people), announcements (every society needs to broadcast), and the thing nobody else had bothered to build: cross-society discovery.

Discovery is a feature, not an afterthought

The cross-society discovery took longer than we expected to get right. It would have been easy to slap on a 'View all societies' page and call it done. Instead, we built something that actually helps a student understand what they're looking at.

When you open Campus Fellowship on your campus, you see the events your own society is running. But you also see what else is happening: other groups' events, announcements from communities you haven't joined yet, and a directory that shows you who's where. If you're interested, you can see what a society is about before you commit to joining. No mystery. No awkward walk into a meeting wondering if you've made a terrible mistake.

For campus ministry leaders and chaplains running multiple groups, this is the tool that stops duplication and actually strengthens the whole community. Instead of six separate WhatsApp groups and a Facebook page nobody updates, there's one place where the entire campus Christian community can see itself. Attendance at events goes up. New students find their people faster. Bigger issues (mental health struggles, questions about faith, isolation) get caught earlier because the community is actually connected.

Built for who's actually using it

Campus Fellowship is free for student-led societies because we built it for them first. A student leading a prayer group of fifteen people shouldn't have to justify software costs to anyone. They should be able to set up an event calendar, share prayer requests, and keep their community together without friction.

For the larger campus ministries running three, four, or five groups across a campus (or across multiple campuses), there's a premium tier. Those teams need more: multi-group management, better analytics on attendance, the ability to handle real scale without the whole thing creaking. But we started with the students, and we stayed focused on what actually makes their life easier.

We also built Campus Fellowship for UK and US universities specifically, not churches in general and not generic 'faith communities'. The rhythms are different. Term dates matter. The academic calendar shapes everything. American fraternities and sororities have their own faith chapters. British Christian Unions function like proper societies within the student union structure. A generic church platform misses all of this.

The quiet measure of whether it matters

Six months in, the metric that surprised us most wasn't activity within groups. It was the number of students who discovered a second community they wanted to join. We have no way to know exactly how many people found something new because of the cross-society feed, but messages come in regularly. 'Didn't know there was a prayer group for engineering students.' 'Found out about the Bible study, this is exactly what I was looking for.' 'Joined a second society because I saw what they were doing.'

That's what we built for. Not to replace the WhatsApp groups or to add another notification to the pile. To make the invisible visible. To let a 19-year-old on a new campus see the full shape of the Christian community around her, and choose what fits.