Low-Code and No-Code Tools Are Quietly Eating Enterprise Software
Business teams are building their own internal apps and automations without a dev team, and it's changing what enterprise software even means.
Ask an operations manager at almost any mid-size company right now what they’ve built this year, and there’s a decent chance the answer isn’t a spreadsheet — it’s an app. Not a shipped, App Store app, but an internal tool: an approval workflow, a customer intake form wired to a database, a bot that reads incoming invoices and files them automatically. Built by someone with no engineering title, using a low-code platform or a robotic process automation (RPA) tool, in an afternoon.
This isn’t new as a category, but 2020 has been the year it stopped being a niche and started being infrastructure. The reason is not mysterious: companies everywhere have had to digitize processes fast, with hiring frozen or slowed, and with IT departments already buried fielding remote-work fires. When you can’t get three sprints of a real dev team’s time to automate a manual reporting process, and you can drag-and-drop something that mostly works using a tool built for exactly that, you do it.
Why now, specifically
The pandemic didn’t invent low-code, but it created the perfect pressure. Every company suddenly needed new digital processes — remote onboarding, contactless workflows, digital forms replacing paper ones — at the same moment that budgets for new engineering headcount got cut. RPA tools, which automate repetitive tasks by literally scripting clicks and data entry across existing software, saw the same dynamic: a finance team drowning in manual reconciliation work doesn’t want a custom-built system, it wants the tedious part gone by Friday.
The tools themselves have also gotten good enough to be dangerous, in the best sense. Drag-and-drop database builders, workflow automation platforms that connect dozens of common business apps together, and RPA suites that can be configured by someone comfortable with Excel formulas but not with code — these have matured to the point where “shadow IT” isn’t a handful of rogue macros anymore. It’s real, semi-durable software running real business processes, built entirely outside the engineering org.
What it means for developers
The obvious anxiety is “will this replace programmers.” It won’t, not in any near-term sense — these tools are good at well-defined, form-and-workflow shaped problems, and they get messy fast once requirements involve real edge cases, scale, or integration with anything unusual. But it does change the job. Professional developers are increasingly going to be the people called in after a low-code tool has been stretched past its limits, or the ones setting guardrails so a department doesn’t quietly build a system that becomes an unmaintainable liability nobody documented.
There’s also a quieter shift worth watching: as these platforms proliferate, IT and security teams are going to have to figure out governance for software they didn’t build and may not know exists. A workflow tool with access to customer data, assembled by someone in sales ops, is still a piece of software with a blast radius. Enterprise software used to mean something bought and deployed top-down. Increasingly, it means something assembled bottom-up, and the rest of the org is going to spend the next few years catching up to that reality.