Skip to content

Programmes I've worked on.

What each programme needed, what I did and what changed. Named where I can, anonymous where an NDA applies, and the numbers are the ones that were signed off.

8 case studiesFMCG / Retail · Finance / Banking · Government / Public Sector · Manufacturing · Defence
SAP migration team reviewing S/4HANA cutover plan on whiteboard with ECC system architecture diagrams in backgroundFeatured case study
FMCG / RetailGCC

Middle Eastern retailer · 18,000 employees · 7 countries

18,000 employees. 1,200+ outlets across 7 countries. A decade of custom ECC code that had become a liability. Brownfield S/4HANA with selective redesign. Finance close went from weekends to before lunch.

44%custom code, cleaned
1,200+outlets migrated
7countries in scope
Hand-picked

Programmes that show the range.

Different industries, same playbook.

Finance process modernization: CFO reviewing consolidated group financials on dashboard after SAP implementationFinance / Banking
UKSolution Architecture

15 days to close. Five.

Multi-entity group running consolidation on spreadsheets across three continents. SAP S/4HANA Group Reporting plus SAC for planning. The CFO could finally act on opportunities weeks earlier.

15 → 5day month-end close
ERP recovery case study. FMCG finance team reviewing unified SAP Analytics Cloud dashboard combining Oracle and SAP dataFMCG / Retail
South AsiaProgramme Recovery

Two ERPs, two answers. One source of truth.

Singapore on Oracle, UK on SAP, numbers that never matched. SAP Analytics Cloud connected live to both. Six months from recovery start to a unified reporting model finance and operations actually trusted.

6 mofrom stalled to relaunched
UAE government ministry procurement team reviewing SAP Ariba tender evaluation dashboard and supplier onboarding progressGovernment / Public Sector
GCCECC to S/4HANA Migration

Paper tenders. Auditable in months.

Multi-billion-dirham procurement run on paper and spreadsheets. SAP Ariba integrated with S/4HANA under UAE data-residency law. Tender cycles down 30–40%; the quietest win was a structured audit trail that auditors could read.

30–40%faster tender cycle times
ERP implementation contract negotiation. CFO reviewing statement of work with advisor before signingManufacturing
GCCContract Review

120-page SOW. $850K out before signature.

A 120-page proposal that looked clean and read vague. Three weeks of SOW decomposition surfaced $340K in scope rationalisation, $310K in role reallocation, $200K in contract modifications, all before the CFO signed.

$850Kremoved before kick-off
The archive

Everything else. Filter to your situation.

Full numbers. Anonymous where it matters.

Most case studies either name everyone or anonymise everything and tell you nothing. Here is the rule I follow.

  1. Rule 01

    Named where I can.

    Public references, client-approved stories, projects signed off as public. Where I can put a name on the work, I do, and the case study points to a citable source.

  2. Rule 02

    Anonymous where I must.

    NDA-bound engagements stay anonymous. Industry, region, scale and timeline are preserved so a reader can judge fit. Identifying details are removed.

  3. Rule 03

    Real numbers, no padding.

    What I report is what was signed off. No vanity metrics, no rounding up to the next pretty figure. If the close went from 15 days to 5, that's what the case study says.

Tell me what you're working on.

A 30-minute call. You describe the programme, the decision or the problem. I'll tell you whether I can help, and if I can't, who might.

Discuss your project