Understand before changing
No proposal is made before the current system, its data and its deployment path have been read directly.
/aboutThe company
An engineering
practice, plainly
described
ASO Immobilienservice GmbH provides information technology services: building software, running infrastructure, connecting systems and making data usable. This page explains how we work, without claims we cannot support.
01Overview
What the company does
We are a technical services company. Our work spans custom application development, web platforms, cloud architecture, systems integration, data engineering, interface design, testing and long-term maintenance. Engagements range from a single well-defined piece of engineering to continuous responsibility for a system in daily use.
The legal name of the company is ASO Immobilienservice GmbH. Its activity is information technology services, and every capability described on this site is one we perform ourselves. Where a project needs expertise outside that range, we say so rather than stretch to cover it.
We publish no client names, project statistics or awards. Anything of that kind would have to be verifiable, and we prefer a description of method that a prospective client can evaluate directly.
02Mission and principles
Software that can keep changing
Our purpose is to leave organisations with systems they can continue to change. That means resisting the short-term shortcut that makes a demonstration easier and the next ten changes harder, and being explicit when a request and a constraint are genuinely in conflict.
Small, reversible steps
Changes are sized so they can be reviewed, released and undone without ceremony.
Written reasoning
Decisions and rejected alternatives are recorded next to the code they explain.
Boring where it counts
Well-documented, widely supported tooling in the load-bearing parts of a system.
Accessibility as function
Keyboard operation, contrast and reduced motion are requirements, not enhancements.
Leave it maintainable
The measure of finished work is whether someone else can safely change it next.
03Technical problem solving
Diagnosis before prescription
A stated problem is usually a symptom. Slow reporting can be a query, a data model, an infrastructure limit or a definition nobody agreed on. We separate the observed behaviour from its cause by looking at evidence — logs, traces, schemas, deployment history — before choosing a direction.
Once the cause is understood, we look for the smallest change that resolves it and can be verified. Larger rewrites are proposed only when incremental work is genuinely blocked, and then with the risk stated openly.
04Collaboration
Communication in writing
We work in the open with the people responsible for the system. Progress, blockers and decisions are shared on a regular cadence in written form, so that they can be read later by someone who was not in the room. Meetings exist to resolve things writing cannot.
Technical trade-offs are explained without jargon where a non-technical decision is required. When we disagree with a requested approach, we say so once, clearly, with the reasoning — and then implement the decision that the client owns.
Access, credentials and environments are handled through the client's own systems wherever possible, so nothing essential depends on us being reachable.
05Quality and responsibility
Responsible engineering
Quality is enforced by process rather than goodwill: automated checks on every change, review by a second engineer, reversible releases, and monitoring that shows whether a deployment actually improved things.
Responsible engineering also means restraint with data. We collect what a feature needs, keep access scoped, and raise privacy and security implications early, when they are still cheap to address. These are practices we follow — not a claim of certification or of compliance with any particular standard.
Enquiries about IT services: ASO Immobilienservice GmbH — anthonywils27@gmail.com