Bit Reactor, the studio behind the eagerly anticipated Star Wars Zero Company, made the difficult choice to furlough a substantial number of its employees in the weeks leading up to the game’s release. A spokesperson for the company told Game File that the decision was taken "before it was clear how the launch would go" and described it as a "difficult decision" that was not dictated by the publisher Electronic Arts or the Star Wars IP holder Disney. The move was framed as a financial necessity rather than an external pressure from partners. Zero Company has been met with enthusiastic responses from both players and critics, quickly climbing to the No.
2 spot on Steam’s top‑seller chart. Despite the strong market reception, insiders revealed that about 80 % of Bit Reactor’s staff were placed on furlough, leaving only a skeletal crew to monitor and fix any bugs that might emerge after launch. The furloughs, according to sources, stemmed from the studio having "run out of most of its money just ahead of the launch of its first game." Former senior technical artist Zachariah Scott took to LinkedIn to allege that the studio was "concealing the fact that the team was furloughed weeks ago." In an interview with Game File, Scott explained that budgets had been "tight" throughout his tenure and that founder Greg Foertsch often spoke about the need to secure a new game deal in order to keep the operation afloat.
Scott recalled that developers had requested additional lightsaber animation work, only to be told that the budget could not accommodate the extra polish. He summed up the development environment as one of "shocking austerity," indicating that cost‑cutting measures were pervasive across the project. The Bit Reactor representative added that the studio hoped to re‑hire the furloughed workers once the launch proved successful, suggesting that a strong commercial performance could generate the cash flow needed to bring staff back.
However, Scott noted that many of his former colleagues were skeptical about the likelihood of regaining their previous positions, even if the game performed well financially. This uncertainty contributed to a sense of unease among the remaining team members.
The furlough issue 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 employees but also terminated contractors. The legal dispute centers on whether Kelly holds co‑ownership of Bit Reactor or whether Greg Foertsch is the sole proprietor. Kelly cites a draft operating agreement from April 2021 that proposed splitting equity among Foertsch, herself, and early co‑founder Tom Whittaker.
Both Whittaker and another co‑founder, Steve Meyer, have since departed the company. Foertsch’s legal team argues that the draft agreement was never executed, implying that Kelly never became an owner and that her termination 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 Bit Reactor’s financial strain reflects a common challenge for indie studios that take on high‑profile licensed projects. Developing a Star Wars title brings both significant opportunity and considerable risk, as licensing fees and expectations from a massive fan base can quickly outpace a small studio’s cash reserves.
In Bit Reactor’s case, the timing of the furloughs—just before the launch—suggests that the company was operating on a razor‑thin margin, hoping that initial sales would cover remaining obligations and possibly fund a rehiring wave. From a player perspective, the situation raises concerns about post‑launch support. With only a skeleton crew left to address bugs, patches, and community feedback, there is a risk that critical issues could linger longer than usual.
However, the studio’s public statements emphasize a commitment to fixing problems promptly, leveraging the remaining talent pool to prioritize the most impactful bugs. Industry observers note that the Bit Reactor scenario underscores the volatility of the modern gaming market, where even a title that quickly ascends the sales charts can be plagued by internal financial turbulence.
The case also highlights the importance of transparent communication with both staff and the player community. While Bit Reactor has indicated an intention to bring back furloughed workers, the lack of concrete timelines fuels speculation about the studio’s long‑term viability.
In summary, Bit Reactor’s decision to furlough roughly four‑fifths of its workforce was driven by an acute cash shortfall just before the release of Star Wars Zero Company. The move was made independently of EA and Disney, and the company maintains that a successful launch could enable the rehiring of affected staff. Meanwhile, former employees and a former COO have raised legal and ethical questions about the handling of contracts, equity agreements, and the overall treatment of the workforce.
As the game continues to perform strongly on Steam, the next few months will be crucial in determining whether Bit Reactor can stabilize its finances, honor its commitments to its employees, and sustain the level of post‑launch support that players expect.