Targeted AI AdvisoryA specific
question.
A considered
direction.

One AI decision, answered by people who build these systems: build or buy, which vendor, which use case first, which tool policy. A focused one-hour consultation, or a written direction memo.

Ask your question

Questions we answer

Four kinds of decision.
One clear answer each.

Each kind of question gets the answer that fits it, built on your own contracts, systems and data. The examples come from Rasikh Holding Group, a fictional Saudi group.

  1. 01Build or buy

    Adopt the vendor's AI module, or build our own?

    Build-or-buy memo

    • AAdopt the ERP vendor's module
    • BBuild our own approvals layer

    Adopt the module. Keep the group layer ready.

    Worked through below
  2. 02Which vendor

    Which of three vendors makes the final round?

    Vendor scorecard

    CriterionVendor 1Vendor 2Vendor 3
    Arabic accuracy3 of 32 of 31 of 3
    Data residency1 of 33 of 32 of 3
    ERP integration2 of 33 of 31 of 3
    Exit terms1 of 32 of 33 of 3

    Vendor 2 to the final round

  3. 03Which use case first

    Of three candidates, where do we start?

    Use-case-first shortlist

    1. 1Delivery exceptionsRasikh LogisticsStart here
    2. 2Work orders from shift WhatsAppRasikh Industries
    3. 3Parts lookup across branchesRasikh Motors

    Why first: the data is ready and one team owns it.

    One decision. To rank opportunities across the whole group, start with the Audit.

  4. 04Which tool policy

    What may our people use AI tools for?

    One-page AI tool policy

    1. 1Approved tools only
    2. 2No customer or patient data in public tools
    3. 3A named person checks anything that commits the group
    4. 4Misuse is reported to Group IT

    Owner: Group IT · approved by the ExCo

Illustrative example

One closed folder under a brass desk lamp at the end of a long, empty meeting table, a mashrabiya screen behind

Our approach

Focus the question
before expanding the work.

We start from the decision in front of you and stop when you have an answer you can act on.

  1. 01

    Clarify

    We pin the question to one decision: who owns it, when it must be made and what a good outcome looks like.

  2. 02

    Review evidence

    We read the contracts, check system access and data samples, and talk to the people who run the process.

  3. 03

    Compare implications

    We compare the options on time to value, running cost, lock-in, data handling and Arabic quality.

    Lock-in and exit
    BStronger
    Maintenance owner
    AStronger
  4. 04

    Recommend direction

    A written recommendation, the assumptions behind it and what would change it.

Adopt or build

Two viable options.
A clear comparison.

We weigh both options on your own evidence: the vendor's contract and licence terms, access to the systems involved, a sample of real requests, and the capacity of the team who would run it.

Railway points: one track splits into two branches, A, adopt the module, and B, build our own. The lever is thrown, the switch blades move across to route the track to A, and A's signal turns green while B's stays red.

AAdopt the moduleRecommended

BBuild our own

Adopt our ERP vendor's AI module, or build our own?

Illustrative example · Rasikh Holding Group

One inter-company requestRasikh Motors · Jeddah service centre · email · 09:40

نبي ننقل 6 طبليات قطع غيار من مستودع الدمام لمركز الخدمة في جدة قبل الخميس، عن طريق راسخ للخدمات اللوجستية. مين يعتمد الطلب؟

“We need six pallets of parts moved from the Dammam warehouse to the Jeddah service centre before Thursday, through Rasikh Logistics. Who approves the request?”

Crosses two entities · group approval rules apply

AERP vendor's AI moduleAdopt the vendor's module

SeesRasikh Motors only

  1. Jeddah service centreRasikh MotorsRaised
  2. Branch managerRasikh MotorsApproved
  3. Entity line: the module stops here
  4. Operations managerRasikh LogisticsNever asked
  5. Group financeAuthority matrixNever asked

Approved inside Motors only: Logistics' capacity and the group sign-off are never checked. Someone re-routes it by hand.

BGroup approvals layerBuild our own approvals layer

SeesThe whole group

  1. Jeddah service centreRasikh MotorsRaised
  2. Branch managerRasikh MotorsApproved
  3. Operations managerRasikh LogisticsAccepted
  4. Group financeAuthority matrixSigned
  • Entity policyWork between two entities needs both sides
  • Authority matrixAbove the set limit, group finance signs

Routed by policy and authority; a person signs off.

FactorAAdopt the vendor's moduleTurn on the AI add-on in the group ERP and configure it to your approvals.BBuild our own approvals layerSpecify a layer over the group ERP and email that routes each request by the authority matrix.
Time to liveFastest: configured on the ERP you already runStrongerSlower: specified, built and tested before it goes live
Upfront costA licence add-on, with nothing to buildStrongerA Blueprint and a build before it runs
Data residency and PDPLWherever the vendor's AI service runs: confirm the region in the contractWhere you decide, under your own controlsStronger
Lock-in and exitTied to the vendor's licence; leaving means rebuilding the rules elsewhereYou own the specification and the rules, and they move with youStronger
Arabic qualityAs the vendor ships it: test it on your own requests firstAccepted only once it passes on your own Arabic requestsStronger
Maintenance ownerThe vendor, with every ERP releaseStrongerYour team, or a support agreement
Fit to processApprovals inside one entity, as the vendor designed themYour authority matrix, across every entityStronger

Illustrative exampleRasikh Holding Group is fictional. In your case, your contracts, systems and request volumes decide the call.

Deliverables

One hour.
One memo you can act on.

A focused consultation with the people who own the decision, and a direction memo when the call needs to be written down: the options, the evidence, the recommendation and what would change it.

Consultation notesAV-12

Question
Adopt our ERP vendor's AI module, or build our own?
Duration
1 hour
In the room
Group IT · group finance · Rasikh Motors operations
What we checked
  • Vendor contract and licence terms
  • Approval set-up in the group ERP
  • A sample of real inter-company requests
Open points
  • Where the vendor's AI service processes data (PDPL)
  • The authority matrix for inter-company work

Next: the direction memo

Illustrative exampleAV-12

Consultation

A one-hour working session with the people who own the decision. We test the options against your contracts, your systems and real requests.

Direction memoAV-12

To: Group IT, Rasikh Holding Group

Question

Adopt our ERP vendor's AI module, or build our own?

Recommendation

Adopt the module. Keep the group layer ready.

Turn on the vendor's module for requests that stay inside one entity. Keep the approvals layer specified for the requests that cross entities.

How the options comparebetter

  • Speed to liveA5 of 5B2 of 5
  • Light upkeepA4 of 5B2 of 5
  • Fit across entitiesA2 of 5B5 of 5
  • Freedom to exitA2 of 5B4 of 5

Assumptions

  • Most approval requests stay inside one entity.
  • The module's licence terms are confirmed with the vendor.

Illustrative example · Rasikh Holding Group is fictionalAV-12

Direction memo

A short memo leadership can act on: the recommendation, the evidence behind it, the assumptions and what would change the call.

Your next step

Bring us the question
worth solving.

Contact us