
We are proud of what we have already been able to help shape.
A selection of our completed consulting engagements. Mostly unnamed, because confidentiality is part of our client relationships.
- The question
How do first AI pilots become an enterprise-wide strategy that creates measurable business value instead of remaining stuck in pilot status?
Our answerWe operationalised an enterprise-wide data & AI strategy: through a hub-and-spoke model, a portfolio management function as the link between corporate strategy and execution, and transformation concepts across five fields of action: organisation, people, data, technology and compliance. Assessed by an interdisciplinary team of management consultants and technology experts, geared towards maximum ROI.
Three building blocks01 — Strategy frameworkFive action fields with a clear target picture.
Organisation, people, data, technology and compliance — each with a concrete roadmap for implementation.
02 — Operating ModelHub & Spoke, connecting strategy and implementation.
Portfolio management as the connective link. Who prioritises, who delivers, who steers.
03 — Portfolio steeringAn ROI-maximised use-case portfolio.
Data and AI initiatives steered with purpose, instead of isolated one-off projects.
What it enables- AI strategy anchored across the entire enterprise, with clear target states.
- Action fields backed with concrete roadmaps for implementation.
- An ROI-maximised, strategically aligned portfolio of AI use cases established.
- Data and AI initiatives steered with purpose - business value sustainably increased.
- The question
How can distributed GenAI initiatives be scaled company-wide when a shared vision, binding governance and a consistent technological target picture are missing?
Our answerA shared GenAI vision and strategy creates the binding framework for the entire organisation. Building on this, we established a central programme organisation with clear governance, consolidated existing technology initiatives and translated business requirements into a shared technology blueprint as well as an aligned architecture and implementation roadmap.
Three building blocks01 — GENAI TARGET PICTUREShared direction for all GenAI initiatives
Vision, strategic guidelines and target picture aligned company-wide and bindingly defined.
02 — PROGRAMME GOVERNANCEBinding governance instead of parallel individual initiatives
Programme organisation, responsibilities and decision paths established for coordinated GenAI activities.
03 — TECHNOLOGY BLUEPRINTA shared foundation for scalable GenAI solutions
Technology initiatives consolidated and business requirements translated into platform capabilities and architecture decisions
What it enables- A shared GenAI target picture creates direction for all initiatives
- A technology blueprint prevents isolated platform and architecture decisions
- Central programme governance reduces duplicate effort and accelerates decisions
- An aligned roadmap enables scalable GenAI implementation
- The question
How can end-to-end processes be realised when systems interpret the same business objects differently and do not represent relationships and lifecycles consistently?
Our answerStarting from the relevant business objects, we developed a shared domain data understanding. Entities, lifecycles and dependencies were modelled graph-based and transferred into a technical ontology. The architecture artefact provided in Turtle format can be integrated directly into existing systems and data platforms.
Three building blocks01 — BUSINESS OBJECT MODELConsistent definition of central business objects
Entities, properties and lifecycles identified across domains and unambiguously described
02 — RELATIONSHIP MODELDependencies made visible and usable graph-based
Relationships between business objects represented in a consistent semantic model
03 — TECHNICAL ONTOLOGYFrom domain model to integrable architecture artefact
The aligned ontology provided in Turtle format for systems and platforms
What it enables- Shared data understanding across domains and systems
- Unambiguous object relationships improve data quality and reusability
- A technically usable ontology accelerates downstream data integrations
- A semantic foundation enables scalable automation and AI applications
- The question
How can prioritised GenAI initiatives be realised in the short term without fragmented tool decisions and missing integration capability blocking the long-term agentic architecture?
Our answerWe validated the prioritised GenAI initiatives against the existing IT, application and data landscape. Dependencies, risks and success factors were translated into concrete short-term measures. In parallel, a long-term target picture for the Agentic Enterprise emerged, along with an experimental approach to investigate a semantic layer as a future architecture foundation.
Three building blocks01 — FEASIBILITY VALIDATIONGenAI initiatives checked against real prerequisites
Technical and organisational feasibility assessed against the existing system and data landscape
02 — IMPLEMENTATION ASSURANCERisks translated into concrete immediate measures
Dependencies, success factors and action areas prioritised to secure short-term implementation
03 — AGENTIC TARGET ARCHITECTURELong-term connectability beyond individual initiatives
A target picture and experimental approach for a semantic architecture layer developed
What it enables- Robust decisions on the feasibility of strategic GenAI initiatives
- A long-term target picture prevents isolated technology and architecture decisions
- Prioritised immediate measures reduce risks in implementation
- A semantic layer concretely investigated as a future architecture foundation
- The question
How can relevant AI potential in complex finance processes be identified and prioritised without investing resources into unclear or economically unattractive use cases?
Our answerWe analysed finance processes down to activity level and identified suitable starting points for AI and automation. The expected efficiency potential was quantified, translated into concrete use cases and business cases and prioritised by impact and feasibility. This resulted in a robust roadmap for targeted implementation.
Three building blocks01 — POTENTIAL MAPAI levers made visible at activity level
Process activities analysed and suitable starting points for AI and automation identified
02 — BUSINESS CASESEfficiency potential quantified and made economically comparable
Expected effort reductions assessed and translated into robust business cases
03 — IMPLEMENTATION ROADMAPInvestments focused on the highest-value use cases
AI use cases assessed and prioritised by impact and feasibility
What it enables- A transparent potential map shows AI levers along the finance processes
- A prioritised roadmap focuses resources on value-creating AI use cases
- Quantified business cases create a robust basis for investment decisions
- Identified automation potential opens up concrete efficiency gains
- The question
How does corporate IT move from cost block to enabler: agile, product-oriented and tightly meshed with the business?
Our answerWe established an agile, product-oriented IT organisation, structured along value streams instead of functional silos. Through cross-departmental project teams, a scaled agile framework (SAFe) and modern collaboration tools, we addressed the requirements of a complex corporate IT and positioned IT as a central driver of the digital transformation.
Three building blocks01 — TARGET OPERATING MODELIT products instead of functional responsibilities
Structures and responsibilities consistently aligned to business requirements and IT products
02 — GOVERNANCE & ROLESClear decisions across organisational boundaries
Roles, decision rights and processes between business and IT bindingly defined
03 — DELIVERY MODELEnd-to-end ownership in cross-functional teams
An agile delivery model established for faster, high-quality and adaptable execution
What it enables- Clear end-to-end ownership accelerates decisions and operational execution
- Product-oriented teams reduce handovers between business and IT
- Business priorities steer resources, products and technological advancement
- A scalable operating model increases speed, quality and adaptability
From projects to products in an agile, cross-functional delivery and operations organisation.
- The question
How do you give employees one central working cockpit without having to replace the entire legacy world for many millions?
Our answerWe developed a central, cloud-based platform that virtualises the data from all legacy systems, complemented by a frontend for ML-based analyses. From the technical concept through to the architecture, we delivered every component in BizDevOps mode. The result is consistent information across system boundaries — information that enables data-driven decisions and end-to-end process control.
Three building blocks01 — DATA INTEGRATIONLegacy data harmonised and centrally available.
Data from different legacy systems integrated and linked, as one consistent foundation.
02 — CLOUD PLATFORMScalable architecture with an ML frontend.
Cloud-based platform for data integration and virtualisation, complemented by embedded ML analyses.
03 — BIZDEVOPSContinuous further development in operation.
From concept to architecture in BizDevOps mode, for efficient delivery of new features.
What it enables- Harmonisation and integration of legacy data into one central platform.
- Cloud-based architecture for scalability and flexibility.
- Embedded ML analyses for optimising the processes.
- BizDevOps approach for continuous improvement and efficient delivery of features.
- The question
How do fragmented analytics initiatives become one powerful organisation that responds quickly and reliably when acute field issues arise?
Our answerWe consolidated the distributed analytics initiatives into one integrated, agile organisation. Through a comprehensive data-flow analysis, we captured the existing use cases, harmonised objectives across all teams and set up cross-functional AI, analytics and data teams. Scalable prioritisation processes and a sustainable funding structure ensure that data is firmly anchored in the decision-making structures.
Three building blocks01 — DATA-FLOW ANALYSISInventory captured, objectives harmonised.
Existing analyses, dashboards and use cases recorded and the core questions unified across every team.
02 — ANALYTICS ORGANISATIONCross-functional, agile, fully funded.
Teams from engineering, production and after-sales defined, key roles staffed, funding secured.
03 — EMBEDDINGInsights firmly embedded in decision-making structures.
Scalable prioritisation processes that feed analytics results into decision-making for the long term.
What it enables- A high-performing, fully funded organisation for vehicle data analysis built on all relevant data sources.
- Cross-functional structure with experts from engineering, production and after-sales.
- Significant financial value from data-based product decisions and series production support.
- Faster, reliable answers to acute field issues instead of contradictory insights.
- The question
How does fragmented vehicle knowledge become usable company-wide when inconsistent data models require individual pipelines and complex integrations for every application?
Our answerA central ontology represents vehicle types, configurations, components and attributes in a unified semantic model. Existing data structures are harmonised in a knowledge graph and made accessible for domains, applications and AI through automated data pipelines, standardised interfaces and flexible queries.
Three building blocks01 — VEHICLE ONTOLOGYA semantic model for all vehicle product data
Vehicle types, configurations, components and attributes unambiguously defined and linked with one another
02 — KNOWLEDGE GRAPHFragmented data structures connected into vehicle knowledge
Existing models harmonised and their relationships represented in a shared knowledge architecture
03 — DATA PROVISIONProduct knowledge made accessible flexibly and reusably
Automated pipelines, standardised interfaces and flexible queries provided for different usage scenarios
What it enables- Unified vehicle knowledge replaces application-specific data preparation and integrations
- Standardised interfaces accelerate new applications and data products
- Consistent product data reduces contradictions between systems and domains
- Semantic access creates a robust basis for AI applications
- The question
How can quality deviations be detected early when relevant process data is spread across isolated systems and not semantically comparable?
Our answerAn ontology-based process and data model unifies the meaning of distributed quality data. Building on this, we developed a scalable cloud platform and a central user interface that integrates data across systems, makes quality processes transparent and enables AI-supported anomaly detection as well as future automation.
Three building blocks01 — ONTOLOGY & DATA MODELShared semantics for distributed quality data
Processes, data objects and relationships modelled across systems and unambiguously linked
02 — CLOUD PLATFORMA platform connects existing quality systems
Distributed process and quality data integrated in the cloud and made centrally accessible
03 — QUALITY MONITORINGDetect quality deviations centrally and early
A unified user interface creates transparency and supports AI-supported anomaly detection
What it enables- Unified access to distributed quality and process data
- Central process transparency improves well-founded decisions in quality management
- Earlier detection of quality deviations supports faster countermeasures
- A scalable data foundation enables further AI and automation cases
- The question
How does a historically grown ERP landscape, outdated and overly complex, become a modern, manageable foundation?
Our answerWe set up the ERP transition holistically: from analysing the business processes and aligning them with the corporate strategy through to evaluating different landscape scenarios. Taking users and data into account, we defined the approach, timeline and budget and drastically reduced the landscape of systems and interfaces.
Three building blocks01 — NEEDS ANALYSISProcesses, strategy and status quo compared.
Business processes analysed and mirrored against the corporate strategy and the current landscape.
02 — LANDSCAPE SCENARIOSScenarios, rated for fit with the target state.
Derived different landscape options and assessed their fit with the company's own goals.
03 — ROLLOUT PLANNINGApproach, timeline and budget, aligned to users and data.
Defined a project approach that takes user needs and data reality into account.
What it enables- A modern, integrated and manageable enterprise IT landscape.
- Systems and interfaces drastically reduced.
- An ERP landscape tailored precisely to needs and capabilities.
- A scalable, low-maintenance and cost-efficient foundation laid.
- The question
How does a DAX-listed group become truly data-driven when clear responsibilities, uniform processes and governance are missing?
Our answerWe built a scalable data governance & management organisation. Based on the core Data Mesh concept, we established group-wide data domains, defined domain boundaries and responsibilities in cross-functional workshops with business and IT, and anchored data-owner roles in the structure. In parallel, we standardised data management processes, documentation, approval and governance, and prepared the organisation for the new data architecture through enablement.
Three building blocks01 — DATA DOMAINSData Mesh as the core organisational element.
Group-wide domains: boundaries and responsibilities defined cross-functionally with business and IT.
02 — ROLES & OWNERSHIPData-owner roles, firmly anchored in the organisation.
Owners and supporting functions made concrete and integrated into the company structure.
03 — GOVERNANCE FRAMEWORKStandardised, system-supported data processes.
Documentation, approval and governance unified, operationalised smoothly through enablement.
What it enables- Tailor-made data management and governance framework implemented.
- Cross-functional data domains established group-wide as the central organisational element.
- System-supported processes for data documentation and approval introduced.
- Data-owner roles successfully anchored across the entire organisation.
- The question
How does the data potential in After Sales become a measurable economic contribution, rather than scattered individual ideas without prioritisation?
Our answerWe developed a specific data strategy that supports the long-term business-field strategy in After Sales. To do so, we assessed the strategic goals for how well data, analytics and AI can support them, derived concrete and measurable objectives from them, and defined suitable use cases for each objective. We then prioritised these by business value, described them functionally and technically, and translated them into an implementation plan with concrete measures.
Three building blocks01 — GOAL MAPPINGBusiness strategy examined for data potential.
Strategic goals assessed and translated into concrete, measurable data and AI objectives.
02 — USE-CASE PORTFOLIODefined, assessed, prioritised by business value.
Concrete use cases developed for each goal and ranked by business value and feasibility.
03 — IMPLEMENTATION PLANFrom identified needs to a concrete roadmap.
Measures defined and translated into a step-by-step implementation plan.
What it enables- Clear strategic objectives defined for the effective use of data and AI.
- Relevant use cases with high business value identified and prioritised.
- Concrete measures derived for implementing the data strategy.
- Implementation plan created for a step-by-step rollout.
- The question
How does an automotive manufacturer comply with the EU Data Act when transparency across vehicle usage data, clear responsibilities and processes are missing?
Our answerWe took over project management for the data-governance stream and implemented a multi-stage approach. First, we identified all relevant usage-data sources from vehicles and connected services, anchored data ownership at management level and secured budgets for maintenance and classification. In parallel, we assessed data flows in backend systems for EU Data Act relevance together with the responsible owners and the legal department, and developed a standardised metadata model that we integrated into the company-wide inventory approach.
Three building blocks01 — DATA INVENTORYUsage-data sources identified systematically.
Captured all relevant data from vehicles and connected services and assessed it for EU Data Act relevance.
02 — RESPONSIBILITIES & BUDGETOwnership anchored at management level.
Data ownership clearly assigned, budgets secured for continuous maintenance and classification.
03 — METADATA MODELStandardised and integrated company-wide.
Uniform documentation and categorisation, aligned with the central architecture and meeting compliance requirements.
What it enables- Developed a standardised metadata model to comply with the EU Data Act.
- Anchored clear responsibilities for data assessment and upkeep.
- Identified the relevant backend systems for connecting to outbound data-sharing technologies.
- Created a governance foundation that lowers regulatory risk and makes data-sharing processes efficient.
- The question
How does a company use data in AI applications compliantly when the EU AI Act demands transparency and traceability, but the roles and processes are missing?
Our answerFrom the legal requirements of the EU AI Act, we derived specific governance requirements for handling AI-relevant data. In cross-functional workshops with business, IT and legal departments, we defined roles and responsibilities, in particular for data use in AI applications. Building on that, we developed a target process for the documentation, assessment and approval of data, handed it over to the development team and interlocked it closely with the existing data-management processes.
Three building blocks01 — REQUIREMENTS DERIVATIONFrom legal text to concrete governance requirement.
Specific requirements for the handling of AI-relevant data formulated from the EU AI Act.
02 — ROLES & RESPONSIBILITIESDefined cross-functionally, from business to legal.
Clear responsibilities for data and its use in AI defined in workshops with business, IT and legal.
03 — TARGET PROCESSDocumentation, assessment and approval in the tooling.
Target process derived, handed over to development and interlocked with existing data-management processes.
What it enables- Governance framework established to satisfy the EU AI Act.
- Defined roles and processes for data approval and data use.
- Requirements derived for implementing the target process in the central governance tooling.
- The new processes integrated into existing data-management structures.
- The question
How do data stay usable for business and AI when unclear responsibilities, missing documentation and new regulatory requirements create significant compliance risks?
Our answerTogether with business, IT and legal, we translated regulatory requirements into operationally applicable governance principles. Roles and responsibilities were bindingly defined and integrated into an end-to-end process for data inventory, review and approval. This anchors compliance traceably without unnecessarily slowing down the use of data.
Three building blocks01 — REGULATORY FRAMEWORKRegulatory requirements made operationally applicable
Requirements of the EU Data Act and EU AI Act translated into concrete governance principles
02 — ROLES & RESPONSIBILITYClear ownership for review and data usage
Responsibilities and decision paths bindingly defined together with business, IT and legal
03 — GOVERNANCE PROCESSCompliance integrated into data usage
An end-to-end process for inventory, review, approval and documentation of data established
What it enables- Regulatory requirements translated into operationally usable processes
- Integrated compliance processes reduce risks and manual coordination effort
- Clear responsibilities accelerate data review and approval across the company
- A usable data inventory creates transparency and reliable auditability
- The question
How can a business-critical legacy system be fundamentally modernised without endangering central functions, overlooking dependencies or taking on uncontrollable migration risks?
Our answerStarting from the existing value streams and core functions, we developed a cloud-native and AI-ready target architecture. Technical components were consistently aligned to the business logic and transferred into a concrete migration plan that transparently brings together implementation steps, dependencies and required resources.
Three building blocks01 — VALUE-STREAM-BASED SYSTEM MAPBusiness logic as the basis for modernisation
Value streams, core functions and dependencies of the existing system mapped in a structured way
02 — TARGET ARCHITECTURECloud-native architecture along the value streams
Business functions and technical components connected in a scalable target architecture
03 — MIGRATIONA controlled path from legacy to target state
Migration steps, dependencies and resources brought together in a realistic implementation plan
What it enables- A cloud-native target architecture creates scalability and long-term technological flexibility
- Integrated AI capabilities enable future intelligent services
- A value-stream-oriented system structure reduces complexity and eases further development
- A concrete migration plan creates planning certainty for resources and implementation
No engagements match this selection.












Let us talk about your objectives.
In 25 minutes you will understand whether we can help. No slides. No demo.
HubSpot Meetings
Marketing cookies are required to load the booking widget.
Loading the widget transfers data to HubSpot Inc. (USA). The transfer relies on EU Standard Contractual Clauses; access by US authorities cannot be ruled out.