Bit Reactor, the studio behind the much‑anticipated title Star Wars Zero Company, made the difficult choice to furlough a significant segment of its staff in the weeks leading up to the game’s debut. According to a spokesperson for the company, the decision was taken well before any concrete data about the launch’s performance was available, and it was driven purely by internal financial considerations rather than any external pressure from the publisher Electronic Arts or the franchise owner Disney.

The announcement came during a conversation with Game File, where the Bit Reactor representative described the move as "a difficult decision made before it was clear how the launch would go." The spokesperson emphasized that the furloughs were not a directive from EA or Disney, but rather a measure the studio felt compelled to adopt to preserve its remaining resources. Star Wars Zero Company has been greeted with enthusiasm from both players and critics. Since its release, the game has climbed to the second spot on Steam’s top‑seller chart, reflecting strong initial sales and a positive reception. Despite this early success, the internal situation at Bit Reactor appears precarious.

Multiple sources close to the studio have told Game File that roughly 80 percent of the workforce was placed on furlough, leaving only a skeletal crew to monitor the game’s health, patch bugs, and provide post‑launch support. The underlying cause of the furloughs, according to these insiders, was a near‑exhaustion of the studio’s cash reserves just before the launch of its first major title. The financial strain left the company with little flexibility, prompting senior management to cut costs dramatically. Former senior technical artist Zachariah Scott took to LinkedIn to allege that the studio was actively trying to hide the fact that a massive portion of its team had been furloughed weeks before the public became aware.

Scott’s comments add a layer of context to the internal budgeting challenges that plagued Bit Reactor during development. He told Game File that the studio operated under "tight" budgets throughout his tenure, and that founder Greg Foertsch frequently expressed hope that securing a new game contract would provide the necessary lifeline to keep the studio afloat.

Scott recounted specific instances where developers requested additional lightsaber animation work, only to be denied due to insufficient funds. He described the overall development environment as one of "shocking austerity," where creative ambitions were constantly weighed against a shrinking financial runway.

In the wake of the furloughs, Bit Reactor’s public relations team indicated that the studio hoped to re‑hire the affected employees once the game proved successful. The representative suggested that a strong launch could generate enough revenue to bring the furloughed staff back on board, framing the decision as a temporary measure rather than a permanent layoff. However, Scott relayed that many of the workers he spoke with were skeptical about the promise of reinstatement, noting that even if the game performed well, there was no guarantee that every furloughed employee would regain their previous positions. The furlough situation also intersected with a legal dispute that surfaced in 2024.

Former chief operating officer Alison Kelly filed a lawsuit alleging that she was a co‑owner of Bit Reactor, a claim contested by the studio’s legal counsel. The suit references the same period of financial distress, noting that the company also terminated several contractors alongside the mass furloughs. Central to the litigation is a draft operating agreement dated April 2021, which purportedly outlined a share split among Foertsch, Kelly, and early co‑founder Tom Whittaker. Both Whittaker and another co‑founder, Steve Meyer, have since departed the company.

Foertsch’s attorneys argue that the draft agreement was never executed, meaning Kelly never attained ownership status and was instead dismissed for alleged poor performance. Kelly, however, rejects these accusations and is seeking more than $20 million in damages, asserting that she was unfairly pushed out of the company. The broader implications of Bit Reactor’s financial maneuvering raise questions about the sustainability of indie studios that take on high‑profile licensed projects.

While the partnership with Disney and EA offered a marquee opportunity, the financial realities of developing a large‑scale game under a tight budget can be unforgiving. The case of Bit Reactor illustrates how even a game that achieves early commercial success can be hampered by behind‑the‑scenes fiscal challenges, leading to drastic measures such as mass furloughs and legal battles. Looking forward, the future of Bit Reactor hinges on several uncertain factors. If Star Wars Zero Company continues to sell strongly and generates enough post‑launch revenue, the studio may be able to restore its workforce and stabilize its operations.

Conversely, prolonged financial strain could force further staff reductions, additional legal entanglements, or even the eventual shuttering of the studio. For now, the remaining skeleton crew is tasked with maintaining the game’s live environment, addressing player‑reported bugs, and ensuring that the title remains a viable product on Steam’s competitive marketplace.

In summary, Bit Reactor’s decision to furlough a large portion of its employees was a pre‑emptive cost‑cutting move made in the face of dwindling cash reserves, not a direct result of pressure from its publishing partners. The studio’s leadership hopes a successful launch will provide the financial breathing room needed to re‑hire staff, but internal skepticism and ongoing legal disputes underscore the fragile state of the company.

The situation serves as a cautionary tale for other developers navigating the high‑stakes world of licensed game development, where creative ambition must be balanced against the hard realities of budgeting and cash flow.