This article is part of the Capgemini Series β an ongoing investigation into one of the world's largest IT services firms and what its strategy means for Australian workers.
The Failure Pattern
Capgemini's project failures are not isolated incidents. They follow a predictable pattern:
- The bid β Senior consultants with impressive credentials present a compelling solution
- The contract β Capgemini signs, often with aggressive pricing to win the deal
- The handoff β Work is transferred to junior or offshore teams
- The scope creep β Requirements change, but the fixed-price contract doesn't
- The dispute β Capgemini blames the client for changing requirements; client blames Capgemini for poor delivery
- The failure β Project crashes, goes over budget, or is delivered below specification
- The escape β Confidential settlement, NDAs, and Capgemini moves on to the next bid
This is the bid-to-delivery gap β and it's the single most common thread across every failure in this catalogue.
The Major Failures
1. NHS 24: The Β£117 Million Crash (UK, 2016)
The project: A Β£117 million IT system for NHS 24, Scotland's health advice service.
What happened: The system crashed on launch day. NHS 24 leadership admitted "systematic failure." The project nearly collapsed entirely when the contract dispute between Capgemini and NHS 24 escalated to the point of termination.
The cause: Contract specifications didn't match delivery requirements. Capgemini and NHS 24 blamed each other. The system was never fit for purpose.
The cost: Β£117 million in taxpayer money, plus years of operational disruption. The dispute required arbitration to resolve.
"This led to a dispute between Capgemini and NHS 24 that nearly terminated the deal and made it obvious there were flaws in the contract." β Computer Weekly
2. Razer Data Breach: US$6.5 Million in Damages (Singapore, 2022)
The project: IT services for gaming hardware company Razer, including handling customer data.
What happened: A Capgemini employee caused a cybersecurity breach that leaked customer information β including shipping details and order records. The breach was discovered during a lawsuit, and the employee admitted mid-trial to causing the leak.
The cost: The Singapore High Court ordered Capgemini to pay US$6.5 million (S$8.7 million) in damages. Capgemini appealed but accepted liability after the employee's admission.
The aftermath: This case exposed Capgemini's inadequate security controls and data handling practices. The company fought liability until its own employee's admission made further denial impossible.
"Capgemini has accepted liability for damages after its former employee admitted mid-trial that he caused a cybersecurity breach." β Channel NewsAsia
3. BOQ Offshoring Disaster (Australia, 2022-2024)
The project: Bank of Queensland's IT operations, managed by Capgemini under a major outsourcing contract.
What happened: BOQ moved significant IT operations to Capgemini's offshore delivery centres. Customer service collapsed. System outages became frequent. The bank's reputation suffered as retail customers experienced degraded service.
The cause: The classic bid-to-delivery gap. Senior BOQ-facing consultants sold the deal with promises of quality; the actual work was delivered by offshore teams without the same level of expertise or institutional knowledge.
The aftermath: BOQ became a cautionary tale in Australian banking. The relationship between Capgemini and BOQ deteriorated significantly, with the bank ultimately reducing its dependence on Capgemini's offshore delivery model.
4. The ASC (Australian Submarine Corporation) Project (Australia)
The project: IT systems and digital transformation for Australia's submarine program.
What happened: The project ran significantly over budget and faced delivery delays. As a government defence contract, the details are partially shielded by confidentiality, but industry sources confirm the project underperformed against its original specifications.
The cause: Complex government requirements met Capgemini's standard delivery model β experienced sales team, offshore delivery. The mismatch between the complexity of defence IT and the cost-driven delivery model was fatal.
5. The Former Empired Clients (Australia, 2020-2025)
The project: Multiple contracts inherited through Capgemini's acquisition of Empired in 2020.
What happened: Empired was a respected Australian IT consultancy with a strong client base. Post-acquisition, Capgemini's integration process led to significant client dissatisfaction. Former Empired clients reported a sharp decline in service quality as Capgemini's offshore model replaced Empired's local delivery teams.
The cause: Acquisition trauma. The cultural and operational gap between a local Australian consultancy and a β¬22 billion French multinational was too wide. Promises of "business as usual" were broken within months.
6. The ME Bank Offshoring (Australia, 2021-2023)
The project: ME Bank's IT operations, another Capgemini outsourcing client.
What happened: Similar to BOQ, ME Bank experienced service degradation after Capgemini moved work offshore. The bank's IT stability suffered, and customer-facing systems experienced outages.
The cause: Cost-cutting through offshoring at the expense of service quality. The arbitrage between Capgemini's Australian billing rates and Indian delivery costs was the driving factor.
The Unreported Failures
The projects listed above are the ones we know about. The ones that made it to court, into the media, or onto employee review sites.
For every public failure, there are likely multiple failures that never made the news:
- Projects resolved through confidential arbitration β Capgemini's standard contracts often include arbitration clauses that keep disputes out of public courts
- NDA-protected settlements β Clients who sign confidentiality agreements as part of settlement terms
- Failures quietly absorbed β Projects that failed but were managed internally, with the client too embarrassed or too locked-in to go public
- Employee accounts β Reviews on Glassdoor, Reddit, and TheLayoff that describe failed projects without naming the client
"They hire you for a project, the project goes badly, management blames the engineers, and the client quietly walks away. Rinse and repeat." β Former Capgemini employee, Glassdoor 2025
The Root Cause: The Bid-to-Delivery Gap
Every failure in this catalogue traces back to the same structural problem.
Capgemini wins contracts by deploying its most experienced, most impressive consultants in the sales process. These are the people who understand the client's industry, speak the client's language, and promise the client's desired outcomes.
Then the contract is signed, and the work is handed off to:
- Junior engineers who lack the experience of the sales team
- Offshore teams who don't understand the client's business context
- Fixed-price delivery targets that incentivise cutting corners
- A management structure that measures success by utilisation, not outcomes
The gap between what was sold and what is delivered is the single most consistent theme in Capgemini's failure history.
The Verdict
Capgemini is not a uniquely bad technology company. The bid-to-delivery gap is an industry-wide problem in IT services. What makes Capgemini stand out is the scale and consistency of the failure pattern.
When a company: - Has 66% of its workforce offshore - Pays below-market salaries - Freezes wages while restructuring - Uses bench-PIP pipelines to manage headcount - Fights liability until its own employees admit fault in court
...then project failures are not accidents. They are the predictable outcome of a business model that prioritises margin over delivery.
If you have information about a Capgemini project failure that isn't listed here, contact us confidentially. We will verify and add it to the record.
Related Articles
- Capgemini: The Dossier β Data breaches, lawsuits, project failures β the complete evidence file
- Capgemini: The Forced Resignation Playbook β How Capgemini pushes employees out without official layoffs
- Capgemini: Bench & PIP Factory β The bench-to-PIP conveyor belt
- Capgemini: The Invisible Workforce β 66% offshore, the WNS acquisition, the offshoring machine
- Capgemini: Visa Machine β The 482 sponsorship trap
Was this helpful?