Nodes instead of Code: The No-/Low-Code programming shift

Digitalization is no longer an optional future topic. While large companies often have their own IT departments or substantial budgets for digital projects, small and medium-sized enterprises (SMEs) and public administrations face very different conditions: limited resources, skill shortages, and high demands for flexibility. No-/Low-Code platforms offer a promising approach. In this article, we explain what No-/Low-Code means exactly, how SMEs and public administrations can specifically benefit, and which success factors play a role in implementation.

What are No-/Low-Code platforms?

No-/Low-Code platforms enable software development with minimal programming effort. Instead of complex code, graphical user interfaces, drag-and-drop functionality, and reusable modules (nodes) are used. Even employees without deep IT knowledge - so-called “citizen developers” - can independently create digital solutions or adapt existing applications.

No-/Low-Code platforms are like toolkits for software. Instead of programming every function by hand, you get ready-made building blocks: forms, tables, buttons, workflows, which you combine via drag-and-drop into your own application.

• Low-Code means: Most things can be visually assembled, but for special functions, small code snippets can still be added if needed.
• No-Code means: Everything is implemented entirely without code - ideal for simple applications where no special logic or complex interfaces are required.

Why are No-/Low-Code platforms particularly attractive for SMEs?

SMEs often face typical challenges:

• Limited IT resources: skill shortages, small IT teams, and external dependencies slow down innovation
• Rapid pace of change: markets, customer requirements, and legal frameworks evolve quickly
• Desire for individual digitalization: standard software often does not fit the specific processes of smaller companies

No-/Low-Code platforms offer practical solutions for these:

1. Faster implementation of digital solutions
Visual development and modular building blocks enable creating applications up to 10 times faster than with traditional programming. This shortens project durations, reduces time-to-market, and increases agility.

2. Lower development costs
Reusing components, reducing reliance on external service providers, and less programming effort significantly cut total software development costs.

3. Stronger involvement of business units
No-/Low-Code approaches promote collaboration between IT and departments. Employees from sales, logistics, or HR can implement their own ideas or participate directly in development without learning complex programming languages.

4. Flexibility with changing requirements
No-/Low-Code platforms allow quick adaptation to new circumstances - whether due to legal requirements, new business models, or internal process changes - keeping the IT landscape dynamic and future-proof.

5. Promotion of digital skills within the company
Using No-/Low-Code strengthens digital mindsets and enhances understanding of IT-supported processes. This is a key element for sustainable digital transformation.

Possible Use Cases in SMEs/Public Sector Organisations (PSOs)

• Automating business processes: e.g., approval workflows, travel expense management, or contract management
• Digital customer portals: e.g., for orders, service requests, or complaints
• Custom reporting solutions: e.g., dashboards for sales or inventory management
• Integration of existing systems: e.g., ERP, CRM, and accounting software via interfaces

Case Study: Digital service order system in a machinery manufacturer

A medium-sized machinery manufacturer wants to modernize its service process. Currently, repair and maintenance orders are handled via emails, phone calls, and Excel sheets, leading to unclear responsibilities, delays, and lack of transparency.

Goal: A central system to record service orders, prioritize them, and assign them to technicians including status tracking and direct customer feedback.

Implementation without programming skills:

Using a Low-Code platform, the company can largely build the system itself:

• Service order form: input fields created via drag-and-drop (customer data, machine type, error description, urgency)
• Automated workflow control: orders automatically routed to the appropriate technician based on machine type
• Status tracking: technicians can accept orders, upload photos, and update status via smartphone
• Automatic customer notifications: emails sent when orders start or complete

Everything happens through the platform’s visual interface - without a single line of code.

Points where programming skills are needed:
Despite the Low-Code foundation, some areas require expertise:

• Special logic for deployment planning: e.g., if a job requires multiple qualifications (hydraulics + electronics), custom scripts may be needed to find the right technician
• ERP system integration: API interfaces often have to be programmed to automatically transfer material use and work times
• Custom PDF reports: automatically generated service reports with company logos and specific layout requirements usually need server-side scripts or specialized templates

Case Study: Digital vacation requests in a city administration

A city administration wants to digitize its paper-based vacation requests. The goal is for employees to fill out the request online, have it automatically forwarded to the appropriate supervisor, and allow HR to import approved data directly into the time-tracking system.

Building the application without coding:

HR can implement much of this independently with a Low-Code platform:

• Form design via drag-and-drop: fields for name, period, reason for vacation, upload of documents
• Workflow definition: automatic forwarding based on department assignment
• Notifications: automatic emails on approval or rejection
• Simple reports: monthly overview of approved vacation

All within a graphical interface - no manual coding required.

Where programming Is helpful or necessary:

• Custom business logic: e.g., if a request exceeds 20 days, it must be additionally approved by the HR manager, and this rule only applies to certain departments—usually embedded as a small script
• Special interface connections: integration with the time-tracking system often requires API connections or database queries written in SQL or another language
• Custom frontend design: exact adherence to corporate design (CSS layouts, animations, mobile optimizations) often requires additional coding

Challenges and success factors

As promising as low-code and no-code platforms are, implementation should not be seen as a purely technical project. Success depends heavily on how well the platform is integrated into the existing organization.

A central challenge is strategic embedding. No-/Low-Code should not be introduced as a “one-off solution for a department” but as part of an overarching digitalization strategy. This avoids isolated solutions and enables synergy across applications.

Clear IT governance is equally important. Even if business units create their own apps, standards for data security, access control, privacy, and maintenance must be defined. This is especially critical in the public sector to comply with regulations like GDPR.

Training and enabling employees is another success factor. No-/Low-Code platforms are easy to use, but even the best tools remain underused if users don’t know how to make the most of them. Training, internal communities, and practical examples help lower barriers and foster creativity.

Change management should also not be underestimated. No-/Low-Code changes how applications are created and often also processes and responsibilities. Actively managing this change, transparently communicating benefits, and making successes visible are key.

Starting small and using pilot projects is advisable. A clear, simple use case - like an approval process or internal reporting system - delivers quick wins and builds acceptance. From there, adoption can be scaled.

In short: Low-Code is not just a matter of technology but above all of approach. Clear goals, technical standards, employee involvement, and manageable projects lay the foundation for sustainable success.

Conclusion

Low-Code and No-Code platforms are undoubtedly innovation drivers for digitalization - both in SMEs and public administrations. They lower entry barriers, speed up development, and enable ideas from business units to quickly become working solutions. This democratizes software development and creates space for digital solutions without deep programming skills.

At the same time, their limitations must not be overlooked. Complex or highly specialized applications often hit technical limits in No-/Low-Code environments. Customizing individual business logic or seamless integration into established IT landscapes can be demanding. Dependency on platform providers and long-term maintainability are also factors to consider from the start.

Among professional developers, opinions vary. Many appreciate No-/Low-Code as a valuable tool to implement simple or standardized requirements faster and relieve IT. Others see it as a complement - not a replacement - for classical development and warn against underestimating software complexity.

All in all, SMEs investing in No-/Low-Code today invest not only in technology but in future viability. Low-Code and No-Code platforms are no silver bullet but a powerful building block of modern digital strategies. Their innovation potential unfolds especially when consciously used as a complement to traditional development, with clear use cases, good governance, and awareness of their limits.