By Niklas Wikstrom, Sirocco Group
A CRM programme delivered exactly to a twelve month plan in the Middle East can still arrive obsolete the day it goes live, and after years of running transformations across the GCC I have stopped being surprised. The reason is rarely the technology. It is rarely the people. It is the contract.
I have just written a short Sirocco leadership guide on this, Beyond Waterfall: How management teams in the Middle East should think about CRM transformation. The core of the argument is below, and the full guide is available to download at the end of this post.
Why waterfall keeps failing GCC CRM programmes
In a fixed scope, fixed price, twelve month contract the business is forced to define every requirement before any building begins. That works for construction. It does not work for CRM. Users discover what they actually need only once they start working with early builds. Partners uncover process and data realities nobody anticipated. The market itself moves. Every one of those discoveries becomes a change request, and every change request becomes friction. By go live the system is built for a business that has already moved on.
The really damaging part is not the change requests themselves. It is that management teams start resisting genuinely valuable changes simply to keep the contract whole. Scope rigidity becomes a substitute for governance, and the programme ships something that satisfies the paperwork while missing the point.
What disciplined agile actually looks like
Agile is not improvisation. The teams I see getting CRM transformation right in Dubai, Riyadh, and Doha are usually more disciplined than their waterfall counterparts, not less. They fix the business value streams at the start of the programme, the outcomes the business has to achieve, and trace every feature, user story, and integration back to one of those streams. What stays flexible is the detail of how those outcomes get built.
At Sirocco we structure the work around eight week increments and two week sprints, with a live demo to senior stakeholders at the end of every sprint. The demo cadence is the most important alignment mechanism in the programme. Real, working software, every fortnight, in front of the people paying for it. That is what stops a CRM programme drifting away from the business it was supposed to serve.
Why the GCC calendar matters more than people admit
Ramadan, Eid Al Fitr, Eid Al Adha, National Day periods in the UAE and Saudi Arabia, and the deep summer slowdown all reshape the working calendar across the region. A twelve month monolithic plan tries to absorb those rhythms inside one big timeline and usually fails. An agile programme absorbs them naturally, because each sprint and increment can be planned around them. The teams that win build their programme cadence around the regional rhythm rather than against it.
Download the full leadership guide
The full guide goes deeper into the product owner role, how the backlog replaces change requests, value traceability, how to plan around the GCC calendar, integration risk on ERP, billing, and VAT linked systems, and the eight practices I would push every senior team in the region to adopt.
Get in Touch
If you are scoping a new CRM programme in the Middle East, mid-flight on one that is not delivering, or rethinking governance for a multi-entity GCC rollout, I would be glad to talk it through.
