Systems
Integration first.
A new system rarely replaces everything. Most of the time it has to run alongside what is already there — and talk to it. What needs settling in the process is set out here.
A system that only works on its own is a second place where the same data is maintained. That is precisely what nobody wanted.
Integration
What a system has to talk to.
Not a vendor catalogue. What is listed here is what we settle before building — not which third-party brands we supposedly master. What we have actually connected, we name in conversation.
Interfaces
Almost every system has to fetch data from somewhere or hand it over. Whether an interface exists decides half the effort — and it is decided before the first draft, not in the middle of the build.
What gets settled firstIs there a documented interface, an export, or nothing at all?
Data and databases
Where the data lives, who owns it and what it looks like once it is wrong. A data model that does not reflect the business gets worked around in the business — and then someone maintains a spreadsheet on the side again.
What gets settled firstWhich record is the truth when two places contradict each other?
Hosting and delivery
Where it runs, how it gets there and what happens when a deployment goes wrong. Not a side issue: it decides speed, availability and whether a change takes minutes or days.
What gets settled firstWho has access to servers, domain and certificates today?
Billing and payments
The part where mistakes turn into money. Amounts, tax rates, documents, deadlines — and the rules of the country the billing happens in. Nothing here is estimated and nothing is rounded.
What gets settled firstBy which rules is it calculated, and who checks the result?
Documents and records
Contracts, invoices, evidence, photographs from the job. They arise along the way and have to be findable again — otherwise the system becomes a filing cabinet nobody opens.
What gets settled firstWhat has to stay findable, for how long — and for whom?
Access and permissions
Who may see what, who may change what, and what happens when somebody leaves. The least conspicuous question in a project and the one that hurts most often in operation.
What gets settled firstWhich roles really exist — not on the org chart, but in daily work?
AI services
Worthwhile where something has to be read, sorted or prepared that a person does by hand today. Not worthwhile as a label on a system that would have worked anyway.
What gets settled firstWhich step costs time today — and may a machine prepare it?
In practice
How we operate.
Monitoring
The systems report themselves when they are unreachable. For the enquiry path it goes further: a self-test checks whether an enquiry can still be delivered at all — a silent failure there looks from the outside like a weak market.
Logging
Enough to find a fault. No more than can be justified: what somebody typed into a form appears in no log.
Backups
Backed up and restored. A backup that has never been restored is not one — it is a file you hope about.
Security
Access, permissions, transport encryption and response headers at the level set when it was built — and measured again afterwards, not assumed.
Deployment
Every change takes the same route: build, check, deliver. If one of the checks breaks, nothing is delivered — not even when it is urgent.
Which of these can be booked as a service is set out on the managed operations page.
Managed operationsEvidence
Verifiable on this page.
Showing beats claiming. Every point can be checked from outside in the response header, in the delivered source or in the repository — without asking us.
Security headers
HSTS with subdomains and preload, X-Content-Type-Options, Referrer-Policy, X-Frame-Options set to DENY, Permissions-Policy and a Content-Security-Policy that already enforces object-src, base-uri, form-action and frame-ancestors.
Delivered statically
The pages are generated at build time and served from the CDN, not rendered on every request. That is why the site is fast — and why an application outage does not immediately take it down.
Two languages, two addresses
German and Turkish have their own URLs, their own titles, their own structured data and are linked by hreflang — not a switch that swaps text in the browser.
Images in AVIF and WebP
The photographs are converted at build time and delivered at the size the layout actually needs. Anyone who cannot handle AVIF gets WebP — automatically, not by a branch in the code.
Three checks in the build
The build stops if a function grows too large, if structured data would claim star ratings that do not exist, or if a service page says less in Turkish than in German. Not a statement of intent — a hard stop.
Self-test of the enquiry path
A dedicated route checks whether the keys, sender domain and abuse protection of the enquiry path still work, without sending an email. If a check fails, it answers with an error a monitor understands.
Our own accessibility audit, published
We audited this site ourselves and published the defects we found, instead of issuing a statement without findings. Read it under Accessibility.
Next step
You run the business. We build the system behind it.
Twenty minutes, free and without obligation. We look at the operation and tell you honestly whether we can help.