Inside the 33-hour failed boardroom coup to overthrow WordPress founder Matt Mullenweg

Automattic CEO Matt Mullenweg was placed on paid leave by three directors, but returned to control within 33 hours; the directors were removed or resigned, and CFO Mark Davies and legal officer Andy Missan were fired. The boardroom conflict unfolded amid Automattic’s litigation with WP Engine and concerns over missing messages and evidence preservation; a judge said he was leaning toward denying WP Engine’s request to dismiss Automattic’s claims, while criticizing former lawyers’ account of preservation efforts. The dispute has contributed to 159 employee departures, about 8.4% of Automattic’s staff, and Mullenweg has said he holds about 84% of its voting power.

Analysis

The investable signal is not the courtroom headline but the loss of credible internal checks: if the founder can reverse a board intervention, outside capital has little practical governance protection. That raises Automattic’s private-market risk discount and could impair future fundraising or exit optionality even if the underlying WordPress franchise remains valuable. WordPress itself is open source; do not equate Automattic’s governance turmoil with an immediate failure of the software or all WordPress-based businesses.

For the ecosystem, the second-order risk is trust. Hosting firms, plugin developers and enterprise customers need predictable access to the platform and neutral rules. If they conclude that commercial disputes can disrupt access or trigger public retaliation, they have an incentive to diversify toward other CMS and commerce stacks. Shopify and Wix could benefit at the margin, but only if there is measurable migration; the article alone does not establish it. Automattic could also lose contributors and product velocity, while a negotiated settlement or clearer platform governance could arrest that erosion.

Near term, the judge’s ruling on evidence preservation is the key catalyst: sanctions or adverse inferences could increase litigation cost and weaken Automattic’s leverage, while denial would reduce—but not eliminate—this risk. Over 6–18 months, monitor customer retention, developer contributions, product releases and financing terms. The contrarian point is that founder control may protect strategic continuity, but it also makes conventional board oversight largely nonbinding. No clean public-equity expression is supported without evidence of customer or revenue displacement.

Key Decisions for Investors

• No direct directional trade: Automattic and WP Engine are private, and the supplied information does not quantify damages, customer losses or public-company read-through. Avoid treating broad WordPress usage as equivalent to Automattic revenue exposure.
• Set an event alert for the court’s evidence-preservation ruling and subsequent sanctions, discovery or antitrust developments. Escalate risk assessment if the court imposes sanctions or makes adverse findings; a denial would be a limited de-risking catalyst, not proof the dispute is resolved.
• Watch for independently verifiable migration signals—hosting/customer churn, CMS adoption, plugin or contributor activity, and enterprise renewals. Only then consider a relative long in Shopify or Wix against a relevant software/commerce basket; absent those signals, the proposed beneficiary trade is premature.
• For any Automattic private exposure, reassess governance and liquidity discounts rather than extrapolating WordPress’s ecosystem reach into company value. Thesis improves if the parties settle and Automattic establishes durable independent oversight; it worsens with further senior departures, product execution slippage or deteriorating financing terms.