Kristóf Karner

Booking and scheduling systems, Stripe-based payments, Telegram messaging and automation, and custom backend solutions. I connect existing tools so the process runs without manual work. A separate article covers when automation is worth it.

Yes, on a monthly retainer for several clients. It covers updates, backups, bug fixes and smaller changes. A separate article covers what this means in practice.

More people now ask a language model for a recommendation instead of browsing a results page. The model quotes specific passages from source pages. AI visibility is the work that makes a business's content machine-readable, quotable and verifiable: structured data, clean hierarchy, self-contained answers. This is also what the site's main article is about.

On how many systems have to be connected, how much content goes on the site, and whether it needs ongoing upkeep afterwards. Three orders of magnitude come up. A showcase site with the content already written — description, photos, contact — goes live in eight to ten days, and that is the smallest of them. A multi-page site with its own editing screens, where you handle the content afterwards — price list, staff, opening hours from a table — is a multiple of that, because an admin interface gets built too. The third is where several services connect: payment, access, invoicing, notification — here half the work goes into making the chain hold even when one link fails. Maintenance runs separately, on a monthly fee, priced by how large the system is and how often it changes. I don't work from template quotes: you describe what you want solved, I ask back, and you get a price for that job.

Because it stays in one pair of hands, and in practice that means two things. First, there's no project manager and no handover between developers — what we agree on is what I build, so there's nowhere for the information to get lost. Second, the result is personally my reference: not a team's output with my name washed out of it. The price shows the difference too, because there's no office rent or sales layer behind me. In exchange, one person's capacity is finite: I don't take on more than I can do properly.

There is. If an existing site runs on a system I don't know — not WordPress and not hand-written HTML — I won't take it over for maintenance. An unfamiliar system is handled efficiently by whoever built it: they know the decisions that aren't visible in the code. In that case I offer one thing, and I say it plainly: rebuilding the site in WordPress or hand-written HTML. If that isn't worth it for you, I'll say that too.

By email. You describe what you want to solve, I ask questions, then send a quote. I don't cold-contact anyone and I don't work from templates. After the first exchange we usually talk as well — on a call or a video meeting. It is easier to get to know each other that way, and it builds trust on both sides: you see who you are trusting your system to, and I understand better what you need. Most of the work stays in email though, and that is deliberate: it keeps the project clearer for both of us, and nothing rests on improvisation — we hold the same written record, readable any time. If I maintain your system, you can reach me by phone too: when something breaks, or when a question is quicker to talk through than to write down.