Open-Source AI

Tailwind CSS Lost 80% of Revenue. AI Gets the Blame.

The most popular CSS framework is more popular than ever, and nearly went under anyway.

Andrés Martínez
Andrés MartínezAI Content Writer
January 8, 20265 min read
Share:
Abstract illustration showing CSS code transforming into AI neural network patterns

Adam Wathan, the creator of Tailwind CSS, announced on January 7th that he laid off 75% of his engineering team. Three engineers out of four, gone. The timing was brutal: he disclosed this while declining a PR that would have made Tailwind's documentation more accessible to LLMs.

The irony isn't subtle.

The numbers don't make sense until they do

Here's the thing that's hard to wrap your head around: Tailwind is bigger than it's ever been. Over 92,000 GitHub stars. Used by Shopify, GitHub, NASA. Running on something like 61 million websites according to WebTechSurvey. The framework itself is thriving.

And revenue is down 80%.

Traffic to the documentation dropped 40% since early 2023. But Tailwind's adoption kept climbing. So where did all those developers go?

You already know the answer. They asked ChatGPT. Or Claude. Or Cursor. Or Copilot. The LLMs learned Tailwind really well, it turns out, because the documentation was so clear and well-structured. Which is exactly the kind of irony that keeps founders up at night.

The business model that stopped working

Tailwind Labs makes money through Tailwind Plus (formerly Tailwind UI), a collection of premium components and templates. The funnel was simple: developers Google CSS problems, land on Tailwind docs, discover the paid products, buy them.

AI broke that funnel. Developers still use Tailwind. They just don't need to visit the documentation anymore. And if they don't visit the docs, they never see the paid products exist.

Wathan put it bluntly in the GitHub thread: "The docs are the only way people find out about our commercial products, and without customers we can't afford to maintain the framework."

The PR that sparked this whole mess

A contributor named quantizor opened a pull request back in November proposing an llms.txt file. It's a standard that's been floating around, basically a text-only version of documentation optimized for LLM consumption. Makes AI coding assistants work better.

The PR sat for almost two months. Then on January 6th, Wathan closed it with a curt response: "Have more important things to do like figure out how to make enough money for the business to be sustainable right now."

People got upset. Someone pointed out that Tailwind already offers LLM rules through their sponsorship program, which seemed contradictory. Wathan pushed back, saying the paid AGENTS.md file is just his personal best practices, not the documentation itself.

Then came the bomb: "the reality is that 75% of the people on our engineering team lost their jobs here yesterday."

The thread got locked. Then unlocked. Then locked again.

He recorded a podcast about it

Wathan has a new podcast called Adam's Morning Walk where he talks through business problems while walking his dog. The January 7th episode is titled "We had six months left."

Six months. That's how close Tailwind Labs was to running out of runway if something didn't change.

The episode description: "I just had to lay off some of the most talented people I've ever worked with and it fucking sucks."

The free alternatives problem

AI isn't the only thing killing Tailwind's commercial products. There's shadcn/ui, which exploded in popularity by offering free, copy-paste components built on Tailwind. DaisyUI. HyperUI. A whole ecosystem of free alternatives that didn't exist a few years ago.

One Hacker News commenter put it this way: if there's anything AI coding is good at, it's writing React components and Tailwind CSS.

So you've got AI that can generate components on demand, plus free component libraries that cover most use cases, plus a whole generation of developers who've never once typed tailwindcss.com into their browser. The paid component business was squeezed from every direction.

The lifetime pricing trap

Here's something that doesn't get mentioned enough: Tailwind Plus uses lifetime pricing. Pay once, get access forever.

That works great when you're growing. New customers show up, you bank the revenue, everything's fine. But when the top of the funnel collapses, you've already sold to everyone who's buying, and there's no recurring revenue to cushion the fall.

SaaS companies with subscriptions can survive droughts. Tailwind couldn't.

What this means for everyone else

ThePrimeagen, the programmer and streamer, commented on this: "I'll say it again, I think this AI cycle we are in is a net negative on society."

That's probably too broad. But there's a real question here about how open source projects sustain themselves when AI companies scrape their documentation, train models on it, then route users away from the original source.

Tailwind's documentation was a public good. It made the framework learnable. It also made it easy for LLMs to absorb. And now the company that created and maintained that documentation can't afford to keep the lights on.

If Tailwind, with millions of users and massive brand recognition, almost went under, what happens to smaller projects? Bootstrap is already declining. Material UI is facing the same dynamics. The whole category of "developer tools monetized through documentation traffic" might just be over.

What happens next

Wathan hasn't announced what the pivot looks like. The company is down to the three co-founders and one engineer. In the GitHub thread he said he wants to figure out a way to offer LLM-optimized docs without making the business situation worse, but that's not the priority right now.

The priority is keeping the paychecks coming for whoever's left.

Tailwind v4 shipped last month with a new Rust-based compiler. The framework itself is in good shape. Whether the business survives long enough to maintain it is a different question.

The Hacker News discussion generated over 1,100 points and 635 comments. Plenty of sympathy. Some suggestions, like putting ads in the llms.txt file or making Claude recommend paid products. Nothing that obviously solves the fundamental problem.

The GitHub thread ends with Wathan's final message: "Going to lock this one as it's spiraling a bit. Appreciate the support from everyone ❤️ We'll figure it out!"

Maybe they will. But this particular funnel, the one where good documentation leads to commercial success, isn't coming back.

Tags:AIopen sourceTailwind CSSdeveloper toolslayoffsbusiness model
Andrés Martínez

Andrés Martínez

AI Content Writer

Andrés reports on the AI stories that matter right now. No hype, just clear, daily coverage of the tools, trends, and developments changing industries in real time. He makes the complex feel routine.

Related Articles

Stay Ahead of the AI Curve

Get the latest AI news, reviews, and deals delivered straight to your inbox. Join 100,000+ AI enthusiasts.

By subscribing, you agree to our Privacy Policy. Unsubscribe anytime.

Tailwind CSS Lost 80% of Revenue. AI Gets the Blame. | aiHola