↰ Home // Legacy code documentation · Part of Intentron

Your most experienced colleague is retiring. Their knowledge doesn’t have to go with them.

I make legacy software understandable – for your team and for the AI tools that are meant to keep working with it. The basis is a proven standard method that I tailor to your codebase. Every statement in the documentation carries a source reference in the code.

Curated AI image composition by Sanne Jerxsen: a glass puzzle whose missing piece reveals an owl – an image for knowledge about grown software that lives in a single head
TÜV-certified AI consultant
Every statement backed by a source reference
Fully on your own infrastructure if you wish
Assessment fee credited if you commission the work
The starting point

Legacy systems: when software grows faster than its documentation

Curated AI image composition by Sanne Jerxsen: a crookedly stacked tower of glass slabs with an owl perched on it – an image for software that has grown faster than its documentation

Legacy software – software that has been in use for many years – carries knowledge that is written down nowhere. As long as the right people are in the building, hardly anyone notices.

One person as the bottleneck

Only one person still understands a core module. Every major change waits for them – and their retirement or departure is in sight.

Onboarding takes months

New developers take a long time before they can make changes safely. The time to bring them up to speed is exactly what the experienced people lack.

Code nobody touches any more

A small fix in the wrong place once brought down features at a client’s site. Since then, some things are better left as they are.

The benefit

What changes once your codebase is documented

Module pages and architecture overview

The knowledge belongs to the company

For every part of the software it is clear what it does, what it depends on and where it sits in the code. A change of staff is no longer a risk to further development.

Pre-filtered question catalogue

Your knowledge holders get relief

In conversation, they answer targeted questions that the analysis has selected in advance. They don’t have to write anything down.

Every statement must be backed up

Decisions on a proven basis

Every statement points to a file and line. Anything that cannot be backed up appears in the documentation as an open question – nothing is guessed.

Machine-readable format

Ready for AI-assisted development

With the documentation, AI tools find the right place in the code. That makes your codebase the foundation for working with Intentron.

What you have in hand at the end

  • A description of every module with source references
  • Architecture diagrams of the overall structure
  • A question catalogue with your knowledge holders’ answers
  • A list of open points and anomalies in the code
  • Everything in Markdown – readable in a wiki, in the browser or directly in the repository
The process

From discovery call to documented software

// 4 steps

The method is proven and standardised. What gets adapted is what makes every piece of software different: programming languages, build environment and the format in which your team wants to use the documentation.

01
// 30 minutes · free of charge

Discovery call

We establish whether the approach fits your situation and who holds the knowledge in your company.

02
// 2 hours · €1,500

Assessment

A structured conversation with the people responsible, guided by a proven questionnaire. No access to your code is needed for this.

03
// by quotation

Tailoring

The standard method is tailored to your software. Your IT department checks the tools before they are used.

04
// a few days to weeks

Documentation

The documentation is built up over several analysis runs. In parallel, your knowledge holders answer the open questions.

Assessment: 2 hours, €1,500 plus VAT

You receive a written overview of your challenges and a concrete quotation for the documentation phase. If you commission the documentation phase, I credit the €1,500 in full.

From practice

A codebase that has grown over decades

A manufacturer with firmware that has grown over many years and across numerous repositories. The most experienced developer is about to retire, and much of the knowledge lies with him.

The analysis first separated the company’s own code from third-party and generated code – what remained was a fraction of the total. Over several runs, it produced documented descriptions of the modules and a question catalogue that the knowledge holder answers in conversation. Along the way, bugs in the code came to light that nobody had noticed until then.

Curated AI image composition by Sanne Jerxsen: a tangle of cables grown over the years that leads into a small circuit board – an image for firmware whose knowledge first has to be mapped
Security

Your code stays where it is

Curated AI image composition by Sanne Jerxsen: a pinstripe suit woven from lines of code hangs in your own wardrobe, guarded by an owl – an image for code that stays in-house

If you wish, the entire analysis runs on your own infrastructure with an on-premises language model. I only use cloud models with your written sign-off and on the basis of a data processing agreement.

The tools read your code but never change it. Your ongoing development continues undisturbed throughout the documentation phase.

Is this right for you?

When documentation pays off

A good time

  • Your software has been in use for many years and is still being developed.
  • Important knowledge lies with a few people.
  • A generational change in the team is coming up.
  • You want to use AI in development and need a reliable foundation for it.

Probably not needed

  • The codebase is small and already well documented.
  • The software will be replaced in the foreseeable future.
  • You are looking for a quick code review of a single change.
Stefan Weimar as a curated AI image composition by Sanne Jerxsen – a visual for AI consulting and compliance at PRODOC Digital
Your contact

Stefan Weimar

I am managing director of PRODOC Digital GmbH and a TÜV-certified AI consultant. My focus is safeguarding company knowledge with on-premises AI, especially in regulated industries.

Within the Intentron network, I am responsible for opening up legacy code: from the assessment and the tailoring of the method to the finished documentation. Your developers remain the subject-matter authority throughout.

Frequently asked questions

// FAQ

No. The assessment is a conversation with the people responsible. Code is only read in during the documentation phase, and even then read-only.

That depends on the size and structure of the software. For a codebase with several thousand files of your own, expect several analysis runs over a few days. You receive a reliable estimate with the quotation after the assessment.

The standard method is adapted for each client to the languages and build environment in use. The assessment shows which adaptation your codebase needs.

If you wish, no code leaves your premises: the analysis then runs with an on-premises language model on your infrastructure. Cloud models are only used with your written sign-off.

Every statement must have a source reference in the code. Anything that cannot be backed up is marked as an open question and clarified with your knowledge holders. That way you never get documentation that sounds convincing but is wrong.

The assessment costs €1,500 plus VAT. You then receive a fixed-price quotation for the documentation phase; if you commission it, the assessment fee is credited in full.

// Discovery call · 30 min · free of charge

How much knowledge is in your code – and with whom?

In a free discovery call, we establish whether the assessment is worthwhile for you.

You will find Intentron’s full offering at intentron.ai.

You might also be interested in