From low-code to AI-native development: “build versus buy” dilemma is back again

Artificial intelligence is fundamentally changing the economics of knowledge work. Activities that once required hours of manual effort can increasingly be completed in minutes: analyzing reports, summarizing large volumes of information, preparing documentation, writing code, designing interfaces, building prototypes and, in some cases, creating substantial parts of software applications. 

The debate around AI often focuses on how much responsibility should be delegated to machines. How thoroughly should AI-generated work be validated? Can AI-generated code meet the same standards as code written entirely by experienced engineers? Where should human oversight remain mandatory? 

These questions are far from settled. One development, however, is already clear: AI is dramatically reducing the time between an idea and its implementation. 

This shift has particularly important implications for software development. 

From low-code to AI-assisted custom development 

For years, low-code and no-code platforms have addressed one of the fundamental problems of software development: building custom functionality takes time, specialized expertise and significant investment. 

Platforms such as Microsoft Power Platform, Salesforce, SAP, Microsoft Dynamics and other enterprise ecosystems have enabled companies to create applications, automate workflows and build analytical tools without developing every component from scratch. 

The trade-off is standardization. 

Businesses gain speed by operating within the architecture, licensing model, functionality and technical boundaries of a particular ecosystem. This approach can work extremely well when business requirements correspond closely to the capabilities of the platform. However, the more specialized the workflow becomes, the more organizations may need to adapt their processes to the software rather than adapting the software to their processes. 

AI-assisted development begins to change this equation. 

Consider business intelligence as a relatively simple example. A company can use an established BI platform to aggregate information from multiple sources and present it through dashboards and reports. This is often efficient, but it can also introduce additional licensing, infrastructure, integration, access-management and governance considerations. 

AI-assisted software development makes another approach increasingly practical: building analytics directly into the company’s own product or internal software environment. 

Instead of adding another application to the technology stack, businesses can potentially create purpose-built dashboards, analytical workflows and decision-support functionality around their existing architecture, data and business logic. 

The important change is therefore not simply that AI can write code faster. It is that AI can gradually reduce the economic penalty businesses historically paid for choosing customization over standardization. 

The economics of “build versus buy” are changing 

Enterprise software has traditionally presented organizations with a familiar choice. 

They could buy an established platform and configure their processes around it, gaining faster implementation and proven functionality but accepting licensing costs and platform constraints. 

Or they could build custom software around their exact requirements, gaining greater flexibility and ownership but accepting considerably higher development costs, longer implementation timelines and greater technical responsibility. 

AI is beginning to narrow the gap between these alternatives. 

Requirements can be transformed into prototypes faster. Boilerplate code can be generated automatically. Interfaces can be assembled more efficiently. Tests, documentation and integrations can be partially automated. Developers can explore alternative architectures faster and spend less time on repetitive implementation work. 

As these capabilities improve, organizations may increasingly ask a different question: 

Why adapt our business to software if software can increasingly be adapted to our business? 

This does not mean that SAP, Microsoft Dynamics 365, Salesforce or other enterprise platforms will disappear. Their value extends far beyond their interfaces. They provide mature business logic, extensive ecosystems, compliance capabilities, integrations, support structures and decades of accumulated domain expertise. 

Instead, the boundary between packaged and custom software is likely to shift. 

Companies may use enterprise platforms for standardized processes while developing increasingly sophisticated custom layers, applications and AI agents around the areas where their competitive differentiation actually exists. 

From low-code to AI-native development 

Low-code and no-code platforms abstract programming by giving users predefined building blocks. 

AI introduces a fundamentally different abstraction layer: intent. 

Instead of selecting predefined components and connecting them manually, a user or engineer can increasingly describe the desired business outcome, architecture, rules and constraints in natural language and allow AI systems to translate those requirements into software components. 

This makes requirements engineering even more important. 

The easier it becomes to generate software, the more important it becomes to specify precisely what should be generated. 

A vague requirement can produce a functional prototype surprisingly quickly. But enterprise software is more than visible functionality. It involves access rights, exception handling, integrations, data models, security, scalability, performance, logging, regulatory requirements, recovery mechanisms and hundreds of business rules that may not be immediately visible. 

The bottleneck may therefore gradually move from writing code toward defining systems correctly. 

Developers will not simply disappear from this process. Their role is more likely to move upward: from manually producing every implementation detail toward architecture, orchestration, validation and control of increasingly AI-generated systems. 

Can AI help build enterprise-scale systems? 

The same principle could eventually extend far beyond dashboards and relatively small internal applications. 

AI-assisted engineering may make it possible to create much larger customized systems at a speed that would previously have been economically unrealistic. 

This does not mean that an organization will simply ask an AI system to “build an alternative to SAP” and receive a production-ready enterprise platform. 

Complexity does not disappear because code becomes easier to generate. 

Instead, the nature of complexity changes. 

When implementation becomes faster, architecture, requirements, data governance, integrations, security and validation become proportionally more important. Organizations may save considerable time during development while investing more attention in defining processes and verifying that the resulting system behaves correctly. 

AI therefore creates an interesting paradox: 

The easier software becomes to build, the more important software engineering discipline becomes. 

Human oversight will remain uneven across industries 

The pace of adoption will also differ significantly between industries. 

