The questions everyone asks.
Honest answers to the questions from our initial consultations — including the ones where the answer is "it depends" or "no".
GETTING STARTED / 01
Getting started
FAQ-01 We want to adopt AI — but where do we start?
Not with the tool, but with the foundation: what are you allowed to do (GDPR, EU AI Act), what do you need (policies, responsibilities), where is it worth it (process analysis)? That is exactly what stage 1 of our approach settles. Our readiness check gives you a first indication in five minutes — free, with no data transferred.
FAQ-02 Is AI even worth it for us?
Honest answer: not everywhere. AI carries where processes are digital, recurring and data-rich — in engineering, for instance, reviews, test case creation and pipelines. Where that is not the case, we tell you in the initial consultation, before you spend money. Our business model is the long-term support of working systems, not the quick project.
FAQ-03 How long until we are productive?
The governance foundation takes weeks, not months. A bounded pilot in the development process is typically productive in four to eight weeks. Company-wide expansion is then a question of prioritisation and your pace — we work in stages so every step delivers value on its own.
FAQ-04 What does it cost?
The initial consultation costs you nothing but an hour. After that, the scope depends on your goal: a readiness analysis is a manageable fixed-price package, an engineering pilot a project of weeks, a company-wide rollout a programme. You receive a concrete offer with a clear scope before every stage — and can stop after any of them.
LEGAL / 02
Legal & standards
FAQ-05 What does the EU AI Act actually require from us?
That depends on which AI you use and what for. The EU AI Act sorts applications into risk categories — from minimal (hardly any obligations) to high (extensive documentation, transparency and control duties), with staged deadlines and substantial fines. The first step is always an inventory and classification of your AI applications — after that you know exactly which obligations apply to you.
FAQ-06 Do we really need ISO 42001 certification?
Not necessarily the certificate — but the principles behind it. An AI management system to ISO/IEC 42001 answers exactly the questions AI adoptions fail on: responsibility, risk, approval, monitoring. Whether you pursue the certificate is decided by market requirements — tenders, or customers from regulated industries. We build your AIMS so that certification is reachable at any time.
FAQ-07 Who is liable when the AI makes a mistake?
Your company — which is why this question is the core of all governance. The answer consists of clear responsibilities (who approves, who checks), human control at the critical points, and documented decision paths. That is exactly what we establish in stage 1, before AI enters productive processes.
FAQ-08 How do we involve the works council and the workforce?
Early and honestly. AI adoption touches co-determination rights and raises worries — neither can be ignored away. What works: works council at the table from the concept phase, a clear message (AI takes over routine, not jobs), training for everyone affected, and a pilot phase whose results are shared openly. We support this path — drawing on the adoption in our own, fully AI-led company and on our work in the engineering environments of our clients.
TECHNOLOGY / 03
Technology & data protection
FAQ-09 Does our data leave the house?
Only if you decide so — and never uncontrolled. Our principle is self-hosted first: sensitive data, engineering knowledge and customer data stay on your infrastructure or in German data centres under your contract. Where cloud AI is the better choice, with a sound legal basis, a data processing agreement, and no training of third-party models with your data.
FAQ-10 What does "self-hosted" mean — and do we need it?
Self-hosted means: the AI models run on servers you control — instead of at a US provider. You do not need it everywhere: for uncritical tasks, cloud AI is often more economical. For trade secrets, development data and personal data, control over the infrastructure is the cleanest path. We build both and recommend per use case — not per ideology.
FAQ-11 Do we have to switch our toolchain?
No — that is the point. We integrate AI into the tools your teams use today: Polarion, Codebeamer, Jira, Git, Jenkins, GitLab, Confluence, Artifactory — and many more, from DOORS through SonarQube to VectorCAST. No two companies run the same toolchain; the integration follows your process, not the other way round. A parallel system nobody looks into is the surest way to bury an AI adoption.
FAQ-12 What if the AI does something unforeseen?
Nothing is worse than an AI agent doing unforeseen things — so we do not build any. Our AI processes run deterministically: an unambiguous task, a defined scope, defined gates and clear handovers to humans. No system that finds its own tasks. As engineers we treat it like any machine: behaviour you cannot predict is not a feature, it is a defect.
FAQ-13 Our people already use AI privately — is that a problem?
Yes, but a solvable one. When AI is used uncontrolled through private accounts (shadow AI), design knowledge or customer data quickly flow into third-party models — bypassing IT, data protection and governance. The answer is not a ban but order: we bring the usage into the company, with approved tools, clear guardrails and — where needed — self-hosted. That turns shadow AI into a controlled, productive use you can be accountable for.
FAQ-14 What does our IT need to bring to the table?
Less than many fear — and we clarify it upfront. We work in direct exchange with your IT from the start: we embed the solution cleanly into your permissions, data-protection and infrastructure landscape and surface constraints — compute, network, access rights — before they become a bottleneck. This holistic approach, from every stakeholder down to the infrastructure, is exactly what AI governance means in practice.
ENGINEERING / 04
Engineering & process
FAQ-20 Where in the development process can AI be used?
AI can support the entire development and verification process: requirements, system design, architecture, module design, implementation, unit tests, integration test, system test and acceptance. The technical depth changes by phase: from management-level risk and evidence to concrete work on code, test data, interfaces and pipeline gates.
FAQ-21 Do executives, engineering leads and teams need different AI views?
Yes. Everyone sees the same process map, but not the same level of detail. Executives and compliance need risk, cost, obligations and approvals. Engineering and QA leads need traceability, gates, dependencies and test strategy. Developers and testers need concrete artifacts, prompts, reviews, test cases and automation in their toolchain.
WORKING TOGETHER / 05
Working together
FAQ-15 Do you only consult, or do you implement too?
Both — that is our core promise. We analyse, design, implement and support from one team. You do not get a slide deck with recommendations, you get running systems with documented processes. And we stay accountable for as long as they run.
FAQ-16 How quickly can our teams really use AI?
Faster than most expect — because nobody starts from zero. We bring a structured approach and the experience from our own AI-led operation directly to the table and pick up every team where it stands: development, test, project management, leadership and IT, with training and best-practice playbooks. That way the value comes early, instead of after months of self-teaching. The goal is a team that masters AI as a matter of course — not a handful of tools nobody operates properly.
FAQ-17 What happens after go-live?
That is when the most important part begins. AI systems need monitoring, care and further development — models age, regulation changes, your processes grow. Our support covers operations, audit support, further development and training, with one fixed contact person. Service comes first with us.
FAQ-18 Are you not too small for us?
A fair question — and our answer is built, not claimed: everything we deliver is documented, traceable and operable without us. Your team is trained, not made dependent. You stay capable of acting at all times — with us that is a design criterion, not a concession. And the flip side of size: with us, the certified AI officer who built your system talks to you — not the junior consultant the big firm sends after the contract is signed.
FAQ-19 Do you only work in Munich?
Our focus is the greater Munich area — we are convinced process work needs presence, especially at the start. For companies beyond that we find a model of on-site visits and remote work, depending on the project. Asking costs nothing.
YOUR QUESTION / 06
Your question was not here?
Then ask it directly — we answer honestly, even if the answer is "we are the wrong people for that".