Services
Legacy Risk Assessment
Problem
You know that your system landscape carries risks. But you don't know which ones are critical and which you can ignore. Your teams are busy with day-to-day operations and nobody has two weeks to thoroughly investigate a legacy system.
Approach
I analyse your existing systems — not the documentation, but the systems themselves. I test interfaces, check dependencies, and look for the errors that others miss because they trust the documentation rather than the system.
Result
A report with clear statements: This works. This doesn't. This will be expensive. This is a showstopper. Written so that you can continue working without me.
Timeframe
One to two weeks, depending on the complexity of the system landscape.
AI Readiness Assessment
Problem
You want to use AI, but your data sits in systems not built for it. Confluence, SAP, Outlook archives, a DMS from 2008 — and somewhere a Lotus Notes archive that nobody wants to touch. The question is not whether AI works. The question is whether your data landscape supports it.
Approach
I check which of your systems are AI-capable, which interfaces exist, and where the gaps are. Not theoretically, but through concrete tests on the relevant systems.
Result
An assessment of your data landscape: what is accessible, what is not, and what needs to happen to prevent an AI project from failing due to infrastructure. Including a realistic effort estimate for the next steps.
Timeframe
Two to three weeks.
Interface POC
Problem
You have a modernisation strategy — on paper. But nobody knows whether the critical interface between the old and new system actually works. Before you put a team on it, you need an answer.
Approach
I build a proof of concept for the most critical interface. Not as a prototype, but as a real test under real conditions. If it works, you have the foundation for the implementation. If not, you know before it gets expensive.
Result
A working interface or a documented explanation of why it doesn't work as envisioned — and what would be needed instead.
Timeframe
Two to four weeks, depending on the complexity of the involved systems.
Architecture & Implementation
Problem
The analysis is done, the path is clear. Now someone needs to design and implement the architecture — someone who understands the old systems and can integrate the new components.
Approach
I design the target architecture and implement it. From interface design through data integration to production operation. In regulated environments with the corresponding requirements for compliance, availability, and security.
Result
A production integration that works — not just in testing, but under load and in daily operation.
Timeframe
Project-dependent. Typically as a follow-up to an assessment or POC.
Not sure which service fits? Write to me about what's on your agenda. I'll tell you honestly whether and how I can help.