Bit Reactor, the studio behind the highly anticipated title Star Wars Zero Company, took the drastic step of furloughing a substantial segment of its staff in the weeks leading up to the game’s debut. According to a spokesperson for the company, the decision was a "difficult one" that had to be made "before we had any clear picture of how the launch would unfold." The representative emphasized that the move was entirely internal, stating that neither Electronic Arts, the publisher, nor Disney, the holder of the Star Wars intellectual property, had any influence over the choice to reduce the workforce.
The timing of the furloughs has raised eyebrows because Zero Company has been enjoying a wave of positive feedback from both players and critics. Within days of release, the title climbed to the No.
2 spot on Steam’s bestseller chart, a testament to its strong reception and the enthusiasm of the Star Wars fan base. Yet behind the scenes, the studio was grappling with severe financial strain. Multiple sources close to the development team told Game File that approximately 80 % of Bit Reactor’s employees were placed on furlough, leaving only a skeletal crew to monitor the live service, patch critical bugs, and keep the community experience stable.
Industry insiders suggest that the root cause of the furloughs was a cash‑flow crunch that left the studio with "almost no money left" just before the launch of its first major game. Former senior technical artist Zachariah Scott, who publicly shared his perspective on LinkedIn, accused the studio of trying to hide the fact that the majority of its staff had been furloughed weeks earlier. Scott’s comments painted a picture of a studio operating under "shocking austerity," where even seemingly minor enhancements—such as additional lightsaber animation variations—were scrapped because the budget simply could not accommodate them.
Scott also revealed that during his tenure, budgets were consistently tight, and the studio’s founder, Greg Foertsch, frequently expressed hope that a new publishing deal or a follow‑up project might inject the necessary capital to keep the operation afloat. This environment of financial uncertainty meant that many development decisions were driven more by fiscal survival than creative ambition. The Bit Reactor spokesperson added that the company’s intention was to re‑hire the furloughed employees once the launch proved successful, implying that a strong commercial performance could generate the revenue needed to bring the workforce back to full strength. However, Scott relayed that many of his former colleagues were skeptical about this promise.
They feared that even if the game generated significant returns, the company might not be able—or willing—to restore everyone to their previous positions, especially if the financial recovery was slower than anticipated. The furlough saga also surfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly.
In her complaint, Kelly highlighted that the studio not only furloughed a large portion of its staff but also terminated several contractors. The legal dispute centers on the ownership structure of Bit Reactor. Kelly claims she is a co‑owner of the company, referencing a draft operating agreement from April 2021 that proposed splitting equity among Foertsch, herself, and early co‑founder Tom Whittaker.
Both Whittaker and another original co‑founder, Steve Meyer, have since departed the studio. Foertsch’s legal team countered that the draft agreement was never executed, arguing that Kelly never obtained any ownership stake and that her termination was justified by alleged poor performance. Kelly has denied these allegations and is seeking more than $20 million in damages, asserting that she was unfairly pushed out and that the company’s leadership concealed the true state of its finances and workforce. The broader implications of Bit Reactor’s situation underscore the volatility that independent studios can face when launching a high‑profile title tied to a major franchise.
While the partnership with a globally recognized brand like Star Wars can provide a massive boost in visibility and potential sales, it also brings heightened expectations and pressure to deliver a polished product on a tight schedule. When funding runs low, studios may resort to extreme measures such as mass furloughs, which can jeopardize post‑launch support and damage morale.
From a consumer standpoint, the presence of a thin post‑launch team raises concerns about the long‑term health of the game. Players rely on timely updates, bug fixes, and new content to keep the experience fresh.
A reduced development staff may struggle to address critical issues promptly, potentially leading to a decline in player satisfaction and a negative impact on sales momentum. Looking ahead, the fate of Bit Reactor will likely hinge on several factors: the sustained commercial performance of Star Wars Zero Company, the ability of the studio to secure additional funding or a new publishing partnership, and the resolution of the ongoing legal battle with Kelly.
If the game continues to sell strongly and maintains its high ranking on platforms like Steam, there is a realistic chance that the company could recover enough capital to re‑engage its former employees and perhaps even expand its team for future projects. Conversely, if sales taper off or the legal costs become burdensome, the studio may be forced to maintain its minimal operational footprint for an extended period, potentially compromising the quality of future updates and eroding the goodwill it has built with its community.
In summary, Bit Reactor’s decision to furlough the majority of its staff just before the launch of Star Wars Zero Company reflects a precarious financial reality faced by many mid‑size developers. While the game’s early success offers a glimmer of hope, the underlying challenges—tight budgets, legal disputes, and the need for robust post‑launch support—remain significant hurdles that the studio must navigate to ensure both its short‑term stability and long‑term viability.