A practical issue is that a lot of big software is used to solve small problems. For instance with his example, in the past perhaps instead of creating a little custom app it would have been a series of excel sheets with some other third parties tool as needed. And I think this is a very common use case. At most/all companies there tend to be convoluted processes to do relatively simple things, often enriching the big generalist companies in the process. As people become capable of creating competent ad-hoc solutions to problems, the utility of big high-utility software goes down.
Like a quote I've read on here multiple times about replacing e.g. excel or whatever, people often mention that users only use 5% of a software's functionality, but it's a different 5% for each person. The argument being that to replace excel you'd then need to mimic every esoteric thing it does, but when users can now achieve that 5% in a highly customized way with no real knowledge needed, it's going to have a major impact on big software.
The people who were twisting Excel+VBA into massive "applications" in-house should be getting Claude licenses and guidance how to do that with a custom application instead.
We've done that internally already with a few very successful use-cases and a bunch of "this is nice" -level things. I think one case saved us 4 figures a month when we built a bespoke service that does just the things we need and could replace a SaaS that had 420 features - of which we used 2.
Like a quote I've read on here multiple times about replacing e.g. excel or whatever, people often mention that users only use 5% of a software's functionality, but it's a different 5% for each person. The argument being that to replace excel you'd then need to mimic every esoteric thing it does, but when users can now achieve that 5% in a highly customized way with no real knowledge needed, it's going to have a major impact on big software.