A few ideas have been bouncing around my head for a while now so I decided to codify them on a Osterwalder-style business model canvas.
This particular concept is called CMS Vault. It addresses hosting disasters that I personally faced with clients' sites over the past few years, including failed upgrades, hackings, site-jackings, and buggy plugins.
What I'm looking for from the HN community is the following:
- intuitiveness of the overall concept.
- validation of stated problem.
- viability of the solution.
- tips for execution.
- market segmentation.
- cautionary tales.
The canvas can be viewed here:
http://www.scribd.com/doc/75834784/CMS-Vault
I will appreciate any and all feedback from the HN community.
I've been developing with CMS applications for 12+ years and have never once ran into any of the issues you described above (failed upgrades, hackings, site-jackings, buggy plugins) to such a degree that I wanted/needed to completely switch the CMS platform.
I'd urge you to NOT build a product for developers. I know it's tempting because the ideas we (developers) come up with follow the 'scratch your itch' advice. I wrote a blog post about this: http://www.travisdoes.com/you-itch-sucks-scratch-somebody-el...
I'd highly recommend you focus your efforts on building a B2B SaaS product. There are millions of great opportunities to build boring, but profitable niche products.
If you need help finding some ideas, shoot me an email.