Bit Reactor, the development studio behind the eagerly anticipated Star Wars Zero Company, made the difficult choice to furlough a substantial segment of its staff in the weeks leading up to the game's debut. A spokesperson for the company told Game File that the decision was taken "before it was clear how the launch would go" and was driven by financial constraints rather than any external pressure from publisher Electronic Arts or the Star Wars IP holder Disney.
The game itself 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, insiders reveal that the studio’s internal situation was far from stable. Multiple sources close to Bit Reactor informed Game File that approximately 80 % of the workforce was placed on furlough, leaving only a skeletal crew to monitor the live service, patch critical bugs, and provide customer support after launch. According to these sources, the furloughs were prompted by the studio exhausting the majority of its cash reserves just before the launch of its first title.
Former senior technical artist Zachariah Scott took to LinkedIn to allege that Bit Reactor had been "concealing the fact that the team was furloughed weeks ago." In an interview with Game File, Scott added that the studio operated on a "shocking austerity" budget throughout development. He recounted that even relatively modest requests—such as adding more lightsaber animation variations—were denied because the budget simply could not accommodate them. Scott also described a broader atmosphere of financial strain within the company. He said founder Greg Foertsch frequently expressed hope that a new publishing deal might arrive to keep the studio afloat.
While the team was encouraged to push forward with the game, the limited resources meant that many creative aspirations were trimmed or postponed. The result, Scott suggested, was a product that succeeded in many areas but was built under severe fiscal pressure. The Bit Reactor representative emphasized that the studio hoped the furloughed employees could be rehired once the launch proved successful.
"We are optimistic that a strong commercial performance will allow us to bring staff back," the spokesperson said. However, Scott reported that many of the affected workers were skeptical. "Even if the game does well, there’s no guarantee that everyone who was furloughed will get their old jobs back," he told Game File.
The furlough situation has also surfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly. In her complaint, Kelly alleges that Bit Reactor not only furloughed employees but also terminated a number of contractors. The litigation centers on a dispute over ownership stakes: Kelly claims that a draft operating agreement from April 2021 indicated that the company’s equity would be split among founder Greg Foertsch, herself, and early co‑founder Tom Whittaker. 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 a co‑owner and that her termination was due to unsatisfactory performance. Kelly denies these allegations and is seeking more than $20 million in damages, asserting that she was unjustly pushed out of the company.
The broader context of the Bit Reactor case highlights a recurring challenge in the video‑game industry: smaller studios often operate on razor‑thin margins, especially when they are developing a high‑profile licensed title. Development costs—including licensing fees for a franchise as prominent as Star Wars—can quickly outpace revenue streams that only materialize after launch. When a studio’s cash flow dries up before the product reaches consumers, difficult personnel decisions become inevitable.
In Bit Reactor’s situation, the timing of the furloughs—just weeks before the launch—suggests that the company was attempting to preserve enough cash to cover server costs, marketing spend, and the initial wave of post‑launch patches. By retaining a core team, they aimed to ensure that critical bugs could be addressed swiftly, preserving the game's reputation and sales momentum. Nevertheless, operating with such a reduced staff can strain the remaining developers, potentially leading to longer patch cycles and higher stress levels. Industry observers note that the outcome of this scenario could set a precedent for how other indie or mid‑size studios manage financial risk when working with major IPs.
If Star Wars Zero Company sustains strong sales and the studio can rehire its furloughed employees, it may serve as a case study in navigating fiscal hardship while still delivering a successful product. Conversely, if the game underperforms or the studio fails to secure additional funding, the remaining skeleton crew may be forced to make tough calls about further layoffs or even closure. For now, the game's community remains largely supportive, praising its gameplay, narrative integration with the Star Wars universe, and technical polish. The developers continue to release updates, and the limited team appears committed to maintaining the title's quality.
Whether the promised rehiring will materialize remains uncertain, but the situation underscores the precarious balance between creative ambition and financial reality in modern game development.