Initially I would say pivot, but I always wouldn't force a pivot (e.g. try to think of a similar idea, make that instead). The fact that your product is well-kn

Initially I would say pivot, but I always wouldn't force a pivot (e.g. try to think of a similar idea, make that instead). The fact that your product is well-known in your niche means that you've got a slightly easier job at marketing a similar project. Other options you could consider: A) How technical is the support you get caught doing? Is it something only you can do? Would hiring a technical support "employee" via oDesk or Elance make sense? Would an open forum for support (if it doesn't already exist) help users solve simpler problems? Can you reasonably charge a support / maintenance fee (Charging for exceeding X hours of support per month)? B) Are there other ways to encourage the time commitment and get churches to keep using? Are there small features or changes you could make to encourage involvement? What's your motivation for creating the product? If you really believe in it, you could find ways to minimize your current involvement while building another smaller service that may not mean as much to you but generate more cashflow and allow you to pursue projects. Most of those questions are rhetorical but hopefully they help you narrow down the issue and possible solutions.