Vendor lock-in and business continuity would be my top concerns from a high-level perspective.

And as a developer I would be less than excited to take over the maintenance of low-code based applications, because well to a high-code person such usually web-app/saas based proprietary dev environments feel like a straitjacket. And anyways you'll likely be asked to jump in when the limits are reached and all extension efforts are uphill battles.

If you get the handover out of the low-code tooling to a "standard" development tooling (meaning something text-based in a non-proprietary programming language that I can edit in a IDE of my choice and have under proper version control) smooth, I'd be listening.