[MarleTangible]

Speaking from experience, it's because most systems and companies miss a lot of edge cases and standard business processes while they're trying to reinvent the wheel.

A recent example of this is, when a job has multiple shipments, there can be no single due date, e.g. 5 EA due on Tuesday and remaining 7 EA due on Friday. It's a big surprise to new comers and when you add a couple of hundred edge cases like this, SAP becomes the standard way of both obtaining this information and in a way enforcing it.

[firemelt]

I think its because sales, I think all u said is the only reason to not use sap but going bespoke

[MarleTangible]

Bespoke works to a certain extend, just like having various spreadsheets with macros in them, but after a while having a standard business process becomes quite vital. Especially when other people already made the same mistakes and came up with good solutions, but also you will need talent that is already trained for these procedure. Otherwise, you may need to take the burden of training folks all the time for something that they will not be able to transfer anywhere.

[firemelt]

yeah my pov and mean with bespoke is

where the company that needs the app, call smaller company to bespoke their requirements instead of big names like sap

[MarleTangible]

You're absolutely right on that one. It usually starts with querying data from complex systems, and slowly morphs into a dedicated solution of itself. I started seeing a lot of OEMs integrating projects like Grafana and Metabase into their product, and LLMs is making things a lot easier for everyone to start other bespoke apps as well.