Why I Build World-Class AI from Cairo, Not London

The default assumption

When investors, analysts, or enterprise buyers hear that a product was built in Cairo, something shifts. Not hostility — more a quiet recalibration. The mental model of "world-class technology" has a geography baked into it: San Francisco, London, Tel Aviv, maybe Bangalore. Cairo is not on the shortlist.

R&D density is what happens when your economics let you hire four times the engineering headcount for the same budget — not to do the same work cheaper, but to do deeper work that a smaller team would never attempt. Cairo gives me that density. Building from Cairo is a strategic advantage, not a compromise — it is the decision to locate where talent depth and cost structure let you invest in infrastructure instead of cutting corners.

I have spent the last decade proving that assumption wrong. Not through argument — through output. Through a platform that now sits inside KPMG's annual Customer Experience Excellence Report, authored by a Cambridge professor, alongside the largest brands in the UK. Through enterprise deployments processing over a million messages per month. Through a team of 60+ engineers, all based in Cairo, who built every layer of that technology from scratch.

Building from Cairo is not a constraint I overcame. It is a decision I made — and I would make it again.

The economics nobody wants to talk about honestly

Here is a number that changes how you think about geography and R&D: 60 engineers in Cairo cost less than 15 in London or San Francisco.

Read that again. Not 60 versus 60 for less money. Sixty versus fifteen. Four times the engineering headcount for the same budget.

This is not about cheap labour. I reject that framing entirely. The engineers on my team hold degrees from Cairo University, Ain Shams, AAST, and the Arab Academy. They build distributed systems, train AI models on real enterprise conversation data, design multi-language NLP pipelines, and ship infrastructure that serves customers across the Middle East, Europe, and Africa. There is nothing cheap about what they do.

What Cairo gives me is R&D density. Instead of hiring a small team in an expensive city and hoping they can cover everything, I have the depth to build properly. Dedicated teams for each layer of the stack. Engineers who specialise, not generalise out of necessity. The capacity to invest in hard problems — like native Arabic language AI, or real-time conversation routing across channels — that a 15-person team would never prioritise.

Over the past three years, we invested $5M+ in R&D. That same spend in San Francisco would have produced a fraction of the output. Not because San Francisco engineers are worse — they are not — but because the economics compress what is possible. When your burn rate dictates your architecture, you cut corners. When your burn rate gives you room, you build infrastructure.

Egypt's engineering pipeline

Egypt produces over 30,000 engineering graduates every year. The top tier — Cairo University, Ain Shams, AAST, the Arab Academy — are rigorous programs that produce technically strong graduates. I know this because I have hired from these programs for nearly a decade.

But there is a gap between what these universities produce and what the market absorbs. Egypt's tech ecosystem, while growing rapidly, still does not create enough companies that challenge these graduates at the level they are capable of. Many of the best engineers end up at multinational outsourcing centres, doing solid but prescribed work. Others leave for the Gulf or Europe. The pipeline is extraordinary. What has been missing is the ambition to apply it to globally competitive products.

That gap is where I build.

The hiring philosophy

I do not compete for experienced hires from multinationals. I do not post senior engineering roles on LinkedIn and wait for people with ten years at Google or Microsoft to apply. Instead, I hire fresh graduates and train them from the ground up.

This is deliberate, and it is the single most important operating decision I have made.

When you hire a fresh graduate, you get someone with raw technical ability and no institutional habits. They have not yet learned that "this is how things are done." They have not inherited someone else's engineering culture — the shortcuts, the assumptions, the unexamined conventions. They come in capable but unformed, and that is precisely the point.

We train them in our engineering culture. We teach them to think in infrastructure layers. We give them ownership of real systems from early on — not busy-work tickets, but actual product responsibility. Within two years, a graduate who joined us knowing textbook algorithms is designing distributed conversation routing systems. Within three, they are leading teams.

I have a line I use often: "We don't hire entrepreneurs. We build them." This is not a motivational slogan. It is a literal description of what happens. Several people who started as junior engineers at Tactful now lead product teams. Some will eventually leave to build their own companies. That is not a loss — it is the whole point. I want to produce founders, not just employees. If the only thing my company creates is software, I have not built enough.

The retention question comes up often: "If you train them, won't they leave?" Some will. But here is what most people miss about retention in Cairo versus retention in San Francisco. In the Bay Area, your best engineers are constantly being recruited by Google, Meta, Apple, and fifty well-funded startups. The turnover pressure is relentless. In Cairo, an engineer building globally competitive technology at a company that invests in their growth has fewer reasons to leave and more reasons to stay. The competitive pull is lower. The meaning of the work is higher. That combination compounds.

