The chaplain's inbox problem, and how we solved it

The splintered reality of campus ministry

If you work in campus ministry, you already know the problem. A Christian Union runs events. The student prayer group does their thing separately. The Bible study circle has their own WhatsApp. A small church group meeting in halls has a different calendar entirely. Meanwhile, a new student arrives at university and finds exactly none of this. They Google "Christian stuff at my uni" and get results from 2015.

The chaplain with 47 emails wasn't disorganised. She was managing the structural reality of campus faith: students organise themselves into small, self-led groups. That's authentic. That's grassroots. That's also a messaging nightmare if there's no shared space where all the activity lives.

We built Campus Fellowship because student-led faith groups are brilliant at organising themselves, but terrible at knowing what everyone else is doing. The app isn't meant to replace that energy. It's meant to amplify it. One calendar. One directory. One place where a first-year can find prayer groups, Bible studies, events, and the faces of people leading them.

What we actually learned from chaplains

When we started talking to campus ministry leaders, we expected them to want control. A central dashboard. Permission levels. Email reporting. What they actually wanted was simpler: visibility without interference.

Chaplains told us they needed to know what was happening on their campus without having to chase five different group leaders every week. They wanted to see the prayer request board. Not to moderate it (though they could if needed), but to understand where their students' hearts were. They wanted to be able to find a student's contact details without emailing three different people. They wanted new students to be able to find their groups without asking around.

That shaped every decision we made. The member directory isn't invasive. The announcement feed doesn't replace how groups communicate internally. The cross-society discovery feature just makes it easy to see that yes, there's a Bible study happening on campus, and here's who to contact. These aren't control mechanisms. They're connective tissue.

The prayer board moment

One feature we initially thought was simple turned out to be the most important: the prayer request board. A chaplain at a mid-sized university told us that once it was live, she discovered her students were dealing with mental health crises, family problems, and isolation that she'd had no idea about. Not because the students didn't trust her. They did. They just hadn't thought to tell her individually when they could post it somewhere the whole faith community could see and intercede.

That one feature connected the chaplain to her students' actual lives instead of just their attendance. A student leader running a Bible study realised one of his regulars had a sick parent. They'd never mentioned it in the group. He called her. That matters.

It's why we kept the prayer board anonymous if people want it to be. Why it's readable by anyone in the campus community. Why the chaplain can see it without moderating every post unless something genuinely needs addressing.

Why we didn't build the generic church platform

There are church management systems out there. They do budgeting, volunteer scheduling, sermon archiving. We could have built those things. Instead, we asked ourselves a harder question: what does campus ministry actually need that a church doesn't?

Universities are different. Students move through in four years. Leadership cycles fast. Groups form and dissolve. A group of six people running a Bible study from a student flat has completely different needs than a church with a paid staff and a building. They need event RSVPs, not volunteer rosters. They need to find each other, not manage volunteers. They need a prayer board, not a giving platform.

So we built deliberately small. Campus event calendar. Prayer group manager. Bible study coordinator. Member directory. Announcements. Cross-society discovery. That's it. It's enough because it's exactly what campus faith communities do: gather, pray, study, connect.

The chaplain as curator, not gatekeeper

Here's what surprised us most: most chaplains didn't want to be the bottleneck. They wanted to be a resource. A chaplain at one university told us she finally had breathing room because students could find things without her being the central hub. She could spend her time on the students who needed actual pastoral support instead of fielding "when's the next event" emails.

That's the chaplain's actual job. Not managing logistics. Serving the students and leaders on their campus. Knowing what's happening so they can offer guidance when it matters. Being present without being in the way.

The premium tier we built for larger campus ministries lets people running multiple groups do this at scale. A chaplain coordinating five student-led societies can see all of it. Announce things that affect everyone. Jump in when something needs their attention. But the day to day? That stays with the students.

What we're still learning

We've been live now for two and a half years. We're in 34 UK universities and 12 in the US. The feature we thought would be essential (the announcements feed) is useful but quiet. The feature we almost left out (member directory) gets used constantly. Students message each other through the app. Chaplains discover leaders they didn't know existed. New students find their first prayer group through cross-society discovery, which means they actually show up to something in week two instead than week six.

The thing we're most proud of isn't that Campus Fellowship exists. It's that chaplains tell us they finally have time to do what they were actually called to do.