Packaged Software vs In House Development

That, I will say here, is not theoretical, but pure reality, in my opinion!

Most associates (employees) in companies are having one duty: to “consume (read) data“ and then to “produce (write) data“ according to their expertise, and after that, “transfer data produced“ to others.

It is as simple as that.

Even employees that their main job is “handling“ of “matter“ or “people“ are “heavy consumers“ of data. After consuming the data, they “produce“ some data (...check some boxes or writing some essays) and then “transfer“ the data to others.

The “good quality,“ “right quantity,“ and “proper timing“ of the arrival of data to be “consumed“ by the good experts “produces“ the “good products“ to be delivered to the market.

We have made Mykosmos streamline the flow of data from expertise to expertise, collect their produced data, and transfer it to others. In addition, Mykosmos lets companies create their own “way of working“ into “automated teamwork.“ So our tool permits companies to build automation to their organized team, exclusive expertise known to the company and nowhere else.

On the other hand, packaged software mainly targets the “expertise data producing.“ This feature creates obstacles and “lakes of data“ before its usage and after its usage. I mean that data are imported heavily (creating also duplicates) and are exported to the others also heavily needing conversions. The final experience by a plethora of “packaged software“ used in a company supports my argument here.

Naturally, the above analysis on packaged software is from the point of view of Mykosmos technology. However, by continuing the above, I think the future in well-packaged software is strict as a tool for “data production“ by experts. Given that data “read-in“ is made directly from the “one big company‘s“ database and the “write-out“ to the same database in order not to form “data lakes“ before or after the package usage.

In conclusion, I believe that business processes heavily concern “data transfer“ and “coordination of work.“ Something that is every company‘s exclusive technology on the field and not “data producing,“ because the final data outcome is in most cases some lines of “guidance“ or “numbers“ to be “directed“ or flow to the proper associates).

I believe that an experienced IT expert can see reason in the above.

Rafael J. Pavlides