Bit Reactor, the studio behind the much‑anticipated title Star Wars Zero Company, made the difficult decision to furlough a substantial segment of its staff in the weeks leading up to the game’s debut. According to a spokesperson for the company, the move was taken "before it was clear how the launch would go" and was not the result of any pressure from the publisher Electronic Arts or the franchise owner Disney. The representative described the choice as a "difficult decision" driven by financial realities rather than external influence. Zero Company has been warmly received by both players and critics since its release, quickly climbing the charts to secure the second spot on Steam’s top‑seller list.
Despite the positive reception, insiders revealed that approximately 80 percent of Bit Reactor’s workforce had been placed on furlough, leaving only a skeletal crew to monitor the game for bugs and to provide post‑launch support. The furloughs were reportedly necessary because the studio had "run out of most of its money just ahead of the launch of its first game," according to sources familiar with the situation. Former senior technical artist Zachariah Scott took to LinkedIn to allege that the studio had been "concealing the fact that the team was furloughed weeks ago." In an interview with Game File, Scott added that budgets during his tenure were "tight" and that founder Greg Foertsch frequently expressed hope that a new publishing deal might keep the operation afloat.
Scott recounted that developers had requested additional lightsaber animations to enhance the combat experience, but those ideas were dismissed due to insufficient funds. He described the overall development environment as one of "shocking austerity," where creative ambitions were constantly weighed against a dwindling cash reserve.
The Bit Reactor spokesperson also hinted at optimism, stating that the studio hoped to re‑hire the furloughed employees if the launch proved financially successful. The idea was that a strong commercial performance could generate the revenue needed to bring the displaced staff back on board.
However, Scott noted that many of the workers he spoke with were skeptical. They feared that even if the game generated a profit, there was no guarantee that all furloughed staff would be reinstated to their previous positions. The furlough controversy resurfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly.
In her filing, Kelly highlighted that the studio had also terminated several contractors during the same period. The lawsuit centers on a dispute over ownership stakes in Bit Reactor.
Kelly argues that she should be recognized as a co‑owner, pointing to a draft operating agreement from April 2021 that proposed splitting the company’s equity among founder Greg Foertsch, herself, and early co‑founder Tom Whittaker. Both Whittaker and another co‑founder, Steve Meyer, have since departed the studio. Foertsch’s legal team countered that the draft agreement was never executed, meaning Kelly never obtained an ownership interest.
They also claimed that Kelly was dismissed for poor performance, a charge she vehemently denies. In response, Kelly is seeking more than $20 million in damages, alleging that the termination and the handling of the furloughs were part of a broader pattern of mismanagement and exclusion.
The situation at Bit Reactor underscores a growing tension in the video‑game industry between creative ambition and financial sustainability. Small and mid‑size studios often operate on razor‑thin margins, especially when they are developing a high‑profile licensed title like Star Wars.
The pressure to deliver a polished product on time can lead to cost‑cutting measures that affect staff morale and long‑term stability. In Bit Reactor’s case, the decision to furlough a large portion of its team just before the launch reflects both the precarious cash flow that many indie developers face and the high stakes associated with a blockbuster franchise. From a broader perspective, the Bit Reactor episode raises several questions for developers, publishers, and investors alike. How should studios balance the need for fiscal prudence with the responsibility to maintain a stable workforce?
What safeguards can be put in place to protect employees from abrupt furloughs or terminations when a project’s financial outlook changes suddenly? And how might publishers like Electronic Arts or licensors such as Disney intervene—or refrain from intervening—when a partner studio encounters financial distress?
Industry observers note that while the legal battle between Foertsch and Kelly is still unfolding, the outcome could set a precedent for how ownership agreements are drafted and enforced in the future. Clear, signed contracts that delineate equity distribution and decision‑making authority are essential to prevent disputes that can jeopardize a studio’s operations and its employees’ livelihoods.
Meanwhile, the remaining Bit Reactor team continues to monitor Zero Company for any post‑release issues. Players have reported a few minor bugs, but the core experience remains solid, contributing to the game’s strong sales performance. Whether the financial windfall from the launch will be sufficient to re‑hire the furloughed staff remains uncertain, but the studio’s public statements suggest that they are hopeful.
In summary, Bit Reactor’s pre‑launch furloughs illustrate the harsh realities that can accompany the development of high‑profile games. While the company strives to recover and possibly bring its former employees back, the ongoing lawsuit and the broader industry implications highlight the need for transparent governance and realistic budgeting within the fast‑moving world of video‑game production.