Building for Baku, for the world

I build in Baku, for a market most software companies overlook. That is not a limitation. It is the whole point.

Building for Azerbaijan means building for real constraints: a smaller market, several languages, and users who have been handed a lot of software that was clearly made for somewhere else. You cannot paper over that with a big budget. You have to actually understand the people you are building for.

Local first is a feature

When you build for a place you know, you notice things a distant team never would. The language has to be right — not translated, right. The product has to assume the conditions people actually have, not the conditions a polished demo assumes.

Zirva is built for Azerbaijani state schools, with an AI tutor, Zəka, that meets students in their own language. That is not something you bolt on at the end. It is the reason the product exists.

Global from day one

Here is the part that sounds like a contradiction: building local does not mean building small. The foundations — the stack, the architecture, the design language — are the same ones any global product would use. I build for Baku first, and I design so that nothing has to be torn out to go further.

Solve a specific problem for specific people, and you usually end up with something that travels better than the thing built for everyone and no one.

The bet

The bet I am making is simple. The tools people here deserve are the same caliber as the tools anywhere else — and almost no one is building them. So I am. For Baku, and for whoever needs them next.