Business intelligence in the GCC: what to look for

Family groups and multi-entity reporting

A large share of Gulf businesses are family-owned groups: a trading arm, a contracting company, two retail brands, a property portfolio and a holding company, each with its own accounting system and often its own currency. The reporting need is the same across the region — a group view for the family board, an entity view for each managing director, and both from the same numbers.

What to look for:

1. One dashboard, many entities. A single group P&L or cash page where the entity is a filter, not a separate report per company. A permission rule then decides that the MD of the contracting company sees only contracting rows, while the group CFO sees all of them.
2. Currency handling. AED, SAR, QAR, KWD, BHD and OMR entities consolidated into one reporting currency at a rate table you control, with the original currency still visible per entity.
3. Intercompany lines. The ability to tag and exclude intercompany sales so group revenue is not double-counted.
4. Mixed source systems. Entities acquired at different times run different accounting packages. The tool should relate them by a shared chart of accounts rather than requiring everyone to migrate first.

A group with 14 entities and 3 currencies typically needs about 5 pages — group overview, entity P&L, cash and receivables, intercompany, and headcount — not 14 copies of each.

Arabic and English users on the same dashboard

In most Gulf companies the finance team, the operations team and the board do not all read in the same language, and a tool that serves one group well and the other poorly ends up with two sets of reports.

The requirement is not translation of your numbers — it is that the interface, menus, filters and layout switch to Arabic with a right-to-left layout for the users who want it, while English users see the same dashboard left-to-right, from one build. Check specifically:

• Chart titles, column names and filter labels you write yourself can be in either language, or both.
• Numbers, dates and currency symbols format correctly for each reader.
• Scheduled PDFs render right-to-left cleanly for Arabic recipients — this is where many tools break.
• The AI assistant, if there is one, accepts a question in Arabic and answers in Arabic.

Klayara’s interface is available in English and Arabic with right-to-left support; the Arabic version of this site shows what that looks like.

Keeping data in the region or on your own servers

Many organisations in the Gulf — government-linked entities, banks, healthcare groups, and increasingly ordinary private companies — want business data to stay within their country or region, or inside their own network. Whether that is a formal requirement or a board preference, the buying question is the same: where does the tool run, and where does the data go?

The honest options, from most to least control:

1. On your own servers, in your data centre or office network. Nothing leaves. Requires someone to look after the installation, or a vendor who does it with you.
2. In your own cloud account, in a region of your choice. The vendor installs and supports the software; the account, the keys and the data stay yours.
3. Vendor cloud with live connections, where dashboards query your systems in place and no copy of your data is held by the vendor. Ask this specifically — many tools copy data by default.
4. Vendor cloud with imported data, where a copy sits with the vendor. Ask which region.

Ask every vendor which of the four they support and whether the self-hosted product is the full product or a reduced one. Klayara runs in the cloud region you choose or on your own servers, as the same product; see self-hosting and security.

Local working weeks, calendars and reporting habits

Working weeks vary across the region and even within a group — one entity may work Monday to Friday, another Sunday to Thursday — and hours change during Ramadan. A scheduled report that arrives on the software’s idea of Monday morning is of little use to a team whose week started the day before.

Check that scheduled reports can be set to the recipient’s local time and to the days your teams actually work, and that a "last week" comparison can be defined as your week, not the default one. Reports delivered by WhatsApp are common in the region, alongside email and Slack, and should carry the same permissions as the dashboard.

Since VAT arrived across much of the GCC, businesses have also become used to a periodic filing rhythm and to reconciling reported sales against what finance submits. Two reporting habits follow from that and are worth building into any BI tool from day one:

• Tie the dashboard to the books. The revenue on the management dashboard should reconcile to the figure finance reports for the period, with the difference (timing, credit notes, exclusions) explained rather than argued.
• Keep the period as it was. A snapshot of each month’s pack as it stood when it was reviewed, so a restated figure can be traced. Version history on dashboards does this without anyone saving PDFs to a shared drive.

Choosing between cloud and self-hosted

For a Gulf buyer the decision usually turns on three questions rather than on cost:

1. Is there a data-location requirement, formal or from the board? If yes, self-hosting or your own cloud account in-region is the answer, and the vendor cloud is only acceptable if it queries your systems in place and holds no copy.
2. Do you have someone to run it? Many groups have an IT provider or an in-house team already running servers; if so, self-hosting adds little. If not, the vendor cloud or your own cloud account with vendor support is faster.
3. Do any sites have restricted connectivity? Plants, remote sites and secure premises may need the platform on the local network.

Whatever you choose, ask for the same product either way — the same charts, permissions, scheduling and AI — so the decision can be revisited later without rebuilding. The general guide to self-hosted versus cloud BI covers the trade-offs; the regional pages for the UAE and Saudi Arabia cover how Klayara serves each.

Questions to ask a BI vendor in the GCC

1. Can one dashboard serve all our entities, with each MD seeing only theirs?
2. How are multiple currencies consolidated, and who controls the rate table?
3. Does the interface work in Arabic, right-to-left, including scheduled PDFs?
4. Where does our data sit — your cloud, our cloud account, or our servers — and is a copy ever held?
5. Is the self-hosted product the full product?
6. Can scheduled reports run on our working week and in our time zone, to email, WhatsApp, Slack or Telegram?
7. Do permissions hold in downloads, scheduled reports, embedded portals and AI answers?
8. Is there version history so we can see a pack as it was at the board meeting?
9. Who builds the first dashboards, and how quickly?
10. How is pricing structured as we add entities and users?