I think regardless of whether what you say is correct or not - there is another benefit you are missing, the same one that Unity brought to game development - i.e. removing the developer as the bottleneck / gatekeeper for making changes - lost count of how many times our designer has created tickets to just update small styling things, or our PO wants wording or small flow changes. A tool that solves this at scale for teams will be worth it's weight in gold. #fulldisclosure am CTO of HarmonyCB - this is exactly what we are trying to achieve. Rightly or wrongly we still use a nocode moniker though, as it explains the area of work to non-tech people rather well.