Hacker News new | ask | show | jobs
by leakycap 247 days ago
> pretty opinionated, geared toward quick setup and intelligent defaults

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.

1 comments

Thanks for the feedback. I understand the challenges of a small volunteer team trying to deal with old technology. I also have 20+ years in SaaS, so I get the scalability and reliability concerns.

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.