Build a survival ledger: Heart Machine's breakout and layoffs

One publisher became the payroll

You are about to commit the next project to one publisher, investor, or anchor customer. Heart Machine, the studio behind the Hyper Light series and Possessor(s), laid off almost its entire staff after an unnamed publisher dropped funding for its next game.

On September 16, Alx Preston posted on LinkedIn that a publisher had stopped moving forward with an unannounced title, removing a key source of studio income. Preston said the studio's survival was uncertain because he did not know how or whether Heart Machine would continue. Work on Hyper Light Breaker stopped while it remained in early access, and the studio reduced staff.

The sequence matters. A publisher can be a key source of income without being the only source. The problem appears when the next project's schedule, staffing, and payroll all depend on that one source. At that point, a publisher exit becomes a shutdown risk. Single publisher dependency is visible in the ledger: one deal becomes the studio's next payroll. The ledger should show that before the deal is signed.

The hit and the follow-up changed the risk

Heart Machine's first game, Hyper Light Drifter, came out in 2016 and succeeded both critically and commercially. That result changed the studio's priorities from a debut to a continuing line of work. A startup that has one strong release can start treating the next project as a second act, not a test. The risk is that the second act gets built on money that arrives from one place.

The studio's second game, Solar Ash, was released in 2022 and failed to match the earlier game's acclaim. A team that can no longer assume a debut's reception will carry the next one has to look harder at who is paying for the next one. In a small, cash-constrained studio, that question is usually about one publisher, one anchor customer, or one investor. When a follow-up lands below a debut, the studio still has to pay for the next idea. The gap between expectation and result is where the ledger becomes necessary. If the next project is already being planned, the funding question should be answered before the team grows around it.

The ledger should be built before the next commitment

Before you commit the next project to one funder, write a dated survival ledger. Keep it short enough that you can update it in one sitting. The ledger should be dated because a funder's share changes as the project changes. A deal that looks safe at kickoff can become dangerous when scope expands, a milestone slips, or a new role is added. The date is what lets you compare the plan to the actual state of the company.

• Date and revenue source, including who pays and when payment is expected.
• Funding source, including the largest funder's share of the next project.
• Product milestone, including what is shipped, in early access, or unannounced.
• Layoffs or staffing changes, including which roles depend on the next project.

The largest funder's share is the number that matters. It does not need to be a precise percentage if the company is small. It needs to be honest enough to answer the payroll question. If the share is high, the next question is what happens to the team if the deal stops.

Remove the funder from the next project and see what remains: a smaller version, a pause without losing the team, or payroll covered by existing revenue or a separate funding source. If the answer is no, the ledger has exposed the risk before the risk becomes a layoff. Then ask one question: can the company pay its people if that funder stops? If the answer depends on a single deal, the ledger has done its job.