The Tailwind Labs' Problem

Source: Dev.to

Credits

• Original post from Adam Wathan
• Theo
• Maximilian Schwarzmüller

TailwindCSS’ Impact

Without getting too deep into the many ways of doing CSS, it’s clear that Tailwind CSS is a widely‑used and loved library.

• Weekly downloads: ~26 million (early January 2026)
• Monthly downloads: ~75 million+
• Total downloads: several billion cumulatively (and still growing)

Derivative UI kits such as Daisy UI, Flowbite, Aceternity UI, and Retro UI have spawned profitable businesses and helped make Tailwind CSS especially popular among newer developers.

The Problem

So, what happened? If Tailwind CSS is so beloved and deeply embedded in the ecosystem, where did things go wrong?

Tailwind Labs’ core product—Tailwind CSS—is completely free and open‑source. They generate revenue through a few channels, all of which run through their website:

These revenue streams were hit hard by the rise of AI‑assisted coding. A large part of “vibe coding” is the built‑in search provided by large language models (LLMs). Developers no longer need to scour YouTube tutorials or Stack Overflow threads; an LLM can answer a question instantly.

I’m guilty of this too. After deliberately avoiding AI for a long time, I started using LLMs in my workflow late last year, treating them as a glorified autocomplete—especially for writing JSX. I remain pedantic about business logic and tests, but the AI assistance has dramatically changed how developers interact with documentation.

This shift caused a cascade of problems:

• A developer asked for a better llms.txt file so AI agents could work more effectively.
• The founder explained that this request highlighted a larger issue: less traffic to the documentation site.
• Both seasoned developers and “vibe‑coders” stopped spending time on the docs, causing an 80 % drop in site traffic.
• Revenue plummeted, forcing Tailwind Labs to lay off 75 % of its already lean team.

The Honor System & Value Capture

What makes this situation especially painful is how wholesome Tailwind Labs’ business model is.

As consumers, we’ve complained for years about:

• Endless subscriptions and hidden fees
• Lack of true ownership (e.g., perpetual licenses)
• Predatory monopolies and re‑activation fees
• Fragmented streaming services that cost more than traditional cable
• Intrusive ads and the sale of user data

Meanwhile, companies like 37signals, Drizzle, and Cake build sustainable, simple, and reasonably‑priced tools. They offer clear free tiers, fixed pricing for paid tiers, and even true “buy‑once” options—something rare these days.

Tailwind CSS has delivered massive value to production software: real‑estate listings, indie‑hacker SaaS projects, AI wrappers, and more. Yet that value hasn’t translated into commercial sustainability for the project.

Call to Action

If we want to keep seeing good companies and products that prioritize users over bad practices, we need to be intentional with our choices—essentially, vote with our money.

• Support local production when you can.
• If a project has given you value, back it in any way you’re able.

Big names are already stepping up as sponsors, and many individuals are contributing, but Tailwind Labs could still use more support.

My Personal Support

I purchased Tailwind Catalyst because I use Tailwind CSS in several of my projects. I also bought a copy of Refactoring UI, as I plan to focus more on front‑end development and product design this year.

If Tailwind Labs has helped you, please consider supporting them—whether through a sponsorship, buying a product, or simply spreading the word.

ey have provided value to you.

Cheers