For an internal reporting dashboard, an AI-generated error may be inconvenient. In healthcare, aerospace, financial infrastructure, industrial control or defense systems, an error can have much more serious consequences. 

Organizations operating in safety-critical or heavily regulated environments are therefore likely to apply stricter requirements around validation, explainability, security, traceability and human approval. 

AI-assisted development will not necessarily be absent from these industries. In fact, it may become deeply embedded in their engineering processes. But the principle of human-in-the-loop validation is likely to remain particularly important where software decisions have physical, financial or safety consequences. 

This reinforces another important point: faster software generation does not eliminate responsibility for the resulting system. 

More software means more software to maintain 

There is another consequence of AI-assisted development that receives considerably less attention. 

If AI makes software cheaper and faster to create, businesses will probably create more software. 

More departments will be able to justify custom applications. More temporary prototypes will evolve into operational systems. More companies will build proprietary tools instead of purchasing standalone applications. Existing products will acquire new AI-generated functionality at a faster rate. Every successful application, however, eventually becomes a system that someone must maintain. 

Dependencies change. Security vulnerabilities emerge. APIs evolve. Infrastructure requirements grow. Business processes change. Data volumes increase. AI models and external services are updated. Functionality that worked for 100 users may need to support 100,000. 

This creates a significant opportunity for the software services industry. 

The next generation of software services 

As software becomes more complex and increasingly interconnected, responsibility for its outcomes can be difficult to assign when many systems, providers, and stakeholders are involved. This makes it especially important to work with a reliable software services provider that has the necessary competencies, experience, and support capabilities to manage this kind of software effectively. Such a provider can help coordinate responsibilities, implement improvements, monitor performance, and maintain the software properly over time. 

The rise of AI-generated and AI-assisted software may reduce demand for certain categories of repetitive development work. At the same time, it is likely to increase demand for expertise surrounding the entire software lifecycle. 

Software Maintenance service becomes particularly important. Rapidly generated applications still require monitoring, bug fixing, dependency management, security updates, performance optimization and adaptation to changing business requirements. 

Software System Audit may become equally important. Before an organization scales an AI-generated application, introduces major functionality or integrates it into critical infrastructure, it needs to understand what has actually been built. Architecture, code quality, security, scalability, maintainability and technical debt need independent assessment. 

Architecture and Integration Services may grow as organizations combine enterprise platforms, proprietary applications, AI agents, external APIs and legacy systems into increasingly complex environments. 

AI Governance and Quality Assurance will become another layer of the software lifecycle, particularly where AI-generated code or autonomous agents participate in critical business processes. 

And Software Modernization may become continuous rather than periodic. If development cycles become dramatically shorter, applications may evolve constantly instead of undergoing major upgrades every several years. 

The competitive advantage of a software development company may therefore gradually shift from simply having enough engineers to produce code toward having the expertise to design, validate, integrate, secure, operate and continuously improve software created at AI speed. 

The next five years 

Software development companies will increasingly focus on maintaining AI-created software and taking responsibility for systems they did not build entirely from scratch. As AI makes it possible to produce more custom software with fewer people, the role of the engineer will change significantly. 

It will no longer be enough to specialize in only one narrow area. The most valuable professionals will be universal specialists: people with a broad pool of competencies who can understand the entire system, identify problems across different layers, and make informed decisions about architecture, security, infrastructure, data, and user needs. A useful analogy is a pediatrician. A pediatrician does not replace every specialist, but can understand the whole patient, recognize a wide range of problems, and know when deeper expertise is required. In the same way, future software engineers will need to see the whole product before deciding where specialized intervention is necessary. 

This shift will also influence employment. Fewer people may be needed to maintain AI-generated software, so the number and nature of workplaces in software development will change. If the industry previously had less custom software and required more engineers to build it, the next five years may bring more custom software maintained by fewer people. This will affect not only the total number of engineers, but also the type of engineers companies seek. Demand will increasingly favor skilled full-stack engineers who can operate across the entire software lifecycle and act as universal specialists rather than experts limited to a single technology or layer. 

The most important effect of AI on software development may ultimately be neither code generation nor developer productivity. 

It may be the democratization of customization. 

For decades, highly customized enterprise software has largely been available to organizations with sufficient budgets, development teams and implementation timelines. Smaller companies often had little choice but to adopt standardized SaaS products and adapt their processes accordingly. 

AI has the potential to reduce this barrier. 

Over the next five years, we may see a transition from an era dominated by software configuration toward one increasingly characterized by software generation and continuous customization. 

Low-code and no-code platforms will remain valuable. Enterprise systems will remain essential. But the economics surrounding them are changing. 

The question for businesses will increasingly move beyond: 

Which software should we buy?  toward:  Which capabilities should we buy, which should we build, and which parts of our technology should be uniquely ours? 

For software service companies, the same transformation creates a new strategic direction. Producing code will remain important, but code itself will become less scarce. Architecture, domain knowledge, integration expertise, quality assurance, security, governance and long-term responsibility for software will become increasingly valuable. 

AI may make software easier to create. 

It will not make good software easy to create. 

And that distinction may define the software development and IT services market for the next five years. 

0 0 votes
Article Rating
Subscribe
Notify of
0 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments

You may also like

you're currently offline

0
Would love your thoughts, please comment.x
()
x