Look to Excel for guidance. Excel reigns as the most widely-deployed and used non-code/low-code tool.

Multiple studies show that something like 90% of spreadsheets contain logic errors. That might come from the UI and the tool, but in my experience it mainly comes from the users. Most people can't write out their business requirements on paper consistently and completely. We have known for decades that gathering and thinking through requirements describes the hard part of programming, not writing the code.

Where do no-code builders get stuck the most? At the very beginning, trying to describe their problem in plain English. They aren't thinking in terms of if/then conditions or organizing their data in a way to get good results from the tool.

A long time ago SQL got promoted as a way for non-coders and managers to query databases without needing programmers. Look how that worked out.

Possibly the most effective thing a llm style system could be doing here is asking the user follow up questions. Translating the requirements into code is rarely the hard part.