Build or Buy? The Ultimate Question

The old phrase comes to mind, “If you want something done right, do it yourself.” There are a million other phrases that come to mind but I won’t bother you with them.

In a nutshell many companies feel that they can build something internally versus going outside the company. There could be many reasons for this, “we control the code” or “we’ll save money”, etc… But the real question that should be asked is TCO or “Total Cost of Ownership.” What’s it going to cost you to build versus buy?

The reality of this situation shows itself only too late for most companies who make the unwise choice. There are a miriad of consulting firms out on the web who are chomping at the bit for an opportunity to get your business. Why should you try to take on a large project in an attempt to save a few bucks, or feel that you control the code when at the end of the day, outsourcing will yield all of these things and more for most.

It really boils down to the scale and scope of a project. If you have a project that you really feel your company can handle internally and keep TCO down then by all means go for it.

However, if you have any second thoughts at all about the project you should really think about outsourcing. Unless you are a development firm you really should be spending your energies on whatever you do best, which probably isn’t programming.

There are hundreds if not thousands of quality companies out there who can do it better and much cheaper than you can; not to mention get your product to market faster.

So, the next time you think about build vs buy, why not submit your project for proposal to a few companies and see what they come back with. You will be surprised.

About the Author

by C_Bradshaw.
Article Source:,4212).aspx