For us, artificial intelligence is not an end in itself, but a tool. We integrate AI functionalities where they usefully complement existing industrial software - for example in the form of assistant or agent functions that relieve users, process information or support decisions. At the same time, we make sure that the architecture, interfaces and data models remain resilient even without AI and that AI components can be integrated or removed in a controlled manner.

Yes, if it makes technical sense, we design and integrate AI components directly into the solution - for example as a service in the existing architecture, as a cloud or edge component or embedded in existing workflows. Transparency is important to us: our customers understand which data is used, how decisions are made and how AI components can be operated and maintained in the long term.

Yes, we use AI tools specifically to make development processes more efficient and focused - for example, for small-scale code generation, analyses, tests or documentation. Architecture decisions, domain understanding and responsibility for the solution remain with the team. AI is a productivity booster for us, but it does not replace our architecture, industry and domain expertise.

It all starts with requirements and the existing environment. In joint workshops, we define goals, use cases and framework conditions. Building on this, we develop the architecture and technology stack and, if required, implement a prototype or MVP. This is followed by implementation, testing and commissioning. After the go-live, we support the operation, monitoring and continuous development of the solution.

We work predominantly agile, in close coordination with product management and development on the customer side. Depending on the project context, we combine agile methods with clear milestones and decision points. Transparency is important to us: our customers can always see where the project stands and what decisions need to be made.

Yes, we often work as an extension or sparring partner for internal development teams. For example, we take on the architecture, device integration, selected components or prototypes, while the customer team is responsible for other parts of the implementation. The aim is always to share know-how and create solutions that can also be understood and further developed by the customer's team.

The easiest way is a non-binding discussion in which we look at the requirements, environment and goals together. On this basis, we provide an initial assessment of feasibility, a sensible approach and possible cooperation. You decide whether this becomes a project - we provide clarity first.

A blanket answer here would be dishonest.

Projects vary greatly in scope, complexity and environment. What we do offer, however, is a clear framework: In an initial meeting, we clarify objectives, requirements and boundary conditions. Based on this, you will receive a transparent cost estimate within a few working days.

Depending on the project context, billing is based on fixed-price sprints or an agreed daily rate - always with clear scope management and no hidden costs. The decisive factor for us is that the approach and model suit your project and your planning horizon.

This depends on the scope and the initial situation. As a rule, the first step is a joint discussion for classification, followed by a rough cost and procedure outline. Smaller workshops or evaluations can usually start within a few weeks, larger projects after joint planning and coordination of resources.