Skip to content

Working together

Start with a real task.

AI raises technical and business questions at the same time. We help you bring them together and take a useful next step. The starting point is your work, your data and the people who will use the result.

Approach

Technology and organisation

Implementation the organisation can carry.

An application only stays useful when responsibilities, review and operation are clear. We build the technical parts and, alongside them, the working model around them, so that your team can run and improve what we build together.

Close-up of a fingertip against a deep blue background.

Where we help

Four kinds of work, one aim.

  • You may already have plenty of ideas, or you may still be working out where AI could help. With the people who know the process and are responsible for it, we narrow the task down. We weigh expected value, available data, technical feasibility and the effort of introducing and running an application, so that you can decide what to pursue next.

  • An application needs reliable access to the knowledge it works with. We establish what data exists, how well it is maintained and who may use it, then connect the systems involved. The architecture follows your IT and your requirements for data flows, access and where things run, from a cloud service to a model on your own infrastructure.

  • A focused prototype tests assumptions on real tasks, including the cases where the approach can fail. If it proves useful, we develop it further and integrate it into the workflow, with interfaces, permissions, results people can check and a clear plan for operation. Established software components let us concentrate on what is specific to your task.

  • AI changes how people research, develop and decide. Through talks, workshops and work on concrete tasks we explain what the tools can do, where their limits are and how to judge their output. Leadership, domain specialists and IT need different answers; we bring those perspectives together and leave approaches your team can keep using.

The aim: a real task that works better in everyday use, carried by your own team.

How an engagement runs

Step by step, validated and adjusted as we go.

  1. We frame an important task with leadership, domain specialists and the people who will use the result. We record where things stand today and agree what success means and where the boundaries are.

    OwnerProblemSuccessBoundariesUnderstand

    A named owner, a defined problem, success measures and explicit boundaries.

    Understand

  2. We connect the knowledge and data the task needs and clarify the workflow, access and decisions, so that people can find and check what they rely on.

    KnowledgeDataWorkflowAccessMap

    People can locate and check the information the task requires.

    Map

  3. We build a limited application and test it against real work, including the cases where it fails. If it proves useful, we integrate it with responsibilities, review and operation.

    TestCompareLimitsOperationActivate

    A comparison with the starting point, acceptable quality, known limitations and sustained use.

    Activate

  4. We teach, document and hand over what your team needs to run and improve the system, and reuse what works where it fits.

    TeachDocumentHand overReuseEvolve

    Your team can maintain the approach and make informed changes. The next improvement comes easier.

    Evolve

Every step can end with a decision to stop or change course. Sometimes the useful result is a decision against AI.

Control

Governance is part of the design.

We work through these questions for your situation and plan export, handover and replacement from the start. For us, European self-determination means having the capability and the choices to act, not just picking a provider with a European address.

  • Where data flows.
  • Who can access it.
  • How the system operates.
  • Which dependencies matter.

Starting points

Where engagements usually begin.

  • 01

    An innovation workshop.

    Leadership and teams want a shared view of what AI can do for them. In a workshop we work on your own tasks and data, sort the ideas by value and feasibility and leave with a short list of what to try first.

  • 02

    From a vibe-coded prototype to production.

    Someone has built something useful with AI tools in a few days. We review it, keep what works and make it ready for real use: security, permissions, integration, tests and operation.

  • 03

    A need for sovereign AI.

    Your data, your customers or the rules you work under require AI that runs under your control. We work out which models and infrastructure fit, in your own environment or with European providers, and what that means for cost and quality.

  • 04

    A prototype for leadership.

    Before a larger decision, the board or management wants to see it work. In a short, fixed time frame we build a focused prototype on a real task, so that the decision rests on evidence rather than slides.

Typical situations to start from, not descriptions of completed client work.

How we work with you

Jodok and a team of specialists

Close to the work, with Jodok in the room.

You work directly with Jodok and specialists who fit the task, without layers in between. Scope, responsibilities and handover are agreed for each engagement.

Close-up of an amber eye in low, warm light.

What is it about? What is on your mind?

No complete briefing needed. A few keywords are enough to start.