Low-code and no-code development has moved from the margins to become a valuable aspect of enterprise software delivery. This change carries particular weight because of the demands of enterprise-scale processes, the regulatory environments most customers operate within, and the long-term consequences of technical decisions.
The promise is faster delivery of apps, automation, and workflows by people outside of IT contributing towards the IT workload. The risks, however, are equally clear: poorly governed adoption risks eroding trust in systems, complicating upgrades, and creating problems that consultants and project teams may spend years trying to repair.
For SAP consultants and consultancies, as well as customers and internal SAP teams, this development raises a practical question: how can speed and accessibility be welcomed without letting quality slide?
The answer is in building the right balance of governance, standardization, and coaching.
This article from IgniteSAP examines those practices, showing where consultants can contribute, where clients need to focus, and how stakeholders can think about the long-term impact.
SAP has made low-code and no-code an important part of its platform strategy, so business users can take part in development alongside IT.
The term “citizen developer” describes someone working in a business unit who can design and build small apps or workflows without traditional programming.
In SAP projects, citizen developers are not replacing professional developers, but they add capacity in areas where IT cannot move quickly enough, such as automating departmental approval chains or producing dashboards for local teams.
SAP promotes a two-tier model for extensibility.
On one tier, professional developers use tools such as ABAP in the cloud and integration platforms to build stable extensions and APIs.
On the other, citizen developers use low-code tools to create apps and workflows that consume these APIs.
The goal is to have both groups working in complementary ways that avoid conflict, helping SAP projects move faster without jeopardizing upgrades or stability.
Low-code projects move quickly, but that speed can cause problems without oversight.
Without rules, it is easy for citizen developers to create apps that duplicate work already happening elsewhere, bypass security controls, or rely on fragile data connections. Shadow IT can grow when well-meaning employees try to solve problems with little visibility into what has been built.
For SAP customers, this could be more than a technical nuisance.
A low-code app that uses HR or finance data in the wrong way can violate GDPR requirements, and in industries such as healthcare, mishandling data can break laws.
Even outside compliance, quality issues matter. If an app created by a business unit uses direct database access instead of APIs, it might break as soon as an upgrade to S/4HANA is applied. What was intended as a convenient shortcut could become an obstacle for transformation projects.
Potentially, a client may celebrate quick wins in low-code adoption, only to discover that unreviewed apps are incompatible with upgrade schedules or cannot pass audit checks.
The risks make it clear that quality and standardization are the foundation of sustainable low-code adoption.
In practice, governance for SAP low-code projects works best when it is federated. Central IT or a Center of Excellence (CoE) sets the policies, approved APIs, and rules for security and data usage. Business units then build only within those boundaries.
Good governance provides both visibility and control. Approved connectors and APIs are published so that citizen developers know what is safe to use. Peer review processes are defined so that each app can be checked before it moves into production.
Consultants can play an important role in setting up these governance frameworks, especially in the early phases when clients are still learning.
The point is to make sure creativity runs along safe tracks. When governance is described this way to business units, it is received as an encouraging and supportive framework.
Standardization complements governance by making low-code apps practical and sustainable.
In the SAP context, the most important guidance is the Clean Core principle: not to alter the ERP system directly. All extensions should sit side-by-side on the platform, using APIs and approved methods of integration. Citizen developers are expected to work only with approved APIs that have been published for external use, rather than trying to improvise connections.
Consistency also applies to user experience and data. Apps should use Fiori design principles so that the user experience does not become fragmented. Data should come from centralized and curated sources, ideally through Datasphere or other governed repositories, so that different apps do not generate conflicting reports. Integration should always flow through IT-managed tools, which keep cross-system workflows visible and auditable.
For consultants, this is a challenge. Standardization is the same logic that has always guided enterprise architecture. But what is new is the need to apply it to development that is happening outside IT. Helping clients build reusable templates and monitoring for drift are practical ways consultants can keep low-code projects tied to standards.
The human side of the process matters, and peer review is one of the strongest tools available. Each app or workflow built by a citizen developer can be reviewed by a colleague or mentor before being promoted into production. Structured reviews can check for compliance with rules on security, data, and Clean Core compliance, and they also catch practical mistakes that a new developer may not see.
Experienced citizen developers and IT mentors can guide newer participants, helping them understand what is acceptable and how to work more effectively. Communities of practice can support this culture, giving business technologists a forum to share tips, reusable assets, and lessons learned.
Consultants and consultancies are able to provide the initial coaching, acting as reviewers and mentors in the early stages of adoption. Over time, the goal is to shift this capability into the client’s own organization. Together, peer review and coaching help citizen developers feel supported, while giving IT confidence that apps moving into production meet agreed standards.
When organizations first experiment with low-code, the focus is usually on a small group of business users building lightweight apps under the supervision of IT.
At this stage, governance rules are often informal, and the number of apps is manageable.
The challenge comes when demand grows. A handful of apps could become dozens, even hundreds. As different departments create their own citizen developers, daily processes may begin to fragment unless a system of checks and balances is in place.
This is why scaling citizen development requires a clear maturity model.
In the early pilot phase, consultants often work closely with IT to create frameworks and mentor initial developers. In the expansion phase, governance rules must be written down, reusable templates created, and centralized resources published.
As adoption matures further, citizen development can become part of enterprise digital strategy, embedded in transformation programs alongside professional development. In an optimization phase, organizations can introduce AI-based assistance, advanced analytics, and continuous improvement cycles.
The key lesson for consultants and customers is that scaling is not simply a question of training more people. It is about building organizational structures that can handle the growing volume of apps without losing oversight.
As low-code development becomes more widely adopted, a frequent question in client discussions will be how to know whether a citizen development initiative is working.
Just counting the number of apps is not meaningful. What matters is whether those apps are reliable, compliant, and useful. Measuring success therefore requires a broader set of indicators.
One set of metrics looks at adoption. How many employees have been trained as citizen developers? How many business units are taking part? Another set looks at quality. What percentage of apps pass peer review on their first attempt? How many use approved APIs and data sources?
Business value metrics then show whether IT backlogs are being reduced, whether small requests are being addressed more quickly, and whether automation is saving measurable time. A final group of indicators concerns sustainability: how many apps are active, how many have been retired, and how many have been abandoned.
Consultants can help clients by building KPI dashboards and by comparing progress against industry norms. The important point is that value and compliance must be measured together. An initiative that produces many apps but fails audits is a liability, not an achievement.
Not all industries face the same constraints and governance frameworks for low-code development must reflect these differences.
In the public sector, data sovereignty and security laws dominate, though this is increasingly the case for private companies as well.
Citizen developers should usually be restricted to internal workflows such as approvals and HR processes. In healthcare, regulations forbid citizen developers from working with patient data in almost all contexts, so activity is limited to administration, training, and logistics. In financial services, regulations block citizen developers from building apps that post transactions or calculate regulated financial metrics, but there is room for automations that help with compliance reporting.
Manufacturing offers more scope for experimentation, with potential for apps that track machine downtime, schedule maintenance, or provide shop-floor dashboards. Yet even here, production control systems must remain untouched by citizen developers.
Retail is another fertile area, where store managers can build apps for stock replenishment or promotions approvals, but customer-facing systems require IT oversight. Energy, utilities, aerospace, and defense sectors are highly regulated, so low-code is limited to support processes and compliance-related workflows.
When creating governance frameworks in response to industry-specific risks, a one-size-fits-all model does not work. Each sector brings its own set of restrictions, and recognizing these early helps clients to avoid expensive mistakes.
Citizen development changes the career landscape for SAP consultants. The work is not disappearing, but it is changing.
SAP developers are no longer expected to build every single app or automation themselves, as other technical and functional consultants are well-placed to understand the systems and business context of low-code development. But all three types are also being asked to guide organizations in setting governance rules, coaching new developers and citizen developers, and embedding low-code development within transformation programs.
This creates new areas of demand. Consultants who can design governance frameworks, run peer review processes, and advise on integration points are highly valuable because they help internal employees to add value too. Those with experience across industries can provide extra perspective on regulatory requirements. Knowledge of enterprise architecture is also becoming more important, because consultants need to understand how low-code fits into larger projects such as S/4HANA migrations.
Consultants who align their careers with this can move towards strategic roles as advisors, architects, or transformation leaders. On the other hand, those who dismiss low-code as superficial or unimportant risk being left behind.
Citizen development also opens new opportunities for consultancies. Beyond their traditional project delivery work, firms can now offer governance frameworks, run training sessions and low-code workshops, and help set up communities of practice for client teams.
They can provide industry-specific low-code templates that save clients time and reduce duplication. Some firms may even offer managed services for ongoing low-code governance oversight.
In helping clients manage low-code adoption, consultancies differentiate themselves as the bridge between business users eager for quick solutions and IT leaders concerned with compliance and stability. The firms that develop expertise in this area early are likely to stand out in competitive bids, especially for large-scale transformation projects where citizen development is already in play.
Looking ahead, citizen development is set to become more deeply embedded in enterprise life. The rise of the business technologist, or employees who combine domain expertise with low-code capability, means that development capacity will expand well beyond IT departments. IT itself will continue to evolve into the role of enabler and governor, managing platforms, APIs, and governance frameworks.
AI assistants are already appearing in SAP’s ecosystem, making it easier for business users to build apps safely. Future platforms will make integration and compliance checks more automated, reducing friction. At the same time, the expectation will grow that every business unit can contribute to digital transformation through their own apps and workflows.
By the end of this decade, the number of citizen developers in SAP landscapes may well be close to the number of professional developers, particularly as the ramp up to effective development presents a realistic learning curve for most professionals. The work of consultants will not disappear, but it will focus less on building small apps and more on helping organizations manage quality, governance, and long-term strategy.
The challenge is to guide clients through this, and to build careers and services that add value in this new environment.
If you are an SAP professional looking for a new role in the SAP ecosystem our team of dedicated recruitment consultants can match you with your ideal employer and negotiate a competitive compensation package for your extremely valuable skills, so join our exclusive community at IgniteSAP.
Python for SAP Consultants: Where It Appears and How Much You Need
