I don't want to second guess your strategy—but here I go. If your tool is appealing to developers _and_ you have identified a way to reach developers, then I think you should seriously consider focusing on that.
Consider for a moment Dropbox: For a very long time they and their competitors catered to the needs of designers and other freelancers who had to share large files with clients. Was Dropbox anathema to IT departments? Yes, totally. But building a product that appeals to corporate IT departments has been a huge undertaking.
If your goal is to build a successful business, the easiest way to do that may be reaching critical mass with developers and then maybe finding ways to offer more value to your exiting (developer) customers and charging accordingly.
As I love self-deprecation, I also love it when people second-guess me :) Thanks for the feedback, yes you are right actually. I want to provide better tooling so that it requires less development effort (and make it easier for less sophisticated devs to use) but I am wrong to lump in "business users" as you are absolutely right that it would be a distraction to entertain that demographic.
Consider for a moment Dropbox: For a very long time they and their competitors catered to the needs of designers and other freelancers who had to share large files with clients. Was Dropbox anathema to IT departments? Yes, totally. But building a product that appeals to corporate IT departments has been a huge undertaking.
If your goal is to build a successful business, the easiest way to do that may be reaching critical mass with developers and then maybe finding ways to offer more value to your exiting (developer) customers and charging accordingly.