Conjola was born from the observation that SAP transformation projects too often rely on workshops and assumptions instead of data. We flip that around. At our core we're a product — a SaaS platform; we complement it with hands-on, tool-related consulting around its adoption.
Our mission
Every decision about an SAP landscape should be based on what the system actually does — not on what someone believes. Conjola makes real usage visible and gives teams a reliable foundation for their transformation.
What we stand for
Data over opinion
We analyze real document flows instead of idealized target processes.
Clarity over complexity
Complex landscapes deserve simple, honest views.
Consulting as a partner
We build tools that let consultants and clients work as equals.
I have been in the SAP world since 2014 — starting out as a developer, trained as an SD consultant and given real responsibility early on in an international template rollout. Ever since, my projects have revolved around what actually hurts in a transformation: interfaces, data migration, business partners, rollouts across borders.
Along the way I have come to know SAP from several angles: as an external consultant on the client side and in-house on the other side of the table, where the same decisions are made under entirely different constraints. The past few years were almost entirely S/4HANA — brownfield, greenfield, bluefield — plus a stint as product owner of an integration solution that is available in the SAP Store today. Most recently I led the Center of Excellence for transformation at one of Germany's large IT consultancies: the approach, the methodology and the tooling our consultants take into an S/4HANA project. After that, the public cloud projects of my unit were my responsibility across the board.
The same pattern repeated in every one of those projects. Anyone new to an SAP system — an external consultant just as much as an in-house colleague who has just joined — faces a landscape grown complicated over years and is expected to form an overview of it. Aggregated documentation rarely exists, and where it does, it is patchy and out of date. So the picture people form of the system is assembled in workshops, based on assumptions and on what individuals happen to remember. And the most consequential decisions rest on that picture.
Yet the answers had been in the system all along; nobody could get to them in reasonable time. That is precisely what has changed: what used to fail on sheer effort can now be answered with AI-assisted analysis in days rather than months. And that is exactly where Conjola comes in — it makes visible what a system really does, before the first big decision is made.
The name has a personal origin: “Con” stands for consulting, plus the first syllables from the private founding context — combined into ConJoLa. That it also reads as CONnect · JOurney · LAndscape came as a happy coincidence, and captures exactly what we do: connect an SAP landscape across the journey of transformation and make it make sense — seeing it as a living journey again, not legacy ballast. Make SAP make sense. The “.AI” stands for the core: Conjola is built with AI and uses AI — source-code analysis, topical clustering of custom developments and a chat assistant.
