Skip to content

Case studies

What the engagements actually looked like

The trigger, the constraint, what was delivered and in what order. Anonymised by default, and without a number we have not confirmed.

How we write these

Cloudgap case studies describe the trigger that started the engagement, the constraint that shaped it, what was delivered and in what sequence. Client names appear only with written permission, and outcome metrics appear only where they were measured rather than estimated. Everything else is anonymised by sector.

Sectors worked in

Six further engagements, pending verification

These are real engagements. Their write-ups carry specific outcome figures which are being confirmed as measured rather than estimated before they are published. The sector and the shape of the work are accurate now.

  • Global media

    Cloud migration and Zero Trust architecture

  • Logistics and critical infrastructure

    Rapid technical security audit

  • Payments and fintech

    Certification programme, managed vCISO

  • Healthtech

    AI governance framework and data residency

  • Education technology

    Web and mobile penetration testing

  • Central government

    Supply chain assurance at scale

[Client input required · Q9]

Per case study: confirmation that each stated outcome was measured rather than estimated, and that each attributed pull-quote is genuine and cleared for publication. Also Q3 - the fintech engagement is written up as ISO 27001 on one page and SOC 2 Type II on another.

Want to talk to someone who ran one of these? We will put you in touch with a reference where the client has agreed to it. Ask for a reference.