> If you use your own tokens and solve it yourself, it's still your problem.
The flip side, of course, is that I can fix my problem - which may be unique and not something a large SaaS will ever do - on my timeline.
The flip side, of course, is that I can fix my problem - which may be unique and not something a large SaaS will ever do - on my timeline.
I would not want to be a SaaS that offers some really simple service that can be replicated in a heartbeat, though. Something like "how do I pay people all over the world" is already very complicated, and over the next decades as governments start writing laws with the understanding that AIs can implement them in code no matter how complicated they are, it's likely these problems will become even more complicated and even more important to just buy a service that can deal with them. (I'm not celebrating that, merely predicting it.) But I sure wouldn't want to be selling some super simple scheduled reminder service or something else really small.
In the worst case, envision a world where home owner associations or townships or whatever other local governmental division of just perhaps a few hundred people start levying sales taxes, with their own complicated exclusions and offsets and conditions, because LLMs make it possible to handle the code for all of the literally hundreds of thousands or millions of such jurisdictions. Even if you can throw tokens at that problem to solve it yourself, you probably don't want to. And again... I'm not celebrating that. More a world-weary bowing to the inevitable despite it being an obviously bad idea.
But the ability to meaningfully make a personal implementation has changed.
I think there might be space for "source available" enterprise software where you can use an LLM to modify it in a way that is cheap to continue reintegrating in new releases.
It may also be reasonable to send your prompts to the vendor and see if it is a feature they are willing to maintain.