Running one agency across Saudi and the UAE
Two currencies, two working weeks and two sets of client paperwork. Most agencies end up running two of everything, including the client record.
The fastest growth in regional agency work right now is not new agencies. It is existing ones extending across the border, usually because a client asked them to rather than because they planned it. The creative travels well. The administration does not.
Two currencies is not a display setting
A Riyadh client billed in riyals and a Dubai client billed in dirhams cannot be summed into one revenue figure without deciding, explicitly, at what rate and on what date. Software that stores one currency and displays others will happily produce a number. It is just not a number anyone should put in front of a board.
Currency belongs on the client, and reporting should keep the two apart by default. If you want a consolidated figure, that should be a deliberate conversion with a stated rate and date, not the accidental output of a spreadsheet column.
Two working weeks, one deadline
Saudi works Sunday to Thursday. The UAE moved to Monday to Friday in 2022. A cross border team therefore shares only four working days, and a deadline of Thursday means something quite different at each end of it.
No software setting dissolves this. What helps is that everyone sees the same calendar with the real dates on it, so the mismatch is planned around rather than discovered on a Thursday afternoon when half the team has already gone.
In practice most teams that work well across the two markets protect Monday to Wednesday as the window where everything collaborative happens, and treat the edges of the week as local time.
The paperwork differs, and the fields should too
Registration and tax identifiers are not the same across the two markets, and a generic system gives you one free text field for both. It works until an invoice goes out carrying the wrong identifier and comes back through a finance department that will not chase you to correct it.
The same applies to invoicing requirements more broadly. Saudi and the UAE have moved at different speeds on e-invoicing, and what your accountant needs from you differs by market. Wiro is not an accounting or tax filing system, and neither is most agency software: what matters is that the invoice carries the right details for whoever does file.
Resist running two of everything
The instinct is to set up a second workspace for the second market. It is tidy for about a quarter. Then a client active in both exists twice, the two records drift, and nobody can answer what that relationship is worth in total.
One client record with a country on it beats two client records that agree with each other most of the time.
Decide what is genuinely local
Some things must be local: the entity that invoices, the bank account, and the person who understands the market well enough to tell a client they are wrong. Those are not efficiencies to chase.
Most other things should be shared. Project structure, approval process, reporting format and the client record itself are better held once, because that is what lets one team cover for another when a deadline falls in the wrong week, and what stops the two offices developing incompatible ideas of what good work looks like.
Price for the market, not for the border
Agencies extending into Saudi often carry their Dubai rate card across unchanged, or discount heavily to win the first account. Both are guesses. The costs are different, the competitive set is different, and the client expectations around presence and responsiveness are frequently higher.
Price the second market on its own numbers, including the cost of the travel and the local presence that clients there will expect. An account won at a rate that only works if nobody visits is an account that becomes unprofitable the first time somebody does.
