Matt Mullenweg Built a Company Around Software Anyone Could Use

The story

Matt Mullenweg grew up in Houston, studied jazz saxophone at the High School for the Performing and Visual Arts, and became interested in publishing photographs and writing online. His technical education developed through using the web and changing the tools he depended on. He attended the University of Houston but left without completing a degree. The later company did not begin with an MBA-style exercise in choosing an attractive industry. It began with a user encountering a maintenance problem in software he already cared about—and realizing that its open license allowed him to help continue it.

The software was b2/cafelog, a blogging system whose development had stalled. In January 2003, Mullenweg wrote publicly about the possibility of creating a new branch of the project. British developer Mike Little responded, and they began collaborating. WordPress 0.7 appeared in May 2003. This origin matters because it was a fork, not an invention assembled from nothing. Existing code, an open-source license, and contributions from other people supplied a foundation. Mullenweg's initiative was to recognize that abandoned momentum could be restarted through cooperation, then participate in turning that possibility into working releases.

WordPress entered a publishing market where individuals wanted control over their sites without writing every page by hand. Its appeal grew through usability improvements, extensibility, and a community that could adapt it to different needs. Plugins and themes allowed developers and designers to build on the core rather than wait for every feature to arrive from one central team. In 2004, changes to rival Movable Type's licensing encouraged some users to consider alternatives. WordPress benefited, but retaining those users still required useful software. A competitor's unpopular decision can open a door; it cannot maintain your product for you.

Mullenweg moved to San Francisco in 2004 to work at CNET, gaining experience inside an established internet business while continuing his involvement with WordPress. In 2005, he left to found Automattic. The distinction between the projects is essential: WordPress is open-source software, while Automattic is a company that operates businesses around publishing and related services. WordPress.com offered a hosted route for people who did not want to install and manage the software themselves. Akismet addressed comment spam. These offerings targeted work that remained inconvenient even when the underlying publishing code was available without a purchase price.

That separation created an entrepreneurial model built around convenience and service rather than exclusive possession of all the code. Some people wanted to run WordPress independently; others preferred to pay for hosting, features, support, or reduced operational burden. An ecosystem of agencies, developers, hosting providers, and contributors could also benefit without being employees of Automattic. This made collaboration economically powerful, but it required careful distinctions between community interests and company interests. An open project is not simply a conventional product with its price set to zero. Its legitimacy depends partly on participation, licensing expectations, and how decisions are made.

Automattic also became known for distributed work, hiring people across locations rather than making a single office the center of every interaction. Written communication and asynchronous coordination suited an organization connected to a global open-source community. The company expanded through products and acquisitions, including WooCommerce in 2015 and Tumblr in 2019. That expansion moved it beyond a single blogging service. Still, the original commercial insight remained visible: when people adopt a flexible tool, they also create demand for help with operating, extending, securing, and earning a living through it.

The story also includes difficult governance questions, not just a frictionless celebration of openness. Public conflict involving Mullenweg, Automattic, and WP Engine in 2024 brought renewed attention to trademarks, access, commercial relationships, and authority within the WordPress ecosystem. For a prospective founder, the lesson is to copy neither a personality nor a dispute. Learn from the underlying method: contribute before demanding attention, solve a real maintenance problem, and distinguish the shared asset from the paid service. Then make the boundaries understandable, because a community's confidence is an operational resource as consequential as servers or cash.

The Cheat Code: shortcuts that worked