Low-Code and No-Code

Short answer: Low-code and no-code are labels for building tools that replace most hand-written programming with visual building blocks. These include drag-and-drop screens, form designers, ready-made connectors and rule editors. No-code tools aim to let business users build without writing any code. Low-code tools reduce coding but still let developers add their own code for more complex logic. The line between the two labels is not precise. That raises the same questions about control, ownership and dependence on one vendor.

Typical uses include internal applications, approval forms, simple databases, customer portals and workflow automations. Some companies call staff outside the technology team who build such tools citizen developers. The main benefit is speed. A team close to the problem can build and change a tool without waiting for developers to have time. The trade-offs are less control over how the application works and dependence on the platform vendor. Limits also appear as an application grows in users, data or complexity.

A builder works in a visual editor that the platform hosts. They set up data tables, design screens and forms, and add rules such as "send orders over 5,000 to the operations lead". They connect to other systems through ready-made connectors or direct software connections. The platform hosts the application, handles user logins and applies updates. Pricing can be per user, per application, by usage or a mix. In well-run companies, the technology team sets the rules. It decides which platforms staff may use, what data builders may use and who can publish applications. It also decides how builders document their applications and hand them over when they leave.

An operations team wants a mobile app for site inspections. A development agency quotes 40,000 for a custom build, plus yearly hosting and upkeep. A low-code platform for the 25 inspectors would cost about 9,000 a year in licenses. An analyst would also spend about 80 hours building the app. Over three years, the licenses come to 27,000, which is less than the custom build alone. The team picks the low-code platform and has the app in use within six weeks. It agrees to review the choice if the number of users grows sharply or the app needs features the platform cannot offer.

Low-code and no-code tools can ease the pressure on scarce technical staff and let teams solve their own problems quickly. Leaders should decide which kinds of applications suit these tools and which need professional developers. Internal, lower-risk tools are often a good fit. Base the decision on total cost over several years, security and the effort needed to support the tools as more teams use them.

An application that one person builds can become critical to the business without documentation, testing or backup. That creates risk when the builder leaves. Per-user pricing can rise quickly as more people use a tool. Moving an application off a platform is often difficult, because the logic exists only in that vendor's format. Data protection, access control and record-keeping rules still apply. These tools need the same oversight as any other system.