Anonymised case studies

Managed IT projects and anonymised case studies

Real situations, presented with discretion. We protect our clients' confidentiality: names, logos, architectures, vulnerabilities, incidents and figures are never published without written permission.

Confidentiality commitment

What we do not publish.

Information we receive is limited to the people who need it to do the work.
Access is personal and logged, according to the service scope.
Client documents are never used for marketing purposes without consent.
A named reference or an introduction is only arranged with the client's permission.

Case 1Anonymised

Multi-site industrial organisation

Taking over operations without interrupting the business

Context

An organisation with several sites wanted fewer providers, more reliable backups and a single procedure for incidents.

Constraint

No business interruption during the takeover, across several sites at once.

Read the full case study

Actions

Inventory of assets and dependencies
Gradual takeover of systems and networks
Standardised monitoring
Documented backups and restores
A shared escalation procedure

Results

Centralised operations, identified responsibilities and documented recovery procedures.

Deliverables

Inventory of assets and dependencies
Documented backup and restore procedures
Shared escalation procedure

Presented without sensitive data or figures, in line with our confidentiality commitment.

Case 2Anonymised

Growing SaaS platform

Regaining control of cloud spending

Context

A growing company wanted to understand its costs, assign every resource to a service and cut unnecessary spending without weakening production.

Constraint

Reduce spending without putting a growing production platform at risk.

Read the full case study

Actions

Resource inventory and tagging
Usage analysis and rightsizing
Budgets and alerts
Regular reviews with technical and finance teams
Documented architecture decisions

Results

Budget visibility per service and regular management of capacity and costs.

Deliverables

Resources tagged and assigned to a service
Spending budgets and alerts in place
Documented architecture decisions

Presented without sensitive data or figures, in line with our confidentiality commitment.

Case 3Anonymised

Organisation with strict security requirements

Improving incident detection and response

Context

An organisation wanted to strengthen access, endpoints, logging and procedures after several significant risks were identified.

Constraint

Strict security requirements, with several significant risks to address first.

Read the full case study

Actions

Review of access and configurations
Multi-factor authentication rolled out across in-scope access
Detection tools deployed or improved
Backups secured
Response plan formalised and rehearsed

Results

Better visibility of security events, clearer responsibilities and a response procedure that can be tested.

Deliverables

Access and configuration review delivered
Multi-factor authentication across all in-scope access, with documented exceptions
Formalised and rehearsed response plan

Presented without sensitive data or figures, in line with our confidentiality commitment.

Your context

Does your situation look like one of these?

Tell us about your environment. We will explain our approach without disclosing anything about other clients.

See our commitments