Bit Reactor, the studio behind the newly released 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. In an interview with Game File, a Bit Reactor spokesperson described the move as a "hard decision" that was taken "before we knew how the launch would unfold." The company emphasized that the action was not dictated by its publisher, Electronic Arts, nor by the franchise owner Disney, but was instead an internal financial maneuver. Zero Company has quickly earned praise from both players and critics, climbing to the second spot on Steam’s top‑seller chart shortly after release. Despite the positive reception, insiders reveal that about 80% of Bit Reactor’s workforce was placed on furlough, leaving only a skeletal crew to monitor and patch any post‑launch bugs that may arise.

Sources close to the studio told Game File that the furloughs were prompted by a cash crunch that left the company with "very little money left" just before the title hit the market. Former senior technical artist Zachariah Scott took to LinkedIn to allege that the studio had been trying to hide the fact that the majority of its team had been furloughed weeks before the launch. Scott added that, during his time at Bit Reactor, budgets were "extremely tight," and founder Greg Foertsch frequently expressed hope that a new publishing deal would arrive to keep the studio afloat.

According to Scott, developers had requested additional lightsaber animation work, but the request was denied due to insufficient funds. He characterized the entire development process as being carried out under "shocking austerity." When asked about the possibility of rehiring the furloughed employees, the Bit Reactor representative said the studio hoped a successful launch could provide the financial breathing room needed to bring staff back. However, Scott noted that many of the workers he spoke with were skeptical, believing that even a strong commercial performance might not guarantee the restoration of their former positions. The furloughs have also surfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly.

In her filing, Kelly alleges that Bit Reactor not only furloughed employees but also terminated a number of contractors. The lawsuit centers on a dispute over ownership: Kelly claims she is a co‑owner of Bit Reactor, citing a draft operating agreement from April 2021 that proposed splitting 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 counters that the draft agreement was never executed, arguing that Kelly never attained ownership status and that her termination was due to poor performance. Kelly refutes these assertions and is seeking more than $20 million in damages.

The broader context of Bit Reactor’s situation reflects a growing trend in the video‑game industry where mid‑size studios, often buoyed by a single flagship title, find themselves vulnerable to cash‑flow problems once development costs have been incurred. The high expectations attached to a licensed property like Star Wars can amplify both the potential upside and the financial risk. In Bit Reactor’s case, the studio appears to have invested heavily in creating a high‑quality experience—evidenced by the game's strong Steam performance—but may have overextended its budget before securing a reliable post‑launch revenue stream. Industry analysts note that the timing of the furloughs—just before the launch—suggests the studio was attempting to preserve cash for marketing, server costs, and other launch‑related expenses.

By reducing payroll obligations, Bit Reactor could allocate more resources toward ensuring a smooth release and addressing any immediate technical issues that players might encounter. However, this strategy also carries the risk of demoralizing the remaining team and potentially compromising post‑launch support if the reduced staff is unable to handle the influx of bug reports and community feedback. From a legal standpoint, the dispute between Foertsch and Kelly highlights the importance of clear, signed agreements regarding equity and ownership in start‑up studios.

Draft documents, while indicative of intent, do not carry the same weight as executed contracts, and the absence of a signed operating agreement can lead to protracted litigation that distracts from the core business of game development. Looking ahead, the future of Bit Reactor hinges on several factors: the sustained sales performance of Star Wars Zero Company, the ability of the remaining team to maintain and update the game, and the outcome of the legal battle with Kelly. If the game continues to sell well and generates enough revenue, the studio may be able to rehire a portion of its furloughed staff, stabilizing operations and possibly laying the groundwork for a sequel or new IP. Conversely, a prolonged legal dispute or a dip in sales could exacerbate financial strain, potentially leading to further staff reductions or even studio closure.

For now, the remaining developers are tasked with keeping the game running smoothly for its growing player base, while fans and industry watchers keep a close eye on how Bit Reactor navigates these turbulent waters. The situation serves as a cautionary tale about the delicate balance between creative ambition, financial planning, and the human element of game development.