Nana Wu
The landscape of the video game industry has been defined by a brutal wave of contractions over the last eighteen months, but few studios have experienced a decline as precipitous or as controversial as Build a Rocket Boy (BARB). The developer behind the ambitious, high-concept title MindsEye—a project envisioned as a cornerstone of a new interactive entertainment ecosystem—is currently navigating what appears to be its most devastating period of instability to date.
Following reports surfacing this week, it has become clear that the studio has undergone yet another significant reduction in its workforce. With recent estimates suggesting that only approximately 80 staff members remain at the company, the developer is a shadow of the organization that once boasted a massive, global headcount. This latest round of cuts marks a desperate attempt to stabilize a company that has been plagued by performance issues, shifting corporate strategies, and allegations of external sabotage.
The Current State of Affairs: A Studio Reeling
The latest wave of layoffs has reportedly claimed 170 positions, gutting key departments including technical level design, audio engineering, and quality assurance (QA). The scale of these departures, confirmed in part by departing staff on the studio’s official Discord server, represents a massive loss of institutional knowledge.
For a studio that was designed to build a sprawling, multi-layered "Everywhere" platform, losing the technical talent responsible for the foundational architecture of MindsEye creates an existential threat to the project’s future. The current headcount—a mere 80 employees—raises urgent questions regarding the feasibility of continued development. Can a team of this size support a title that requires massive technical oversight, ongoing server maintenance, and complex performance optimization?
A Chronology of Decline: From Ambition to Austerity
To understand the current crisis, one must look at the rapid-fire succession of negative events that have defined Build a Rocket Boy’s last year.
2022: The Height of Optimism
The company’s trajectory began with significant promise. Following the announcement of the studio’s expansion into Montpellier, France, the company was in a period of aggressive hiring. The vision for MindsEye and its parent platform was grand, attracting veteran talent and substantial investment.
March 2025: The First Signs of Fracture
The cracks began to show in the spring of 2025. The company announced the closure of its French studio in Montpellier, a move that sent shockwaves through the local development scene. This was quickly followed by reports of layoffs in March, which CEO Mark Gerhard controversially framed as a response to "organized espionage and corporate sabotage."
July 2025: The Mass Redundancy Event
The situation worsened significantly in mid-2025, when approximately 300 UK-based employees were issued "at-risk" notices. This mass redundancy event was the largest in the company’s history and effectively dismantled the studio’s mid-level management and support layers.
Late 2025: The Publishing Pivot and Continued Attrition
The end of the year brought the formal dissolution of the company’s publishing agreement with IOI Partners. This decoupling was widely interpreted by industry analysts as a sign that the company was struggling to secure a viable path to market for MindsEye. When the news broke, CEO Mark Gerhard issued a sobering statement warning that layoffs were not yet finished, setting the stage for the current catastrophe.
Analysis of the "Espionage" Narrative
Perhaps the most peculiar aspect of the Build a Rocket Boy saga is the rhetoric employed by leadership. CEO Mark Gerhard has repeatedly cited external interference, specifically "corporate sabotage" and "organized espionage," as the primary drivers for the studio’s failures.
According to Gerhard, bad actors allegedly manipulated the perception of MindsEye at launch, ensuring that the product did not receive a "fair chance" to find its community. While it is true that the game faced significant backlash due to performance issues, bugs, and a perceived lack of polish, many industry observers remain skeptical of the espionage narrative.
From a PR perspective, blaming sabotage is a high-risk strategy. It positions the studio as a victim of a systemic conspiracy rather than a victim of its own development pipeline or project management shortcomings. However, this narrative served a specific purpose: it allowed the studio to initiate a "reset" phase. By framing the initial launch as a "sabotaged" release rather than a failed one, the company has attempted to clear the slate for a future marketing push, though investors and former employees alike remain unconvinced.
Implications: Can MindsEye Survive?
The "reset" of MindsEye is now being marketed as a "new phase of ongoing development." For a product to successfully pivot after such a disastrous launch, it requires a robust, energized, and well-funded team. With the staff reduced to roughly 80 people, the "new phase" faces three primary hurdles:
1. Technical Debt
MindsEye was plagued by performance issues at launch. Fixing these requires deep, granular work on the game’s engine and optimization layers. With the loss of specialized QA and technical design staff, the remaining team is left with a massive technical debt that will be difficult to clear.
2. Loss of Public Trust
The gaming community is notoriously unforgiving. Once a "live-service" or ambitious platform project loses its momentum, regaining the interest of the player base is a Herculean task. The constant cycle of layoffs creates a negative feedback loop: news of staff cuts leads to player concern about the game’s longevity, which leads to lower engagement, which ultimately validates the decision to cut more staff.
3. Operational Sustainability
Maintaining a studio is an expensive endeavor. Even with a reduced headcount, the overhead of operating the remaining infrastructure is substantial. Without a major publishing partner (following the IOI Partners split) or a massive infusion of new capital, the runway for MindsEye is likely very short.
Conclusion: The Industry’s Cautionary Tale
The story of Build a Rocket Boy is indicative of a broader, uncomfortable truth within the current gaming industry. The era of "unlimited growth" and massive, open-ended development projects is being replaced by an era of extreme fiscal conservatism.
When a studio grows too fast, as BARB did, it builds a complex machine that requires constant, high-level investment to maintain. When the funding slows or the product fails to meet immediate KPIs, that complexity becomes a liability. The "reset" of MindsEye is not just a game update; it is a desperate effort to downsize the company into a configuration that can survive the winter.
For the 170 employees who were let go in this latest round, the human cost is the most significant aspect of this story. For the 80 who remain, the challenge is nearly insurmountable. As the studio enters its next chapter, the industry will be watching closely to see if the vision for MindsEye can survive the wreckage of the company’s recent history, or if the "reset" is merely a prelude to a final, inevitable shutdown.
The silence from leadership regarding the specific plans for the remaining staff suggests that Build a Rocket Boy is no longer in a position of strength. They are in a position of survival, and the road ahead for MindsEye remains clouded by doubt, uncertainty, and the lingering echoes of a workforce that has been fundamentally dismantled.
Ali Ikhwan
Iffa Jayyana
