Family-owned groups in the Gulf usually start best with shared services, not with each company separately. Finance, HR and procurement do similar work across the group, so one workflow can be tested in one company, measured, then offered to the others under one set of governance rules, in Arabic and English.
#Key takeaways
- Start with work that repeats across the group's companies: finance, HR and procurement.
- Pilot in one company whose leadership wants it and whose data is reachable, not in the flagship.
- Set governance at group level once, then apply it in each entity.
- Keep each company's data separate unless the group decides otherwise, and write that decision down.
- Test Arabic, including Gulf dialect, on the group's own documents and messages.
#Why start with shared services?
Because the same work happens in every company. Each one reconciles vendor statements, enters invoices, answers staff questions about policy and matches purchase orders. A workflow that works in one entity can usually be offered to the next with modest changes, so the group pays for the learning once.
- finance: vendor statement reconciliation, invoice entry, month-end checks.
- HR: policy questions from staff, onboarding documents, leave and letter requests.
- procurement: purchase order matching, supplier queries, contract renewals.
#How do you choose the pilot company?
Choose the company whose leadership wants it, whose data is reachable, and whose process owner has time to approve output and measure the result. It does not need to be the largest or most visible business in the group. A measured result in a smaller company is more persuasive to the family than a stalled project in the flagship.
We set out the selection criteria for the first workflow in how to pick the first process to automate with AI.
#How should governance work across several companies?
Set the rules at group level once: who approves AI output, what is logged, where data is stored and where models run, and who can stop a workflow. The NIST AI risk management framework treats human oversight and accountability as part of managing AI risk (NIST, january 2023), and it gives the group a shared reference.
Then decide data boundaries. One company's customer or staff data should not reach another's workflow unless the group chooses that and writes it down. Decide whether accounts sit with the group or with each company, so the off switch has a clear owner.
#Why do group-wide rollouts stall?
Often because staff are already using AI on their own. The Work Trend Index found 78% of AI users bring their own AI tools to work, and only 39% had received AI training from their company (Microsoft and LinkedIn, may 2024). In a group, that means each company may already have unmanaged use before any official project starts.
Gartner also expects over 40% of agentic AI projects to be cancelled by the end of 2027, citing costs, unclear value and weak risk controls (Gartner, june 2025). A group that measures one shared workflow first avoids committing every company at once.
#What about Arabic?
Most groups run on a mix of Arabic and English documents, and customers or staff may write in Gulf dialect. Test the workflow on your own material before extending it. Our post on whether AI can understand Gulf Arabic customer messages explains how.
We are
Stennir starts with one shared workflow in one company, sets group-level rules for approval, logging and data, and works in Arabic and English.
We aren't
Stennir does not run a separate AI project in every company at once, or move one company's data into another's workflow without the group deciding it.
#What should a group CEO or head of shared services do next?
List the shared workflows that repeat across your companies and name a likely pilot company. AI consulting ranks them, AI training prepares the teams who will use them, and AI for operations shows typical workflows. take the free readiness assessment or book a 30-minute call.
#Common questions
Do all the companies in the group need to take part?
No. One company runs the pilot, and the others watch the measured result before deciding. The governance rules are set for the whole group from the start, so a company that joins later follows the same approval, logging and data rules rather than inventing its own version.
What stays with the family and the group?
The accounts, the data, the logs and the off switch. Stennir sets them up in the name of the group or of each company, as you decide. If you stop working with Stennir, every workflow keeps running under your control, with its documentation and logs readable by your own team.
What do you need from us to start?
A sponsor from the family or the group executive, one pilot company, a process owner there, and access to the systems the workflow touches. With those, Stennir can map the workflow, agree where data is stored and processed, and set the measures before anything is built.
What could go wrong?
The pilot company's data may be harder to reach than expected, each company may want its own rules, and staff may keep using personal AI tools alongside the official one. Agreeing group rules first, measuring the pilot honestly and training the users reduces each of these, though none disappears completely.
