Bit Reactor, the studio behind the newly released Star Wars Zero Company, announced that it had placed a significant number of its employees on furlough in the weeks leading up to the game’s debut. A company spokesperson told Game File that the decision was a "difficult choice" made before the outcome of the launch could be assessed, and emphasized that neither Electronic Arts, the publisher, nor Disney, the holder of the Star Wars licence, had any role in prompting the move. Zero Company has been met with enthusiastic reviews from both players and critics, quickly climbing to the No.
2 spot on Steam’s top‑seller chart. Despite the strong market reception, insiders disclosed to Game File that roughly eighty percent of Bit Reactor’s staff were put on furlough, leaving only a skeletal crew to monitor and patch any bugs that surface after launch. The underlying reason, according to the spokesperson, was that the studio had "run out of most of its money just ahead of the launch of its first game." This financial strain appears to have forced the company into a severe cost‑cutting mode at a critical moment. Zachariah Scott, a former senior technical artist at Bit Reactor, took to LinkedIn to claim that the studio had been "concealing the fact that the team was furloughed weeks ago." In an interview with Game File, Scott described the studio’s budget as "tight" throughout his tenure and recalled that founder Greg Foertsch frequently expressed hopes of landing a new development deal to keep the operation afloat.
Scott also recounted that the development team had requested additional lightsaber animation work, only to be told that the budget could not accommodate the extra assets. He characterised the entire production as being carried out under "shocking austerity," with resources stretched to the breaking point. The Bit Reactor representative added that the studio hoped the furloughed employees could be rehired if the launch proved successful, suggesting that a strong commercial performance might generate the cash needed to bring staff back on board. However, Scott noted that many of the workers he spoke with were skeptical, expressing doubt that a successful launch would automatically translate into reinstatement for everyone who had been furloughed.
The furloughs have also surfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly. In her complaint, Kelly alleges that the studio not only furloughed staff but also terminated a number of contractors. The litigation 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 would have divided the company’s equity 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 countered that the draft agreement was never signed, arguing that Kelly never became an owner and that her termination was due to poor job performance.
Kelly disputes those assertions and is seeking more than $20 million in damages. The situation at Bit Reactor highlights a broader trend in the games industry where small studios, especially those launching high‑profile licensed titles, can find themselves financially vulnerable despite critical acclaim and strong sales. The rapid climb of Zero Company on Steam’s charts demonstrates consumer appetite for well‑crafted Star Wars experiences, yet the studio’s cash flow problems illustrate how front‑loaded development costs, licensing fees, and marketing expenditures can quickly erode a fledgling studio’s runway.
Industry analysts note that many indie‑level developers rely heavily on external financing, milestone payments, or publishing advances to bridge the gap between development completion and revenue generation. When a launch does not immediately deliver the anticipated cash influx, studios may be forced to make painful staffing decisions, as appears to be the case with Bit Reactor.
The legal dispute involving Kelly further underscores the complex ownership structures that can arise in start‑up studios, where equity splits, operating agreements, and founder‑employee relationships are often informal or poorly documented. For the remaining Bit Reactor team, the immediate priority is to monitor Zero Company’s live environment, address any technical issues that players encounter, and maintain community goodwill. The studio’s ability to quickly patch bugs and roll out post‑launch content will be crucial not only for preserving the game’s reputation but also for generating the ongoing revenue needed to stabilize the company’s finances.
If the game continues to perform well commercially, there is a realistic chance that Bit Reactor could secure additional funding, either through a new publishing partnership, a sequel contract, or even a strategic acquisition. Such a windfall could enable the studio to rehire furloughed staff, restore contractor relationships, and perhaps settle the pending lawsuit with Kelly. Until then, the company remains in a precarious position, balancing the demands of a live game with the constraints of a dramatically reduced workforce. The Bit Reactor case serves as a cautionary tale for developers and investors alike: even a product that garners critical praise and strong sales can be jeopardised by insufficient financial planning and the pressures of high‑cost licensing agreements.
It also raises questions about the responsibilities of publishers and licence‑holders in supporting smaller studios during the critical launch window, a topic that may see increased scrutiny as more high‑profile IPs are handed to indie developers in the future.