In late September 2026 the tech world watched a corporate drama that could have been scripted for a Hollywood thriller. Matt Mullenweg, the 19‑year‑old co‑creator of WordPress and long‑standing figurehead of Automattic, was ousted from his own company for a brief 33‑hour window, only to return with the board dismantled, two senior executives terminated, and a multi‑million‑dollar severance bill on the company’s books. The episode is more than a sensational headline; it is a case study in the fragility of open‑source governance, the perils of concentrated voting power, and the ways in which personal vendettas can intersect with corporate strategy. This commentary unpacks the core narratives, examines the broader industry implications, and asks what lessons founders, investors, and community members should draw from a saga that turned a boardroom into a battlefield.

The Board’s Gambit: Why Executives Thought They Could Fire a Founder

The board’s decision to replace Mullenweg was not a spontaneous power grab; it was rooted in a series of strategic miscalculations and an underestimation of the founder’s leverage. The board, led by CFO‑turned‑CEO Mark Davies, framed the move as a routine leadership transition, issuing a public statement of “full confidence” while quietly drafting severance packages for themselves. As the transcript notes:

“Earlier this month, while I was migrating my WordPress blog to Kubernetes, the board of directors at Automattic, the company behind other companies like wordpress.com, Tumblr, and WooCommerce, that has two T's in its name for its founder Matt, they tried to pull an open AI and fire their founder out of nowhere.”

This line captures the surreal nature of the board’s maneuver: an attempt to “pull an open AI” — a metaphor for a sudden, opaque corporate coup. The board likely believed that Mullenweg’s legal entanglements with WP Engine, coupled with his public persona as a “pirate”‑styled CEO, would make him a liability rather than an asset. The move also reflects a growing trend in venture‑backed tech firms where boards, often populated by investors with little technical background, feel empowered to replace even the most iconic founders if they perceive a threat to short‑term valuation.

What went wrong for the board? First, they ignored the structural reality of Automattic’s voting system. Mullenweg holds roughly 84 % of the voting power, a figure that gives him a virtual veto over any board decision. Second, the board misread the cultural capital that Mullenweg commands among the open‑source community. By attempting to remove him, they inadvertently galvanized a legion of developers, employees, and even external observers who view any assault on a founder as an attack on the ethos of open‑source collaboration.

Matt Mullenweg’s Counter‑Strike: From “Pirate” to CEO in 33 Hours

The speed and precision of Mullenweg’s response turned the board’s plan on its head. Within hours of receiving a written proposal to remove him, he mobilized legal counsel, leveraged his voting majority, and issued a series of public statements that combined defiance with theatrical flair. Two memorable moments illustrate his approach:

“Oh, since I'm a pirate now, I curse.”

This self‑declaration was more than a colorful turn of phrase; it signaled a deliberate reclamation of the “pirate” identity he had cultivated. By embracing the label, Mullenweg reframed the narrative from a board‑driven dismissal to a rebellious stand against corporate overreach.

“If you don't have a coup attempt every few years, you're not hiring strong enough leaders.”

Here he turns the criticism on its head, suggesting that a healthy organization should be robust enough to survive internal upheavals. The statement also hints at a broader leadership philosophy: constant tension and power checks are essential to prevent stagnation. By publicly acknowledging the coup, Mullenweg forced the board to answer not only to shareholders but to the wider WordPress ecosystem, where his credibility remains paramount.

Practically, Mullenweg exercised the very voting rights the board had ignored. He called a special meeting, dismissed the incumbent CFO and chief legal officer, and appointed a new board composed of allies who pledged loyalty. The board’s severance agreements—each promising a full year’s salary, health insurance, and immediate stock vesting—were rendered moot as the executives were terminated before they could collect. Automattic now faces an $8 million liability, a cost that, while sizable, is dwarfed by the symbolic victory of a founder reclaiming control.

Open‑Source Governance Under the Lens: Power, Community, and Accountability

The Automattic episode forces a reevaluation of how open‑source projects are governed when they evolve into profit‑driven enterprises. Traditionally, open‑source projects thrive on meritocratic contribution models, decentralized decision‑making, and transparent roadmaps. However, once a project scales into a multi‑billion‑dollar corporation, the tension between community ideals and shareholder expectations intensifies.

One of the core arguments presented in the transcript underscores this friction:

