What does a project cost?
It depends on scope, so there are no package prices here. After the first conversation you get an estimate with a range and the assumptions behind it. Clearly bounded stages I bill at a fixed price, ongoing development by time spent. I quote my hourly rate on request — before you commission anything, not after.
How long does a project take?
I cut projects so that something usable exists after a few weeks — something you can work with and decide on. How long the full scope takes I commit to only after the analysis phase; anything earlier would be a guess.
Do you work outside Vorarlberg?
Yes. The studio is in Götzis in the Rhine valley; in Vorarlberg, around Lake Constance and in the neighbouring eastern Swiss and southern German area I come to you in person. Beyond that I work remotely with clients across Austria, Germany, Switzerland and Liechtenstein — workshops on site, everything else over video call and repository.
Who writes the code?
I do. Nothing is passed to subcontractors, and the person who quotes is the person who builds. If a project needs more capacity than I have, I say so in the first conversation instead of quietly outsourcing it.
Which technologies do you use?
Mainly .NET and C# with PostgreSQL on the backend, React on the web and Flutter for mobile applications; delivery is containerised with Docker, connected over REST or MQTT. The choice follows the task and what your team can maintain later — not what happens to be new.
Who owns the source code in the end?
You do. On payment the rights of use to the code written for you transfer to you, along with the repository and documentation. Open-source libraries keep their respective licences; which ones are involved is recorded in the project and discussed beforehand.
What happens after launch?
The rollout is not the end. On request I take on operation, monitoring and further development. An orderly handover to your own team, with a walkthrough and documentation, is equally possible. Which of the two applies is agreed before launch, not after.
Can you replace or take over existing software?
Yes, that is a common starting point: an overgrown spreadsheet, a legacy system nobody maintains, an application whose original developer is no longer available. It begins with taking stock — what stays, what gets replaced, how the data moves across — before anything is switched off.
How do you handle data protection and hosting?
Wherever possible, hosting stays in Europe; this website itself runs in a German data centre, with no cookies and no analytics services. For your project, data processing agreements, storage locations and retention periods belong in the concept — not in an addendum shortly before launch.
How do I get started?
With a few sentences through the form below, or directly by email to contact@ozal.cc. I reply within two working days with an honest assessment of feasibility, scope and next steps. The first conversation is free and commits you to nothing.