Tailwind UI's $2 million was five months of a commercial product, not a URL typo

The story

On 2 August 2020, Adam Wathan republished a Twitter thread on his site as Tailwind CSS: From Side-Project Byproduct to Multi-Million Dollar Business. The URL still says multi-mullion, a typo; the title and body say million. About a month earlier, he wrote, Tailwind had cracked 10 million total installs. They were also about to cross $2 million in revenue from Tailwind UI, their first commercial Tailwind CSS product, released about five months earlier, a bit under two years after the first Tailwind CSS release. Those three clocks, installs, Tailwind UI dollars, and time since first CSS release, are his. This record does not invent a different multi-million total to match the broken slug.

The CSS started as an abandoned idea. In 2015 he told Steve Schoger about Digest, a site where companies would share links and outsiders could subscribe. He took a week off work and spent most of it on the tech stack, including CSS, because Bootstrap 4's first alpha had dropped Less for Sass and he hated Sass. Less let any class work as a mixin. He built Bootstrap-inspired components plus a small set of utilities. Digest died. The stylesheets lived. He copied the Less files into at least four or five later projects and watched utilities grow while component files shrank, which is when he started calling the approach utility-first rather than a bag of helper classes.

KiteTail, a later abandoned checkout idea, was streamed on YouTube with those styles in view. Viewers asked about the CSS. That, he wrote, is the benefit of working in public: he and Schoger would never have built the Tailwind Labs business, which in the same essay he said had done over $4 million in revenue in under two years, if he had not been live-streaming yet another failed side project. The $4 million line is a Tailwind Labs claim in that paragraph, not a restatement of the $2 million Tailwind UI line, and not an audited combined total. Keep them labeled as two founder sentences on the same page.

Open source was not the original plan. People asked to collaborate. Stefan Bauer, in Wathan's memory, suggested responsive prefixes like sm:font-bold instead of sm-font-bold. Jonathan Reinink wanted the utilities for a SaaS redesign with a completely different look, which forced the framework to be project-agnostic. The name Tailwind came from throwing tail-star into a reverse dictionary to stay tied to KiteTail. For two or three months in mid-2017 they pushed toward a release. Less configuration became so cryptic that tests felt impractical. David Hemphill pointed him at PostCSS. He described the rewrite on Full Stack Radio and still jokes that Tailwind abuses PostCSS in ways Andrey Sitnik never intended.

Halloween night 2017 they finished documentation for 0.1.0 and shipped the next day to attention he still calls surprising. Andrew Del Prete's PurgeCSS post, a few days later, is named as one of the most important in the framework's history. After a year of 0.x releases he announced he would go full-time on Tailwind CSS, dropping a planned new SaaS. Refactoring UI, a book with Schoger released in December 2018, had given him what he called a big bankroll, and he believed commercial offerings around the framework were possible. Tailwind v1.0 went out on 13 May 2019. He then spent the rest of the year with Schoger trying to figure out what Tailwind the business would be, discarding prototypes until they pursued what became Tailwind UI.

The first public glimpse of that gallery idea is a March 2019 tweet about hundreds of responsive components to copy. Early access shipped in February 2020 after they worked what he described as thirty-six hours straight into a self-imposed deadline. In the August 2020 essay he said Tailwind UI had been successful beyond their wildest dreams and was going to cross $2 million in revenue the following week, the same $2 million already attached to a five-month-old product. That sentence is still his projection on 2 August, not a closed audited year. As a result they had started hiring, naming Brad Cornes, Simon Vrachliotis, and a then-unnamed third developer.

What this story must not do is launder later company folklore into his 2020 list. He did not state a Tailwind CSS support-plan ARR in this essay. He did not state a headcount beyond those names. He did not convert 10 million installs into unique developers or paying customers. Installs are cumulative package installs in his wording. Tailwind UI revenue is commercial product revenue, about to cross $2 million, about five months after launch. Tailwind Labs over $4 million in under two years is a separate clause about the studio that exists because of the streams. The URL typo does not license a third number.

The abandoned products are load-bearing. Digest paid for the utility files. KiteTail paid for the audience that asked for a framework. Refactoring UI paid for the year of full-time framework work. None of those is Tailwind UI's $2 million, and none of them is proof that every CSS hobby should become a component store. Wathan's own plot is accident plus public work plus a book that funded a bet, then a gallery that sold. The Halloween 2017 open-source date and the May 2019 1.0 date sit before Tailwind UI. Mixing them into one overnight business erases the years of unpaid CSS.

He closes by thanking people who supported them and promising more products. That is a founder's forward look, not a second revenue print. For an editorial file the discipline is quotation boundaries. If he wrote 10 million installs, $2 million Tailwind UI, about five months, a bit under two years since first CSS, 13 May 2019, February 2020 early access, thirty-six hours, and over $4 million Tailwind Labs in under two years, those are the figures. If a catalog title somewhere says multi-mullion, treat it as the same typo as the slug, not as a metric.

Independently verified: false. Downloads and dollars are founder-reported in a blog post that began as a thread. This draft does not pull Stripe screenshots or npm audit trails. The useful caution is double: do not correct his million using the misspelled URL, and do not add millions he did not write.