Most digital transformation programs are not stopped by executive resistance, budget constraints, or technology failure. They are stopped by a simpler and more embarrassing problem: the program never properly started.
The mobilisation gap — the period between a contract being signed and meaningful, value-generating delivery beginning — is the graveyard of GCC enterprise transformation ambition. Programs lose 6 months here. Political windows close. Sponsor attention moves on. The program starts over with new priorities and, often, a new partner.
The Crawl–Walk–Run engagement model exists to eliminate this gap — and to give enterprise buyers a procurement-friendly path to high-confidence transformation programs.
The Problem with the Traditional Approach
The standard enterprise transformation engagement model works roughly as follows: a long RFP process, a multi-vendor evaluation, a contract negotiated at full programme scale, a large statement of work, a mobilisation phase, and then delivery.
The RFP-to-delivery cycle in the GCC typically runs 9–12 months for a programme of meaningful scale. This is not because procurement is slow; it is because the engagement model requires a large contract to be negotiated before any delivery trust has been established. Buyers are being asked to commit to multi-year programmes based on a vendor’s pitch documents, reference architecture, and relationship management — not based on observed delivery in their environment.
The result is predictable: when delivery does begin, it reveals gaps between what the contract assumed and what the environment requires. Scope changes follow. Commercial disputes follow scope changes. The mobilisation lag that the large contract was supposed to avoid reappears in the form of rework.
There is a better way to structure these engagements.
Phase 1: Crawl (4–8 Weeks)
The Crawl phase is a focused, fixed-scope diagnostic. It is not a discovery phase in the traditional consulting sense — an open-ended research period that produces a long slide deck. It is a time-boxed assessment with defined deliverables, designed to be scoped narrowly enough to clear divisional procurement approval in GCC organisations.
The Crawl phase typically produces four outputs:
A maturity assessment. Where does the organisation currently sit across the relevant capability dimensions (CX maturity, data governance, MarTech stack, analytics infrastructure, AI readiness)? What are the critical gaps relative to the organisation’s stated ambitions?
An opportunity sizing. What is the commercial value of closing the identified gaps? Quantified in the currency that matters to the executive sponsor — revenue impact, cost reduction, compliance risk, customer satisfaction movement, operational efficiency.
A business case. A structured case for the transformation investment, built to the organisation’s internal approval format. Designed to support the next procurement cycle, not to justify a pre-agreed scope.
A phased roadmap. A sequenced delivery plan, structured as Walk and Run phases, with defined gates between phases and explicit exit rights at each gate. Not a Gantt chart that will be wrong before the ink is dry — a phase structure that gives procurement something it can approve incrementally.
The Crawl phase is priced and contracted to be signed quickly. In most GCC organisations, a 4–8 week engagement of this scale can clear divisional approval without escalating to board level. This is deliberate. The goal is to get delivery started, not to get a large contract signed.
Phase 2: Walk (3–6 Months)
The Walk phase is a defined transformation engagement against the highest-priority opportunity identified in the Crawl. It is not a pilot — a small-scale proof of concept that the organisation will need to rebuild at enterprise scale. It is the first production implementation: a CDP rollout, a CX operating model redesign, an analytics governance rebuild, an AI-enabled personalisation layer.
The Walk phase has three structural characteristics that distinguish it from a traditional programme phase:
Defined gates. The Walk phase begins with an agreed set of deliverables and KPIs that constitute successful completion. These are negotiated at the start of the phase, not retrofitted when delivery is under pressure. If the gates are not met, the client has an explicit exit right before the programme scales.
Named KPIs. Not “improved customer satisfaction” or “enhanced data maturity” — specific, measurable outcomes. 38% increase in cross-sell conversion. 22-point improvement in CSAT against the national benchmark. Full PDPL compliance across six markets by a defined date. The business case from the Crawl phase sets these KPIs. The Walk phase is contracted against them.
Founder-level oversight. The Walk phase is governed by the same accountable individual who led the Crawl — not handed to a delivery team while the commercial relationship manager moves to the next opportunity. Decision-making authority, escalation paths, and commercial accountability remain with a named individual who is in-region and accessible.
Phase 3: Run (12+ Months)
The Run phase is the long-term programme: multi-workstream, scaled delivery, managed services integration, and continuous modernisation. It is the phase that most traditional enterprise engagement models want to sell first.
The Crawl–Walk–Run model makes the Run phase earn its place. By the time a client enters the Run phase, they have observed delivery in their environment, validated the governance model, and measured outcomes against defined KPIs. The Run phase is not a speculative investment in a vendor’s capabilities — it is a decision to scale something that has already been demonstrated to work.
In practice, Run phase programmes typically include:
- Multiple concurrent workstreams across capability pillars (CX, data, AI, application modernisation)
- Managed-services integration for run-state operations (MarTech ops, analytics ops, application ops)
- AIOps-enabled service delivery and continuous modernisation
- Quarterly programme reviews at founder/executive level with outcome measurement against the original business case
The Run phase is also where the local-prime model delivers its clearest commercial advantage. A programme at this scale, governed by a single Dubai Mainland entity with direct accountability for outcomes, is structurally more efficient than the same programme governed through an offshore majority model — because every decision cycle is shorter, every escalation path is cleaner, and every commercial conversation happens in the same time zone.
On our Agentforce practice, the same three phases are packaged as Discovery → Pilot → Enterprise. Crawl maps to Discovery, Walk to Pilot, Run to Enterprise. The names differ to fit how AI delivery is bought; the risk-managed sequencing is identical.
Why This Works for GCC Procurement
The Crawl–Walk–Run model is designed around the specific realities of GCC enterprise procurement — not adapted from a European or North American model.
GCC enterprise procurement is approval-cycle-driven. Large programmes require board-level approval, which requires long lead times. Small programmes can be approved divisionally, which means they can start faster. The Crawl phase is structured to clear divisional approval. The Walk phase is structured to demonstrate value before seeking programme-scale investment.
GCC enterprise procurement is also increasingly outcome-oriented. Buyers who have been through large transformation programmes — and watched them fail to deliver against their business cases — are demanding proof before commitment. The Crawl–Walk–Run structure provides that proof naturally: each phase produces outcomes that justify the next.
And GCC enterprise procurement is time-bound in a way that is not true in other markets. The 2026–2027 Vision 2030 window creates a hard deadline for programme mobilisation. The organisations that move through this window will be the ones that start with a small, fast Crawl phase — not the ones that spend 9 months in an RFP process for a programme that will not begin meaningful delivery until 2028.
How to Start
The Crawl phase requires three things from the client organisation: a named executive sponsor with the authority to approve the engagement, a defined scope question (what capability are we assessing?), and the willingness to start before the full programme design is complete.
None of these is a significant ask. The executive sponsor is usually the person who raised the transformation priority in the first place. The scope question can typically be narrowed in a single conversation. The willingness to start before full programme design is complete is the part that requires a shift in procurement habits — but it is the part that makes the difference between capturing the Vision 2030 window and watching it close.
The fastest path to a running enterprise transformation programme is a 30-minute conversation to scope the Crawl phase. Everything else follows from there.
Rami is the Founder of Emerge Digital — the Dubai Mainland local prime for enterprise CX, Data, AI, and digital transformation programs across the MEA region. To discuss a Crawl-phase diagnostic for your organisation, book a briefing.