Why we'll never build Campus Fellowship for your local parish

The temptation to become everything

Every founder hears the same siren song: expand the addressable market, broaden the use case, appeal to a wider audience. Someone uses your product well, so surely others will too. A church of 50 people is just a smaller version of a church of 500, right? A university fellowship is just a secular version of a traditional parish group.

Except it isn't. And the moment you pretend it is, you're building a product for no one in particular.

Campus Fellowship exists because university Christian life is genuinely different from Sunday morning church. A student-led Bible study that meets in a dorm lounge at 10 p.m. on a Wednesday has different rhythms, different attendance patterns, different communication needs than a Wednesday evening service in a church building. A prayer request board used by 40 students who all see each other in lectures the next day functions completely differently from one used by 200 people who might never meet face to face.

The specificity isn't a limitation we're waiting to grow out of. It's the entire point.

What happens when you design for one thing

Campus Fellowship's event calendar, for instance, isn't generic event software. It's built around how university groups actually schedule things: semester-by-semester planning, recurring weekly meetings, last-minute prayer vigils that need to reach 30 people in an hour. When a student society secretary uses our RSVP system, they're not thinking about how to grow their congregation. They're thinking about whether enough people are coming on Thursday to need two pizzas or three.

The member directory works the way it does because student-led groups care about something churches don't: cross-campus discovery. A fresher at one campus ministry needs to find out what's happening at a different group across town. That's a feature built specifically for the fractured, multi-site nature of university faith societies. It wouldn't make sense in a parish context. Parishes don't worry about discovering other churches in their own building.

The prayer request board is another example. In a university context, prayer needs often feel more immediate and interpersonal. A student posts something vulnerable about exam stress or family stuff, and twelve people who actually know them see it within minutes. That creates a completely different dynamic from the prayer request card passed around in a vestry.

Every design decision we make assumes a specific kind of user in a specific kind of space. Remove that specificity, and you're not broadening the product. You're diluting it.

The math of saying no

There are roughly 150,000 churches in the UK and US. There are roughly 3,000 university campuses. On a pure market-size basis, churches are the obvious bet. But here's what matters: a university Christian Union knows exactly what Campus Fellowship is for. They land on the site, read that it's built for student-led faith societies, and either think 'that's us' or they move on. They're not confused. They're not disappointed when we don't do something a megachurch would need.

A parish administrator, by contrast, would arrive expecting something different. We'd spend energy explaining what we aren't. We'd collect requests for features we'd never build: multi-site worship scheduling, giving management, volunteer coordination across dozens of ministries. We'd be perpetually saying no, and every no would feel like a shortcoming rather than a design choice.

Some companies can pull off being general purpose. It requires enormous resources, careful product management, and a genuine ability to serve multiple masters well. We're a small team. Our energy is better spent making Campus Fellowship absolutely brilliant for the specific thing it does: connecting students with their campus community of faith.

The math works better when you're not fighting the product's own nature.

What staying focused actually gives you

Constraints are useful. They force you to talk to your actual users constantly. We hear from student society secretaries about what's broken in their workflow. We hear from campus ministry leaders about what would help them coordinate across multiple groups. We build in that direction. We don't spend cycles wondering whether we should also support something we don't understand.

There's something else, too. Right now, if a campus group shows up with a genuine problem, we can solve it for them in a way that makes sense for their context. We're not negotiating with other customer segments. We're not saying 'we'd do that, but it would break things for users at the other end of the market.' That clarity is rare, and it matters.

And when we get a message from someone at a parish asking if we can help, we can point them toward what actually suits them better. That feels like a win, not a loss.

The question beneath the question

This isn't about being precious about university spaces or thinking student ministry is somehow more important than congregational life. It's about the unglamorous work of doing one thing well.

A lot of early-stage products fail not because their original idea was wrong, but because they abandoned it too fast in pursuit of something that looked bigger. The pressure to expand is constant. Investors, advisors, and even customers sometimes push you toward 'broader appeal.' Broader appeal is a beautiful phrase. It's also how you end up building something no one actually wants to use every day.

Campus Fellowship will always be for students and campus ministry leaders. We'll keep building deeper into that space. We'll stay focused on the specific rhythms and needs of faith communities on university campuses. That's not a temporary constraint. It's the whole strategy.

The question isn't 'why won't we expand?' The better question is: 'why would we expand when we haven't finished building something genuinely excellent for the people we exist to serve?'