About InnovaTech Solutions
Who writes these platform assessments
InnovaTech Solutions GmbH is an enterprise software advisory based in München, at Königsallee 45. We assess and compare enterprise platforms for mid-market and large organisations in Germany, and advise on the integration, compliance and readiness questions that decide whether a selected platform actually works in the estate it lands in.
Published assessments
8
Resale commission
0
Office
München
Engagement model
Fixed-fee scoping
Assessment author
Your point of contact
Vendor copy
Not accepted
The mandate
What we do, and what we do not
We advise. We do not resell the platforms we assess, we do not implement them, and we do not take a commission on a selection outcome. That keeps the assessment independent of the recommendation, which is the only way it is worth anything to a buyer. Where we have a relationship with a vendor, it is disclosed in the written work before any recommendation is made.
We do
- Assess a platform against the estate it will actually land in.
- Compare two or three serious candidates on integration, operating model and fit.
- Advise on compliance and sovereignty constraints before a selection is fixed.
- Document the reasoning so a buyer's team can audit the recommendation.
We do not
- Resell platforms or take a commission on a selection outcome.
- Implement or run the systems we assess.
- Charge a vendor for a position on a shortlist.
- Accept vendor marketing copy as assessment content.
Disclosed
Where a vendor relationship exists, it is named in the written assessment before the recommendation, not in a footnote afterwards. The disclosure sits in the same document a buyer reads to make a decision.
If we recommend against a platform, the reasoning is printed alongside the recommendation so the team can trace how the conclusion was reached.
Editorial coverage
The eight platforms we cover
The list is deliberate rather than exhaustive. These are the platforms that appear repeatedly on German enterprise shortlists across procurement, ERP, low-code, infrastructure, cloud and HCM. Covering them properly is more useful than covering everything superficially.
Procurement
SAP Ariba
Shortlisted where source-to-pay is being separated from the core ERP and re-documented for audit.
Application platform
SAP Business Technology Platform
Comes up when an SAP landscape needs extension, integration and analytics under one operational roof.
Container platform
Kubernetes
Assessed on operating model and skills, not on feature lists — the choice changes who runs what.
ERP
Oracle NetSuite
Typically weighed against SAP or an in-house system by mid-market groups with multi-entity structure.
Low-code
OutSystems
Considered where a business needs to shorten delivery cycles without dissolving its integration governance.
Infrastructure
SUSE Linux Enterprise Server
Enters the picture where long-term support windows and patch discipline matter to operations.
Cloud
Google Cloud
Assessed on the specific workloads moving there — data residency decisions land at the workload, not the account.
HCM
Workday
Comes into the estate through HR, and then puts its own requirements on identity, reporting and works-council process.
For platforms outside this list we can still advise on fit and integration. The difference is that the assessment draws on general architecture practice rather than maintained platform documentation, and we state that limitation up front rather than in a footnote.
Editorial method
How an assessment is written
Each assessment describes intended use case, integration fit and operating model. It states the constraints under which we would advise against the platform, not only the conditions under which it works. Where a claim cannot be supported by the vendor's own documentation or by observed deployment practice, it does not go in.
No metrics are invented. No reference customers are implied. No deployment is described as successful unless we can point to what made it work — the constraint it cleared, the integration it took on, and the operating model that resulted.
The assessment is drafted where the deployment runs, not from a slide deck.
Source
Vendor documentation, product documentation, and observed deployment practice.
Excluded
Vendor marketing copy, unverifiable benchmarks, and unnamed reference customers.
Published
Use case, integration fit, operating model, and the constraints against it.
Reviewed
Any vendor relationship in play is written into the same document before the recommendation.
Conflict-of-interest policy
Editorial standards we hold to
The assessment is independent of the vendor relationship. If we hold a relationship with a platform vendor, it is named in the written work before the recommendation, not in a footnote afterwards. If we recommend against a platform, the reasoning is documented alongside the recommendation so your team can audit the logic.
Position on a shortlist
We do not accept payment for a position on a shortlist, in cash or in kind.
Never
Vendor-written content
We do not accept vendor copy as assessment content, regardless of length.
Never
Working relationship with a vendor
Named in the written assessment, above the recommendation — not below it.
Always disclosed
Recommendation against a platform
Documented with its reasoning, so the buyer's team can inspect how the conclusion was reached.
Reasoned
Correction of a published assessment
Issued in place, with a dated note of what changed and why.
In place
The team
Who works on this
Small team, senior people. The work is done by advisors who have run or reviewed enterprise deployments rather than by analysts working from public material alone. That is a deliberate limit on how much we take on at once, and it is the reason engagements are scoped rather than open-ended.
It also means the person who writes the assessment is the person you speak to about it. There is no handover layer between the analysis and the conversation, and no second reading of a document you have already read once.
Write to the advisor directly
InnovaTech Solutions GmbH
Königsallee 45, 80539 München, Deutschland
+49 30 2009 5341
[email protected]
Monday to Friday, 9:00 AM – 6:00 PM
Assessments are scoped before they are started — never open-ended.
Why the location matters
The München context
Being based in München is not incidental. The German mid-market and the large organisations around it have a particular set of constraints: SAP compatibility, data sovereignty, works council involvement, and a preference for documented reasoning over confident slides.
Working in this market shaped the assessment method. It is also why compliance appears as a selection criterion in our work rather than as a later review stage.
First step
How engagements usually start
Most begin with a specific decision: a shortlist that needs a second opinion, an integration question that has not been answered, or a compliance constraint that has stalled a project. Some begin earlier, with a genuine uncertainty about where to start. Both are workable.
The useful first step is a written description of the systems in place and the constraint that triggered the search. If your question is about a specific platform or an integration boundary, say so in the first message and we will route it to the right part of the assessment.
Frequently asked
Questions we get before the first call
Two questions come up most often when a new team makes first contact. If yours is not answered here, the message we need is short: the systems in place, and the constraint that triggered the search.
Do you sell the software you review?
Can we commission an assessment of a platform outside your eight?
Still unsure whether we are the right advisory for your question? The next section shows exactly what the reader is handed in a written engagement.
Reading the assessment
Your stack, judged by what it must actually do.
If the assessment we publish helps you decide, the same method applies to a specific decision in your own estate. Send the systems in place and the constraint that triggered the search, and we will tell you which part of the assessment answers it first.
Direct line
InnovaTech Solutions GmbH
Königsallee 45, 80539 München, Deutschland
+49 30 2009 5341
[email protected]
Monday to Friday, 9:00 AM – 6:00 PM