A lit rack corridor in a Munich integration hall, brushed-steel trays along the wall, an indigo patch lead crossing the tray edges

Editorial notes

Short notes on the enterprise software landscape, written for buyers rather than for vendors. Procurement digitisation, low-code modernisation, cloud-native operations, and HR and finance consolidation, with the German market kept in view.

Start reading

Notes on where enterprise platforms are moving

The editorial position

No press releases, no vendor announcements reproduced as analysis

This is the notes page of InnovaTech Solutions. It collects what changed in the platforms our clients actually run, and what that change means for the people choosing them. Procurement digitisation, low-code modernisation, cloud-native operations, HR and finance consolidation — each note is tied to a specific shift in the market, not to a fixed publishing schedule.

The notes are written by the same team that runs platform assessments, so a claim that appears here has been answered at least once against a real landscape. Vendor input is welcome as information. It is not welcome as copy.

Average read for each note — 4 minutes

The notes, grouped

Where enterprise platforms are moving

Five areas we watch closely. Each note is short enough to read between meetings and specific enough to argue with.

Two colleagues at a supplier review meeting in a German procurement office, morning light from the left Lead note 01
Procurement digitisation Reading note

Procurement digitisation is a data problem wearing a platform costume

The platforms have matured. SAP Ariba and its competitors can run sourcing, supplier management, contracts, and procurement workflows at a level of sophistication that was not available a decade ago. What has not matured at the same pace is the data underneath: supplier masters that differ by business unit, contract taxonomies that were never agreed, and approval hierarchies that exist in people's heads.

Digitisation projects stall there, not in the software. Before a shortlist is written, it is worth checking whether the supplier master is one list or five, whether the contract taxonomy has an owner, and whether the approval chain can be drawn without asking three people. The right answer to a stalled procurement programme is usually a two-week data conversation, not a new module.

Published 2026 — revisited when the market shifts

Low-code modernisation

Low-code's second act is governance

OutSystems, Mendix, and the rest proved that business apps can be delivered in weeks rather than quarters. The interesting question now is what happens in year three, when hundreds of apps exist and nobody is certain who owns them.

The organisations getting value from low-code modernisation are the ones that answered the governance question early: who may build, what gets reviewed, and how an app that touches the ERP is treated differently from an internal form. Those three questions, answered before the second hundred apps exist, decide whether the platform stays an asset or becomes an audit line.

ERP extensions

ERP extensions are moving out of the core

The pattern of extending ERP through custom code inside the core is being replaced, slowly, by platform-based extension. SAP Business Technology Platform is the clearest example in the SAP world, used to connect SAP and non-SAP systems and to build beside the core rather than inside it.

The attraction is upgrade safety: fewer modifications inside the core means fewer upgrade surprises. The cost is a new architectural layer that has to be operated and governed, which some organisations underestimate. The trade is real, and the choice is usually easier to make with the operating model drawn first.

HR and finance

Cloud-native HR changes the finance conversation

Workday and similar cloud HR and finance systems arrive with cloud-native architecture and deep HR and process functionality. What organisations notice afterwards is a second effect: once people data and finance data sit in the same cloud-native model, reporting that used to require a data warehouse project becomes a configuration exercise.

That is the real argument for consolidation, and it shows up a year after go-live rather than during the demo. The configuration exercise still needs someone to own the reporting model — the point is that the first report no longer starts with a data warehouse purchase.

Mid-market ERP

Mid-market ERP: the quiet majority

Most German mid-market firms are not running a full enterprise suite, and Oracle NetSuite sits in the space between lightweight accounting tools and large-suite ERP for exactly that reason. The choice is rarely about capability at the top end. It is about how much of the standard model fits before customisation begins, and how many entities and countries the system has to consolidate.

Two infrastructure notes

Infrastructure is back in the vendor review

Cloud-native operations

Kubernetes stopped being a decision

A few years ago, choosing container orchestration was a project. Kubernetes won, and the question changed from which layer to use to who operates it and to what standard. In hybrid and regulated environments the operating model matters more than the technology, because the same cluster platform can be run well or run as an unmanaged collection of risks.

That is now an infrastructure governance topic rather than an infrastructure selection topic.

Enterprise Linux

The infrastructure layer stopped being invisible

Enterprise Linux rarely makes headlines, but SUSE Linux Enterprise Server and comparable platforms sit underneath a large share of SAP and hybrid estates. When compliance and audit requirements tighten, the infrastructure layer stops being invisible: certification status, support model, and patch governance become part of the vendor review.

Expect more of this, not less — and expect the questions to arrive from procurement rather than from the platform team.

The editorial position, narrowed

What to watch next

Two things, in our view. Both will shape shortlists over the next few years, and neither is settled yet.

Sovereignty

How hyperscale clouds get assessed against sovereignty

Hyperscale clouds such as Google Cloud are being assessed against sovereignty requirements in practice, because the answer is becoming more specific and more contractual. Expect the review criteria to keep tightening, and expect the differences between providers to become easier to write down.

Governance

Whether low-code estates get governed before or after

The second question is whether low-code estates get governed before or after they become a problem. The organisations that answered the governance question in year one are writing the playbook the rest will follow; the ones that did not are discovering the cost of a second governance project.

The editorial standards

How these notes get written

How often do you publish these notes?

When there is something concrete to say. We would rather publish less and keep each note tied to a specific change in the market than maintain a fixed schedule of commentary.

Do you accept vendor contributions?

No. The notes are written by the same team that runs platform assessments, and the editorial standards on the About page apply here as well. Vendor input is welcome as information, not as copy.

InnovaTech Solutions GmbH Königsallee 45, 80539 München Monday–Friday, 9:00 AM – 6:00 PM