Bit Reactor, the studio behind the much‑anticipated title Star Wars Zero Company, took the drastic step of furloughing a substantial segment of its staff in the weeks leading up to the game’s debut. According to a spokesperson for the company, the move was a "difficult decision" made before the outcome of the launch could be assessed, and it was not driven by external pressure from the publisher Electronic Arts or the franchise owner Disney. The studio emphasized that the timing was intended to protect the company’s financial stability in a period of uncertainty. Zero Company has been met with enthusiasm from both players and critics, quickly climbing to the No.
2 spot on Steam’s top‑seller chart. Despite the positive reception, internal sources disclosed that about 80 % of Bit Reactor’s workforce had been placed on furlough, leaving only a skeletal crew to monitor and fix any bugs that might emerge after the game goes live. This dramatic reduction in personnel was reportedly the result of the studio exhausting most of its cash reserves just before the launch of its inaugural title. 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 described the budgeting environment at Bit Reactor as "tight" throughout his tenure, noting that founder Greg Foertsch frequently expressed hope of landing a new development deal that could sustain the studio’s operations.
Scott recalled that developers had requested additional lightsaber animation work, but those ideas were shelved due to insufficient funds, characterizing the overall development process as one carried out under "shocking austerity." The Bit Reactor representative added that the company hoped the furloughed employees could be rehired if the launch proved successful, suggesting that a strong commercial performance might generate the cash flow needed to bring staff back on board. However, Scott pointed out that many of his former colleagues were skeptical about the likelihood of being reinstated, even if the game generated significant revenue. Their concerns reflected a broader unease about the studio’s long‑term viability and the fairness of the furlough strategy. The furloughs also feature in a 2024 lawsuit filed by former chief operating officer Alison Kelly.
In her filing, Kelly alleges that Bit Reactor not only furloughed employees but also terminated contractors, and she disputes the ownership structure of the company. The lawsuit centers on whether Kelly holds a co‑ownership stake alongside founder Greg Foertsch, or whether Foertsch is the sole proprietor. Kelly cites a draft operating agreement from April 2021 that would have allocated 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 executed, arguing that Kelly never became an owner and that her termination was justified by poor job performance.
Kelly refutes these claims and is seeking more than $20 million in damages, asserting that she was unfairly pushed out and that the studio’s leadership misrepresented the company’s financial health. The situation at Bit Reactor highlights the precarious nature of indie game development, especially when a studio bets its future on a single high‑profile title. While the Star Wars franchise brings considerable brand recognition, it also comes with high expectations and costly licensing fees. For a relatively small studio, managing cash flow while delivering a polished product can be a daunting balancing act.
The decision to furlough the majority of staff before launch suggests that Bit Reactor was operating on a very thin margin, with limited runway to absorb any post‑release issues such as patches, updates, or community support. Industry observers note that such pre‑launch furloughs are rare but not unheard of. In many cases, studios opt to delay payments or reduce salaries rather than lay off large portions of their workforce outright. Bit Reactor’s approach, however, indicates a more severe cash crunch, possibly exacerbated by the costs associated with securing the Star Wars license and meeting the high production values expected by fans of the franchise.
From a broader perspective, the case raises questions about the sustainability of relying on a single blockbuster title to sustain a studio’s operations. Diversification—through multiple projects, early access releases, or service‑based revenue models—can provide a buffer against the financial volatility inherent in the games industry. Bit Reactor’s experience may serve as a cautionary tale for other developers considering similar high‑risk, high‑reward ventures.
Looking ahead, the fate of the furloughed employees will likely depend on the commercial performance of Star Wars Zero Company. If the game maintains strong sales, generates ongoing microtransactions, or spawns downloadable content that keeps players engaged, the studio may find the resources to rehire its former staff. Conversely, if sales plateau or the game encounters technical setbacks that require extensive post‑launch support, Bit Reactor may be forced to keep its workforce trimmed or even consider further reductions.
For now, the remaining skeleton crew is tasked with monitoring live servers, addressing bug reports, and ensuring that the player experience remains smooth. Their workload is amplified by the reduced manpower, meaning each team member must wear multiple hats—ranging from quality assurance to community management. This situation underscores the resilience and dedication of the remaining staff, who continue to support a product that has already garnered significant attention. In summary, Bit Reactor’s decision to furlough a large portion of its workforce just before the launch of Star Wars Zero Company reflects a combination of financial strain, strategic risk‑taking, and the high stakes associated with developing a licensed, high‑profile game.
The ongoing legal dispute adds another layer of complexity, potentially affecting the studio’s future ownership and operational structure. As the game continues to climb the sales charts, all eyes will be on whether the studio can translate that commercial success into a stable, sustainable future for its employees and stakeholders.