What a Digital Modernization Company Does, and Which Type Fits Your Gap

What a Digital Modernization Company Does, and Which Type Fits Your Gap

"Digital modernization" is sold by three different kinds of firm — marketing agencies, IT consultancies and integrated providers — and they cover different layers of the same problem. Choosing the wrong type can produce competent work in the wrong area, making the mismatch difficult to detect.

The useful first question is not which company is best, but which layer your gap sits in. The map below sets out the four layers modernization work usually touches, what each one changes, and which kind of firm typically covers it.

A capability coverage map

AY prepared this map for this guide. Find the layer where your problem actually sits, then read across to see who covers it:

What you do with this: name the layer before you shortlist. A firm strong in one layer is not weak — it is scoped. The risk this map is meant to reduce is hiring for the demand layer when the constraint sits in core systems, which may improve the front end without resolving the underlying problem.

Where your gap spans more than one layer, you may consider an integrated provider. You should also ask how the layers are governed together, because one party covering several layers benefits from a written review arrangement. That applies to us as much as to anyone else.

Modernization and transformation are not interchangeable

The two words are used loosely, and the difference decides who sponsors the work and what success looks like.

Modernization updates what already exists so it can meet current expectations: the system is replaced or upgraded, the process largely survives. It is usually sponsored by whoever owns the system, and success is measured by capability regained — the change now takes days rather than months.

Transformation changes the process, the decision and the customer experience together, and measures the result. It needs an executive sponsor, because it reassigns work across departments.

What you do with this: decide which you are funding before you write the brief. A modernization budget with transformation expectations attached to it is a common reason a delivered project may be judged unsuccessful despite working as specified.

What to ask a modernization company to show you

Five requests that can be addressed before signature and are often more informative than a capabilities deck:

• A previous deliverable with the client name removed. The format tells you what you would actually receive.
• The named people who would do the work, and how much of their time is committed, in writing.
• What is explicitly out of scope. A boundary that exists only in conversation may create disagreement later.
• How the system is operated after go-live, by whom, and at what annual cost.
• A reference from an engagement that ended at least a year ago — recent references describe delivery, while older ones can show what remained effective.

How to read the answers: the fifth item may be difficult for some firms to provide. If no older reference is available, ask whether this reflects the firm's age, client confidentiality, retention or another constraint; none is automatically disqualifying.

On rankings: we have not identified an independent rating for this market that you could rely on, and a firm's own claim to lead it is not evidence in either direction. Judge the five items above instead.

Where local knowledge changes the work, and where it does not

"Understands the Saudi market" is offered as a credential. The testable part of it is narrow and worth isolating:

• Prior work against the regulatory requirements that apply to your activity. Ask for one specific example: which requirement, and how it became a line in a system specification. A general statement about compliance is not an answer.
• Presence during process mapping. Who attends, how often and where — a question that helps clarify the delivery model.
• Familiarity with locally common accounting and operational practice. This shows up in the questions a firm asks you, more than in what it presents.
• Arabic as a design requirement rather than a translation step. Ask to see a delivered Arabic interface.

What location alone does not guarantee: engineering quality, documentation discipline and the ability to operate a system after launch. Those are assessed from evidence. And a firm does not need to be Saudi-registered for you to meet requirements that apply to you — the obligation sits with you, does not transfer by contract, and its scope for your organisation is a matter for regulatory review rather than a supplier's assurance.

Three failures that recur after the contract is signed

No owner on your side. Work owned only by the provider may produce something technically correct that does not match how the work is done. What you do: name one person with authority to settle process disputes, and give them real time rather than additional time.

The old way is never retired. Keeping it "as a backup" may encourage continued use and make adoption figures less meaningful. What you do: plan the retirement of the old process as part of go-live, with the conditions that have to be met first rather than a date alone.

Training on screens rather than on the method. A session explaining the interface alone may not change behaviour; the transition also requires reviewing what is asked of people and how they are measured. What you do: remove one old task for every new one, and adjust targets for the transition period.

Resistance to change may result partly from these conditions rather than being a separate obstacle. For the person doing the work, a new system may feel like a cost before its benefit becomes visible.

The adjacent decisions, and where they are made

• How do I score and compare the shortlist itself? The guide to choosing a transformation company.
• What engagement model and cost structure should I ask for? The digital modernization provider guide.
• Which of my existing systems do I keep, replace or retire? The digital modernization guide.
• Should we build this capability in-house instead? The build-or-buy guide.
• Who decides what once the change lands? The digital operating model guide.
• How do I get this approved and funded? The transformation business case guide.

How AY works

AY works across all four layers in the map above, which is the case for asking us how they are governed together rather than taking integration as a benefit in itself. The principle this guide recommends is the one we work to: name the layer where the gap sits before scoping the work, because this helps determine the appropriate scope and value.

What we can provide in a given case is confirmed at proposal stage rather than promised in an article, and we expect the five requests above to be put to us as they would be to anyone else. Examples are in our work, and the scope is set out in enterprise digital transformation.

This article is not a substitute for regulatory review: which requirements apply to a specific organisation depends on its activity and its data.

Next step

Take the coverage map to your own team and mark the layer where your problem sits. If two people mark different layers, that disagreement is a valuable signal that the problem may not yet be clearly diagnosed and that a proposal could be priced against uncertain assumptions.

If the layer cannot be identified because the symptoms point in several directions at once, 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.