Bit Reactor, the studio behind the much‑anticipated Star Wars Zero Company, made the difficult decision to furlough a significant share of its employees in the weeks leading up to the game’s debut. According to a spokesperson for the company, the move was taken before any concrete data on the launch’s performance was available and was not the result of pressure from either the publisher, Electronic Arts, or the franchise owner, Disney. The representative described the action as a "difficult decision" that had to be made in a period of uncertainty, emphasizing that the company acted independently of its external partners.
Zero Company has enjoyed a warm reception from both players and critics since its release, quickly climbing to the second spot on Steam’s top‑seller chart. Despite the positive market response, internal sources disclosed to Game File that approximately 80 percent of Bit Reactor’s staff were placed on furlough, leaving only a skeletal crew to monitor and resolve any bugs that might emerge after launch. This drastic reduction in manpower was reportedly driven by the studio’s financial situation; insiders say the company had exhausted most of its cash reserves just before the game went live.
Zachariah Scott, a former senior technical artist at Bit Reactor, took to LinkedIn to allege that the studio had been trying to hide the extent of the furloughs from the public. In his post, Scott claimed that the company was "concealing the fact that the team was furloughed weeks ago" and described the budgetary environment during his tenure as "tight".
He recounted conversations with founder Greg Foertsch, who frequently expressed hope that a new development deal could provide the financial lifeline needed to keep the studio afloat. Scott also mentioned that developers had requested additional lightsaber animations for the game, but those ideas were rejected due to insufficient funds, underscoring the austerity under which the project was completed.
The Bit Reactor spokesperson added that the studio hopes to re‑engage the furloughed employees once the launch proves successful, suggesting that a strong commercial performance could generate the resources required to bring staff back on board. However, Scott noted that many of his former colleagues were skeptical about the likelihood of regaining their previous positions, even if the game’s sales were robust. This uncertainty has contributed to a sense of unease among the remaining team members, who are now tasked with handling post‑launch support with limited resources. The furloughs have also surfaced in legal proceedings.
In 2024, former chief operating officer Alison Kelly filed a lawsuit that highlighted not only the mass furloughs but also the termination of several contractors. The lawsuit centers on a dispute over ownership of Bit Reactor, with Kelly asserting that she should be recognized as a co‑owner alongside founder Greg Foertsch.
Kelly points to a draft operating agreement from April 2021 that proposed splitting the company’s equity among herself, Foertsch, and early co‑founder Tom Whittaker. Both Whittaker and another co‑founder, Steve Meyer, have since departed from the studio. Foertsch’s legal team counters that the draft agreement was never executed, arguing that Kelly never attained ownership status and that her dismissal was due to poor performance. Kelly refutes these claims and is seeking more than $20 million in damages, alleging that she was unfairly pushed out of the company.
The broader context of this situation reflects the volatility that many mid‑size game developers face in today’s market. While a successful launch can catapult a studio into financial stability, the period leading up to release is often fraught with cash‑flow challenges, especially when development costs run high and external funding is limited.
Bit Reactor’s experience illustrates how a studio can be forced to make harsh staffing decisions in an effort to preserve its core operations, even when the product itself is well‑received. Industry observers note that the practice of furloughing staff—temporarily laying them off with the expectation of rehiring later—has become more common in the gaming sector, particularly after the pandemic-induced surge in development costs and the subsequent tightening of investment capital. For employees, furloughs create a precarious situation: they retain a formal connection to the company and may receive limited benefits, but they lose regular income and face uncertainty about future employment. In the case of Bit Reactor, the remaining team is tasked with maintaining the game’s live services, addressing player‑reported bugs, and possibly rolling out post‑launch content—all while operating with a fraction of the original workforce.
This scenario puts additional pressure on the developers who stayed, potentially leading to longer response times for bug fixes and updates, which could affect player satisfaction over time. Looking ahead, the studio’s fate may hinge on several factors: the sustained sales performance of Star Wars Zero Company, the ability to secure additional publishing or development deals, and the outcome of Kelly’s lawsuit.
If the game continues to generate strong revenue, Bit Reactor might be able to restore its full staff and resume normal development cycles. Conversely, prolonged legal battles and ongoing financial strain could force the studio to consider more drastic measures, such as selling assets or merging with another company. For now, the community of players and industry analysts will be watching closely to see how Bit Reactor navigates this turbulent period.
The company’s public statements suggest optimism about a potential rebound, but the reality on the ground—marked by a reduced team, legal disputes, and lingering doubts among former employees—paints a more complex picture of a studio striving to survive in a highly competitive market.