Most digital transformation programmes in Saudi Arabia do not fail on technology. They fail because a platform was chosen before the decision it was meant to serve was written down, and everything after that is an expensive attempt to make the platform fit. A digital transformation company earns its place by starting at the other end - with the decision, the constraint and the outcome - and only then reaching a product.
We work as an independent adviser through that sequence and stay involved after go-live. What that looks like in practice is set out below, along with what we will not put on this page.
Your systems each work and none of them agree - the same customer, order or asset has a different truth in three places, and reconciliation has quietly become somebody's full-time job. A board, regulator or shareholder is asking for a multi-year technology plan you do not have. A platform decision is being made this quarter that will be expensive to reverse, and the business case for it was written by the vendor. Or a mandate tied to Saudi Vision 2030 has given you a date and a digitisation target without giving you an operating model to reach it.
You already have a current, documented roadmap the business agrees with and a team executing it - in that case what you need is delivery capacity or assurance, not another strategy. Or your problem is genuinely one system behaving badly, in which case fixing that system is cheaper, faster and less disruptive than a transformation programme wrapped around it. We will tell you when that is what we see.
We start with the business outcome you need, not a product shortlist. That means sitting with the people who own the outcome, mapping current constraints, and agreeing what "solved" actually looks like before any vendor conversation starts.
We score realistic options against your own criteria - cost, fit, implementation risk, local support - without a reseller margin sitting behind the answer. Where a vendor in our partner network is not the best fit, we say so.
You receive a written recommendation with the trade-offs made explicit, not a single option presented as the only one. Sign-off is yours; the case for it is ours to make clearly.
Once a direction is chosen, we oversee delivery and integration with your existing systems, so the handover from decision to working system stays our responsibility, not yours to chase. Where the programme spans platforms that have to keep talking to each other, that work is described in more depth under systems integration.
The relationship does not end at go-live. We stay engaged as an advisor for the decisions that follow - scaling, renewals, the next system that needs to talk to this one.
A written statement of the decisions the programme exists to serve and the constraints they sit inside. A current-state assessment of the systems, integrations and data definitions in scope. A sequenced target operating model and technology roadmap, with each step tied to the business milestone it unlocks. A written, reasoned platform recommendation including the options rejected and why. And an integration and data plan describing how the chosen systems will exchange information with what you already run. Where a longer-range technology plan is the actual need rather than a transformation programme, that is IT strategy work and we will scope it as such.
The advisory stages - understanding the decision, evaluating options, and producing the written recommendation and roadmap - are scoped and dated in the proposal, so you know the length before committing rather than discovering it. Delivery and integration timelines are set by the chosen platform and the number of systems in scope, and we will not quote them before that scope exists.
The advisory stages are scoped and priced as a fixed-fee engagement agreed after an initial discovery conversation, so the cost of the decision is known before the decision is made. Delivery and integration oversight, where you choose to take it up, is contracted separately against the timeline the chosen platform sets, so cost tracks actual scope rather than a flat retainer. Ongoing advisory after go-live is a separate, cancellable arrangement rather than something bundled into the implementation fee. We do not earn a margin on your software licences; you should ask every other firm bidding the same question, because the answer changes what their recommendation is worth.
This work benefits CEOs and boards who have committed to a transformation target and need it turned into a sequence somebody can actually deliver; CIOs and IT directors inheriting an estate that grew by acquisition or by accident; finance and operations leaders whose reporting is slow because the underlying systems disagree; and public-sector programme owners working to a mandate and a procurement regime, whose particular constraints are covered on our government and public sector page.
Where our clients have approved publication, the engagement is written up on our success stories page with the detail they approved. That page, not this one, is where the record lives - and it is deliberately not a complete record, because most clients in regulated sectors do not publish. The absence of a story matching your situation is evidence about permission, not about experience. Ask in a first conversation and we will describe comparable work and, where the client agrees, put you in touch with them directly.
There is no honest single answer, and a firm that gives you one before seeing your estate is quoting a sales number. What actually drives the duration is knowable in the first conversation: how many systems hold the same data today, how many of them have supported integration paths, whether the target operating model is agreed or still being argued, and whether the programme has to run alongside a regulatory or fiscal deadline. We scope and date the advisory stages in the proposal, and we date delivery only once the platform and integration scope are fixed. Ask any bidder which of those four factors they measured before quoting you a duration.
Licence is usually the smallest line. Over three years the cost that matters is the sum of: subscription or licence including the seats you will add in years two and three; implementation and integration, including the interfaces to systems nobody plans to replace; data migration and the cleanup that precedes it; internal staff time, which is real cost even when no invoice is raised; training and the productivity dip after each go-live; support and managed services; and the cost of exit - what it would take to leave, which is the line vendors are least keen to quantify. We model those lines against your own numbers as part of the evaluation stage rather than publishing a figure here that could not be true for two different organisations.
Compliance is a property of the architecture you end up with, not of the service that recommends it, so the honest answer is that it depends on what is being processed and where. The obligations that most often bind a transformation programme in the Kingdom are the Personal Data Protection Law, administered by the Saudi Data and Artificial Intelligence Authority (SDAIA), which governs how personal data is processed and transferred; the National Cybersecurity Authority's controls, which apply to national and critical entities and to the cloud services they consume; and ZATCA's e-invoicing requirements where the programme touches billing. We treat classification as the first step - what data, at what sensitivity, under whose mandate - and only then ask which hosting region and which contractual commitment satisfy it. Get the residency commitment as a contract clause rather than a datasheet claim.
Whatever is realistic for your size, budget and regulatory context, including options outside our own partner network where they are the better fit, and including the option of not running a transformation programme at all. The evaluation is scored against criteria you agree in advance, and you receive the rejected options with the reason for rejection rather than only the winner. Where the decision is principally a platform choice rather than an operating-model change, we will say so and scope it as a vendor selection instead.
Usually, and that is normally the cheaper answer. Most enterprises run more systems than any single vendor will admit to supporting well, and forcing everything onto one stack to make the integration story simple is a decision that costs more than the integration would have. We assess which systems must exchange data, which have supported integration paths, and which are genuinely at end of life - and we recommend replacement only for the last group. The detail of that work sits under systems integration.
There are no numbers in this section, and that is deliberate. The heading was drafted for a page that would publish a count of transformation programmes, a number of systems migrated and a set of improvement percentages. We will not publish figures we cannot evidence to you on request, and you have no way to tell a real one from an invented one - which is exactly why the invented ones are so common.
More useful than our numbers is knowing which ones to demand, of us and of everyone else bidding. Ask for named engagements of comparable shape with the client contactable, not a count. Ask what baseline every improvement percentage was measured against, over what period, and whether that baseline was recorded before the work started or reconstructed afterwards. Ask what the organisation could operate without the adviser after handover. Ask about the engagements that went badly and what changed as a result. And ask how the adviser is paid, and whether they intend to bid for the work their own recommendation will define. Where our clients approve publication, the results are on our success stories page.
We name a client only where that client has agreed to be named for the specific purpose. The organisations who have agreed are on our customers page, which is maintained against those permissions rather than assembled for this page. If you would like a reference from an organisation of comparable size, sector or system complexity, ask during a first conversation - we will approach a suitable client and put you in touch directly if they agree, which is worth considerably more than a grid of logos.
Our published project record is on the success stories page. It carries the engagements our clients approved for publication, with the detail they approved, and it contains no anonymised composites. That is the honest extent of what we can show a stranger on a web page; the constraint is publication, not disclosure to a prospective client under an appropriate agreement.
Client feedback we have permission to publish appears below this page's content and on our customers page. No quotation is written into this section, and the absence is deliberate: we do not publish a client quote until the client has reviewed and approved the exact wording attributed to them, for the specific place it will appear. If what you want is to hear from somebody who has been through this decision, ask for a reference call - ideally with the programme or operations lead rather than the executive sponsor, because they are the one who lived through go-live.
Our current vendor relationships, accreditations and the certifications our consultants hold are published on the partners page. We keep them there rather than restating them in service copy for a practical reason: partner tiers and individual certifications change, and a page asserting a status it can no longer stand behind is worse than one that does not assert it at all. Treat that page as the current answer, and ask us directly about any platform you are evaluating. Ask for the certifications of the named individuals who would be on your programme rather than the firm's aggregate status, and ask whether they are committed to your dates.
A first conversation is a diagnostic, not a pitch: what decision is in front of you, what constrains it, and whether a transformation programme is even the right instrument. If it is not, we will say so - that outcome costs you an hour and saves considerably more. Book a decision session to start there.