Questions, answered honestly

Mostly AI-assisted development — vibe coding — which lets me build considerably faster than the traditional route without losing control of the result. For automation I work with n8n and Make.com. The site you are reading right now is built with Astro and Tailwind CSS: static pages that load fast, have no plugins to break or update, and that search engines can read properly. I pick the tool that fits the problem rather than defaulting to whatever I used last.

No — automation is where most of my experience actually sits. I have spent years automating business processes on low-code platforms, mainly n8n and Make.com, and a great deal of Microsoft Power Automate before that, which I no longer take on. I also build simple Android applications, though that is a service I am still developing. Websites are one answer among several: which one fits depends on the problem, and if the answer is neither, I will say so.

Always. Everything I deliver — a website or a mobile application — is built to work on phones from the start rather than adjusted afterwards. The mobile view is designed as its own layout, not squeezed down from the desktop version, and every page is tested at phone, tablet and desktop sizes before handover.

Yes, if we build an admin area in. Then you can change texts and images or add entries without touching any code — one of the projects above works exactly like that. Whether it is included is something we decide together in the proposal, since it does add to the build.

A fixed price per project, agreed in writing before anything starts — never an hourly rate that grows while you watch. Current starting prices are in the pricing section further up this page; I keep them there rather than here so they stay up to date. For automation and AI agents, platform and API usage is billed separately at cost, with no markup.

A one-page site usually takes two to seven days once I have everything I need to start. A multi-page site takes five days to two weeks. Automation depends entirely on the use case — a simple workflow is quick, a complex one is not — so you get a realistic figure before we begin. The honest caveat: the build is rarely the bottleneck. What decides the timeline is how quickly texts, images and answers come back.

Before development starts we both sign a written agreement that describes every part of the finished solution in detail. If something needs to change while we are building, it gets written down as well — and depending on what it is, it can affect the price. That protects both sides: you know exactly what you are getting, and I know exactly what I am building. If something new comes up at the end that is not in the agreement and we have not agreed on it, I deliver what was agreed.

You do, completely. I keep nothing. During development I work locally or in a staging environment, and once the work is paid for you receive the entire source code and everything that belongs to it. No licence fees, no lock-in, and another developer can take the project on without asking my permission. The only thing I would like to keep is the right to show the work as a sample — and if you would rather I did not, that is fine too.

I do not sell hosting myself. I can recommend providers I use and trust, and set everything up for you — but the accounts stay in your name. That means you are never locked in, and you are never paying me a margin on somebody else’s service. If you already have hosting you are happy with, I will work with it.

Usually you — you know your business better than I do, and it keeps the site sounding like you rather than like a template. If you do not have the texts, I can write them and you simply review and approve them. Images work the same way: your own are always best, and I can point you to properly licensed sources when you need them.

I can write them and build them in — I use a specialist generator for the wording rather than drafting legal text myself. What I cannot do is take responsibility for the content: you have to review and approve it before launch, and for anything beyond the standard case it belongs with a tax consultant or a lawyer. That responsibility sits with them, not with me. What I do take care of is the technical side, and the site is privacy-friendly by default — fonts served from your own server rather than Google, and analytics that does not track individuals.

English, German, Ukrainian and Russian. Multilingual sites are something I build regularly: two of the projects above run in two languages at once, including the content, not just the buttons. I can also build a site in any other language using AI translation — but those four are the ones I actually speak, so for anything else I cannot vouch for the wording being right. Have a native speaker check it before it goes live.

Two weeks of fixes are included. If something is broken or does not match what we agreed, I fix it and it costs nothing — that is separate from new features, which are quoted. After that, ongoing updates and maintenance are optional and arranged separately, either monthly or per change. You are never obliged to keep paying me for your site to keep working.

Eight years of them — just not ones I am allowed to name. I have worked as a technical consultant and developer for companies between 50 and 10,000 employees, largely well-known German, Swiss and Austrian businesses, advising them and implementing the solutions. That work was done as an employee, for my employer’s clients, so those names are not mine to publish here. As a freelancer I am at the beginning, and I would rather tell you that plainly than invent testimonials. What I can give you instead: the five live sites above, a fixed price agreed in writing before anything starts, and the finished work in front of you before the final payment.