iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The title makes two claims: that enthusiasm for low-code automation is holding up in 2026, and that this persistence is the problem. The first claim has some support. The second does not follow from the evidence. No source available in 2026 measures whether low-code hype is rising or falling. What the sources do show is a gap between continued interest, cautious enterprise rollout, and thin public evidence of measured value. For teams deciding where to invest, that gap is the practical issue, and it can be tested against a real use case.
What the 2026 evidence actually covers
Five sources shape the current picture. They differ in scope, sponsorship and what they measure, so they should not be read as one body of proof.
| Source | Date | What it measures | Limits |
|---|---|---|---|
| Gartner, Hype Cycle for Enterprise Applications, 2026 | Published May 27, 2026 | A framework for placing emerging enterprise application technologies on the Hype Cycle | Covers enterprise applications broadly. The public abstract does not place low-code automation in any phase. |
| Forrester, Biswajeet Mahapatra, “The Copilot Reality Check” | February 27, 2026 | Observations from conversations with CIOs and CDOs implementing Copilot across Power Platform, Dynamics 365 and Microsoft 365 | Qualitative. It describes Copilot implementations, not a representative low-code survey. |
| Forrester, “The Partner Opportunity For Microsoft Power Platform” | March 2026 | Survey figures on developer intent and partner service opportunities | Commissioned by Microsoft. Reports plans and interest, not realized deployment or outcomes. |
| Microsoft Adoption, Power Platform | Date not stated on the page | Recommended adoption practices, workbooks and a maturity model | Vendor guidance. It does not show that any particular rollout succeeds. |
| Forrester, Low-Code Platforms topic page | Date not stated | Broad analyst framing of the category as a way to help development teams work faster and expand software output, with a warning that hype surrounds it | Not quantified. It is not a measure of 2026 market sentiment. |
Reading the Hype Cycle without over-reading it
Gartner’s Hype Cycle is a framework that maps expectations against proven value over time. It runs through five phases, from the Innovation Trigger to the Plateau of Productivity. The phase that matters most in this debate is the Trough of Disillusionment. The 2026 abstract associates that phase with early adopters reporting performance issues and low ROI.
- The abstract does not place low-code automation in the Trough. It describes the framework and the phase definitions. It makes no claim about where low-code sits.
- The map covers enterprise applications as a whole. A headline that a technology is “in the trough” is only meaningful if the specific technology is named in the report.
- Timing is not fixed. Gartner notes that movement through the cycle often takes three to five years, and that some innovations drop off along the way. That is a description of the framework, not a schedule that every technology follows.
Why pilots persist: what Forrester saw with Copilot
Mahapatra’s February 27, 2026 commentary describes enterprises taking a measured approach to Copilot adoption. Organizations are testing targeted scenarios before broader rollout, and he characterizes most enterprises as still in pilot mode. That is a finding about Copilot programs drawn from practitioner conversations. It is not a measurement of low-code programs as a category.
#1 Best Overall
The same commentary identifies governance as a recurring feature of these implementations. The patterns it names are:
- Permissible uses: which tasks and departments may use AI-assisted building at all.
- Data access: which data sources makers can connect to.
- Approvals: who signs off before an app or agent moves into production.
- Control of low-code development: who can create, change and publish applications.
These are the same questions any citizen-developer program has to answer. Pilots often stay small because those answers are not yet in place, which is a plausible reading of the evidence but not something the sources measure directly.
Interest is not deployment: reading the 82% figure
The number most often repeated in low-code coverage comes from Forrester’s March 2026 study on the Power Platform partner opportunity. Microsoft commissioned that study. It cites the Forrester Developer Survey, 2025, for the following figures.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Measure | Figure | What it shows | What it does not show |
|---|---|---|---|
| Developers adopting or planning to adopt low-code development platforms | 82% | Stated intent to use the platforms | Current production use, scale, or business results. “Planning” is not deployment. |
| Additional developers who are interested | 13% | Expressed interest beyond the 82% | Any adoption at all |
| Realized ROI from low-code automation | Not stated | Not measured in the cited material | Cannot be inferred from survey intent |
| Share of organizations running low-code automation in production at scale | Not stated | Not measured in the cited material | Cannot be inferred from the 82% figure |
Read together, these figures show that developers are receptive to low-code platforms. They do not show that organizations have moved those plans into production or that the results justify them.
What vendor guidance adds, and what it cannot prove
Microsoft’s Power Platform adoption resources recommend a set of practices that map directly onto the governance gap above. Microsoft’s recommendations are:
- Getting started with a structured adoption plan.
- Engaging and training the organization, rather than only the developers.
- Connecting makers through community channels.
- Securing the environment before scaling.
The site provides workbooks, best practices and a maturity model to support these steps. This is Microsoft’s guidance about its own platform. It is sound direction, but it is not independent evidence that organizations following it see better outcomes.
The same Forrester partner study identifies custom AI agents, governance and security frameworks, and organizational adoption support as service opportunities for partners. That signals where paid help is expected to be needed. It does not show which providers deliver results, and it reflects the sponsor’s commercial interest.
Recommended Free Tools
How to test whether a low-code platform is delivering value
Because no universal low-code ROI figure exists in the available sources, value has to be established locally. The following sequence keeps the test honest.
- Choose one use case with a named owner. Pick a bounded process, such as an approval request, a data-entry handoff or a report that someone assembles by hand each week.
- Record a baseline before building. Measure the current cycle time, error rate, or hours spent per period. Use the same measure after launch.
- Limit the pilot to a fixed group. Name the users and the scope so that results can be attributed to the app and not to a general process change.
- Write the governance rules before the first build. Define who may build, which data sources are allowed, who approves production release, and who owns the app after launch.
- Confirm adoption capacity. Check that makers have training, that there is a community or support channel, and that the work fits the organization’s roadmap.
- Set a decision date. At that date, scale the use case, fix it, or stop, using the baseline measure. Include licensing, build and maintenance time in the cost side. If those costs were not recorded, an ROI claim is not yet supportable.
What the evidence supports, and what it does not
The evidence supports three conclusions. Interest in low-code development remains strong among developers, enterprises are testing targeted scenarios before broad rollout, and governance and adoption work is a visible part of that process. Those conclusions do not establish that low-code hype is measurably persistent in 2026, and they do not show that enthusiasm itself is the problem in every organization.
The more defensible concern is narrower. Public evidence on realized outcomes is thin, and much of the 2026 material measures intent, sponsorship-backed survey responses, or Copilot programs rather than low-code automation results. A team that can show a measured gain on one use case has more to go on than the headline debate provides.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors
