WordPress Theme Craftsman Array Themes Joins WP Engine: The Negotiation Lessons of "Selling After Saying No, Again and Again"

The Shape of the Sale

Array Themes, an independent studio that designed and sold minimal, high-quality WordPress themes, was acquired in 2018 by WP Engine, one of the largest names in WordPress hosting. Founder Mike McAlister ran the business almost entirely by himself out of Wisconsin. At the time of the sale, monthly recurring revenue (MRR) was $20,000–40,000 (about ¥3–6M/month at ¥150/$1, the rate used throughout), and the sale price is disclosed as “around $500,000 (mid six figures).”

The protagonist of this case is neither the product nor a growth strategy — it’s the seller’s own act of selection. McAlister kept turning down multiple acquisition offers, and only nodded when WP Engine made contact in the summer of 2018. In his own words: “He wasn’t the first person to make an offer, but he was definitely the most interesting.” What was the basis for refusing some and accepting one? This is worth reading as an exit story for a small, craftsman-style business.

From Custom Work to “a Body of Work” — Six Years of Building Up

McAlister started out as a freelance developer building custom sites for clients. Back when WordPress had barely developed a culture of off-the-shelf templates, he stopped taking custom work and pivoted to designing and selling themes, founding Array Themes in 2012. It was a shift from delivering a one-off project and being done, to work that could reach thousands of people from the same design, a body of work.

Customers included names like TED and Dropbox. The WordPress theme market is a thin-margin, high-volume world where marketplaces overflow with shoddy themes, but Array built a loyal base of around 2,000 annual subscribers by taking the opposite route: maintaining a small number of themes with care. MRR of $20,000–40,000 off 2,000 annual subscribers is more than enough revenue for a team of just McAlister and one contractor, evidence that not chasing scale was a deliberate choice. In his own account, he acknowledges the difficulty of scaling while keeping his autonomy intact, and says outright that he never had the ambition to build a large company in the first place.

A Low Multiple, and “Pricing With No Formula”

Line up the disclosed numbers mechanically and MRR of $20,000–40,000 annualizes to $240,000–480,000. A sale price of “around $500,000” comes out to roughly 1–2x annual revenue, modest next to the 3–5x revenue multiples often quoted for SaaS deals. But reading this subtraction alone as “he sold cheap” would be premature.

First, theme “subscriptions” here are annual-license renewals, structurally different from a pure, monthly-compounding subscription SaaS. Second, this deal carried consideration that doesn’t show up in the price. After the sale, both McAlister and contractor Parris joined WP Engine as software engineers. The product came with jobs for its makers attached. And McAlister’s own words on pricing sum the whole thing up: there’s no universal formula for pricing a business. Factors like your “authority” in the space and the business’s own “momentum” (things that differ business by business, audience by audience, expertise by expertise) shape the price (paraphrased). Calculating the multiple is just the starting point. The final number is decided by the context with the specific buyer.

The Economic Value of Saying No

The first acquisition offer to arrive is rarely the best one. McAlister could keep turning down multiple offers because the business was profitable and he had no need to sell, the same source of negotiating leverage as ScrapingBee’s “don’t-need-to-sell position”.

And in the end, who he said yes to was decided not by price but by who showed up. The person who reached out was Brian Gardner, a principal developer advocate at WP Engine, himself known as a WordPress theme developer, trust between two people who build things was the entry point to the deal. Customers of a theme business are buying the promise that “it will keep being updated.” Hand it to a flip-minded buyer and the trust you’ve built with customers is destroyed. WP Engine had the incentive to run the themes long-term as added value for its own hosting, a buyer under whom the product would not die. The motive for selling wasn’t cashing out, either. What he named was “a new challenge”, the chance to “start from scratch and focus on building great products with a great team.”

Due Diligence as a War of Attrition

Even in a sale that looks smooth on the surface, there’s a stretch McAlister describes as having been “brutally draining.” Even after the agreement, due diligence, contract negotiation, and legal detail piled up, and he needed a lawyer’s help to get through it. In a one-person-business sale, this stretch of months puts both ordinary operations and the mechanics of the sale on the same one person’s shoulders. If even a business as well-organized as Array wore its founder out, a business with murkier books or unclear rights would see the negotiation itself collapse under scrutiny. The freedom to say no rests on having books you can open the moment someone asks to look.

There’s also a glimpse of the craftsman model’s own limits in the reason for the sale itself. Keeping the operation deliberately small bought freedom, but it also meant giving up on a scale of product only a team could build. That McAlister continued building a WordPress-community learning product on his own, even after the sale, hints that both satisfaction with, and a certain saturation of, “being on your own” coexisted.

The Exit Path for “Craftsmen” Inside an Ecosystem

The WordPress economy has an established exit route in which individual theme and plugin developers get bought by hosting companies and large product companies. For a hosting company, themes and plugins are components of differentiation, and buying a craftsman’s work and reputation as a package is the fastest way to acquire them. The same structure we saw with Appfire in the Atlassian ecosystem and the roll-ups in the Shopify ecosystem exists in WordPress too, the oldest ecosystem of them all.

Even for a small, craftsman-style business, a reputation for quality is an asset worth buying to the big players in the ecosystem, quiet good news for developers who refuse to compete on volume.

Conditions for Replication

What generalizes for Japanese readers is fighting to build “a reputation for quality” inside an ecosystem. Not just WordPress, developers who maintain a small number of products for the long haul on top of a platform, whether that’s Shopify apps, Chrome extensions, or Notion templates, can become an asset worth buying, reputation and all, to the big players in that economy. Refusing to compete on price in a mass-market marketplace, keeping a fixed customer base through annual subscriptions, staying profitable and negotiating from a “don’t need to sell” position, none of these depend on the scale of your business. Marquee customers like TED and Dropbox are the kind of credibility that product quality brings, not advertising spend, and that, too, requires no particular scale.

At the same time, the ability to be choosy about buyer quality came partly from living inside WordPress, a huge market with a deep pool of buyers. If the ecosystem itself shrinks, the value of the theme assets built on top of it shrinks with it. Which economy you choose to live in is what ends up determining, six years later, whether there’s an exit at all. Behind that roughly $500,000 price tag sits a market choice made back in 2012.

Related Reading

• Snapbytes — the classic exit for in-ecosystem developers
• ScrapingBee — the leverage of not needing to sell