There’s a story that gets told about enterprise software in this region, and it’s usually told by people who don’t live here. Arab businesses are behind. They resist systems, the market isn’t mature, the talent is thin. I’ve worked in Cairo and the UAE for twenty years — as an employee, as a manufacturer, as an agency co-founder, and now on the implementation side. The story is wrong, and it’s wrong in a way that happens to be convenient for the people telling it.
The budget exists. The talent exists; I hire from it. What’s usually missing sits on the other side of the table: the software is being implemented by people who have never had to run a company under these rules.
The word for this is normally “localisation,” which is a bad word for it, because it makes people think of translation. Translating your interface into Arabic and flipping the layout right-to-left is a courtesy. Localisation is whether the system can survive contact with the actual legal and operational reality of the country it’s running in.
Consider what that reality contains. Egyptian ETA e-invoicing isn’t a reporting feature you switch on at the end — it dictates how documents get structured, coded, and submitted, and getting it wrong isn’t cosmetic. Egyptian payroll runs on tiered calculations that don’t resemble the flat models most payroll modules ship with. Social insurance has its own base and its own rules. There’s a martyrs fund deduction that no global product has ever heard of, and that every compliant Egyptian payslip has to account for. Across the Gulf, UAE corporate tax is now a live constraint that has to be modelled properly rather than approximated at year end.
Watch how those get classified in a typical global implementation. They become edge cases. They go on a list, they go into phase two, they get worked around with an export to a spreadsheet and a person who reconciles it by hand every month.
But in Egypt, payroll is the payroll. E-invoicing is the invoicing. You can’t ship the system and leave those for later, because there’s no version of the business that operates without them. Calling them edge cases is really just an admission that whoever planned the work has never been the one signing the filing.
This is the real gap, and it’s a knowledge gap rather than a capability gap. It has nothing to do with whose logo is on the proposal. A large international firm can absolutely put a capable team on your project. What it usually can’t do is put someone in the room who has personally run payroll for a factory in Egypt, or who has felt what a compliance deadline does to a small company’s cash position, or who knows that a client asking for something “flexible” is often describing a real constraint they haven’t learned the vocabulary for.
That knowledge isn’t a soft advantage. It shows up in the architecture. It decides what you refuse to hard-code, which assumptions you leave open because you know the ministry will revise them, and which parts of the process you don’t automate because in this market they still need a human deciding.
Arab businesses don’t need to be told they’re behind. They need implementers who start from what these businesses actually do, and who have to live with the result afterwards.