Bit Reactor, the 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. In an interview with Game File, a Bit Reactor spokesperson described the decision as a "difficult decision" that was taken "before it was clear how the launch would go," emphasizing that the move was not dictated by the publisher Electronic Arts or the Star Wars license holder Disney, but rather stemmed from internal financial pressures. Zero Company has been met with a warm reception from both players and critics, quickly climbing to the No.
2 spot on Steam’s top sellers list. Despite the strong market performance, insiders revealed that about 80% of Bit Reactor’s workforce had been placed on furlough, leaving only a skeletal crew to monitor and patch any bugs that might emerge after launch.
Sources close to the studio told Game File that the primary driver behind the furloughs was a cash crunch: the company had "run out of most of its money just ahead of the launch of its first game." Former senior technical artist Zachariah Scott took to LinkedIn to allege that the studio had been "concealing the fact that the team was furloughed weeks ago." In his comments to Game File, Scott painted a picture of a studio operating under extremely tight budgets. He noted that founder Greg Foertsch frequently spoke about the hope of landing a new game deal to keep the operation afloat.
Scott recounted that developers had requested additional lightsaber animations to enhance the combat experience, but were turned down because the budget simply could not accommodate the extra work. He summed up the development environment as one of "shocking austerity," where creative ambitions were constantly weighed against a stark financial reality. The Bit Reactor representative added that the studio hoped to re‑hire the furloughed employees once the launch proved successful, suggesting that a strong commercial performance could provide the necessary cash flow to bring staff back on board. However, Scott relayed that many of his former colleagues were skeptical.
They feared that even if the game generated a profit, there was no guarantee that all furloughed workers would be reinstated to their previous positions. This uncertainty contributed to a lingering sense of unease within the remaining team.
The furloughs have also surfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly. In her complaint, Kelly highlighted that Bit Reactor not only furloughed employees but also terminated contractors. The legal dispute centers on the ownership structure of the company. Kelly argues that she should be recognized as a co‑owner, citing a draft operating agreement from April 2021 that proposed splitting equity among founder Greg Foertsch, herself, and early co‑founder Tom Whittaker.
While Whittaker and another co‑founder, Steve Meyer, have since departed the studio, the draft agreement remains a point of contention. Foertsch’s legal team counters that the agreement was never signed, asserting that Kelly never held an ownership stake and that her termination was due to unsatisfactory performance. Kelly denies these allegations and is seeking more than $20 million in damages. The broader context of the situation reflects the volatile nature of the video‑game industry, especially for independent studios attempting to launch a high‑profile title tied to a major franchise.
Development costs for a modern AAA‑style game can easily run into tens of millions of dollars, and even a well‑received product may struggle to recoup those expenses without robust post‑launch support and additional revenue streams such as downloadable content, microtransactions, or merchandising. For Bit Reactor, the timing of the furloughs was particularly precarious. The studio had invested heavily in creating a Star Wars experience that blended cinematic storytelling with immersive gameplay, aiming to capture both longtime fans and newcomers. The decision to cut staff just before the launch risked undermining post‑release support, which is crucial for maintaining player trust, fixing unforeseen bugs, and delivering updates that keep the community engaged.
A skeleton crew, while capable of addressing critical issues, may lack the bandwidth to implement larger patches or new content that players often expect in the weeks and months following a major launch. Industry observers note that such financial strain is not uncommon among studios that secure high‑profile licenses.
While the association with a brand like Star Wars can open doors to a massive audience, it also brings heightened expectations and pressure to deliver a product that meets the franchise’s legacy. In many cases, publishers provide upfront funding, but the responsibility for ongoing development costs can fall heavily on the studio, especially if revenue projections are not met quickly. 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 deliver timely updates, and the outcome of the legal battle with Alison Kelly.
If the game continues to perform strongly on platforms like Steam, it could generate the cash flow needed to re‑hire former staff and stabilize the studio’s operations. Conversely, prolonged legal disputes and a potential erosion of morale among the remaining developers could hamper the studio’s capacity to support the game effectively.
In summary, Bit Reactor’s pre‑launch furloughs illustrate the precarious balance between creative ambition and financial viability in the gaming sector. While the studio’s flagship title has achieved impressive early sales and critical acclaim, the underlying financial challenges have led to drastic workforce reductions, legal entanglements, and uncertainty for the many developers who contributed to the project.
The coming months will reveal whether the company can recover, retain its talent, and continue to build on the momentum generated by Star Wars Zero Company.