Bit Reactor, the studio behind the much‑anticipated title Star Wars Zero Company, made the difficult decision to place a substantial segment of its staff on furlough in the weeks leading up to the game’s debut. According to a company spokesperson speaking to Game File, the move was taken "before it was clear how the launch would go" and was not the result of any pressure from the publisher Electronic Arts or the franchise owner Disney.
The representative emphasized that the timing of the furloughs was driven by internal financial considerations rather than external mandates. Star Wars Zero Company has been met with enthusiasm from both players and critics alike, quickly climbing to the second spot on Steam’s top‑seller chart. Despite the positive reception, insiders revealed that as much as 80 percent of Bit Reactor’s workforce was placed on furlough, leaving only a skeletal crew to monitor and resolve any bugs that might surface after the game goes live. This drastic reduction in staff was reportedly caused by the studio exhausting the bulk 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 studio’s budgetary situation as "tight" throughout his tenure, noting that founder Greg Foertsch frequently expressed hope of securing a new development deal to keep the operation afloat. Scott recounted that developers had requested additional lightsaber animation sequences, only to be told that the budget could not accommodate the extra work. He characterized the overall development environment as one of "shocking austerity," where financial constraints heavily dictated creative decisions.
The Bit Reactor spokesperson added that the company hoped to re‑hire the furloughed employees if the launch proved successful, suggesting that a strong commercial performance could provide the financial breathing room needed to bring staff back on board. However, Scott pointed out that many of the workers he spoke with were skeptical about the likelihood of regaining their former positions, even in the event of a profitable launch. Their concerns stemmed from the uncertainty surrounding the studio’s cash flow and the lack of a clear plan for reinstating the majority of the workforce. The furloughs have also surfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly.
In her filing, Kelly highlighted that the studio not only furloughed employees but also terminated several contractors. The legal dispute centers on the ownership structure of Bit Reactor. Kelly asserts that she is a co‑owner of the company, referencing a draft operating agreement from April 2021 that proposed dividing the company’s equity among founder Greg 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 countered that the draft agreement was never executed, implying that Kelly never acquired an ownership stake. They further claimed that Kelly was dismissed for inadequate job performance.
Kelly denies these allegations and is seeking more than $20 million in damages, arguing that she was unfairly pushed out of the company and that the termination of staff and contractors was mishandled. The situation at Bit Reactor underscores the precarious nature of independent game development, especially when a studio bets its future on a single high‑profile title. While the enthusiasm for Star Wars Zero Company demonstrates the potential for critical and commercial success, the financial strain experienced by the studio illustrates how quickly resources can be depleted in the competitive gaming market. The remaining skeleton crew now bears the responsibility of monitoring live servers, patching bugs, and ensuring that the player community remains satisfied—all while operating with a fraction of the original development team.
Industry observers note that such furloughs are not uncommon in the sector, particularly when studios face cash‑flow challenges after a major release. However, the scale of Bit Reactor’s staff reductions—affecting roughly four‑fifths of its employees—raises questions about the studio’s long‑term viability and its ability to sustain future projects. If the game continues to perform well on platforms like Steam and potentially on console marketplaces, the influx of revenue could allow Bit Reactor to re‑hire former staff, settle outstanding contractor obligations, and perhaps even expand its development capacity for subsequent titles.
In the meantime, the legal battle between Foertsch and Kelly adds another layer of complexity to an already fraught situation. The outcome of the lawsuit could have significant implications for the ownership and governance of Bit Reactor, potentially influencing decisions about profit distribution, future hiring practices, and the overall strategic direction of the studio. Overall, the Bit Reactor case serves as a cautionary tale for developers navigating the high‑stakes world of blockbuster game launches. It highlights the importance of robust financial planning, transparent communication with staff, and clear legal agreements among founders and executives.
As the industry watches how Bit Reactor manages post‑launch support with a dramatically reduced team, the broader lesson remains clear: even a well‑received game can’t fully shield a studio from the harsh realities of budgeting, ownership disputes, and the ever‑present risk of cash shortages.