SAP is rapidly evolving toward the cloud—and anyone operating within the SAP ecosystem can no longer ignore the Business Technology Platform (SAP BTP) and its integrated low-code/no-code (LC/NC) development tools.
In my master’s thesis I focused intensively on this shift:
How are low-code/no-code tools changing the way SAP partners work, and what opportunities and challenges arise in practice?
At first glance, the approach seems like a welcome acceleration of development—less programming effort, faster results, and stronger involvement of business departments. But upon closer inspection, new challenges become clear:
- How can governance and security be reconciled with flexible development?
- What limitations exist when integrating with existing systems?
- And how does the collaboration between IT and business units change when non-developers are suddenly able to build applications?
One thing is certain: Low-code/no-code is here to stay. For SAP partner companies aiming to create innovative, scalable, and user-oriented solutions with their customers, this technology opens up tremendous potential—as long as it is used strategically and with a clear understanding of the framework.
At PRECOGIT, we are seeing this transformation unfold in many client projects. The demand for flexible solutions is growing, yet quality, maintainability, and integration must still be guaranteed. LC/NC offers a new mindset—but not a shortcut. Instead, it represents an expansion of the development toolbox.
Another key aspect is the shifting roles within project teams. Business departments are gaining more influence over solution development, while traditional developers are increasingly taking on roles as architects, integrators, and quality gatekeepers. This new collaboration demands trust, communication, and a solid methodological foundation.
My work also made certain technical limits clear: As business processes become more complex, integration efforts increase. It’s evident that LC/NC cannot be thought of in isolation from the overall system architecture. Instead, it requires a meaningful balance between standardization, extensibility, and governance.
My takeaway after many discussions, tests, and reflections:
Low-code/no-code is not a replacement for strong development—but it is an accelerator for strong ideas. Those who use the technology wisely can deliver results faster, involve users more effectively, and shorten innovation cycles.
If you’re interested in how to use low-code/no-code effectively in your SAP landscape, feel free to reach out to us. At PRECOGIT, we support you with experience, strategy, and just the right amount of pragmatism—from prototype to productive deployment.
