Company

The technology has changed. The task never has.

aiio GmbH, Magdeburg — grown out of a technology holding that has existed since 2002. SharePoint documentation, cloud, AI agents: the means have changed completely several times over that period, the question behind them not once.

What has changed — and what has not.

It began with process documentation on SharePoint, for industry and the public sector. Both have stayed: the sectors, and the question of how an organization gets at its own knowledge. What changed is what you answer it with.

  1. 2002The root

    Lintra GmbH is founded in Magdeburg as a technology holding. Several companies come out of it — one of them later becomes aiio. The subject is the same from the start: helping organizations know their own workflows.

  2. 2007Quam

    A company of its own, entered at the Amtsgericht Stendal under HRB 6552. With Quam, a management system on a SharePoint basis comes into being: processes are documented and become auditable. The first customers are industry and the public sector — the same organizations that today face transformation undertakings.

  3. 2014Best in Cloud

    The sister company LINTRA Solutions GmbH wins the Computerwoche Best in Cloud award in the SaaS category — with an Office 365 platform for the Malteser Hilfsdienst. At that point the holding is a Microsoft Gold competence partner. The move into the cloud happens in-house, not as a latecomer.

  4. 2020The rebuild

    Development of a cloud-native, AI-supported platform begins. Not as an extension of Quam, but alongside it: what is meant to be readable by systems cannot be retrofitted into a tool built for human readers.

  5. 2022aiio

    In March 2022, LINTRA plus GmbH becomes aiio GmbH. Register entry, location and team stay. The name stands for the direction: documentation for people becomes an organization that systems can read too.

  6. 2024Series A

    Institutional funding round, eight-figure valuation. Relevant to anyone whose undertaking runs over several years: the company does not hang on the next order, and the tools do not have to pay off in the short term.

  7. TodayReady for AI

    AI agents put the same question as SharePoint did in 2007 and the cloud in 2014: what is this organization actually working on? Except that this time the answer has to be machine-readable.

What two decades have taught.

What we learned in that time sits in the tools today — and explains why some things deliberately do not belong in them. Every one of these lessons cost us projects first.

No undertaking fails at the modeling.It fails because nobody knew how things ran beforehand. In two decades we have not once seen that reversed — and still, almost every project opens with the question of which notation standard to use.
Whatever has to be collected on top goes stale.We have seen enough documentation that was correct on the day it was signed off and that nobody opened again six months later. Since then we read the holdings instead of rebuilding them.
The gap is the more valuable information.A picture that adds up everywhere has been smoothed over. The places where two sources contradict each other are almost always the places where an undertaking later gets stuck.
Anyone who needs consulting to use their own tool has the wrong tool.That is the most uncomfortable lesson, because it costs revenue. We stay close through the first weeks — after that it should run without us, and if it does not, that is our fault.
Systems are the harder readers.What a person can still infer from an incomplete diagram, an agent cannot. That is why the machine-readable form is the base form and not the export — that order was the real decision of 2020.
The organization belongs to the organization.We have seen often enough how a change of provider foundered on the data format. Operation on servers in the EU, results in open formats: whoever leaves takes the picture of their organization with them.

Who runs the company.

Four managing directors, all four operational, all four a long time in this market. They have seen the problems at issue here from close up — at large corporations, in mid-sized companies and in the public sector — and have spent recent years building a tool against them.

Dr. Christian Graup
Dr. Christian Graup
Management · product and direction

Decides what gets built and in what order — and what does not. Was accountable for the substance of the move from Quam to aiio. Anyone wanting to know why the tool deliberately does not do certain things gets the reasoning from him; the long version sits under Vision.

Knut Köchli
Knut Köchli
Management · operations and delivery

Accountable for rollout and operation: that a project runs in weeks rather than quarters, and that afterwards someone is reachable who knows the installation. When delivery goes wrong, he is the escalation level — not a ticket system.

Jobst von Heintze
Jobst von Heintze
Management · market and communications

Accountable for how aiio is explained to the outside — and for that explanation holding up against what the tool actually does. Point of contact for press, analysts and associations.

Lars Bendler
Lars Bendler
Management · partners and ecosystem

Builds the network of consultancies and integrators. For an undertaking that means: whoever accompanies the transformation does not have to be aiio — but they know the tool and do not have to start from scratch.

Who advises the company.

For the questions where software fails in audited environments, people sit at the table who are better at it than we are — from research, from enterprise sales, from the capital markets and from leadership work. They advise on the decisions touching their field before those decisions are taken.

Prof. Dr. Sebastian Schlesinger
Prof. Dr. Sebastian Schlesinger
HWR Berlin · information security, embedded systems

Examines the technical foundations: security architecture, embedded systems and the requirements that regulated environments place on software before it may be operated there. Previously at Zalando and Deutsche Bank.

Edmund Frey
Edmund Frey
Edventure GmbH · B2B software, enterprise markets

Brings go-to-market experience from enterprise software and B2B SaaS — what large corporations actually examine when buying software, and where new categories in this market regularly fail. Previously at Adobe, SAP and Spryker.

Oliver Sauer
Oliver Sauer
Palladio Partners · M&A, enterprise value

Sees the company from the investor and M&A perspective: what an organization is worth over the long term, which capabilities carry that value — and which only look as though they do. Previously at GETEC, MVV Energie and Rothschild.

René Leitgen
René Leitgen
Advisory board · resilience, leadership under change

Works on the question of how organizations stay able to act under permanent change, uncertainty and growing complexity — and what leadership has to deliver for that.

Certified, awarded, funded.

Certified to ISO/IEC 27001, twice running the CHIP test winner in the BPM comparison, institutionally funded — and the AI platform developed in-house since 2020, not bought in. Set out here with numbers and dates, so that a review does not have to ask first.

aiio GmbH

Klausenerstraße 10a, 39112 Magdeburg. Amtsgericht Stendal, HRB 6552. VAT ID DE 254461500.

CHIP Leading Software

Overall winner in the BPM comparison in 2024 and 2025, plus the highest recommendation rate. Survey among more than 2,000 software users.

ISO/IEC 27001

Certificate 02260301-01, valid until 4 June 2029. Scope and certificate are published.

Series A funded

Institutionally funded since 2024, eight-figure valuation — relevant when an undertaking has to hold for years.

Everything under one roof

Development, operation and support at one location in Magdeburg, more than thirty people. Not outsourced, not offshore, no intermediate layer between a question and support.

KI-Bundesverband

Member. Taking part in the regulatory debate rather than waiting it out.

Data processing, sub-processors and reporting channels: to the Trust Center →

Let us talk.

A conversation, not a pitch: twenty minutes of listening to what is coming up — and then saying whether one of the tools helps with it or not. That too is a lesson from two decades.