Integration, automation, training
Consulting and implementation for integration and automation work, service desk systems and software architecture — and training that goes deep.
Business logic in the script. Rate limits, retries and logging are handled by the runtime.
Services
Consulting and implementation wherever systems need to talk to each other reliably — from architecture through to day-to-day operation.
Software that follows the customer's processes — not the other way round.
Enterprise systems across their whole lifetime.
Service desk systems are the backbone for mastering the complexity of today's systems.
Augmented development
Hands-on and in depth, remote or on site — built around your actual project rather than textbook examples.
Let's set up a meeting to walk through how I think about software, using a9script as the example — and to see whether these approaches fit your project.
As a commission, by the hour or at a fixed price, or directly within your team. AI as a tool brings more pace without giving ground on quality.
Approach
Programming languages have made software simpler time and again: higher-level languages instead of machine code, a garbage collector instead of managing memory by hand. For distributed systems that leap never came. Foreign APIs, rate limits, pagination, retries and state across system boundaries get built by hand again in every project.
The known ways out only move the problem. Frameworks such as Spring are a system of their own in operation, one that has to be mastered. Serverless demands deep knowledge of the particular cloud provider — even a look at the log is hard work. Low-code and iPaaS platforms lead, on harder problems, straight into a full programming language with nothing in between, often without a sandbox and without a versioned path to production. The effort has long since stopped being about the domain and moved to everything around it.
That is what a9script was built for: business logic as an easy-to-maintain script — the complexity optimised in the runtime. That makes integration work simpler, especially with the new possibilities AI brings.
“If I have to choose a system where the humans can read it and a system where the humans can't, I'd much rather have a system where the humans can read and understand about it.”
AI is changing how software gets written — code has become cheap, quality has not! An AI produces thousands of lines, and the actual business logic is hidden somewhere in between. Hard to maintain, hard to adapt. The shorter the code, the better.
With a9script, the company's own AI writes the script (via CLI or MCP with skills). Credentials stay out of its reach, and trade secrets do not end up in a platform AI that runs for all tenants.
In an ever faster world you need code that is easy to understand, logging that is readable, access that is easy to test, a language that humans and AI understand equally well — and a runtime platform that takes care of everything around it.
At build time the AI writes. At run time it has nothing to decide: business logic has to be deterministic. The same input must produce the same decision — today, tomorrow, and in an audit two years from now. AI systems are not: they are probabilistic. That is their strength, and precisely why they should not be the ones executing business rules.
The line belongs in the right place. AI may interpret, suggest and make sense of unstructured input. Execution belongs to deterministic code — repeatable, verifiable, traceable.
Causality is non-negotiable.
The tool for it
The automation and integration middleware this thinking went into: programs hold the business logic, the platform handles everything that makes modern cloud systems complicated. What that looks like in detail:
“I don't like that phrase ‘vibe coding’. I call it augmented development because for me it feels like an exoskeleton. I'm the programmer, I'm still programming, but I can pick up stuff that I never would have been able to pick up without this assistance.”
About
Contact
The fastest start is a few sentences about the project, the timeframe, and where it currently hurts. Then the first conversation can already produce something useful.
Or directly: office@lengauer.biz