Bit Reactor, the studio behind the much‑anticipated Star Wars Zero Company, made the difficult decision to furlough a substantial segment of its employees in the weeks leading up to the game’s release. 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 Star Wars IP holder Disney.
The spokesperson emphasized that the timing of the furloughs was driven by internal financial constraints rather than external demands. Zero Company has been warmly received by both players and critics since it hit the market, quickly climbing to the No. 2 spot on Steam’s top‑seller chart. Despite the positive reception, insiders revealed that roughly 80 % of Bit Reactor’s staff were placed on furlough, leaving only a skeletal crew to monitor the game for bugs and provide post‑launch support.
This drastic reduction in manpower has raised concerns about the studio’s ability to address technical issues that inevitably arise after a high‑profile launch. Sources close to the situation told Game File that the primary reason for the furloughs was a near‑complete depletion of the studio’s cash reserves just before the game’s debut. The financial strain meant that Bit Reactor could no longer sustain its full payroll, prompting leadership to cut costs dramatically. Former senior technical artist Zachariah Scott took to LinkedIn to allege that the studio had been trying to hide the fact that the team had been furloughed weeks earlier.
In his post, Scott described the studio’s budget as "tight" throughout his tenure and recounted that founder Greg Foertsch frequently expressed hopes of securing a new development deal to keep the company afloat. Scott also shared specific examples of how the austerity measures impacted development. He recalled that developers had requested additional lightsaber animation sequences to enrich the gameplay experience, 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 creative ambitions were constantly weighed against the stark reality of limited funds. The Bit Reactor representative reiterated that the studio’s intention was to bring furloughed employees back once the launch proved successful.
The spokesperson suggested that a strong commercial performance could generate the revenue needed to re‑hire the displaced workers. However, Scott noted that many of the staff he spoke with were skeptical about the likelihood of being rehired, even if the game generated a profit.
Their concerns stemmed from the uncertainty surrounding the company’s financial health and the lack of concrete assurances from management. The furloughs have also become a focal point in a 2024 lawsuit filed by former chief operating officer Alison Kelly.
In her filing, Kelly highlighted that Bit Reactor not only furloughed employees but also terminated several contractors. The lawsuit centers on a dispute over ownership of the studio. Kelly claims that she should be recognized as a co‑owner, referencing a draft operating agreement from April 2021 that proposed splitting equity among Foertsch, herself, and early co‑founder Tom Whittaker. While Whittaker and another co‑founder, Steve Meyer, have since left the company, Kelly argues that the draft indicated an intention to share ownership.
Foertsch’s legal team responded by stating that the draft agreement was never signed, implying that Kelly never acquired an ownership stake. They further alleged that Kelly’s termination was due to poor performance, a claim she vehemently denies.
Kelly is seeking more than $20 million in damages, asserting that the wrongful termination and the mishandling of the furloughs caused significant personal and professional harm. The situation at Bit Reactor underscores the precarious nature of indie game development, especially when a studio invests heavily in a high‑budget title tied to a major franchise.
While the success of Star Wars Zero Company on platforms like Steam demonstrates strong consumer interest, the behind‑the‑scenes financial turmoil reveals how quickly a promising project can be jeopardized by cash flow issues. Industry observers note that such financial pressures are not uncommon in the gaming sector, where development costs can balloon quickly and revenue streams are often uncertain until after launch. For the remaining Bit Reactor team, the focus now is on maintaining the game’s stability and addressing any post‑launch bugs that surface. With a reduced workforce, this task is more challenging, but the studio has pledged to prioritize critical fixes to preserve the game’s reputation.
Meanwhile, former employees and contractors are watching closely to see whether the promised rehiring will materialize or if the studio will need to seek external investment or a partnership to survive. The broader implications of this case may also affect how publishers and IP holders approach contracts with smaller studios.
While EA and Disney were not directly involved in the decision to furlough staff, the incident highlights the importance of clear financial planning and contingency measures when developing high‑stakes titles. As the legal battle between Kelly and Foertsch unfolds, it could set precedents for ownership disputes and employee rights within the rapidly evolving game development landscape. In summary, Bit Reactor’s pre‑launch furloughs reflect a confluence of financial strain, ambitious development goals, and internal disagreements over ownership.
The studio’s future hinges on the commercial performance of Star Wars Zero Company, the outcome of the ongoing lawsuit, and whether it can secure additional funding to re‑expand its workforce and continue delivering support for its flagship title.