Bit Reactor, the studio behind the much‑anticipated title Star Wars Zero Company, made the difficult choice to place a substantial segment of its staff on furlough in the weeks leading up to the game's release. According to a company spokesperson, the decision was taken before the launch outcomes were known and was not driven by external pressures from the game's publisher, Electronic Arts, or the franchise owner, Disney.
The spokesperson described the move as a "difficult decision" that had to be made in advance of any certainty about how the market would receive the product. The timing of the furloughs has drawn considerable attention because Star Wars Zero Company has been enjoying strong early reception. Players and critics alike have praised its gameplay, narrative integration, and visual fidelity, propelling the title to the second spot on Steam’s top‑seller chart shortly after launch.
Despite this momentum, internal sources told Game File that approximately 80 percent of Bit Reactor’s workforce was placed on unpaid leave, leaving only a skeletal crew to monitor the live service and address any bugs that emerge after the game goes live. Industry insiders suggest that the underlying cause of the mass furlough was a severe cash‑flow crunch.
The studio reportedly exhausted most of its financial reserves just before the debut of its first major title. In a LinkedIn post, former senior technical artist Zachariah Scott alleged that the company had been "concealing the fact that the team was furloughed weeks ago," implying a lack of transparency with both staff and the broader public. Scott further explained that budget constraints had been a constant theme throughout development. He recounted conversations with founder Greg Foertsch, who frequently expressed hopes of securing a new publishing deal or additional funding to keep the studio afloat.
One particular anecdote highlighted the team's desire for more elaborate lightsaber animations—an element that would have enriched the Star Wars experience—but the request was denied due to insufficient budget. Scott characterized the overall development environment as one of "shocking austerity," where creative ambitions were regularly tempered by financial realities. The studio's representative emphasized that Bit Reactor hoped to re‑hire the furloughed employees once the launch proved successful. The logic, as presented by the spokesperson, was that a strong commercial performance could generate the revenue needed to bring staff back on board.
However, Scott noted that many of his former colleagues were skeptical about this promise. He reported that the mood among the remaining team members was one of uncertainty, with doubts about whether a successful launch would actually translate into reinstated positions for those who had been let go. The furlough situation has also surfaced in legal proceedings. In 2024, former chief operating officer Alison Kelly filed a lawsuit that references the mass furloughs and the termination of several contractors.
Kelly’s complaint centers on a dispute over ownership stakes in Bit Reactor. She argues that a draft operating agreement from April 2021, which outlined a three‑way split of the company's equity among Foertsch, herself, and early co‑founder Tom Whittaker, indicates she should be recognized as a co‑owner.
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, meaning Kelly never obtained an ownership interest.
They further allege that Kelly was dismissed for inadequate performance, a claim she vehemently denies. Kelly is seeking more than $20 million in damages, asserting that the termination and the subsequent furloughs were part of a broader pattern of mismanagement and unfair treatment. Beyond the courtroom drama, the practical implications of the furloughs are significant for the game's post‑launch support. With only a reduced team handling quality assurance, bug fixing, and community engagement, there is a heightened risk that issues may linger longer than they would under normal staffing conditions.
Players have already reported minor glitches, ranging from texture pop‑ins to occasional frame‑rate dips, and the ability of the skeleton crew to address these problems promptly will be closely watched. In the broader context of the video‑game industry, Bit Reactor’s situation underscores the financial volatility that many independent studios face, even when attached to high‑profile IPs. Development costs for AAA‑level titles have escalated dramatically, and securing sufficient funding before a product hits the market remains a formidable challenge. Studios often rely on milestone payments, publishing advances, or external investment, and any shortfall can force drastic measures such as furloughs or layoffs.
Looking ahead, the fate of Bit Reactor’s workforce will likely hinge on the commercial performance of Star Wars Zero Company over the next several months. If the game continues to climb sales charts and generates robust post‑launch revenue, there may be a viable path to rehiring the majority of the staff.
Conversely, if sales plateau or fall short of expectations, the studio may be forced to maintain a lean operational model or consider further reductions. For now, the remaining team members are tasked with a dual responsibility: delivering a polished gaming experience that meets the high expectations of Star Wars fans, and navigating the internal pressures of a drastically reduced workforce. Their ability to balance these demands will not only shape the immediate success of Zero Company but also determine whether Bit Reactor can emerge from this financial strain as a sustainable development house capable of future projects.