The person who designs it, builds it
No handover between a designer who does not code and a developer who did not attend the client call. Fewer people means fewer things lost in translation, and one person to hold responsible.
I design and build websites for businesses in Germany, Austria, Switzerland and across the Balkans who need a site that works harder than the one they have.
I came into this sideways. Before the design work there were years of IT administration — networks, servers, CCTV systems, the kind of infrastructure that only gets noticed when it stops. That background shows up in how I build: I care more about what happens on a bad connection in six months than about how a homepage looks in a portfolio screenshot.
Most of my clients have been through at least one disappointing website already. Usually it was expensive, took a long time, and quietly stopped being updated a year later. The work I do is largely an attempt to avoid repeating that: smaller scopes, clearer pricing, and a site the client can actually operate once I hand it over.
I invoice in euros, work remotely, and reply to email within a working day. If that sounds unremarkable, ask anyone who has tried to get a straight answer out of an agency mid-project.
No handover between a designer who does not code and a developer who did not attend the client call. Fewer people means fewer things lost in translation, and one person to hold responsible.
You get a number and a list of what it covers before anything starts. If the scope changes, we agree the new number first. I have never sent a client a surprise invoice and do not intend to start.
Chasing a Lighthouse 100 on a laptop is easy and meaningless. What matters is the field data from real phones on real networks, which is what gets measured before launch is signed off.
Domain in your name, hosting in your account, source code handed over. Retaining clients by holding their infrastructure hostage is a business model I want no part of.
First builds for local businesses while finishing IT studies. Learned more from fixing other people's sites than from any course.
Network maintenance, CCTV infrastructure and hardware support for offices. It permanently changed how I think about uptime and who gets called when something breaks.
Custom-built front-ends became the default for new work. A CMS stayed on the table for clients who genuinely need one, which is more of them than developers like to admit.
A name for the same work: design, build and technical SEO under one roof, for clients across the Balkans and Western Europe.
No pitch deck, no discovery workshop that costs money before anything is built. Just a conversation about what you need and whether I am the right person to build it.