Bit Reactor, the studio behind the highly anticipated Star Wars Zero Company, made the difficult decision to place a large portion of its staff on furlough in the weeks leading up to the game’s release. According to a spokesperson for the company, the move was taken before the outcome of the launch could be evaluated, and it was not the result of any pressure from the publisher Electronic Arts or the Star Wars IP holder Disney. The representative described the choice as "a difficult decision" that had to be made "before it was clear how the launch would go," emphasizing that the studio acted independently. The game itself has been met with enthusiastic responses from both players and critics.
Since its debut, Zero Company has climbed to the second spot on Steam’s top sellers chart, reflecting strong sales and a robust community of fans eager to explore its Star Wars‑themed world. Despite the positive reception, the internal situation at Bit Reactor has been far less rosy. Multiple sources who spoke to Game File have disclosed that roughly 80 percent of Bit Reactor’s workforce were placed on furlough, leaving only a skeletal crew to monitor the game for bugs and provide post‑launch support. This dramatic reduction in staff was reportedly driven by a severe cash crunch that hit the studio just before the launch of its first title.
The company, which had been operating on a tight budget throughout development, apparently "ran out of most of its money" as the release date approached, forcing management to take drastic cost‑cutting measures. Zachariah Scott, a former senior technical artist at Bit Reactor, took to LinkedIn to allege that the studio was trying to hide the fact that the furloughs had taken place weeks earlier.
In his post, Scott described the financial environment at Bit Reactor as "tight" and noted that founder Greg Foertsch frequently spoke about the need to secure a new game deal in order to keep the studio afloat. Scott recounted that the development team had requested additional lightsaber animations to enhance the combat experience, only to be told that the budget could not accommodate such enhancements. He characterized the entire project as being built under "shocking austerity," a phrase that underscores the severe financial constraints that shaped every aspect of production.
When asked about the possibility of rehiring the furloughed employees, the Bit Reactor spokesperson expressed hope that a successful launch could generate enough revenue to bring staff members back. The statement suggested that the studio’s leadership believed a strong commercial performance might provide the financial breathing room needed to re‑engage the displaced workers.
However, Scott warned that many of the employees he spoke with were skeptical about the likelihood of regaining their former positions, even if the game performed well. He noted that confidence was low among the workforce, with concerns that the company might not be able to honor any promises of reinstatement. The furloughs have also become a point of contention in a lawsuit filed in 2024 by former chief operating officer Alison Kelly.
In her legal filing, Kelly highlighted that Bit Reactor not only furloughed a majority of its staff but also terminated several contractors. The lawsuit revolves around a dispute over ownership stakes in the company. Kelly argues that she should be recognized as a co‑owner alongside founder Greg Foertsch, citing a draft operating agreement from April 2021 that proposed dividing the company’s shares among Foertsch, Kelly, and early co‑founder Tom Whittaker.
While Whittaker and another co‑founder, Steve Meyer, have since departed the studio, the draft agreement remains a focal point of the legal battle. Foertsch’s legal team counters that the draft agreement was never executed, asserting that Kelly never became an equity holder and that her termination was due to unsatisfactory performance.
Kelly, however, denies these allegations and is seeking more than $20 million in damages, claiming that the termination and the subsequent furloughs were part of a broader pattern of mismanagement and unfair treatment. The situation at Bit Reactor illustrates a broader challenge facing many indie developers in the modern gaming industry: the need to balance creative ambition with financial sustainability.
While Zero Company’s strong launch on Steam demonstrates that the product itself resonated with consumers, the studio’s internal financial woes reveal how precarious the economics of game development can be. The reliance on a single title for cash flow, combined with limited access to external funding, left Bit Reactor vulnerable to cash shortages at a critical juncture. Industry observers note that such scenarios are not uncommon, especially for studios that operate without the deep pockets of larger publishers.
The decision to furlough a large portion of staff can be a double‑edged sword: it reduces immediate expenses, but it also risks eroding morale, damaging the studio’s reputation, and potentially compromising post‑launch support. In the case of Bit Reactor, the remaining skeleton crew is tasked with addressing any bugs that emerge after release, a responsibility that can be overwhelming without adequate manpower.
Looking ahead, the future of Bit Reactor hinges on several variables. If Zero Company continues to sell strongly and perhaps expands onto additional platforms, the influx of revenue could enable the studio to rehire some of its former employees and stabilize operations. Conversely, if sales plateau or if the game encounters significant technical issues that require extensive patches, the limited staff may struggle to keep pace, potentially leading to further negative press and consumer dissatisfaction. For the employees who were furloughed, the uncertainty extends beyond the immediate loss of income.
Many in the gaming industry rely on continuous employment to maintain skill relevance and professional networks. A prolonged period of inactivity can make it harder to secure new positions, especially in a competitive market where studios often look for candidates with recent project experience. In summary, Bit Reactor’s pre‑launch furloughs reflect a stark reality: even a critically acclaimed, commercially successful game does not guarantee financial security for its creators.
The studio’s leadership faces the delicate task of navigating post‑launch support with a reduced team while attempting to rebuild confidence among its workforce and resolve ongoing legal disputes. The outcome will likely serve as a cautionary tale for other independent developers about the importance of robust financial planning, transparent communication with staff, and the potential long‑term ramifications of cost‑cutting measures taken at the eleventh hour.