Ting Guides · For the CEO
Should a Saudi holding group use AI at group level or inside each company?
The short answer
Both, for different work. Keep at group level what is genuinely shared: finance, HR and procurement run as shared services, board reporting, and the rules every company follows on data, tools and vendors. Leave customer-facing and operational use cases to each company. Then sequence by readiness, starting with the company whose processes, data and systems are in order.
In this guide9 sections
- What it depends on
- Which AI use cases belong at group level, and which in each company?
- In what order should AI roll across the subsidiaries?
- What should the group record for every AI use case?
- How do AI programmes go wrong in holding groups?
- What changes for groups in Saudi Arabia
- Rasikh Holding: placing four AI candidates
- Questions people ask
- What Ting does and doesn't do here
- Sources
What it depends on
How shared the work really is
A finance team that processes supplier invoices for every company is a shared service; three finance teams that each follow their own steps are not, even if the org chart says so. AI pays at group level only where one process already serves several companies.
How far apart the companies' systems are
Subsidiaries bought at different times often run different ERPs, versions and charts of accounts. A group-level use case has to read each of them, so the gap between systems decides how much it costs to connect, and whether it should start in one company instead.
Who decides and who pays
If the group office funds AI and the companies run it, both sides need to know who approves the spend, who approves go-live, and whose budget carries the running cost. Unclear decision rights stall more group programmes than the technology does.
Who holds each company's data
In most groups, customer, supplier and staff records sit with the company that collected them. A group-level assistant that reads across companies needs that settled first, flow by flow, with your legal adviser.
Which AI use cases belong at group level, and which in each company?
The split follows who runs the work today, not where the budget sits. Use it as a starting map, then check each line against how your group actually operates.
| Area | Where it usually sits | Why | Who owns it |
|---|---|---|---|
| Supplier invoices, payments and the close | Group, where finance runs as a shared service | One team, one process and one set of controls serve every company | The head of the finance shared service |
| HR policy questions and onboarding documents | Group for common policy; each company where terms differ | A policy that is the same everywhere is answered once, with company exceptions listed | Group HR, with each company's HR for exceptions |
| Purchase requests and vendor onboarding | Group for shared categories; each company for operational buying | Shared categories gain from one route; a plant's or a branch's buying depends on its own stock | Group procurement and each company's buyers |
| Board and executive reporting | Group | The figures come from every company and are read at the top; see the related guide below for the method | The group CFO |
| Sales, customer service and operations | Each company | Customers, products and systems differ from one business to the next | Each company's general manager |
| Rules for AI tools, data and vendors | Group | Every company should buy and use AI within the same limits | The group CEO's office, with legal and IT |
In what order should AI roll across the subsidiaries?
Set the group rules before the first project
Write down which data each company may share and with whom, which AI tools staff may use, how a vendor is checked, and who approves spend and go-live. A short page agreed now saves renegotiating it with every company later.
Map what is truly shared
List each finance, HR and procurement process and mark whether one team runs it for several companies or each company runs its own. Only the first kind is a group-level candidate today.
Pick the first company by readiness, not size
Look for a named process owner, clean data in its systems and an interface the assistant can read. The flagship company is often the hardest place to start.
Run one shared-service case and one company case
One project at group level and one inside the ready company teach the group more than ten small pilots scattered across the subsidiaries.
Reuse before rebuilding
SDAIA's AI Adoption Framework recommends linking each initiative to specific performance indicators and aligning initiatives with the entity's wider direction to avoid fragmented effort and duplication (§3.1.2). When a second company wants the same thing, reuse the connection, the test cases and the controls, and change only what differs.[1]
Measure each company against its own baseline
Compare every company with its own figures before launch, not with its sister companies. Businesses in a group start from different places, and a league table hides that.
What should the group record for every AI use case?
Use case: what the assistant does, in one sentence Level: group shared service | company: name Process owner: name and role Data it reads, and the company that holds it: Systems and interfaces: system, interface, service account Basis for any data shared between companies, confirmed by legal: Spend approved by: name · Go-live approved by: name Baseline figures and date taken: Other companies that could reuse it: Review date:
Keep one register for the whole group, so a company that wants something already built finds it before buying again.
How do AI programmes go wrong in holding groups?
| Failure | What it looks like | How to prevent it |
|---|---|---|
| Platform first, problems later | The group buys a platform and asks each company to find a use for it | Start from processes companies want changed, then choose what to buy |
| Every company buys its own | Several subsidiaries sign separate contracts for the same kind of assistant | Group vendor checks and one register of what each company uses |
| Head office reads data it has no basis for | A group dashboard connects straight to subsidiaries' customer records | Settle each data flow between companies with legal before connecting |
| The flagship goes first and stalls | The largest company starts and spends months cleaning data | Choose the first company by readiness |
| Every change waits for a group committee | Small adjustments queue for a monthly meeting and companies lose interest | The group sets the limits; companies decide inside them |
What changes for groups in Saudi Arabia
General information, not legal advice. Each regulatory point summarises the official source cited beside it, as checked on the date shown under Sources; confirm how it applies to your company with your legal adviser.
Each company can be its own controller
The Personal Data Protection Law defines a Controller as any entity or private legal person that specifies the purpose and manner of processing personal data, and Disclosure as enabling anyone other than the Controller or the Processor to access or use it (Article 1). Article 15 allows Disclosure only in listed situations, such as the data subject's consent or the Controller's legitimate interests where no Sensitive Data is involved. Ask your legal adviser which of these applies before a group-level assistant reads one subsidiary's customer or staff records for another.[2]
A central data office fits the national framework
SDAIA's AI Adoption Framework, written for government and private entities, describes a Data Governance Office as a centralized supervisory entity that develops policy, monitors implementation and makes sure teams follow data management controls (§4.1.1). In a group, that office naturally sits at the centre, with each company keeping its own data owners.[1]
Data roles have a national template
The National Data Management Office's standards apply to public entities and to business partners handling government data, so a subsidiary that handles government data as a business partner is expected to apply them to that data. They name a Personal Data Protection Officer and Business Data Executives and Business Data Stewards for each data domain (DG.4.7 to DG.4.9). Other groups can borrow the same split of roles without being bound by it.[3]
Rasikh Holding: placing four AI candidates
ExhibitWorked example
The fictional Rasikh Holding owns a trading company, a car dealership and a logistics company, and runs finance and HR centrally. Four AI candidates came up in one quarter; this is where each was placed and why.
| Candidate | Where it sits | Owner | What decided it |
|---|---|---|---|
| Matching supplier invoices to orders and receipts | Group finance shared service | Head of the finance shared service | All three companies already send their supplier invoices to one team |
| Parts availability across branches | Rasikh Motors | The dealership's after-sales manager | Only the dealership holds parts stock and the system that tracks it |
| Customers' shipment status questions | Rasikh Logistics | The logistics company's customer service lead | The customers and the transport system both belong to that company |
| Staff questions about HR policy | Group HR | Group HR manager | One policy applies to all three companies, with each company's exceptions listed |
The decisionThe group started with invoice matching, because the process was already shared, and with the dealership's parts case, because that company had the cleanest data and a named owner. The logistics case waited for its transport system's interface; nothing was lost by waiting.
Questions people ask
Should the group build one AI platform for all its companies?
Can head office use the subsidiaries' customer data for AI?
Which company should go first?
Where does consolidated reporting fit?
What Ting does and doesn't do here
What we do
- In the AI Transformational Audit we trace how customer acquisition, delivery and support actually run across the companies you put in scope, and where work waits or is typed twice between them.
- You receive the Executive Report, maps of where the work waits, a ranked list of what to build first by impact and ease, and the expected return with every assumption written down, so the group can see which opportunities are shared and which belong to one company.
Where Ting helps: Combined Transformation Engagement
What we don't do
- We don't decide your group structure or replace any company's systems, and we don't give legal advice on data sharing between entities.
- We don't promise savings figures, and the Audit is not a roadmap or a phased plan; the optional next step is a Blueprint for the opportunities you select.
Sources
Primary sources only, each read in full on the date shown.
- AI Adoption Framework, version 2 (May 2025)SDAIA · checked
- Personal Data Protection Law (Royal Decree M/19 of 9/2/1443H, amended by Royal Decree M/148 of 5/9/1444H)SDAIA · checked
- Data Management and Personal Data Protection Standards, version 1.5National Data Management Office (SDAIA) · checked
