Bit Reactor, the studio behind the highly anticipated 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 company spokesperson, the move was taken before any clear picture of the launch’s performance could be formed, and it was not dictated by the game’s publisher, Electronic Arts, nor by the franchise owner, Disney. The representative described the choice as "a difficult decision" that had to be made in advance of knowing how the market would respond. Zero Company has been welcomed by both gamers and critics, quickly climbing to the second spot on Steam’s best‑selling titles chart.
Despite the positive reception, insiders revealed that roughly 80 percent of Bit Reactor’s workforce was placed on furlough, leaving only a skeletal crew to monitor and patch any bugs that might surface after the game goes live. Sources close to the studio told Game File that the furloughs were driven by a near‑complete depletion of the company’s cash reserves just before the launch of its first title. Former senior technical artist Zachariah Scott took to LinkedIn to allege that the studio had been trying to hide the fact that the majority of its team had been furloughed weeks earlier. In his post, Scott explained that the studio’s budget had been extremely tight throughout his tenure, and that founder Greg Foertsch frequently expressed hopes of securing a new development deal to keep the operation afloat.
Scott recalled that his colleagues had requested additional lightsaber animation work, only to be told that the budget could not accommodate the extra expense. He summed up the development environment as one of "shocking austerity." When asked about the possibility of rehiring the furloughed staff, Bit Reactor’s spokesperson indicated optimism, suggesting that a successful launch could generate enough revenue to bring many of those workers back. However, Scott noted that the employees he spoke with were skeptical; they doubted that even a profitable launch would guarantee the restoration of their former positions.
Their concerns were amplified by a 2024 lawsuit filed by former chief operating officer Alison Kelly, which also mentioned the termination of several contractors. The legal dispute centers on the ownership structure of Bit Reactor. Kelly claims she is a co‑owner of the studio, arguing that a draft operating agreement from April 2021 proposed an equity split among founder Greg 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 counters that the draft agreement was never executed, meaning Kelly never attained ownership status, and they further contend that she was dismissed for inadequate performance. Kelly refutes these allegations and is pursuing more than $20 million in damages. The situation at Bit Reactor underscores the precarious nature of independent game development, especially when a studio is betting its future on a single high‑profile release.
While the Star Wars license provides a significant promotional boost, the financial realities of game production—licensing fees, marketing costs, and the need for a sizable development team—can quickly drain a studio’s resources. In Bit Reactor’s case, the company appears to have exhausted most of its capital just as the product was about to hit the market, prompting the drastic measure of furloughing the bulk of its staff. Industry observers note that such large‑scale furloughs are relatively rare in the gaming sector, where studios typically prefer to retain talent through a launch and then make gradual reductions if sales fall short.
The decision to cut back so dramatically before seeing any revenue suggests that Bit Reactor may have been operating on a very thin runway, perhaps relying on external funding that fell through or on optimistic sales projections that were not yet realized. From a broader perspective, the Bit Reactor episode raises questions about how publishers and IP holders manage risk with smaller partners. Although EA and Disney were not directly involved in the furlough decision, their contracts and licensing agreements likely contain clauses that could affect the studio’s financial obligations and future collaborations.
The outcome of Kelly’s lawsuit could also set a precedent for how ownership disputes are handled in rapidly evolving startup environments, where informal agreements and draft documents sometimes become the basis for serious legal battles. For players, the immediate concern is whether the reduced team can adequately support Zero Company after launch.
A skeleton crew may be able to address critical bugs, but more extensive updates, content expansions, or community‑driven features could be delayed or canceled altogether. The long‑term health of the game—and by extension, the studio—may hinge on the commercial success of this first title and the ability of Bit Reactor to rebuild its workforce. In summary, Bit Reactor’s pre‑launch furloughs reflect a confluence of financial strain, ambitious development goals, and legal complexities. While the game itself has been well received, the studio now faces the dual challenges of maintaining a functional post‑launch support team and navigating a contentious ownership lawsuit.
The ultimate resolution will likely influence not only the fate of Zero Company but also the broader conversation about sustainability and equity in indie game development.