One Salesforce org across six Gulf markets.

Single org

A single org with enterprise territory management, so each country's team sees its own market and the group sees everything.

Group sharing model

Role hierarchy and sharing rules reflecting a holding company structure, where confidentiality between operating companies is often a genuine requirement.

Multi-currency

Multi currency with a group corporate currency and dated exchange rates, so consolidated pipeline does not shift as rates move.

Invoicing per country

Integration per country to the correct invoicing system, because ZATCA in Saudi Arabia and the UAE requirement are different problems with different timelines.

Bilingual in one org

Arabic and English layouts coexisting in one org, assigned per user rather than per country.

Group reporting

Group reporting on pipeline, conversion and velocity by country and by entity, with drill down to the originating record.

One org or one per country?

One org in almost every case. Separate orgs mean duplicated configuration, no native group reporting and a migration project later. Territory and sharing give you separation without those costs.

How is confidentiality between group companies handled?

Through role hierarchy, sharing rules and field level security, so an operating company's records are genuinely invisible to its sister companies while remaining visible to group management.

Can one org serve both Arabic and English speaking teams?

Yes. Language and layout are assigned per user, so the same org serves both without duplication.