Hi, I'm Kadir.

I studied industrial and systems engineering. The real lesson there was not technology: every job can be broken into steps, every step can be measured, and the thing that jams is usually the process rather than the people.

Software came out of that. When I built my first site the point was never to write code; it was to turn someone's scattered work into something that actually ran. That view has not moved since.

I don't sell myself as a veteran. But I have worked across very different industries, and in each one I had to learn from scratch how the business actually runs. I think that is where the real experience accumulates.

I work across industries that have almost nothing in common: logistics, furniture, machinery, customs brokerage, hospitality. Each one starts somewhere else. In logistics someone lands on the site to type a tracking number, in a cafe they look at the photographs, in customs they are looking for reassurance. You cannot dress all of them in the same template.

That is also where I am strongest: listening to a problem and seeing how software solves it. The real need is usually not the first thing described; the work is finding the actual problem underneath that sentence and getting it running by the shortest route. Code comes after that.

I run the whole thing myself: design, code, launch and what comes after. No agency, no project manager, no email chain that loses people. The person you talk to is the person doing the work.

And one more thing: the site looking good is not negotiable for me. I don't hand over work that doesn't.

1. 01

   Listen

   I don't write a line before I understand how the business runs. The first conversation is not about design, it's about how your day actually goes.

2. 02

   Cut

   Everyone's list is long. My job is to shorten it: which three things genuinely change the outcome, and finding those first.

3. 03

   Build

   I build until there is something real to talk about. Decisions made without seeing the screen usually turn out wrong.

4. 04

   Finish

   The last ten percent is half the job. The spacing, the transition, the moment it loads. The things nobody ever puts in a quote.

Work that doesn't look good isn't finished work.

When I get to choose, I lean towards work like this:

• Projects where I can talk directly to whoever makes the call
• People who don't get bored talking about details
• Work that continues rather than ending at handover
• Problems worth thinking about

A one-page marketing site works, and so does an end-to-end system. I do both. I like working without a layer in between; wherever someone sits in the middle, the work slows down.

I collect sites I like. I enjoy sitting with a design until I work out why it feels good, and that curiosity carries most of the job.

Most of my day happens in front of a screen, so in the evenings I try to get away from one. Walking, coffee, and people who take their time telling a story.

And I'm still learning. Every project gives me back as much as I give the client.

If you have something in mind, or you're just curious about what I do, write to me.