Digital Transformation Capacity Building
Building the capability inside your organisation to specify, govern and get value from technology. For boards, executives, technology leadership, functional heads and IT departments – whether or not you ever buy a system from us.
Four failures that repeat, in every sector, for the same reason.
Each of these is a capability gap, not a software gap. An ERP project that starts without closing them ends with the old spreadsheet still running.
The board cannot interrogate technology
Technology reaches the board as a status update rather than as a business case, so the hard question is not asked until the money is spent.
The executive cannot specify
Requirements arrive as a wish list rather than a defined outcome, so the vendor scopes the work and the organisation inherits whatever the vendor thought best.
The middle cannot absorb
A system goes live and the parallel spreadsheet survives, because the process was never redesigned around the system.
The technical team cannot advance
Capable engineers spend their time keeping yesterday running, so under‑budgeting and mounting technical risk surface only when something fails.
Three domains, one governed data foundation.
The three domains are transformed together, on one governed data foundation. Change one alone and the other two pull it back.
Processes, models, relationships
Business processes – how the work is actually done.
Business models – how the organisation earns and competes.
Customer relationships – internal employees or external customers.
Data – governed, single source
People. Process. Platform. Policy. The four held together by one data foundation everybody trusts – which, in practice, is what an ERP is for.
Governance, visibility, control
Governance – decisions made on evidence, not opinion.
Visibility – the same picture for everyone who looks.
Control – exceptions found early, not at year end.
Every level that has to carry a decision.
Board and directors
What to expect from the executive, and how to read a technology business review.
CEO, COO and executive committee
Owning the transformation agenda, the investment case and the benefit that follows it.
CIO, CTO and technology leadership
Architecture, security, delivery cadence and the discipline of saying no.
Functional and departmental heads
Process digitisation, one version of the number, and adoption that survives the pilot.
IT departments and technical teams
Integration, resilience, controls and the daily practice that makes all of it real.
Five tracks, selected and adapted to the room.
No generic material is delivered twice. Each track is adapted to the organisation before it is delivered.
| Track A · Boardroom and directors | The technology agenda in the boardroom · Reading the technology business review · Investment, benefit and the case that follows it · Technology risk and the director's exposure · Data as an asset the board owns |
| Track B · Chief executives and executive committees | Owning the transformation agenda · Specifying outcomes, not wish lists · The investment case and benefit realisation · Governing the vendor relationship · Reading the numbers the system produces |
| Track C · Technology leadership and IT departments | Architecture and platform decisions · Security and controls · Delivery cadence · Integration and resilience · Running an open‑source ERP estate responsibly |
| Track D · Functional and departmental heads | Process digitisation · One version of the number · Approval design · Adoption that survives the pilot · Retiring the parallel spreadsheet |
| Track E · Sector tracks | Mining and civils · Logistics, terminals and depots · Government institutions · Financial services · Energy and utilities · Manufacturing and distribution |
Five ways to run it.
Not a lecture. Participants bring their own operation into the room and senior managers present a problem from their own area. Something usable leaves the room – each session produces an artefact the organisation keeps.
Executive briefing
Half a day, boardroom setting, up to fifteen participants.
Workshop
One day, working session with materials and exercises. The standard format.
Tailor‑made programme
Multiple days, structured around one organisation and its systems. For corporates, enterprises and government institutions.
Maturity assessment and roadmap
A structured review with a written baseline and a sequenced plan.
Embedded advisory
A recurring engagement alongside the executive or the technology function.
Mohammed Saleh
Founder and Chief Technology Officer, RailGrid Technologies Limited
More than fifteen years building and transforming secure, regulator‑ready technology functions across multi‑country enterprises, preceded by seven years of university‑level teaching in computer science. M.Sc. Computer Systems, Networking and Telecommunications, University of Greenwich, London.
A diversified group of eighteen operating companies
Group technology strategy held for a decade across East Africa and the Gulf.
A global logistics and trading group across five jurisdictions
Three regional systems consolidated into one estate with international‑standard controls.
A greenfield enterprise software company
Strategy, architecture and governance baseline from inception; platforms delivered to regulated clients.
Tell us what you want to achieve.
We will come back to arrange a scoping conversation. Nothing is proposed before that has happened.