Understanding the system before deciding what to build.
My work extends from physical architecture into software engineering, artificial intelligence, spatial systems, and digital infrastructure.
I work across the entire stack because I want to understand a problem completely before defining what needs to be built.
Some builds are focused technical tools. Others are fully functioning platforms. Some are developed toward independent ventures. All begin the same way: identifying a real problem, mapping the underlying system, and engineering a working response.
I don't start by asking what company to build. I start by asking what problem is worth solving. If the problem is real and the product creates value, the company follows.
My work extends from physical architecture into software engineering, artificial intelligence, spatial systems, and digital infrastructure — across the entire stack.
Every build begins the same way: identify a real problem, map the underlying system, and engineer a working response. Solve the problem first — the company follows.
Proof of building.
I independently take products from idea to functioning platform, managing system architecture, interface design, engineering, data, and deployment.
Selected builds include:
-
The company I run. Everything on this site is built inside it.
-
A code-native design studio. Brand, interface and engineering built together.
-
Road warnings that reach a driver's phone before the road does.
-
Operational intelligence for urban and infrastructure systems.
ZNAKOS
Every vehicle knows before it arrives.Drivers, and the automated vehicles that share the road with them, usually find out about roadworks, closed lanes and obstructions too late. ZnakOS lets a road authority declare a change, signs it, and sends it to the driver's phone, in their own language, before they reach it. It needs no roadside hardware.
It runs on signed messages, a map cut into cells of about 1 km, and five levels of guidance: Clear, Aware, Prepare, Act, Caution. On test phones in Dubai the median delivery time is 0.5 seconds. We are an entrant in the RTA Dubai World Challenge for Self-Driving Transport 2027.
I build the systems behind the idea.
Founding begins with understanding system mechanics rather than simply defining a surface product.
Moving fluidly between problem definition, architecture, design, and software engineering allows these disciplines to stay linked. I take an idea from an initial question to a functional platform without waiting for separate teams or partners to translate it.
The objective is not building technology for its own sake. It is finding problems where technology fundamentally changes how something works—and building the system capable of doing it.
I build the systems behind the idea.
Founding begins with understanding system mechanics, not simply defining a surface product.
The objective is finding problems where technology fundamentally changes how something works — and building the system capable of doing it.
I build to find out.
Building is how I test ideas.
I don't validate concepts through documents or presentations—I want to see the system work. That means taking an idea through research, software, interfaces, and infrastructure into a functioning platform.
Some remain experiments. Some become platforms. Some develop into independent companies.
The question remains the same:
Can a well-designed system change how this problem is solved?
I build to find out.
I build to find out.
I don't validate concepts through documents or presentations — I want to see the system work.
Some remain experiments. Some become platforms. Some develop into independent companies.
The question remains the same:
Can a well-designed system change how this problem is solved?
I build to find out.