Bit Reactor, the studio behind the much‑anticipated Star Wars Zero Company, made the difficult decision to furlough a substantial segment of its staff in the weeks leading up to the game’s debut. According to a spokesperson for the company, the move was taken "before it was clear how the launch would go" and was not dictated by the publisher Electronic Arts or the franchise owner Disney. The representative described the choice as a painful but necessary step, emphasizing that the studio retained full creative control over the decision.

The timing of the furloughs has drawn considerable attention because Zero Company has been met with enthusiastic reception from both players and critics. Within days of release, the title climbed to the second spot on Steam’s top‑seller chart, confirming strong commercial momentum. Despite this early success, insiders reveal that roughly 80% of Bit Reactor’s workforce was placed on unpaid leave, leaving only a skeletal crew to monitor the game for bugs and to provide post‑launch support. Sources close to the studio told Game File that the primary driver behind the mass furlough was a cash‑flow crunch.

The company reportedly exhausted most of its financial reserves just before the launch of its inaugural title. With limited capital remaining, the leadership opted to reduce payroll obligations in order to keep the studio afloat while the game generated revenue. Former senior technical artist Zachariah Scott added another layer to the story in a LinkedIn post, alleging that the studio had been trying to hide the fact that the team had been furloughed weeks earlier. Scott, who worked on Zero Company during its development, described the budgeting environment as "tight" and noted that founder Greg Foertsch frequently spoke about the need to secure a new publishing deal to sustain operations.

According to Scott, developers had requested additional lightsaber animation work, but the request was denied due to insufficient funds. He characterized the overall development process as being carried out under "shocking austerity," with the team forced to make hard compromises to meet deadlines. Bit Reactor’s spokesperson later clarified that the studio hoped to re‑hire the furloughed employees once the launch proved financially successful. The hope was that strong sales and a positive market response would generate enough cash flow to bring the laid‑off staff back on board.

However, Scott reported that many of his former colleagues were skeptical about the likelihood of reinstatement, expressing doubt that a successful launch would automatically translate into job restoration for everyone who had been let go. The furlough saga also surfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly.

In her filing, Kelly claimed that the studio not only furloughed employees but also terminated several contractors. The legal dispute centers on the ownership structure of Bit Reactor. Kelly argues that she holds a co‑ownership stake, citing a draft operating agreement from April 2021 that proposed dividing the company’s equity among 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, meaning Kelly never became an official shareholder. They further allege that Kelly was dismissed for poor performance, a claim she denies.

Kelly is seeking more than $20 million in damages, asserting that she was unfairly pushed out and that the company’s financial mismanagement contributed to the widespread furloughs. The situation at Bit Reactor highlights the precarious nature of independent game development, especially when a studio bets its future on a single high‑profile title. While the launch of Star Wars Zero Company has demonstrated strong market demand, the underlying financial strain reveals how quickly a promising project can become a liability if cash reserves run low. Industry observers note that such furloughs are not uncommon in the sector, where development cycles can be lengthy and revenue streams uncertain until a game finally hits the market.

For the remaining staff, the post‑launch period is a test of both technical resilience and morale. They must address any bugs, balance patches, and community feedback with a reduced team, all while under the watchful eye of a community that expects rapid updates for a flagship title tied to a beloved franchise. The pressure to maintain quality support with limited manpower could affect the studio’s reputation and future sales.

Looking ahead, the outcome of Kelly’s lawsuit may set a precedent for how ownership disputes and employment practices are handled in small to mid‑size studios. If Kelly’s claims are upheld, it could lead to greater scrutiny of internal governance documents and the need for clear, signed agreements before co‑founders assume equity stakes. Conversely, a ruling in favor of Foertsch could reinforce the notion that verbal or draft agreements hold little legal weight in the fast‑moving gaming industry.

In summary, Bit Reactor’s decision to furlough the majority of its workforce just before the release of Star Wars Zero Company underscores the financial tightrope that many indie developers walk. While the game’s early commercial performance is promising, the studio now faces the dual challenges of managing post‑launch support with a lean team and navigating a complex legal battle over ownership and compensation. The resolution of these issues will likely determine whether Bit Reactor can rebound and continue producing titles, or if the company will become another cautionary tale of a promising start-up undone by cash flow constraints.