The problem is if you started with no code, can you round the rough edges?
One reason we use code instead of no code is so we can extend the product in any direction that is necessary, not just the few that were anticipated by a tool.
Many are impressed by the no-code claims and start that way only to get bitten after a few minor successes by said rough edge - then what else can you do than try to soften your current investment's thorns. And arguably anything can be addressed, given the right motivation/time/money.
My last few jobs have been replacing no-code setups. It certainly doesn't take teams long to figure out how bad the current offering suck. Sometimes only 3-4 integrations in.
