Today, technology/product choices and development partners are everywhere. This, coupled with collaborative development tools, makes it possible to have a workforce worldwide. Or, you can Google your technical requirements, and probably find a handful of vendors that already built something close to what you want. So, how do you decide when to build or when to buy?
The answer should be simple, right? You do a cost/benefit analysis of buy vs. build, and you follow its recommendation. Yet, there are many variables that affect our decision, and some of these are myths that need to be recognized and dealt with appropriately.
Myth #1 — We have a fact-based decision making process
We like to believe our decisions are driven by logic and data. Yet, our emotions and instincts play into our decision making process more than we care to admit. Just think back to your personal experiences of buying a car. I remember walking out of a dealer because of the lack of chemistry and trust I felt towards the sales-person. This doesn’t mean you should ignore your intuition and your gut feelings. Quite the contrary, you need to incorporate that into the process and use it to further investigate areas that seem too good to be true.
Myth #2 — We can find exactly what we need
We live in a world where the choices are limitless, right? Unfortunately, the buying process is all about making compromises: price, scalability, maintainability, dependency, flexibility, control, support, functionality, time-to-market, availability, usability, integration, … Just look at iPhone customers and what drives them to unlock their phones regardless of the risk: instant messaging, GPS, voice recorder, eBook reader, cheap roaming, … These are all valid features that one would want on their smart phone. ☺
Myth #3 — Our organization’s culture is irrelevant to our decision making process
Quite the contrary! Your organization’s culture and your leadership is everything when it comes to build vs. buy decisions. NIH (Not Invented Here) syndrome is a classic influencer, which usually is followed by the we will loose control argument. Again, these all are valid concerns that need careful consideration. To be successful, you need to bring the team along, consider their concerns and put an action plan in place to deal with the risks. Oh the other hand, if your team is already feeling overwhelmed, asking them to take on another development effort will likely to backfire.
Myth #4 — Buying is not creative/innovative
This is another take on the Myth #3 and the organization’s culture. You need different strengths and competencies to be good at buying. Your customers expect you to deliver a unified solution that clearly solves their business problems. Your marketing team expects you to continue to deliver on your brand image. Your support team needs a supportable and maintainable product. So, obviously buying is more than just throwing things together and expecting them to work well, there is considerable effort involved.
Myth #5 — Building is cheaper than buying
After all, you are already paying for the engineering hours, right? But, what about the opportunity cost? Or, how about the peanut butter approach of spreading your resources too thin? We tend to think about building as a one-time event, without considering the cost of deployment, support, maintenance or scalability. In my experience, obsolescing anything is an emotional process that takes precious time. So, make sure you consider the full picture and not just the one-time engineering costs.
Myth #6 — We can build it faster/better than integrating
This may be a valid argument. But again, just because you can do something doesn’t mean you should. On the surface, the technology might seem straight forward, but have you considered all other vectors? I once had a discussion about whether or not it makes sense to build our own worldwide labor time tracking solution. Again, it was not just the technology, but the cost (and risk) of becoming an expert at understanding all government and labor policies around the world, which constantly changes.
Myth #7 — Buying is not strategic for us
Proponents of this myth perhaps did not hear about the fast-follower strategy. Fast followers recognize the challenges of entering into a new market and/or technology: unknown customer reactions, cost of educating the market, unforeseen technology glitches, … So, fast followers wait on the sidelines until the new market/technology is sufficiently mature before entry. By building and integrating on others’ technologies, fast followers can further compress their product lifecycle and get to market even faster. Later on, as the value drivers for the new market become clear, the fast follower can decide to re-implement previously bought technologies by building their own.
So, here is a quick summary of different factors to consider when making build vs. buy decisions.
- If your culture is not open to buying and you don’t have the leadership strength to manage the change, then this is a wrong time to buy. However, if the scope is limited, it could also be a precious learning process for your organization.
- Focus on your core value drivers: what really matters to your business and your customers. Make sure your effort and energy is spent in these areas.
- If the technology/product in question is not a strategic value to your customers or to your firm, ask yourself if it is worth developing the competency in-house.
- Time-to-market for extending into new markets and customer segments is an important competitive advantage. In this case, it might make sense to buy first and then build second.
- Consider if this product/technology is a one-time use, or a core building block for your product portfolio.
- Quick prototypes (using off-the-shelf technologies) are invaluable to firms for test-driving new ideas. This quickly (and with low cost) enables the firm to understanding potential risks, opportunities and customer behaviors.
- Consider how well the technology/product to be purchased would be integrated into your product line and to your value-chain (sales, customer support, marketing, …). You need to manage the complete value-chain to be successful.
- Though on the surface buying a technology might reduce your development risks, it might increase risks along another dimension, such as integration and dependency management. Make sure you build these into your plans.
Finally, with apologies to The Clash ☺
Should I build or should I buy now?
If I buy there will be trouble
An if I build it will be double
So come on and let me know
Should I build or should I buy?
Technorati Tags: buy vs. build decision factors, myths of make vs. buy, fast follower strategy