Bit Reactor, the studio behind the much‑anticipated title Star Wars Zero Company, made the difficult choice to place a substantial segment of its staff on furlough in the weeks leading up to the game’s debut. According to a spokesperson for the company, the decision was taken "before it was clear how the launch would go" and was not the result of any pressure from publisher Electronic Arts or the Star Wars IP holder Disney.
The representative described the move as a "difficult decision" driven by financial realities that the studio faced just prior to the release. Star Wars Zero Company has been warmly received by both players and critics, quickly climbing to the second spot on Steam’s top‑seller chart. Despite the positive reception, insiders told Game File that approximately 80 percent of Bit Reactor’s workforce had been furloughed, leaving only a skeleton crew to monitor the game for bugs and to provide post‑launch support. The source explained that the furloughs were a direct consequence of the studio "running out of most of its money just ahead of the launch of its first game," a situation that forced management to cut costs dramatically.
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 the studio’s budget had been "tight" throughout his tenure and that founder Greg Foertsch frequently expressed hope of securing a new publishing deal to keep the operation afloat. Scott recounted that developers had requested additional lightsaber animations to enhance the combat experience, but were told that the budget could not accommodate those enhancements. He characterized the development process as one carried out under "shocking austerity," with resources stretched to the breaking point. The Bit Reactor spokesperson also mentioned that the company hoped to re‑hire the furloughed employees once the launch proved successful, suggesting that a strong commercial performance could provide the financial breathing room needed to bring staff back.
However, Scott noted that many of his former colleagues were skeptical, believing that even if the game generated significant revenue, there was no guarantee that all furloughed workers would be reinstated to their previous positions. The furlough situation has also surfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly.
In her filing, Kelly alleges 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 points to a draft operating agreement from April 2021 that proposed dividing the company’s shares among 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 counters that the draft agreement was never signed, arguing that Kelly never became an owner and that her termination was due to poor performance. Kelly denies these accusations and is seeking more than $20 million in damages, claiming she was unfairly pushed out of the company. The broader context of the furloughs reflects the precarious financial landscape many indie and mid‑size developers navigate when launching a high‑profile title.
Developing a Star Wars‑licensed game entails substantial licensing fees, marketing commitments, and the need to meet the expectations of a passionate fan base. For a studio like Bit Reactor, which was essentially betting its future on a single product, the stakes were especially high.
When revenue projections fell short of the cash needed to sustain payroll, the only viable short‑term remedy was to reduce labor costs through furloughs. Furloughs differ from outright layoffs in that they are intended to be temporary, with employees retaining benefits and the possibility of returning once the company’s financial health improves. However, the uncertainty surrounding a game's performance can make it difficult for staff to rely on a return. In Bit Reactor’s case, the rapid ascent of Zero Company on Steam’s charts may provide some optimism, but the legal disputes and internal morale challenges could complicate any plans to re‑engage the majority of the workforce.
Industry observers note that the situation underscores the importance of diversified revenue streams and contingency planning for developers handling licensed properties. While a successful launch can generate a windfall, the period leading up to release is often fraught with cash‑flow constraints. Studios that can secure secondary funding, stagger development milestones, or negotiate more favorable licensing terms may be better positioned to avoid drastic measures like mass furloughs. For the players, the immediate concern is whether the reduced team can effectively address post‑launch bugs and deliver timely updates.
The skeleton crew remaining at Bit Reactor is tasked with monitoring server stability, patching critical issues, and responding to community feedback. Their limited capacity may result in slower response times, but the company has indicated a commitment to maintaining the game's quality. In summary, Bit Reactor’s decision to furlough a large portion of its staff highlights the financial pressures that can accompany the launch of a high‑profile, licensed game. While the studio hopes that strong sales of Star Wars Zero Company will enable it to bring back its workforce, the ongoing legal battle involving former COO Alison Kelly adds another layer of complexity.
The outcome of both the game’s commercial performance and the lawsuit will likely determine the future stability of Bit Reactor and its ability to retain talent for future projects.