Drag. Drop. Configure. Deploy. The business user builds the workflow without writing a line of code. The IT bottleneck is eliminated. The backlog is dissolved. Everyone is a developer.
Until the requirement exceeds the platform's vocabulary.
⸻
The Happy Path
Low-code platforms are extraordinary at the happy path. Standard forms. Simple workflows. CRUD operations against a database. The kind of work that a junior developer could build in a week, the business user builds in an afternoon.
This speed is real. It is also the entire value proposition. The platform sells velocity on common patterns. It does not sell flexibility on uncommon ones.
The first three months are a revelation. The team ships internal tools faster than IT ever could. The executive sponsor presents the results. The organization increases investment.
Then someone needs a conditional branching logic that the platform does not support.
⸻
The Cliff
The transition from "the platform handles this" to "the platform cannot handle this" is not gradual. It is a cliff.
The business user hits a requirement that requires custom code. The low-code platform offers an escape hatch: write a script, call an API, embed a code block. But the business user is not a developer. The escape hatch is a locked door.
Now the organization needs a developer anyway. But the developer must work within the constraints of the low-code platform, which is more restrictive than writing the solution from scratch. The code runs inside a sandbox with limited debugging, opaque error handling, and dependency on the platform's runtime.
The development that was supposed to be faster is now slower than if it had been built traditionally, because the developer is fighting the platform instead of the problem.
⸻
The Lock-In Gravity
Every workflow built on the low-code platform is stored in the platform's proprietary format. There is no export. There is no migration path. The logic lives inside a system that the organization does not own and cannot inspect.
When the platform raises prices, the organization pays. When the platform changes its API, the organization adapts. When the platform sunsets a feature, the organization rebuilds.
The IT bottleneck was not eliminated. It was outsourced to a vendor who now controls the pace, the cost, and the capability ceiling of the organization's internal tooling.
⸻
The Honest Assessment
Low-code is a tool, not a strategy.
Use it for prototypes, internal dashboards, and workflows that will never exceed the platform's capabilities. Do not use it for systems that will grow, integrate, or require customization beyond the happy path.
The ceiling is real. Build toward it if you want. But know where it is before you start.
End.