1. The cons here are pretty big. Your target customer is somebody who will solve most problems with google and 3 lines of bash/perl/etc scripting. The generic

1. The cons here are pretty big. Your target customer is somebody who will solve most problems with google and 3 lines of bash/perl/etc scripting. The generic .NET software shop pays for this kind of software - *nix people don't. I've written a few more paragraphs about this, and subsequently deleted them. It all really boils down to one thing: it's a bad idea. A lot of fun to write, but there's no money to be made. 2. It's very hard to get any kind of competitive advantage here. If your idea works somebody else will do the same thing and charge less for the service. Also you will spend most of your time managing your (invariably unreliable) overseas contacts, leaving you no time to do anything else. This seems to be the kind of company that is fun in the beginning, and then turns into a nightmarish chore. 3. I kind of like this idea. You have domain knowledge here, and already a few potential customers (or at least companies that can give you some feedback.) It's a niche, and there's still money to be made. Best idea so far.