In my experience with no-code tooling in the past, it works great as long as you stick to the narrow use cases it was designed for and are satisfied with that.

In my experience with no-code tooling in the past, it works great as long as you stick to the narrow use cases it was designed for and are satisfied with that. As soon as you want to do anything advanced that the no code tooling doesn't already handle, it gets ugly and complex, and you have to bring in specialists who know how to modify the system or work around it, and that requires coding and IT specialists. It always happens that people want the application go beyond what the no-code tooling was designed to handle and behave in some particular way that requires advanced functionality and coding. Not once have I ever seen it go any other way. Organizations are attracted by the simplicity and speed of no-code development, but they always want it to something that goes beyond that tooling. Does that mean that no-code tooling is useless? No. Just expect that it is limiting and you will likely require coding specialists to supplement the things that can be done without code.