Build a Rocket Boy has announced another round of job cuts, with CEO Mark Gerhard once again blaming the studio's troubles on what he calls "overwhelming evidence of organised espionage and corporate sabotage." The problem is nobody else sees that evidence, and the pile of contrary facts keeps growing.
This is worth taking seriously because it matters to the people losing their jobs. When a CEO frames redundancies as the unavoidable consequence of external criminal conspiracies rather than internal failure, it shapes how employees, investors, and the industry itself understand what went wrong. It also dodges the harder conversation about accountability.
What Actually Happened to MindsEye
MindsEye released in June 2025 to widespread critical and commercial failure. The game arrived with severe bugs, technical performance problems, and a hollow, unfinished feel. Former developers described months of relentless crunch, unpaid overtime, and erratic leadership in the lead-up to launch. Some staff members endured mandatory four-month crunch periods requiring eight additional hours of work per week.
The micromanagement was brutal. Founder Leslie Benzies personally intervened in minor design decisions through what staff called "Leslie tickets," immediate directives that had to take priority regardless of project needs. This created instability and confusion across development teams, according to former employees. When the game flopped, Benzies accused staff of sabotage during a company video call.
This isn't speculation or disgruntled noise. Roughly 100 current and former employees issued a joint letter through the Independent Workers of Great Britain union in October 2025, explicitly accusing the studio of mishandling layoffs and subjecting teams to forced crunch.
The Sabotage Narrative Isn't Holding
Gerhard has now claimed multiple times that external parties damaged the game's launch. Before release, he said bot farms were posting negative comments. Months later, he alleged a major American company had hired a UK influencer agency to run a £1 million smear campaign. Neither claim has been substantiated.
Now he says there's "overwhelming evidence" of criminal activity and promises prosecution is coming, but cannot share details because the matter is "moving toward prosecution." That's a convenient position. It allows him to make bold claims while avoiding any obligation to prove them.
IO Interactive, the publisher that handled MindsEye's release, rejected the sabotage narrative. The studio later expressed uncertainty about continuing the publishing partnership. Publisher reluctance to support a developer's conspiracy claims tells you something important.
The Real Problem Is Management
This is where the centre-right principles of fiscal responsibility and institutional accountability matter. Gerhard and Benzies had more than £230 million in investment and years of development time to deliver a competitive product. They didn't deliver. The game bombed because it was broken and badly designed.
Blaming that failure on shadowy external sabotage requires us to believe that some rival organisation infiltrated a British game studio to deliberately tank a game, rather than accept that the people in charge made decisions that produced a bad outcome. When you're looking for explanations, simpler ones are usually right.
The counterargument matters too. It's theoretically possible that external forces did interfere. Competitive sabotage exists. Industrial espionage happens. If Gerhard is telling the truth, his credibility suffers only because he hasn't proven it yet. But months of unproven claims during layoff announcements don't inspire confidence.
The Damage to Accountability
The hard question is whether a CEO announcing redundancies while simultaneously insisting external forces beyond the leadership's control caused the crisis is accepting responsibility or deflecting it. Gerhard's statement opened with "As leaders we take responsibility for the outcomes of our projects," immediately before launching into discussion of alleged sabotage. Those two positions don't sit comfortably together.
Reasonable people can disagree about whether leadership failures or external interference caused MindsEye's collapse, but the evidence strongly favours the former. Crunch culture, micromanagement, and poor design decisions are documented. Sabotage conspiracies remain unproven after months of investigation.
A pragmatic approach asks: what does the available evidence suggest? That points to internal dysfunction. What would convince us otherwise? Actual proof. Until that emerges, the burden of explaining MindsEye's failure rests with the people who made the decisions.