Bit Reactor, the studio behind the eagerly anticipated Star Wars Zero Company, made the difficult choice to place a large portion of its staff on furlough in the weeks leading up to the game's debut. According to a spokesperson for the company, the decision was taken "before it was clear how the launch would go" and was not driven by external pressure from the game's publisher, Electronic Arts, nor from Disney, the holder of the Star Wars intellectual property. The representative emphasized that the move was a strategic, albeit painful, internal measure designed to preserve the studio's long‑term viability in the face of financial constraints. Zero Company has been met with strong enthusiasm from both players and critics.
Within days of release, the title climbed to the second spot on Steam's top‑seller chart, reflecting a robust initial reception and a high degree of community engagement. Reviewers have praised the game's immersive lightsaber combat, richly detailed environments, and faithful representation of the Star Wars universe, noting that it delivers a fresh experience while staying true to the franchise's core themes.
Despite the positive market response, insiders reveal that the studio's internal situation was far from stable. Multiple sources close to Bit Reactor told Game File that approximately 80 percent of the company's staff were placed on furlough, effectively reducing the workforce to a skeletal crew tasked with monitoring the live service and addressing any bugs or performance issues that might arise after launch.
This drastic reduction in manpower was reportedly the result of the studio exhausting most of its cash reserves just before the game went live. Zachariah Scott, a former senior technical artist at Bit Reactor, publicly disclosed on LinkedIn that the studio had been "concealing the fact that the team was furloughed weeks ago." In his post, Scott described the financial climate at Bit Reactor as "tight" throughout his tenure and recounted frequent remarks from founder Greg Foertsch about the urgent need to secure a new publishing deal or additional funding to keep the operation afloat.
Scott also mentioned that developers had requested additional lightsaber animation sequences to enhance the combat experience, but those ideas were rejected due to insufficient budget, highlighting the austere conditions under which the game was completed. The studio's spokesperson later clarified that Bit Reactor hoped the successful launch of Zero Company could generate enough revenue to bring the furloughed employees back on board.
The representative suggested that a strong commercial performance might provide the financial breathing room needed to rehire staff and stabilize the company's workforce. However, Scott expressed skepticism, noting that the employees he spoke with were doubtful that a profitable launch would automatically guarantee the reinstatement of their former positions.
Many feared that even if the game turned a profit, the company might opt to maintain a leaner structure to avoid repeating past financial missteps. The furlough situation also surfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly.
In her filing, Kelly alleged that Bit Reactor not only furloughed staff but also terminated several contractors during the same period. The lawsuit centers on a dispute over ownership stakes: Kelly claims she is a co‑owner of Bit Reactor alongside founder Greg Foertsch, citing a draft operating agreement from April 2021 that proposed splitting equity among Foertsch, Kelly, and early co‑founder Tom Whittaker. Both Whittaker and another early partner, Steve Meyer, have since departed the studio.
Foertsch's legal team counters that the draft agreement was never executed, arguing that Kelly never acquired an ownership interest and was instead dismissed for alleged poor performance. Kelly refutes these allegations and 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 exclusion.
The broader context of Bit Reactor's financial strain reflects a common challenge in the modern gaming industry, where mid‑size studios often operate on thin margins and rely heavily on the success of a single flagship title to sustain operations. The rapid development cycle, combined with high expectations from both fans and licensors, can leave studios vulnerable to cash‑flow crises if projected revenues do not materialize quickly enough.
In Bit Reactor's case, the timing of the furloughs—just before the launch—suggests that the company may have been forced to make pre‑emptive cuts to avoid a complete shutdown. Industry analysts note that while a strong launch can indeed generate significant post‑launch revenue through sales, downloadable content, and microtransactions, the immediate post‑release period also demands intensive support. Bug fixing, server maintenance, and community management are resource‑intensive tasks that typically require a sizable development team.
With only a skeleton crew in place, Bit Reactor may face challenges in delivering timely updates and maintaining player satisfaction, potentially impacting the game's long‑term reputation and revenue stream. In summary, Bit Reactor's decision to furlough a majority of its staff underscores the precarious financial balancing act that many independent developers face, even when their products achieve critical and commercial success. The outcome of the ongoing legal dispute, the studio's ability to secure additional funding, and the community's response to post‑launch support will all play pivotal roles in determining whether Bit Reactor can recover its workforce and continue to produce high‑quality Star Wars experiences in the future.