I can see it both ways. Paying 5 bucks for an add-on that's reputable and not having to think about it again may be preferable to shipping your own. It's not evident to me that one-shot-esque LLM programs will ever work as expected, since they're limited by the amount you have to specify, and then maintain as new issues arise. It's the type of work that a lot of people will be unwilling to put in.

That said, I also think that public reviews will start getting recalibrated by the users themselves. People will start noticing that programs are unreliable or lack features which are seemingly simple to implement with an LLM. The quality of an app may very well depend on how hard it is to replicate, otherwise, why not ship your own?

> asking an LLM to reverse engineer and make your own plugin is trivial.

If you already have engineers on staff, a few tens (or even hundreds) of dollars per month per plugin is likely a rounding error budget-wise. If you don't have your own engineers, you're probably not going to be able to produce something as good (reliable, well thought out, etc) as a commercial offering.

I had the same gut reaction as you, but the reality is much more subtle. We work with several clients who are bought into at least one of these ecosystems, and there's no way the math ever works out in favor of building an in-house solution.