Adam Wathan: Tailwind CSS from Side-Project Byproduct to Multi-Million Business
How a live-streamed abandoned side project became the dominant utility-first CSS framework and funded a fully bootstrapped commercial products company.
Editorial profile. Written by IndieFounder Editorial Team from publicly available information. It is not a direct interview: the first-person answers are our summary of the founder's public statements, not verbatim quotes. Figures are approximate and not independently verified. Report an error.
- MRR
- Unknown (declined sharply after AI)
- ARR
- $4M+ cumulative by mid-2020 (self-reported); later estimates vary
- Users
- Tens of millions of downloads
- Founded
- 2017 (open source), 2019 (full-time/company)
- Team
- Small (grew to ~7, later reduced)
- Stack
- PostCSS, JavaScript, CSS
How did Tailwind CSS start?
Tailwind CSS did not begin as a deliberate attempt to invent a new CSS framework. In 2015 Adam Wathan was building a side project called Digest with his friend and later business partner Steve Schoger. The idea was a site where companies could share interesting links internally and outsiders could subscribe to see what teams they admired were reading.
Adam took a week off to prototype it. Most of that week went into deciding on a tech stack. He liked Bootstrap but disliked the switch from Less to Sass in the upcoming Bootstrap 4. So he wrote his own styles from scratch. The system mixed component classes with a growing set of utility classes for spacing, typography, and layout.
Digest never shipped. Adam kept copying the Less files into later projects. Over time the utility classes grew more useful and portable while the opinionated component styles stayed project-specific. He began to see utility-first as a real architectural approach rather than a bag of helper classes.
A later side project, KiteTail (a webhook-driven checkout tool for developers), used the same evolving styles. Adam live-streamed the work. Viewers kept asking about the CSS. That public work is what turned an internal system into something other people wanted. Without the streams, Adam has said, he and Steve never would have built the Tailwind Labs business that later reported over $4 million in revenue in under two years.
Around mid-2017 he decided to open-source the Less framework. Friends including Jonathan Reinink and Stefan Bauer helped shape it. The name Tailwind came from searching for words related to KiteTail. They rewrote the core in PostCSS and JavaScript for better configurability. The first public release (v0.1.0) went out on Halloween night 2017.
From open source to full-time and commercial products
The framework grew through successive v0.x releases. In January 2019 Adam went full-time on Tailwind CSS. He funded that decision with sales from earlier educational products: a 2016 book that did $61,392 in its first week and let him leave his job, a TDD course that eventually crossed $1 million, a Vue component course around $300k, and especially Refactoring UI (the design-for-developers book with Steve Schoger) which has done over $2.5 million.
They spent the rest of 2019 figuring out the business. In February 2020 they launched Tailwind UI, a library of professionally designed, copy-paste components and templates built with Tailwind. Adam reported over $500,000 in the first three days. By August 2020, roughly five months after launch, they were about to cross $2 million from Tailwind UI alone. At that point he wrote that Tailwind Labs had done over $4 million in revenue in under two years.
In a 2022 Indie Hackers AMA he described Tailwind UI as doing seven figures per year and growing, with a team of about seven people splitting time between the open-source framework and the commercial templates. The model was classic open-core: the free, highly configurable framework created massive adoption and word-of-mouth; a percentage of those users paid for high-quality components that saved them time.
What the numbers actually show
Self-reported figures from Adam’s own writing and posts include:
- First book: $61k in the first week (2016).
- Refactoring UI: over $2.5 million total.
- Tailwind UI: >$500k in the first three days; ~$2 million within about five months.
- Tailwind Labs: over $4 million cumulative revenue in under two years (stated in 2020).
- Later (2025 post): total revenue over the life of the product “comfortably into 8 figures,” while noting decline due to AI and open-source alternatives.
Third-party sites and reports have cited various later ARR figures (sometimes in the low-to-mid millions, sometimes lower after the drop). These are estimates or secondary claims, not audited numbers published by the company. In early 2026 Adam publicly discussed an ~80% revenue decline linked to AI coding tools reducing traffic to the documentation—the main discovery path for the paid products—despite continued high download numbers for the open-source framework. Some engineering roles were reduced as a result. Exact current MRR or ARR is not publicly detailed by the founder.
Distribution and the open-source flywheel
Growth came primarily from the quality and usefulness of the free framework itself, amplified by documentation that made it easy to learn, consistent public sharing (tweets, streams, the Full Stack Radio podcast), and the design sensibility from the Refactoring UI work. Adam has noted that much of the “marketing” was long-term and product-oriented: excellent docs, useful free content, and careful copy rather than paid ads or constant outbound.
The live-streaming and public building created the early audience that later converted when commercial products appeared. Once the framework reached critical mass, word of mouth and the natural funnel from docs to paid components sustained the business for years.
What the work looks like now and lessons that still hold
Adam’s X bio currently lists him as building at Shopify while remaining the creator of Tailwind CSS. The commercial business has faced a structural shift as AI assistants answer questions that used to send developers to the Tailwind docs. The free product remains widely used; the paid discovery channel has been disrupted.
Lessons from the arc:
Utility-first (or any strongly opinionated approach) can spread when it solves a real pain that many developers feel. Shipping the open-source version early and iterating in public turned an internal tool into a standard.
Info products and books can fund the riskier full-time jump into an open-source project before the commercial layer exists. Adam used prior course and book revenue to go full-time in 2019.
Open source plus a high-quality paid layer on top can work for years when the free product creates genuine adoption. The flywheel is not automatic; it depends on the docs and community experience staying excellent.
Distribution channels can break. Docs traffic was the primary path to paid products. When AI reduced that traffic, revenue fell sharply even while framework usage stayed high. Owning an audience or having multiple discovery paths matters more than ever.
Finally, the story is a reminder that most side projects fail or get abandoned. The valuable ones sometimes leave behind a reusable idea that, with enough public sharing and persistence, becomes the real business.
All revenue figures above that are not explicitly labeled as estimates come from Adam Wathan’s own posts, blog, or AMA responses. Current exact monthly or annual recurring revenue is not publicly confirmed by the founder.
Sources and further reading
More stories
Meta
The Portfolio Pattern: Why Top Indie Makers Run Multiple Products
Product Origin
Marc Lou: The Week ShipFast Changed Everything
Mature
Pieter Levels (Part 2): Nomad List & Remote OK — The Original Audience Engine
Profitable
Jon Yongfook: Bannerbear — Automated Image Generation to Solid ARR
Educator + Builder
Arvid Kahl: From FeedbackPanda Exit to Teaching Bootstrappers
Early Growth
Fernando Mendes: ScanQueue — QR Queues for Real Businesses
Scale
Danny Postma: HeadshotPro — AI Headshots to Six-Figure Months
Scale
Tony Dinh: TypingMind from 5-Day Build to $130K+/mo
Mature Solo
Pieter Levels: Photo AI to $100K+/mo with One PHP File
Portfolio Scale
Marc Lou: From 20+ Failed Projects to $80K+/mo Solo Portfolio
Mature Solo / Small team
Justin Jackson: Transistor.fm from $33 MRR to a Calm Multi-Million Business
Scale
Charlie Clark: Liinks from Side Project to $31K+ MRR Solo
Scale
Marko Saric: Plausible Analytics from Cold Email to 21k+ Subscribers
Scale
Marie Martens: Bootstrapping Tally from a Failed Travel Startup to $6M ARR
Scale
Tibo Louis-Lucas: From Repeated Failures and an Earnout Exit to a Self-Reported $1M+ MRR Portfolio
Scale
John O'Nolan: Ghost from Kickstarter to $10M+ ARR Non-Profit
Mature / Profitable
Sahil Lavingia: Gumroad from Unicorn Dream to Profitable Creator Platform
Acquired
Josh Pigford: Baremetrics from 7-Day Side Project to $4M Exit
Scale
Damon Chen: Testimonial.to from $1.99 in Failures to $100K+ MRR
Scale
John Rush: From VC Startups to a Bootstrapped Portfolio Built on Unicorn Platform
Mature
Courtland Allen: Indie Hackers from Failed Startups to Stripe Acquisition and Back
Scale
AJ: Carrd from Side Project to $1.2M ARR on $19/Year Pricing
Scale
Dmytro Krasun: ScreenshotOne from Solo API to $33K+ MRR
Growth
Steven Tey: From Vercel Side Project to Modern Link Attribution with Dub.co
Growth
Ashraf Samhouri: Activepieces from Closed Automation Frustration to Open-Source Platform
Scale
Jack Ellis: Fathom Analytics from Tweet Mockup to Independent Privacy SaaS
Scale
Jan Oberhauser: n8n from Side Project to AI Automation Platform
Scale
Yasser Elsaid: From 16 Followers to $10M ARR Bootstrapped
Scale
Nathan Barry: From Near-Shutdown Side Project to $45M+ ARR with Kit
Scale
Nevo David: Postiz from Open Source Pivot to $390K+ MRR
Scale
