> In future I think there will be more things like 'Time' (though presumably not MS Access based!)

That's my assertion - those things like 'Time' can be developed by an AI primarily because there is no requirement of an existence of a community from which to hire.

It's an example of a small ERP system - no consultants, no changes, no community, etc.

Large systems (Sage, SAP, Syspro, etc) are purchased based on the existing pool of contractors that can be hired.

Right now, if you had a competing SAP/Syspro system freshly developed, that had all the integrations that a customer needs, how on earth will they deploy it if they cannot hire people to deploy it?

I still think MS Access was awesome. In the small companies I worked it was used successfully by moderately tech savvy directors and support employees to manage ERP, license generation, invoices, etc.

The most heard gripe was the concurrent access to the database file but I think that was solved by backing the forms by accessing anything over odbc.

It looked terrible but also was highly functional.

> We realized 1 million context window is not enough to explain all facets of Klarna > Every new thread of AI is the same employee starting from scratch again. First day at the job.

Agents are limited. With you so far.

> This week we get a demo of a vibe coded frontend that is more beautiful and easy to use than any ticket management system I have seen

Again, totally matches my expectations. Agents totally make pretty stuff that looks like working software.

I just haven't drunk enough management wine to connect the dots and figure out these facts support a jira replacement.

It also gets me wondering, if Atlassian leaned more heavily into AI (More vibe coding, more agents, more layoffs) would they have been able to keep the Klarna contract?

> Are you sure about that? Because thats exactly what Klarna is doing/has done.

That link does not say that they are switching away from a system that requires armies of consultants to implement.

AFAICT, they are switching away from Jira (Atlassian/confluence products). Those are not ERP systems.

Once again, I must point out that the these sorts of assertions reveal that the person making the assertion has never been involved in an ERP rollout, neither a big one nor a small one.

And, again, I reiterate, the only threat is to small players in the market, who don't have a community to hire from. Because to become a big player, you need to gain traction as a small player, and if every small ERP system can be replaced with an AI generated system, non single one is ever going to gain traction (Why pay $10/user/month for a basic system when you can have AI generate that for a once of fee and some employee time?)

> Hope you're not one of them.

I've been part of enough ERP contracts to know that customers evaluate their options based on how easy it is to hire consultants on the open market.

I did do quite a lot of custom software prior to AI-slop, and that market is completely destroyed with vibe-coding agents. The ERP one looks like it is simply going to further entrench the big players, because new ERPs evolve from some custom application, and once that pipeline is gone, your choices are going to be "build it yourself with no ability to hire for it" or "Go with one of the existing behemoths".

My argument is that AI will remove the pipeline that leads to incumbents seeing more competition.