Brief
You describe the users, the job to be done, current tools and any hard date or constraint. A page is enough.
Locations
Software development for German organisations that expect the details in writing
German and wider DACH buyers usually want architecture, data processing and change control in the open. Hirvex Technologies works that way. Delivery language is English unless German-language UI and documentation are in the statement of work. We do not staff a fake Berlin office on the map.
Who this is for. Mittelstand operators, product companies and IT leads in Germany and neighbouring DACH markets.
Problems we typically meet
These are the patterns that show up before a useful first release—not abstract “digital transformation” language.
- A supplier could not explain sub-processors.
- English UI shipped when the users were German-only.
- Works councils and access policies were ignored.
- The project was agile as a mood, not as a cadence.
How we approach the work
AVV/DPA before personal data. Hosting in the EU when required. German UI is a translation and UX project. Technical documentation is part of handover.
What a serious first release can include
Scope is confirmed in discovery. This is the shape of work we are equipped to deliver—not a menu you must buy in full.
- Custom and integration engineering
- EU hosting options
- German-language interfaces when scoped
- Documentation suitable for internal IT
What we need from you
A useful brief is better than a long one. If you can answer most of the following, we can propose a first slice instead of a theatre estimate.
- Who will use this, and what must they finish in a session?
- Which systems must stay (accounting, payments, identity, a shop)?
- What is already live that we should not break?
- Any hosting region, language or compliance rule that is non-negotiable?
- The date that actually matters—and why.
How an engagement runs
Four steps. No mystery bench.
Scope
We reply with clarifying questions and a first-release outline: modules, roles, integrations and what “done” means.
Build
Named engineers work in visible increments, with staging you can click and a weekly written status.
Run
Launch, handover and a support path. The system is yours to operate—not a black box we disappear from.
Questions we are asked
Do you speak German?
Engineering delivery is English unless we staff or partner for German. UI translation is a defined workstream. We will not advertise native German delivery we cannot staff.
Can you work with SAP landscapes?
As integration around SAP, when interfaces are available. We are not an SAP Gold Partner unless we have that status to show.
EU data residency?
Yes, when the project requires it. We name the region in the architecture.
Start a conversation
If this is the work in front of you
Send the users, the job to be done and any hard constraint. We will answer as engineers—not with a canned brochure.