About
How This Perspective Was Formed.
I’m a founder and operator based in MENA, and the founder of Logisoft — a technology platform built to address real operational and logistics challenges. Building and operating Logisoft has exposed me to how early technical decisions compound over time, especially in complex, operations-heavy environments. Many of the problems I’ve seen were not caused by weak ideas, but by unclear ownership, rushed execution, or technology choices made without enough context.
Alongside building Logisoft, I’ve repeatedly stepped into the technical co-founder role alongside non-technical founders at very early stages. Much of this work happens quietly and isn’t public. What repeats, however, are the same decision points — when to build, who should own what, how teams are formed, and how easily early mistakes become hard constraints later on.
Where the Experience
Comes From.
My experience comes less from outcomes and more from repetition. I’ve worked across multiple early-stage companies as the technical co-founder, often when conviction was high but execution was still undefined. These situations require decisions to be made before there is certainty — about people, scope, architecture, and timing.
Over time, this creates a pattern-level understanding of what tends to work, what tends to fail, and which decisions are hardest to reverse. This perspective doesn’t come from theory or consulting work, but from being accountable for technical direction and living with the consequences of those choices.
What I Pay
Attention to Early.
- Who owns technical decisions, and how that ownership is enforced
- Whether the problem is operationally real or conceptually interesting
- How much uncertainty the founder is actually comfortable carrying
- Whether speed is needed, or clarity is being avoided
- If building is necessary at all at this stage
Two Roles
Logisoft is a focused technology platform built to address real operational and logistics challenges. Building it has meant working through complexity, trade-offs, and long-term technical decisions in real environments, not theory. This experience grounds how I think about systems, ownership, and execution when technology is deeply tied to operations.
The platform I’m building
Logisoft
Separately from building Logisoft, I spend time reflecting on early-stage technology decisions and the patterns that repeat across founders and teams. This isn’t advisory work or a service offering. It’s an effort to document lessons learned, common mistakes, and questions that are often overlooked before momentum is lost.
How I think about early decisions
Notes
What People Say
