The math of software has changed, and the enterprise governance models that were built for a different era are now the bottleneck. When building a custom tool drops from a six-figure, multi-month engineering project to a two-day prototype built by an operations lead, the old assumption that buying is always safer and cheaper simply no longer holds. Retool's data makes this concrete: 35% of teams have already replaced at least one SaaS tool with a custom build, and 78% plan to build more in 2026. That's not a fringe movement. That's the center of gravity shifting under the feet of every procurement department that still thinks in annual contracts and per-seat licenses.
What stands out in this report is the gap between what builders are doing and what governance assumes they're doing. Sixty percent of builders have created tools outside IT oversight in the past year, and a quarter do so frequently. These aren't rogue junior developers. Nearly two-thirds of respondents are senior managers or above. The instinct to route around a slow process is understandable, but the consequences are real: ungoverned tools connected to production data, no audit trail, no access controls, no owner. The answer isn't to clamp down harder. It's to recognize that the energy behind shadow IT is a demand signal, and the organizations that channel that energy into governed environments with real data connectivity, security models, and review processes will be the ones that actually capture the value.
The practical implication for your organization is straightforward: the question is no longer whether your teams will build custom software. They already are. The question is whether you'll let them do it in a way that you can see, secure, and measure. The teams that get homebuilt tools to production reliably have three things in common: access to real data sources, a permissions model they trust, and a review process for what ships. None of those require a massive central IT department. They require a governance framework that's fast enough to keep pace with a builder's timeline. If your procurement cycle takes six weeks to approve a tool that takes two days to build, you haven't solved a governance problem. You've just outsourced it to the shadows.
The companies that treat governed building as a prerequisite, not a constraint, will be the ones with the data to justify their choices. The ones that don't will be left with a growing inventory of unaccounted-for tools, an expanding security surface, and no way to prove what's actually working. The report's finding that 51% of builders have shipped production software in active use, with half of those saving six or more hours per week, is the evidence that building works when it's done right. The path forward is to make the right way the easy way. That means giving builders the guardrails they need to move fast, not the friction that pushes them around. The cost of building has dropped to zero. The cost of governance has not, but it's the only line item that will determine whether this shift creates value or creates risk.