The author pretty accurately describes a business model for a startup in an enterprise company: offering a service that was once hidden in some excel sheets. A

The author pretty accurately describes a business model for a startup in an enterprise company: offering a service that was once hidden in some excel sheets. As a developer at heart turned Senior Manager, I find this article especially interesting. I stumble a lot over complaints like these in the enterprise company I am working for and truth to be told, I voiced many of these before myself. Problems I see: - What is the business problem the author is trying to solve? How does a tool - Python - can help do specifically do what better? - There are no specific measurements mentioned. How big is the data the author mentioned, how long does an analysis cycle take, how large are the teams, the affected people? What about maintaining the software stack? How many requests are there per year? -What about cost savings? How could they help us compete with other companies? Lead cycles of even weeks may bother a developer but not the business. It is not that I don't believe his suggestions. It is just that I don't get to the point other than "my favorite tool could do it, too." We could easily substitute Python with R, for example. "The spreadsheet took 30+ seconds to open" I know this is an annoyance, but how often do you open it? One time a day? 20 times an hour? "The new model logic is testable and can be upgraded independently" this is one of the most valuable points here, as long as you work in a larger environment. So context is needed here as well. I know a colleague of mine who is extremely well versed in Excel who has put a decent amount of magic into her sheets. However, even losing her and starting all over again is from a business perspective way cheaper than trying to put her solution behind a cloud service. It would be fun, to have a conversation with the author.