Are you sure that your solution, however valuable, is monetizable as a discrete product?
I built something some years ago which tied calendars from various sources together in a single view. It was, if I may say so, a neat piece of work, and open source....however, it died on the vine because iOS and Android devices included that functionality as part of their base product. And I do't really have an issue with it, because the base need - consolidation of calendars - was recognized as a near-universal use case (vs consolidation of email accounts, which users often want to view separately).
So great ideas which deal with obvious use-cases may show up in mass-market offerings because they're obvious....and render other efforts redundant. If your use case is truly unique and unlikely to be directly addressed, that's great, but the next question is whether or not there's a sustainable market for it. Right now, there's a huge market for pluggable and easily-implementable analytics, and a number of smaller companies which built such software have been eaten up by the majors to shorten the development curve. Most of these solutions are frameworks, and they're built that way, with the intent to sell to a large commercial buyer who will then tailor the solution to their specific need, and productize it for specific environments. In that kind of case, designers can enjoy both sale of company/IP and ongoing development, so there's a business model.
I think, net-net, that the ecosystem has evolved to a place where most new growth is accretive rather than disruptive. And until the Next Big Thing comes along, the business model of choice will be to layer on add-ons to the existing model.