How to Choose a Digital Transformation Company in Saudi Arabia

How to Choose a Digital Transformation Company in Saudi Arabia

"Which is the best transformation company?" is difficult to answer objectively: we have not identified an independent rating for this market that you could rely on, and a company's own claim to be best is not evidence either way. What you can do instead is score your shortlist on twelve things that are visible before you sign, and treat anything that cannot be evidenced as a zero.

Use the scorecard below to assess a proposal and discuss the supporting evidence in a meeting. AY also applies it to itself later in the guide, including an area where we score lower than we would like.

A provider evaluation scorecard

AY prepared this scorecard for this guide, and applies it to itself below. Score each row 0, 1 or 2: zero means it was not addressed, one means it was addressed in general terms, two means it was evidenced. The maximum score across the twelve rows is twenty-four.

How to read the total. The total matters less than which rows scored zero. Rows 1, 2, 8 and 10 can be especially useful for assessing what the relationship may look like in year two, so a zero on any of them deserves attention even when the total score is high. What you do with this: send the twelve rows to each shortlisted company before the meeting, and ask them to bring evidence for rows 1, 2 and 8 specifically. How a company reacts to being scored is itself information.

Where AY scores on this, including where we score lower

Publishing a scorecard without applying it to ourselves would make the evaluation incomplete. So:

What you do with this: ask every company on your shortlist to do the same thing — to name the row where they score lowest and say why. A company that cannot name one may not have engaged fully with the scorecard or the question.

Six red flags that are visible before signature

Each of these warning signs can be observed in a proposal or an initial meeting:

• A fixed price quoted before the scope is defined. A fixed price is legitimate where the scope is genuinely fixed, and the proposal should show what it is fixed against — the deliverables, the assumptions and the exclusions. Where those are absent, ask what happens when an assumption proves wrong, and who carries that cost.
• No written exclusions. A scope with no stated boundary is likely to create disagreement, often when you have less leverage.
• Post-launch operation left unpriced. It can become a substantial cost after year one, and omitting it may make the proposal appear less expensive than the full commitment.
• "Best practice" as an answer to a controls question. A design built to a specific control should be able to name it. If it cannot, ask what requirements actually shaped the design.
• A team introduced in the meeting that does not appear in the contract. Ask which named people are committed and for how much of their time, in writing.
• Results guaranteed. Outcomes depend on decisions inside your organisation that no supplier controls. Any guarantee should be examined carefully for its conditions, exclusions and enforceability.

What you do with this: treat the first three as questions to resolve in writing before signature rather than as points to negotiate later. None of them means a provider is acting in bad faith; each one means a cost or a boundary has not yet been agreed, and agreeing it afterwards is harder.

Local or international is the wrong question

The useful distinction is not company size or origin. It is two things that vary independently of both:

Who operates the system after go-live, and under what service arrangement. This strongly shapes what year two may look like, and it can be clarified with one question.

Who carries integration risk with your existing systems. Where this is unassigned, the risk may fall to you and may later appear as a change request.

What proximity genuinely helps with is narrow and testable: on-site presence during process mapping, a team in your time zone at go-live, familiarity with locally common accounting and operational practice, and prior work against Saudi regulatory requirements. Proximity alone does not establish engineering quality, documentation discipline or the ability to operate a system — those should be assessed from evidence.

What you do with this: test proximity with one question — "who attends process mapping sessions, how often, and where?" — and test everything else by asking for the documentation from a previous project, with the client name removed.

Certifications and partner badges: what they do and do not tell you

Partner status with a platform vendor tells you a company has met that vendor's commercial and training thresholds. It is real information, and it is not evidence of delivery quality on your project. Management system certifications tell you a process exists and was audited; they do not tell you the team assigned to you follows it.

What you do with this: use certifications as a filter rather than as a ranking. The question that converts a badge into evidence is: "show me where that certified process appears in this proposal's acceptance criteria." If it does not appear, it is not part of what you are buying.

The six questions to ask in the second meeting

1. Which measure moved on a comparable project, and over what period?
2. Who was operating that system twelve months later, and can we speak to them?
3. Which specific controls is this design built to, and how will each be evidenced?
4. What is explicitly excluded from this scope?
5. What does operating this cost per year, and who does it?
6. If one of our existing systems cannot be integrated, what happens then?

How to read the answers: the first two separate delivery records from portfolios. The third separates designs built to a requirement from designs built to a template. The last three are common sources of later disputes, and they are generally easier to clarify before signature.

The adjacent decisions, and where they are made

• What am I buying, and what sets its price? The digital transformation services guide.
• Should we build this capability in-house instead? The guide to choosing a transformation provider.
• Which of my existing systems do I keep, replace or retire? The digital modernization guide.
• Who decides what once the change lands? The digital operating model guide.
• How do I get this approved and funded internally? The transformation business case guide.

How AY works

We expect to be scored on the twelve rows, and we have said above where we would score ourselves lower than a 2. Ask us for the same evidence the scorecard asks of anyone: which specific controls a design is built to and how each would be evidenced, what is excluded, what operation costs and who performs it, and documentation from previous work with the client name removed. What we can provide in a given case is confirmed at proposal stage rather than promised in an article.

What we will not offer is a guaranteed outcome, or a claim to be the best in this field — we have not identified an independent rating that would support such a claim by any party, which is why the scorecard exists in its place. Examples are in our work, and the scope is set out in enterprise digital transformation.

Next step

Send the twelve rows to your shortlist before the next meeting and ask for evidence on rows 1, 2 and 8. Written responses alone will often narrow a shortlist before you spend anyone's meeting time.

If you do not yet have a scope precise enough to be scored against, that is the point at which involving an outside party becomes useful. Talk to us about whether an assessment fits your case and what it would cover — the scope and outputs of any assessment are agreed before it starts rather than assumed in advance.