The Curated Daily
← Back to the archiveDispatch · 5 min read
Dispatch

John Carmack on the mistakes around Quake that ruined id software

By the editors·Wednesday, June 24, 2026·5 min read
A female engineer works on code in a contemporary office setting, showcasing software development.
Photograph by ThisIsEngineering · Pexels

John Carmack, the legendary programmer behind Doom and Quake, isn’t just a coding genius. He’s also a remarkably candid and insightful observer of the business side of game development. Over the years, he’s repeatedly discussed the mistakes made around the launch and post-launch handling of Quake, mistakes that very nearly crippled id Software, despite the game's phenomenal success. This isn't just a story for game developers; it’s a cautionary tale about partnership agreements, revenue sharing, licensing, and the dangers of letting ego dictate business strategy – lessons applicable to any entrepreneur.

The Colossus That Almost Fell: Quake's Initial Success

Quake, released in 1996, was a technological marvel. It introduced true 3D graphics to the first-person shooter genre, a revolutionary leap from the 2.5D sprites of Doom. The game was a critical and commercial hit, dominating the gaming landscape. It sold incredibly well, and established a fiercely loyal fanbase.

However, beneath the surface of success, financial and interpersonal cracks were beginning to form. Carmack has repeatedly outlined the core issues in post-mortems and interviews, revealing a series of decisions, driven by a mixture of naiveté and internal conflict, that threatened to undermine everything they had built. These weren’t technical failures – Quake was a technical triumph. They were business failures.

The Partnership Problem: Romero and the Unequal Split

At the heart of the problem lay the partnership structure between John Carmack, John Romero, and Tom Hall. While all three were co-founders, the financial arrangements were deeply unbalanced. Carmack, as the primary architect of the game engine, received a significantly larger share of the profits – 60% – while Romero and Hall split the remaining 40%.

This arrangement, while perhaps justifiable based on Carmack’s technical contributions, bred resentment within the team. Romero, a key designer and level creator, felt undervalued. The disparity fueled interpersonal tensions that were already simmering.

The issues weren't simply about the amount of money, but the perceived fairness. The underlying problem was a lack of a clearly defined and equitable compensation structure that took into account the various contributions to the success of the game. A clearly defined vesting schedule, for example, might have mitigated some of the tension.

The Licensing Labyrinth: Giving it Away Too Cheaply

Perhaps the biggest financial blunder was id Software’s licensing of the Quake engine. Faced with a burgeoning modding community and the potential for expansion, they decided to license the engine to other developers. However, they drastically underestimated the value of their technology and licensed it out at incredibly low rates – sometimes even for a flat fee of just a few thousand dollars.

This was a colossal mistake. The Quake engine became the foundation for a multitude of other games, generating substantial revenue for those developers, but very little for id Software. They effectively handed away the keys to a money-printing machine.

Carmack later regretted this decision, recognizing they should have implemented a royalty-based system, giving id Software a percentage of the revenue generated by games using their engine. A royalty model would have allowed them to continually profit from their intellectual property. Consider, for example, the success of Epic Games' Unreal Engine and its robust licensing system. https://example.com/ – Resources on game engine licensing can help illuminate these strategies.

The Focus on Technology, Neglecting Business Development

Id Software’s core strength was technological innovation. They were obsessed with pushing the boundaries of what was possible in game development. However, this laser focus on technology came at the expense of developing robust business development strategies.

They lacked a dedicated business affairs team to negotiate favorable licensing agreements, manage IP rights, and explore alternative revenue streams. They relied heavily on ad-hoc arrangements and, in some cases, simply didn’t understand the long-term financial implications of their decisions.

This demonstrates a classic entrepreneurial trap: being brilliant at the product but lacking the business acumen to properly monetize it. Many startups fall into the same pitfall, focusing solely on innovation without a commensurate focus on revenue generation and sustainable business practices.

The Aftermath: Internal Strife and Departures

The combination of financial dissatisfaction, interpersonal conflict, and questionable business decisions took a heavy toll on id Software. John Romero eventually left the company in 1997, followed shortly after by Tom Hall. These departures significantly destabilized the team and left a void in the creative direction of the company.

The situation was further complicated by legal disputes and ongoing tensions between Carmack and Romero. The fractured relationships within the company hampered their ability to innovate and compete effectively. This highlights the critical importance of a healthy company culture and a cohesive leadership team.

Lessons Learned: Applying Quake's Mistakes to Modern Business

The story of Quake and id Software is a powerful reminder of the importance of sound business practices, even in highly creative industries. Here are some key takeaways:

  • Fair Partnership Agreements: Clearly define roles, responsibilities, and compensation structures before embarking on a joint venture. Vesting schedules, equity splits, and dispute resolution mechanisms are crucial.
  • Value Your Intellectual Property: Don’t underestimate the value of your technology or creative assets. Licensing should be approached strategically, with a focus on maximizing long-term revenue. Royalty-based systems are often preferable to flat fees.
  • Invest in Business Development: A strong business development team is essential for negotiating favorable contracts, managing IP rights, and exploring new revenue streams.
  • Prioritize Company Culture: Foster a healthy and collaborative work environment. Address conflicts promptly and ensure all team members feel valued.
  • Don't Let Ego Drive Decisions: Separate technical prowess from business acumen. Be willing to seek advice from experts and make data-driven decisions, rather than relying on gut feelings.
  • Legal Counsel is Essential: Before signing any agreement, particularly around intellectual property, ensure you have experienced legal counsel reviewing the terms.

The Long View: Recovery and Continued Success

Despite the near-disaster, id Software ultimately recovered. Carmack, while acknowledging the mistakes, continued to innovate, and the company went on to create other successful titles like Doom 3 and Rage. However, the lessons learned from the Quake era shaped the company’s approach to business and licensing for years to come. The story serves as a potent case study for anyone involved in the creation and commercialization of intellectual property. It's a stark illustration that even groundbreaking innovation isn’t enough to guarantee success; sustainable business practices are equally crucial.

Disclaimer

This article contains affiliate links (https://example.com/ is an example). If you purchase a product through these links, we may receive a small commission at no extra cost to you. This helps support our website and allows us to continue creating valuable content. We only recommend products we believe in and that are relevant to our audience.

Pass it onX·LinkedIn·Reddit·Email
The Sunday note

If this was your kind of read.

Sign up for the morning email — short, hand-written, and sent only when there's something worth your time.

Free, sent from a person, not a system. Unsubscribe in one click whenever.

Keep reading

The archive →