Cultural proximity as a product advantage

There is a subtler reason why Cairo matters, and it has nothing to do with cost or talent pipelines. It has to do with language.

Tactful's platform serves customers across the Arabic-speaking world — and Arabic is not a simple language to engineer for. Right-to-left rendering, dialect variation across 22 countries, code-switching between Arabic and English within a single conversation, formal versus colloquial registers that carry different emotional weight. Western-built CX platforms treat Arabic as an afterthought — a localisation layer bolted on after the English product ships. The result is predictable: awkward translations, broken sentiment analysis, and AI that misreads the emotional tone of half the conversation.

When your engineering team natively speaks Arabic, thinks in Arabic, and builds in a city where every customer service interaction they personally experience is in Arabic, the product reflects that. Our AI does not treat Arabic as a foreign language to be decoded. It was trained on Arabic from the beginning — on real enterprise conversations, not translated datasets. The multilingual complexity that most platforms avoid is our competitive advantage.

This extends beyond Arabic. The MENA region operates in a web of languages — Arabic, English, French in North Africa, Urdu in parts of the Gulf. Building from Cairo, where multilingual communication is daily life, gives our team an intuitive understanding of the complexity that no amount of internationalisation testing in a monolingual office can replicate.

Deep tech predates the startup ecosystem

People sometimes talk about Egypt's technology sector as if it began with the startup boom of the 2010s. That is historically illiterate.

I spent two years at Silicon Vision in Cairo, building system-on-chip solutions for industrial applications. In July 2015, Synopsys — one of the largest electronic design automation companies in the world, with a market cap exceeding $50 billion — acquired Bluetooth Smart IP from Silicon Vision. Their clients had included Intel and Sony.

This was world-class semiconductor engineering, done in Cairo, years before most people started paying attention to Egyptian tech. The deep tech heritage in Egypt is real. It is just not well-marketed.

After Silicon Vision, I spent nearly seven years at ARM Holdings in Cambridge, managing the delivery of product lines in high-performance infrastructure compute, client compute, automotive, and IoT. When I returned to Cairo to build Tactful, I did not bring the engineering discipline with me — I found it already here. What I brought was the operating model and the ambition to point that discipline at a global market.

What validation looks like

When the KPMG UK Customer Experience Excellence Report featured Tactful's work with Elaraby Group as a headline case study, authored by Professor Mohamed Zaki from the University of Cambridge Service Alliance, the numbers told the story. First contact resolution went from 53% to 92%. First response time dropped from 36 minutes to under 10. Customer satisfaction climbed from 22% to 80%. Automated interactions hit 30,000 per month. Digital sales reached eight-figure USD.

That case study was not produced in London or San Francisco. The technology behind those numbers was built entirely in Cairo.

When Egypt's Entrepreneur Awards named us among the top three in AI Excellence and Deeptech, someone asked me what that recognition meant. I said: it means we are not the only ones who believe world-class AI can be built from here.

We position ourselves as a robust regional alternative to global incumbents like Zendesk and Intercom. That is not a modest claim. It is a direct statement that a Cairo-built product — designed, engineered, trained, and deployed from Egypt — can compete with category leaders funded by hundreds of millions of dollars in Silicon Valley. The evidence says it can.

The ambition gap

The talent in Egypt is not less than anywhere in the world. I have worked in Cambridge, I have collaborated with teams across Europe and the US, and I say this without qualification. What has been missing is not ability. It is infrastructure — the companies, the operating models, the ambition to build globally competitive products rather than outsourcing services for someone else's product.

That gap is closing. Slowly, unevenly, but closing. Every time an Egyptian company ships a product that competes internationally, the gap narrows. Every time an engineer in Cairo builds something that a Cambridge professor writes a case study about, the default assumption weakens.

I build from Cairo because this is where the best version of my company can be built. Not the cheapest version. Not the good-enough-for-the-region version. The best version — with the deepest team, the most relevant cultural intelligence, and the economic runway to invest in hard problems that matter.

The story of why I left and came back — and what the three years away taught me — is in Why I Bought My Company Back. And the infrastructure thesis that this team is building toward is the subject of The CX Industry Has a Tool Problem. I explored the engineering discipline that underpins all of this in What Semiconductor Design Taught Me About Building Software Platforms.

The world is starting to notice. But whether it notices or not, the work continues.