News

21.05.2026, 10:00
A $32 million failure and what Moldova's digitizing businesses should take from it

The Hertz-Accenture collapse was not a budget problem. It was a delivery problem — and that distinction matters everywhere.

Hertz spent $32 million on a full digital overhaul and ended up with broken code, missed deadlines, and a lawsuit against one of the world's largest consultancies. A McKinsey and Oxford study of over 5,400 global IT projects found that 17% fail so badly they threaten the company's survival. Hertz, a billion-dollar brand with access to the best advisors money could buy, still ended up in that 17%. The project — contracted to Accenture in 2016 — missed deadline after deadline through 2017 and into 2018. When Hertz finally terminated the contract, the delivered code was incomplete, buggy, and contained serious security vulnerabilities. A lawsuit followed. Accenture denied wrongdoing. The $32 million was gone regardless.

The instinct is to read this as a cautionary tale about outsourcing, or about trusting large consultancies. But this story is not about vendor selection. It is about what happens when a company treats digital transformation as a procurement event rather than a governed, sprint-by-sprint delivery process — and never builds the internal visibility to catch problems before they compound.

For context: the Hertz project had no working testable output at key milestones, compliance and quality assurance were treated as downstream concerns, and leadership had no real-time view of what was being built. BCG estimates that nearly 70% of digital transformation failures trace back to poor risk management and execution breakdowns — not to the size of the budget or the reputation of the vendor.

Private medical clinics, agricultural exporters, and financial services operators in Moldova are now moving into territory that Western markets navigated a decade ago — building digital booking systems, payment integrations, client-facing platforms, and internal process automation. What is already commodity infrastructure in London or Warsaw is still a genuine competitive advantage in Chisinau, and that window will not stay open indefinitely. The question is not whether to build — it is whether the delivery model is structured to catch problems early rather than absorb them late.

Moldova's market has one structural advantage that large Western projects often lack: the feedback loop between owner, team, and customer is short. A business here can validate a feature, hear from actual users, and correct course inside a single month. That is not a constraint — it is leverage, but only if the development process is built to use it.

If you are currently running or commissioning a digital build — whether that is a payment system for a logistics operation, a client portal for a private clinic, or inventory automation for a retail chain — three questions are worth sitting with:

Are you receiving working, testable output at regular intervals, or are you being asked to wait for a final delivery? The Hertz project produced nothing demonstrably functional until it was too late to course-correct without catastrophic cost.

Is compliance — whether that is data protection, financial regulation, or sector-specific requirements — built into the development process from the start, or treated as a final step? Retrofitting compliance after a build is complete is consistently more expensive and more disruptive than integrating it from day one.

Does your leadership team have real-time visibility into what is being built, what is blocked, and what is at risk — or are you dependent on periodic reports from the vendor? Visibility is not a luxury feature of project management. It is the mechanism by which problems stay small.

Hertz lost $32 million and never got a working product. The delivery model was broken from the start, and no budget could fix that. The real question for any business investing in digital infrastructure today is this: when the first problem surfaces in your project — and it will — will you know about it in time to act, or after it has already become a failure?

Source