AI for the common good

Artificial intelligence is rarely the answer and sometimes the wrong question. I help you tell the difference beforehand rather than afterwards.

The question first, the technology second

Most enquiries about artificial intelligence start from a technique and then look for a problem to attach it to. I turn that around: what is meant to get better, for whom, and how would anyone notice that it had? Once that is settled, we can check whether an AI method is the right means, and often enough it is not.

That check is cheaper than a project that runs aground on the data situation a year in.

My contribution

I explain the basics as far as you need them to have a say in the decision: what machine learning does, where its results come from, where its errors come from. That is all it takes, because you are meant to be able to decide, not to build it yourself.

For designing an application I use cards rather than code: the AI Toolkit lets a team play through the idea, the data sources, the interaction and the learning objective without anyone needing to program. What comes out is a concept prototype solid enough for a funding application or a tender.

Ethics is a design question

Fairness, accountability and data protection cannot be checked at the end like spelling. They are decided where it is settled which data gets used, who sees the results and who is allowed to object. That is why I raise these questions early, not at acceptance.

Boundaries

I do not train models and I do not build infrastructure for running them. Once it is settled what should be built and only the implementation is left, you need a development team, not me. I am useful in the phase before that, when the decisions are made.

What you get

  • A realistic estimate

    What a method can do, what it costs and where it fails.

  • Shaping without prior knowledge

    Tools that let departments take part in the decision.

  • Ethics from the start

    Fairness, traceability and data protection as design questions, not a checklist.

  • A solid basis

    A concept prototype fit for a proposal or a tender.

Process

  1. 1

    Understand

    Fundamentals, as far as needed to take part in deciding.

  2. 2

    Examine

    Data situation, law, benefit, alternatives without AI.

  3. 3

    Design

    Develop the application idea together and make it robust.

  4. 4

    Situate

    Next step, effort, responsibility.

Cost

Billed by person-day, as a senior consultant. I will tell you the day rate in our first conversation, together with an estimate of how many days your project needs. Both binding, before you decide.

Where the scope can be drawn clearly, I also offer a fixed price. I will tell you which of the two comes out cheaper.

Related services

Try it out before deciding

In the AI exploration space we work with cards instead of code. In a single day, you get a tangible sense of what a method could do for you.

To education →

AI on the table but no clarity yet?

Let us talk about your project.

Call +49 228 629 380 60 I can be reached on working days. If I cannot pick up, I will call you back. Book appointment Take a free slot in the calendar A short conversation clears up a lot.