What I mean is that if the people who actually have the problem could describe the problem with sufficient detail and unambiguity, the core coding part would be very straight-forward, fast and cheap to do, regardless of the programming language.

Of course the additional things beside the core, like change management, monitoring, security, APIs etc. would add to the cost, but they are at least possible if you are not on low-coding platform.

The problem is that for anything basides the simplest applications, people cannot describe what they need in sufficient detail and unambiguity. This is where the cost of the application development comes from.

There are many means to bridge this gap: user interface design, prototypes, agile development, waterfall requirements gathering etc. Excel is a way to iterate, that many professionals learn to use. If the end users can develop software that solves their problems, and does not cause other problems, there is no problem.

From what I have seen, low-coding is sold to IT departments with promise of cost savings in the coding part, and to other departments as a means to bypass IT that they consider slow, expensive or not delivering what they want.

So we need to get down to what we mean by low-coding and what context we are talking about. In addition to Excel, Django appears to hit another sweet spot in many contexts. It is very fast to develop and iterate with, comes with built-in admin UI, but it is still possible to add fill all the corporate technical requirements as well.

The low-coding platforms the link points to that seem more problematic usually have some custom programming language, abstraction layers that often limit the extensibility for more complex applications, graphical ui designer, have difficulty supporting enterprise requirements (those security, auditability, monitoring etc.)