“One thing is if you're really open in open source, sometimes you have to stand up to bullies and you have to fight to protect your open source ideals.”

The quote encapsulates the paradox: a founder who built an open‑source platform must now act as a “bully” in corporate terms to defend the very openness that made the platform valuable. This raises several questions for the broader ecosystem:

  • Voting Concentration vs. Community Voice: Should founders retain disproportionate voting power to safeguard the project’s ethos, or does that create an unhealthy power imbalance that can stifle dissent?
  • Board Composition: How can boards balance investor expertise with technical credibility, especially when the product is a community‑driven platform?
  • Transparency Obligations: In open‑source companies, is there a higher duty to disclose internal governance disputes to the community, given that the community’s trust directly impacts product adoption?

Automattic’s experience suggests that retaining founder control can be a double‑edged sword. While it protected the company from a board that seemed intent on sidelining the founder, it also exposed the organization to a public spectacle that could have eroded confidence among users and partners. The key takeaway is that open‑source enterprises must design governance structures that respect both community values and the fiduciary responsibilities owed to investors.

Legal Warfare and the Shadow of WP Engine: How External Litigation Influences Internal Power Plays

The transcript repeatedly references a “ugly legal war with WP Engine,” an ongoing dispute that appears to have been a catalyst for the board’s maneuver. While the exact details of the litigation remain confidential, the narrative suggests that the board feared Mullenweg’s legal entanglements could expose Automattic to risk. One theory posited in the video is:

“One theory is the board figured removing the guy who may have destroyed evidence might make a judge go easier on the company.”

If the board genuinely believed that distancing the company from a founder embroiled in a separate legal battle would mitigate liability, their actions could be seen as a defensive, albeit heavy‑handed, risk‑management move. However, this rationale collides with the reality that Mullenweg’s personal legal battles are largely separate from Automattic’s corporate assets, especially given his distinct ownership of wordpress.org.

The interplay between external litigation and internal governance is a cautionary tale for all tech firms. Companies must clearly delineate personal legal exposure from corporate liability, and boards should avoid conflating the two without solid legal counsel. Moreover, the episode illustrates how a founder’s personal reputation can become a bargaining chip in boardroom negotiations, a dynamic that can be exploited by opportunistic investors or adversarial board members.

Financial Fallout and the Hidden Costs of Executive Severance Packages

Beyond the dramatic power shift, the financial repercussions of the 33‑hour coup are tangible. The severance agreements drafted for Mark Davies and chief legal officer Andy Masaan promised “a full year’s salary, a year of health insurance, and all of their stock would immediately vest.” By terminating them before they could claim these benefits, Automattic now faces a liability exceeding $8 million.

While $8 million may appear modest relative to Automattic’s market valuation, the incident highlights a broader issue: executive contracts that include generous severance clauses can become strategic weapons. Boards may feel emboldened to pursue aggressive leadership changes if they know that termination costs are pre‑negotiated, while executives may leverage these clauses to extract value irrespective of performance.

From a governance perspective, the episode underscores the need for:

  • Clawback Provisions: Including clauses that allow the company to recoup severance if termination is deemed to be the result of misconduct or a bad‑faith board action.
  • Performance‑Based Vesting: Aligning stock vesting schedules with measurable milestones rather than time alone.
  • Transparent Disclosure: Publicly reporting executive severance terms to shareholders to avoid surprise liabilities.

Implementing these safeguards could reduce the likelihood of a board incurring unexpected financial exposure during leadership turbulence.

Conclusion

The 33‑hour saga at Automattic is a vivid illustration of how power, personality, and politics intertwine in modern tech companies, especially those rooted in open‑source culture. Matt Mullenweg’s rapid reclamation of the CEO chair demonstrates the potency of voting concentration, community loyalty, and strategic communication. At the same time, the board’s missteps reveal the perils of underestimating a founder’s influence and the dangers of opaque governance structures.

For founders, investors, and open‑source advocates, the key lessons are clear: governance models must balance founder control with accountability, executive contracts should include robust safeguards, and legal disputes must be compartmentalized to prevent spillover into corporate strategy. As the industry continues to grapple with the challenges of scaling community‑driven projects into profitable enterprises, the Automattic episode serves as both a warning and a roadmap for navigating the delicate equilibrium between open‑source ideals and shareholder realities.