There’s a familiar scene in most large organisations. A business team identifies a process that’s clearly broken — maybe it’s how they track vendor approvals, or how they onboard a new regional partner. They write up the requirements, submit a ticket, and then… wait. Sometimes weeks. Sometimes months. The IT backlog is long, the priorities are contested, and the broken process keeps running.
Low-code and no-code platforms are quietly dismantling that queue. And the interesting part isn’t the technology — it’s what happens to organisations when the power to build shifts to the people closest to the problem.
The Spreadsheet Was Always the First No-Code Platform
Here’s a thought worth sitting with: the humble spreadsheet was arguably the original citizen development tool. Long before anyone used the phrase, operations managers were building complex workflow logic in Excel, finance teams were running entire reporting systems without writing a line of code, and HR teams had pivot tables doing things that would make a developer’s eyes water.
Low-code and no-code platforms are the natural evolution of that instinct. They just do it at enterprise scale, with proper connectors, governance rails, and — increasingly — AI assistance built in. Think of them less as a new category and more as the long-overdue upgrade to the spreadsheet era.
The Numbers Behind the Shift
The pattern worth noting: Gartner projects that roughly 70% of new enterprise applications will be built using low-code or no-code technologies — a jump from under 25% just a few years ago. The global market, depending on which analyst you trust, sits somewhere between $37 and $40 billion and is growing at close to 30% annually.
More telling than the market size is the adoption shape. Around 60% of custom business applications are now being built outside of IT departments entirely. Schneider Electric, as one documented example, launched 60 applications in 20 months — most delivered in under 10 weeks — using citizen development programmes. Ricoh replaced legacy systems with a low-code platform and reported a 253% return on investment, with full payback in seven months.
These aren’t moonshot stories. They’re what happens when the queue gets shorter.
The “Citizen Developer” Isn’t a Hobbyist
The label “citizen developer” can sound a little patronising — like calling someone a “citizen chef” because they can make pasta at home. But the reality is more interesting than the label suggests.
Gartner tracks that 41% of employees across enterprises are now “business technologists” — people who sit outside formal IT but are actively building technology capabilities for their teams. These aren’t people hacking together shadow IT in a dark corner. They’re analysts, operations leads, and product managers who understand the business problem deeply and now have tools capable of solving it.
The pattern that emerges is less “IT versus business” and more a division of labour that actually makes sense. IT handles the architecture, governance, and integration standards. Business teams handle the domain logic, the workflow, the edge cases they’ve been living with for years. Low-code platforms are the interface between both worlds.
The Integration Question Is the Real Test
It’s easy to build a standalone app. The harder question — and the one that separates genuinely useful platforms from demo-ware — is integration. Can this tool actually talk to the ERP? Can it pull from the CRM, push to the data warehouse, trigger notifications in the ops system?
This is where the gap between platforms becomes visible. The better low-code environments come with hundreds of pre-built connectors to enterprise systems, and they’re increasingly using AI to suggest integrations based on what the application seems to be doing. The promise isn’t just speed — it’s that the speed doesn’t come at the cost of connectivity.
What the IT Backlog Was Really Telling Us
Here’s the lens worth applying: the IT backlog was never just a capacity problem. It was an information problem. IT didn’t always know which requests were urgent. Business teams didn’t always know how to articulate requirements in a way that translated cleanly into development work. The backlog was a symptom of a translation gap as much as a resource gap.
Low-code platforms are, in a way, a translation layer. They give business teams enough of a shared language with technology that they can build the things they can describe. And it turns out, a surprising number of enterprise operational problems are well within that range.
This thread connects directly to earlier conversations here about the AI readiness problem — specifically, the data stack and knowledge infrastructure that enterprise applications need to actually work well. A citizen-built application is only as good as the data it can access. The platforms are maturing fast, but the governance question doesn’t go away just because the builder changed.
The Conversation Worth Having
Not every problem should be solved with a citizen-built app. There’s a real risk — and enterprises are starting to grapple with it — that the ease of building creates a new kind of sprawl. Dozens of small apps, each solving a narrow problem, with no visibility across the organisation and no one accountable for maintenance. The same instinct that created the spreadsheet swamp can create an app swamp.
The organisations that seem to navigate this well are the ones treating citizen development as a programme, not a free-for-all. Clear governance, IT oversight on anything that touches core systems, and a feedback loop between what business teams build and what IT learns from it.
The platforms are ready. The question is whether the operating model is.
In your organisation, who’s building things they weren’t building two years ago — and what does that say about where the real bottlenecks still live?
Let’s keep learning — together.
harish.balasubramanian 
Share your thoughts