Make (Freedom) OR Buy (Simplicity)

 The other day I, Touristologistly, tweeted this post:

Jordi, exactly what do you mean with this sentence “Make (freedom) OR Buy (Simplicity)” Well, I try to summarize in a framework (you know how much I love frameworks!) one of the tough decisions you face in any project related to the Internet. You can make a solution from scratch and get exactly (or almost exactly) what you want OR you can use a standard solution to get something similar to the solution you had in your mind faster and cheaper. 

What are the cons of Make? Without any doubt, the cost and time of getting the solution done. Furthermore, you also have to add uncertainty. When the solution is already created you know, for sure, the cost and the time. If you have to develop it… well, it is not so clear. Only people that never code will say that they know exactly the time it takes to finish all the features! 

What are the cons of Buy? As any solution for a lot of people/companies you have limits in the customization you are able to ask for. For instance, here in this video, you can get an idea about the solution WordPress  is proposing for restaurants. It’s easy to implement what is already developed. Adding more functionalities, though it is possible, enters us into a new league!

So, this is the framework. You can Make or Buy a solution. This solution will have functionalities (the things that the program will help do: Reservations, getting recommendations, sharing opinions… you name it!) which you have to specify with a technological scheme. An associated cost and the time in order to do the following concepts:

A) Design and development of the solution: Here the key characteristic will be if we want a database or not. Having a database is essential for any complete solution, but to design the scheme of it (Yes! Even if you are using a schemeless database as MongoDB or CouchDB). Define the CRUD (Create, read, update and delete)... is one of the most gratifying and difficult things to do! 

B)Implementation: Once the solution is created you have to implement it and test the functionality in a real environment. 

C) Training: Somebody has to use this solution! So, you have to train the “homus organizativus” members of your chain of value . As a matter of fact, one of the main problems of software is the lack of use for bad training causes! 

D) Production: ISP / CLOUD: You have to decide if you want this solution in-house: Install the hardware at your office or with an ISP (Internet Service Provider) OR install it in the cloud using the IaaS, PaaS and SaaS features we talked about here. 

As I always said to my Touristologists, Clients and Associates… Functionalities, Cost and Time - you can choose two! A lot of functionalities and very fast? The cost will rise. I will have to outsource and work at night! Low cost and very fast? You will get few functionalities! 

Jordi, what is the meaning of the word integration that appears in the picture? Ah! You noticed it, right? It is a very important word! If you remember, an important characteristic of successful enterprises in web 3.0 is to achieve a chain of value working as a single organization and the integration of all departments, employees and software involved in any servuction process! So, once you get your solution you have to integrate it with other software servicing other departments inside your company and other software in your chain of value. And no, this is not automatic, Touristologists! It is very important BUT complicated… unless you are … A TOURISTOLOGIST!!!