How Low-Code and No-Code Platforms Are Changing Who Builds Automation

For most of its history, building automation required developers. Someone had to write the scripts, configure the integrations, handle the error cases, and maintain the code over time. This created a structural bottleneck in every organization: the number of processes that could be automated was limited not by the number of processes worth automating, but by the availability of technical staff to build the automation. Business teams would identify a process they wanted automated, submit a request to IT, and wait in a queue that could stretch for months.

Low-code and no-code automation platforms are fundamentally changing this dynamic. By providing visual, drag-and-drop interfaces for building automated workflows, these platforms enable business users to build their own automations without writing code. Gartner forecasts the low-code development market to exceed $30 billion in 2026, and by that year, developers outside formal IT departments are projected to account for at least 80% of the user base for low-code development tools. The people who understand the processes best are increasingly the ones building the automations, and the implications for how organizations approach automation are significant.

The Rise of the Citizen Developer

The term "citizen developer" refers to a business user who builds applications or automations using low-code/no-code tools, without formal software development training. These are accountants who automate their own reporting workflows, HR specialists who build onboarding task sequences, operations managers who create dashboards and alerts, and sales coordinators who automate CRM data entry.

Citizen developers now outnumber professional developers roughly 4 to 1 in the automation space, and about 41% of businesses have active citizen development initiatives. The growth is driven by a straightforward economic reality: there are far more processes that need automation than there are developers available to build it. By enabling business users to handle the simpler automations themselves, organizations free up their professional developers to focus on the more complex, enterprise-grade automation work that genuinely requires coding expertise.

The tools have matured to the point where a business user with no programming background can build a meaningful automation in hours or days rather than the weeks or months it would take to get the same work done through traditional IT channels. A typical low-code RPA tool presents the user with a visual canvas where they drag and drop actions (open application, read field, enter data, click button, send email, make decision), connect them in sequence, and configure the parameters for each step. The platform handles the underlying code generation, error handling, and execution infrastructure.

What Citizen Developers Build Well

Citizen-developed automations tend to work best for departmental processes with moderate complexity. These are workflows that the business team understands intimately but that are too specific or too low-priority to make it through the IT project queue. Common examples include:

• Data consolidation. Pulling data from multiple spreadsheets or systems into a single report on a recurring schedule.
• Notification and escalation workflows. Automatically alerting team members when specific conditions are met, such as an overdue task, an approaching deadline, or an approval request that has been pending too long.
• Form processing. Taking data submitted through a form and routing it to the right person, creating records in the appropriate systems, and sending confirmation messages.
• Simple integrations. Moving data between cloud applications that do not have native integrations. For example, when a new row is added to a SharePoint list, create a corresponding task in the project management tool and send a Slack message to the assigned person.
• Document generation. Populating templates with data from a database or form submission to produce contracts, letters, reports, or invoices.

Organizations report a 27% efficiency gain in workflow automation when combining low-code tools with RPA capabilities. The gains come primarily from the speed of deployment. When the person who identifies the need is also the person who builds the solution, the requirements gathering phase (often the longest phase in traditional IT projects) effectively disappears.

The Governance Challenge

Citizen development introduces a real governance challenge, and organizations that ignore it pay for it later. When business users can build automations independently, the result can be dozens or hundreds of automations scattered across departments with no central visibility, no consistent security standards, no documentation, and no maintenance plan. This is sometimes called "shadow automation," and it mirrors the shadow IT problem that has plagued organizations for years.

The risks are concrete. A citizen-developed automation might access sensitive data without proper authorization controls. It might contain business logic that becomes outdated but continues to run because nobody remembers it exists. It might create dependencies on a specific employee who built it and is the only person who understands how it works. It might interact with production systems in ways that IT did not anticipate and cannot monitor.

The solution is not to ban citizen development, which just pushes the bottleneck back to IT. The solution is to establish a governance framework that enables citizen development within defined boundaries. Effective governance frameworks typically include several components:

A registry of automations. Every automation, whether built by IT or by a citizen developer, should be registered in a central catalog that includes who built it, what it does, what data it accesses, and who is responsible for maintaining it.

Tiered approval. Low-risk automations (internal data, no sensitive information, no financial impact) can be deployed by the citizen developer with minimal oversight. Medium-risk automations require review by IT or a Center of Excellence. High-risk automations (handling personal data, interacting with financial systems, affecting customers) require full IT involvement.

Guardrails in the platform. Most enterprise low-code platforms allow administrators to restrict which applications and data sources citizen developers can access. IT can configure the platform so that citizen developers can build workflows using approved connectors and data sources but cannot access production databases, customer PII, or critical infrastructure.

Training and certification. A basic training program that teaches citizen developers how to build reliable automations, including error handling, testing, and documentation. This does not need to be extensive, but it ensures a minimum quality standard.

The IT-Business Partnership Model

The most successful citizen development programs operate as a partnership between IT and business. IT provides the platform, sets the governance rules, manages the infrastructure, and handles the complex automations that require deep technical expertise. Business users build and maintain the departmental automations that they understand best. A Center of Excellence often sits between the two, providing guidance, reviewing automations that exceed the risk threshold, and maintaining the overall automation roadmap.

Gartner predicts that by 2026, 75% of large enterprises will employ at least four low-code tools. This is not a single-platform future. Different tools serve different purposes, and the governance framework needs to accommodate that diversity while maintaining consistent standards across platforms.

The AI Layer

Over 70% of no-code platforms are expected to integrate AI-powered features by the end of 2025, further lowering the skill barrier. AI-assisted development automates parts of the automation-building process itself: suggesting workflow steps based on the user's description of what they want to accomplish, generating conditional logic from natural language rules, and identifying potential errors before deployment. This makes citizen development accessible to an even broader population of business users and accelerates the time from idea to working automation.

The combination of low-code platforms, citizen developers, and AI-assisted building is creating a new model for how organizations approach automation. The IT department is no longer the sole builder of automated workflows. Instead, IT is the enabler, providing the platforms, guardrails, and expertise that allow the entire organization to participate in automation. The backlog of automation requests that used to sit in the IT queue gets distributed across the business, where it can be addressed by the people closest to the work.

For organizations still running all automation through centralized IT, the shift to a governed citizen development model represents a meaningful acceleration in automation capacity. It does not eliminate the need for professional developers. It redirects their time toward the complex, high-value automation work that genuinely requires their expertise, while empowering business users to solve their own simpler but still valuable automation challenges. The net result is more processes automated, faster deployment, and a broader base of people who understand and advocate for automation across the organization.

Related Reading

• AI Governance Frameworks for Responsible Enterprise Deployment
• AI Readiness Assessment and What It Reveals About Your Organization
• Building Custom AI Agents vs Using Off-the-Shelf Solutions
• Change Management Is Where Most AI Projects Actually Fail
• Corporate Data Confidentiality in the Age of AI Processing