Posts

The Investigator's Burden

What it costs to think deeply in a market that rewards speed — and how to carry it without breaking the business I am an Enneagram Type 5. The Investigator. The defining drive is understanding — not just knowing, but comprehending fully, from first principles, before acting. The defining anxiety is incompetence, appearing uninformed, being exposed as someone who spoke before they knew. This profile produces a particular kind of founder: someone who builds very slowly in the mind before moving quickly in the world. Someone who can map a system's hidden constraints before a vendor meeting. Someone who tends toward mastery over visibility, depth over volume. It also produces a particular set of failure modes. And running a business for five years in a market as fast-moving as Qatar has forced me to develop a practice around managing them. The Depth Trap The most seductive failure mode for a depth-oriented founder is what I call the depth trap: the belief that more analysis will produc...

If They Leave Inspired, the Next Project Is Guaranteed

The economics of strategic restraint in a market that rewards relationship over transaction The most powerful sales technique I've ever used is not a pitch. It is a question asked at the right moment, followed by silence long enough for the other person to hear themselves think. I did not develop this method from a sales framework. I developed it from watching what actually produces durable commercial relationships in the GCC — and what doesn't. The Problem With Pitching A pitch is optimized for a single outcome: the deal in front of you. Everything in a conventional pitch — the narrative arc, the case studies, the pricing slide, the close — is calibrated to convert this specific conversation into a signed agreement. That is a rational design for a transactional market. The GCC is not a transactional market. It is a relational one. In a relational market, the pitch that closes today can quietly damage tomorrow. It signals something: that you needed the deal more than you needed...

Why I Call Myself a Builder-Philosopher — And Why That Label Matters

I am frequently asked what I do. The honest answer is harder to give than it sounds. I have founded and run a multimedia and emerging technology company. I have designed and deployed immersive experiences for events that received global attention. I have advised institutions on technology strategy. I have built a VR entertainment business from a concept through to a functioning venue. I am currently helping a company digitise a workforce management process that still runs on paper. None of these things have a single clean job title. What they share is a methodology. And that methodology is why I use the label Builder-Philosopher. What the Label Is Not It is not a lifestyle brand. It is not an attempt to aestheticise work I could describe in simpler terms. It is a description of a cognitive sequence that I have found, over the course of a decade of building and breaking things, to be the only one that produces work I am willing to stand behind. The Sequence Philosophers ask: what is act...

AI in MENA: Why the Gap Between Hype and Deployment Is a Design Problem

  Every conference in the Gulf has an AI track now. Every government strategy document has an AI pillar. Every startup pitch deck opens with a model architecture slide and closes with a Total Addressable Market that runs to the billions. None of this is the problem. The problem is what happens after the slide deck. The problem is deployment. What Deployment Actually Requires I want to be precise about what I mean by deployment — because the word is doing a lot of unearned work in most AI conversations in this region. Deployment is not a proof of concept. It is not a sponsored pilot. It is not a system that runs for ninety days on a committee's approval and then gets quietly deprioritised when the champion leaves the organisation. Deployment is when an AI system is embedded in an operational workflow, is accountable for an output, is maintained, evaluated, and improved over time by people who understand both the domain and the technology. By that definition, genuinely deployed AI in...

XR Is Not a Product. It's a Problem-Solving Language.

Why immersive technology fails when it leads with spectacle instead of structure. Mirsab Al Rahman  ·  March 2026 The first question I ask any client who comes to me with an XR brief is not "what experience do you want?" It is: "what problem are you solving that a screen, a banner, or a brochure cannot?" Most pause. Some cannot answer. That pause is where most immersive technology projects die — before a single line of code is written, before a single headset is charged. The Seduction of the Demo XR is visually compelling. The demos are extraordinary. A volumetric avatar materialises in a boardroom. A free-roam VR experience drops forty people into a shared world with no cables, no controllers. A holographic footballer appears on a pitch and responds to a real ball being kicked at it. These things are real. I have built all of them. And yet — the demo is not the product. The demo is a hypothesis. What it is testing is whether the spectacle can carry a business objec...

The Non-Negotiables: On Ethics, Red Lines, and Walking Away from Revenue

I have walked away from three significant deals in the past four years. In each case, the financial value was real. In each case, the decision was not difficult. That is not a claim to moral superiority. It is a description of what happens when your principles are clear enough to function as operational policy rather than aspirational language. The Difference Between Values and Doctrine Most organisations have values statements. Respect, integrity, innovation — the vocabulary is familiar to the point of meaninglessness. What is rarer is doctrine: a set of non-negotiable operating principles that carry consequences. Principles that, when violated, produce a specific response rather than a discussion. I use the word doctrine deliberately. A doctrine is not aspirational. It is structural. You do not negotiate with it case by case. You apply it and accept the cost. What My Red Lines Actually Are Let me be specific, because specificity is what transforms a values statement into a doctrine. ...

Nobody Told Me the Most Important Skill in Technology Is Knowing When to Say Nothing.

Early in my career, I believed that the best way to win a client was to show them everything. Every idea. Every capability. Every technical possibility that our team could deliver. The logic seemed obvious: more value demonstrated equals more trust earned equals more business won. I was wrong. Not about the value — about the timing. The Moment That Changed How I Pitch I was in a meeting with a senior decision-maker at a government institution. We had prepared an extensive presentation — technology stack, case studies, ROI frameworks, creative concepts. The full arsenal. Halfway through the second slide, I stopped. Not because anything had gone wrong. But because I noticed something: the client wasn't listening to what I was saying. He was finishing my sentences in his head — arriving at conclusions slightly before I delivered them — and each time he did, I could see the micro-expression of someone who felt led rather than inspired. So I stopped presenting. I asked a question instea...