What gets asked most often before work starts.

What the company does and how you currently handle the thing that bothers you. That matters most — the solution follows from the work, not the other way round.

It also helps to know: whether there is existing software the new system has to work with, a rough deadline if there is one, and a budget or a range. A budget does not raise the price; it shortens the conversation — it says at once whether we are building a small tool or a system meant to run for years.

A price cannot be given before it is clear what is being built, but an order of magnitude can. A brochure site is one bracket, a system with an admin panel another, and an integration with existing software a third — because there the time goes into understanding somebody else’s data format, not into drawing screens.

After the first message you get an estimate with a range and an explanation of what moves it up or down. If the range does not suit, that shows immediately, before anyone has spent time.

A brochure site usually takes a few weeks. A system with an admin panel and integrations takes longer, and there the schedule depends most on one thing that is not technical: how quickly content, access and answers arrive from your side.

The deadline is agreed before we start, and progress stays visible during the work — I do not disappear and reappear at the end with a finished product.

Yes, and it is the most common kind of work. A company rarely starts from nothing — there is usually a program, a spreadsheet or a way of working that functions and should not be thrown away.

At Hotel Lane the reception program was left untouched; it gained a website reading the same availability, so the same room cannot be sold twice. At BKC Soft the website issues licences to the software and receives reports back from it.

That is the point. Content, prices, projects and reports are entered by the client, in their own language and when it suits them.

For the German client the admin panel itself is in German, because that is the language they work in. The developer’s job is to make that possible, not to sit in the path of every change.

The site or system stays yours, with all access. Nothing is locked to the developer.

Maintenance, changes and support are agreed separately — as needed, or as an ongoing arrangement. Most relationships turn out long: one client accounts for three separate projects built over time.

Yes, and it all works remotely. The portfolio includes sites for Montenegro and for the German market.

Working abroad is not just translation. For the German client their legal framework was researched before any code was written — Impressum, data protection and cookie consent — because there a non-compliant site is not a formality but a cost.