80% of low-code users in 2026 are outside IT departments — Gartner
72% of IT leaders say backlogs are blocking them from strategic work
$30B+ low-code market size in 2026, projected to exceed $100B by 2030
Last quarter, a logistics company’s operations director got tired of waiting. Her team had been managing a 14-step shipment exception process through a shared inbox, a spreadsheet, and a lot of Slack messages. IT had it on the roadmap. For Q3. Of next year.
So she built it herself. Three weeks on a low-code platform. Live in production. Her team saved four hours a week per person.
IT found out when they noticed the API calls.
This story is playing out across every industry right now — and it’s forcing a reckoning that goes well beyond software procurement. It’s a question about organizational structure, decision rights, and who gets to build things inside a company. The rise of low-code platforms hasn’t just changed how apps get built. It’s quietly dismantled the assumption that building apps was ever just IT’s job.
The Backlog Is Not a Queue. It’s a Signal.
For most of the past decade, a long IT backlog was treated as a resource problem. Add more developers, the queue shrinks. Hire a vendor, offload some builds. Prioritize ruthlessly, and eventually you get to the things that matter.
But 72% of IT leaders now say they’re blocked from strategic work because of backlog volume. That’s not a staffing gap. That’s a structural mismatch between how software development was organized and what the business actually needs.
Low-code platforms surfaced that mismatch by making it optional. When a department can build what they need in two weeks without filing a ticket, they stop filing tickets. And suddenly IT realizes that 60% of what was in their backlog wasn’t really IT work — it was business logic that happened to require a form and a database.
The backlog isn’t shrinking because IT got faster. It’s shrinking because the business stopped waiting.
The healthiest IT organizations in 2026 aren’t fighting this. They’re leaning into it — shifting their role from builders of everything to architects, governance owners, and enablers of citizen development. That’s a harder job in some ways, and a more valuable one.
Shadow IT Was the Warning. Citizen Development Is the Response.
Shadow IT has been an enterprise headache for years — employees using unsanctioned tools to solve problems IT wouldn’t, or couldn’t, solve fast enough. The instinct was to clamp down. Block the tools, enforce the policy, send the memo.
It didn’t work. It never works, because shadow IT isn’t a compliance problem. It’s a demand signal. People build workarounds because they have a real problem and no sanctioned solution. Blocking the workaround doesn’t fix the problem.
Low-code platforms are the response that actually addresses the root cause. Instead of employees duct-taping together unauthorized tools in the shadows, they build on a centralized platform — one that IT controls, can audit, and can govern. The same energy that created shadow IT gets channeled into something visible, maintainable, and secure.
What that governance layer actually needs to cover:
- Centralized visibility into every app built on the platform — who owns it, when it was last updated, how many people depend on it.
- Deployment approval workflows so IT can review citizen-built apps before they go into production, without becoming a bottleneck for every small change.
- Role-based access controls enforced at the platform level, not left to individual app builders to configure correctly.
- Audit trails and version history by default — not as a premium feature, not as something you have to configure.
- Offboarding protocols — what happens to apps when the person who built them leaves the company.
This isn’t a wish list. These are table-stakes capabilities for any low-code platform being evaluated for enterprise use in 2026. If a platform can’t check these boxes, the governance problem doesn’t go away — it just becomes someone else’s emergency later.
The Departments That Are Moving Fastest (And What They’re Building)
The adoption pattern for low-code in 2026 isn’t uniform. Some departments have moved aggressively; others are still running processes on spreadsheets they’ve had since 2017. Here’s where the most activity is concentrated:
Finance and procurement
Multi-step purchase approvals, vendor onboarding, expense workflows, and month-end reporting processes are all high-volume, rule-based workflows — exactly what low-code handles well. Finance teams that have digitized these report dramatic reductions in cycle time and a near-elimination of approval bottlenecks.
HR and people operations
Onboarding is the obvious one, but the real opportunity is in the middle of the employee lifecycle — performance review cycles, transfer requests, policy acknowledgments, and offboarding checklists. These are all multi-step, multi-stakeholder processes that currently live in email threads and shared docs.
Operations and supply chain
Exception handling, incident reporting, asset tracking, and vendor communication workflows are being rebuilt on low-code platforms by operations teams who understand the process deeply but never had the tools to digitize it themselves. The logistics director from the opening of this piece is not a rare case. She’s representative.
IT itself
Change request management, help desk escalation workflows, and internal tool replacement are all active low-code use cases inside IT departments. The teams closest to the platform’s governance layer are often also its most enthusiastic power users.
What the Next 18 Months Look Like
The low-code market in 2026 is estimated at over $30 billion and growing at roughly 22% annually. By 2030, most projections put it above $100 billion. Those numbers matter less than what’s driving them: enterprises are treating low-code platforms as infrastructure, not as a productivity experiment.
The next 18 months will likely accelerate three trends that are already visible:
AI becomes a genuine co-builder
The AI integrations landing in low-code platforms in 2026 are early-stage, but the trajectory is clear. Describing a workflow in plain language and having the platform scaffold it automatically is already possible in limited forms. By late 2027, that will be the standard entry point, not a premium add-on. The platforms investing in AI tooling now will have a significant head start.
Vertical solutions take share
Horizontal low-code platforms cover a wide range of use cases but require configuration for industry-specific requirements. Healthcare compliance workflows, financial services audit trails, and logistics exception handling all have nuances that general platforms handle imperfectly. Purpose-built vertical solutions — or platforms with deep industry template libraries — will grow their share of new deployments.
Governance becomes a buying criterion, not an afterthought
Security and compliance concerns are already cited as a barrier to low-code scaling in nearly half of organizations. As deployments mature and citizen-built app portfolios grow, the question of “how do we manage all of this” becomes unavoidable. Platforms with strong governance tooling will win enterprise deals that weaker ones lose on this dimension alone.
How to Evaluate Without Getting Sold a Demo
The low-code vendor landscape has never been more crowded. Every platform has a polished demo. Most of them work well on simple use cases. Here’s how to see past the pitch:
- Test your ugliest process, not your cleanest one. Bring a real workflow with conditional logic, multiple approvers, exceptions, and integration requirements. If the platform breaks or requires workarounds, that’s the answer.
- Ask about the governance tooling before the building experience. A great builder with poor governance creates tech debt. A slightly less slick builder with enterprise-grade governance creates a sustainable platform.
- Talk to the citizen developers, not just the admins. How long did it actually take a non-technical person to build something useful? Two days or two weeks tells you a lot.
- Evaluate the integration library against your actual stack. Logo walls on vendor websites are marketing. What matters is whether the platform integrates cleanly with the specific systems your teams use daily.
- Ask about the roadmap, specifically AI. The platforms that are investing seriously in AI-assisted building now are the ones that will still be competitive in three years.
For a grounded sense of what enterprise-grade looks like in this space, Kissflow’s take on low-code platforms is a useful reference — particularly their framing around governance, citizen development enablement, and where the platform draws the line between what business teams own and what IT controls.
The logistics director who built her own exception-handling app isn’t an outlier anymore. She’s early. The organizations that give people like her a sanctioned, governed platform to build on — instead of forcing them into shadow IT or a two-year backlog — are the ones that will move faster, build better, and spend less doing it.
IT didn’t lose this battle. The ones who are winning figured out how to lead it.
