WooThemes: The Cape Town WordPress Theme Shop Whose $30M+ Exit Was Earned by a Late-Born "Internal Plugin" — WooCommerce

In May 2015, Automattic, the company behind WordPress.com, announced its acquisition of WordPress theme vendor WooThemes. According to Re/code’s reporting, relayed by WordPress trade publication Post Status and The Tech Portal, the consideration exceeded $30M in cash and stock: Automattic’s largest acquisition to that point.

WooThemes was started in 2008 by three founders (Mark Forrester, Magnus Jepson, and Adii Pienaar) as one of the first commercial WordPress theme shops. Its home was Cape Town, South Africa: far from Silicon Valley, far from Europe, and far from friendly VC markets. It never raised outside money. In Post Status’s words, “as a bootstrapped company, WooThemes had to turn a profit.” Seven years later, that company, 55 people scattered across roughly 20 countries, was bought by the center of the WordPress world.

But the $30M+ price tag was attached not to the original theme business but to a plugin born three years after founding, in September 2011, as an internal project: WooCommerce.

The Numbers

How a Theme Shop Became E-Commerce Plumbing

WooThemes’ original trade was selling paid themes, the visual dress-up layer of WordPress sites. But themes are essentially one-off design goods: little repeat demand, fast-moving fashion. The turn came in 2011, when the company released WooCommerce, a plugin that adds e-commerce capability to WordPress sites, free of charge, and built a structure of selling paid extensions on top of it (346 at the time of acquisition, about 200 developed in-house or with partners).

The elegance of the design is that the free core rides the enormous distribution network of the official WordPress.org plugin directory. With zero advertising, every time someone wants to build a store on WordPress, WooCommerce gets searched and installed. The denominator, over one million active installs, forms first. A fraction of it converts into extension buyers. By the acquisition, WooCommerce held over 24% of e-commerce across all websites, and per Post Status’s estimates the company had stacked up roughly $9–10M of revenue in 2013 and a ~$15M annual pace in 2015, with no sales force.

What Did Automattic Actually Buy?

The striking point in Post Status’s analysis is that the annual renewal rate on extensions was a notably low 17%. Most revenue, in other words, was first-time purchases by new customers, a weak recurring-revenue base. That it still fetched over $30M is explained by who the buyer was. For Automattic, owner of WordPress.com, holding the e-commerce standard on WordPress means holding the platform’s future revenue layer outright. It bought not a standalone P&L but a position: 20%+ share. Even the low renewal rate reads, to a buyer who can redesign the billing model from the platform side, as upside rather than defect.

The picture sharpens next to the sale of WordPress theme company Array Themes. A pure theme company’s exit amounts to absorbing talent and a product line. WooThemes, though a theme shop, held an asset of a different order, the platform’s standard. The difference in exit size is less a difference in business scale than a difference in asset class.

What Didn’t Work, and What Was Precarious

WooThemes’ seven years were no straight line. The original theme business sat squarely in a market of intensifying competition and falling prices. Had the company kept selling only themes, its exit would very likely have been far smaller. The decision that split the company’s fate was staffing the internal WooCommerce project with two full-time development leads and investing in earnest.

The other precarious element is building on someone else’s platform at all. WooCommerce’s distribution depends on the WordPress.org directory. Its technical existence depends on WordPress core. The risk that one policy change upends the premise bears even harder on operators one layer further down, like the solo developer making $8K/month on a plugin for WooCommerce itself. In WooThemes’ case, the platform’s own operator becoming the buyer converted that risk into the exit, the party you depend on most deeply is also your most natural acquirer.

What Generalizes, and What Doesn’t

Three mechanisms outlast this particular deal. A giant platform’s official directory functions as a distribution network that builds your denominator at zero ad cost. “Free core + paid extensions” is the standard play for converting a large denominator into revenue. And for a business that captures a platform’s “standard,” the platform operator itself becomes the most likely buyer. As the case that carved a $1M/year niche out of the Microsoft ecosystem shows, living in an ecosystem’s gaps remains viable, WooThemes achieved the superior version: taking not a gap but the standard.

The limits are just as clear. Each platform has effectively one “standard” seat, and blanks like WordPress×e-commerce in 2011 no longer exist in mature ecosystems. Sustaining a bootstrap for seven years from Cape Town required the discipline of continuous profitability, and growing while carrying a 17% renewal rate, without the option of buying time with funding, was a permanent tightrope. That three people in the Southern Hemisphere built the world’s e-commerce standard is encouraging. But the road was opened less by the luck of a “theme shop’s byproduct” than by the decision to concentrate investment in a late-born project.