At least initially, the system would include:
- Church website publishing - Sermon library - Event management - Service/Liturgy organization - Hymn/Song management
The idea would be to keep things simple and small wherever possible (team and scope), so that the price point could be low enough for small ministries.
Do you think there's a need for something like this, or is the market already too crowded?
churchapps.org is competing in this space with open source software and the price of free for their hosted versions. I don't know what their adoption rate is.
The switching costs are large in terms of time and effort for small churches. It's often one or two persons leading the charge to switch. They may not fully understand how every person interacts with the system, but they would need to set up the new system and do a trial run, likely in parallel with the existing system. Then train staff and volunteers how to use their part of the system.
leakycap•3mo ago
This doesn't sound like it would fit the reality of the needs of small churches
> Do you think there's a need for something like this, or is the market already too crowded?
It sounds uninspiring, do you have a passion to market your services to churches after you've built it?
This kind of sounds like a nightmare to build out for what I'd expect would be very small license fees. It can't fail so it has to be reliable and fast even though many of your services will only be used 2-3 times a week all at the same time, you'll be working weekends & late Wednesday nights forever, and you'll learn that many churches are using a Microsoft Works template from 1998 to print things on a LaserJet from 2002 - tough customers to claim as your own.
rcullins•3mo ago
Marketing would be key. I'm thinking about this market because I know that as much as we'd like to think every church is unique, there's a lot of consistency in, say, conservative Baptist churches, so I think there's a place for a solution that attempts to guide congregations toward best practices through templating, intelligent defaults, automation, etc. so they can get up to speed quickly. The kind of churches I'm used to in rural New England (< 100 attendees) are often all volunteer, no one with real tech chops, and use something like Google Sites or Wordpress for a website. So having something that doesn't require managing hosting, design, etc for their website, and has straightforward all-in-one options for other tools (integrated with the church website) seems like it would be a good approach to begin, if the price point were right.
Marketing-wise, I'd likely start with my own pastor/church networks and go from there.