Services
Most of the work is custom software — systems, portals and integrations. Alongside it comes what keeps a site visible, because a product nobody finds is not doing its job.
Development
Every item below is backed by a project in the portfolio.
Business systems and portals
Admin panels, records, reporting and partner areas — for work that has outgrown a spreadsheet.
See the example →Integrations
Connecting to software a company already runs, to state services and to payment providers.
See the example →Web applications and shops
Selling, configurators and bookings, with automation that removes manual entry.
See the example →Desktop applications
Windows programs with their own database and printing — for the counter, the shop floor, and places that do not work through a browser.
See the example →Multilingual websites
Translated URLs, hreflang and content written for the market — in German, Turkish or English.
See the example →Alongside the build
These come with a project or on their own, as agreed — it depends what you are missing.
SEO and content
Structure and copy written from what people actually search for, then measured by what brings visitors in.
See the example →Google profile and social media
Setting up and running a Google Business Profile and social accounts, so the site does not stand alone.
Maintenance and support
Changes, monitoring and help after delivery — because working software still needs someone who knows it.
How I work
No formal five-step process. This is simply what repeats in practice.
- 01
Start from what already exists
A company rarely starts from nothing — there is usually a program, a spreadsheet or a way of working that functions. The new system fits into that instead of demanding everything be thrown out. At Hotel Lane the reception program stayed; it just gained a website reading the same availability.
- 02
Manual entry goes first
What gets typed every day is both the most expensive part and the commonest source of errors. If the data already exists somewhere — at a supplier, on a fiscal receipt, in a state system — it should be read, not retyped.
- 03
What happened has to be visible
Automation you cannot inspect is not an advantage but a risk — it runs quietly both when it works and when it does not. So every automated job carries a record: what ran, when, and how it ended.
- 04
The client must not depend on me
Content, prices, finished sites and reports are entered by the client, in their own language, when it suits them. The developer’s job is to make that possible, not to sit in the path of every change.
Have a project?
Describe in a few sentences what you need. I reply with a first estimate and the questions that usually reveal the real scope.