Wednesday, September 17, 2008

How you outsource....

As I have started this small ISV, most of the projects I got so far are from various companies who are outsourcing their development. One thing I feel particularly weird is the inability of negotiating a proper deployment platform (by proper I mean for example, a SQL Server Express in a typical IIS installation, which is so normal to me) and yet customer would always insist to keep the deployment internal. IMO this is never a good idea:

  1. Vendors tends to estimate a lot more conservative on platform they don't primary comfortable with, so your cost is being driven up in unnecessary way;
  2. You take unforeseen risk of deployment in house, which can yield additional, not budgeted cost
  3. You create a situation where vendor could blame you on the platform regardless if its really the fault.  
  4. You could end up talking dream because you don't understand how impossible is the vendor trying to deploy on your platform without the key components in place.
My suggestions would be:
  1. Employ a capable people and insource
  2. Employ less capable but good people, employ a consultant
  3. Outsource Everything: The platform, the bandwidth, whatever you can outsource
  4. If you have to keep it in house, let your vendor do a virtual machine deployment, its just so feasible to keep this entire thing isolated and still in house

0 comments: