{"id":1752,"date":"2026-01-09T15:14:48","date_gmt":"2026-01-09T23:14:48","guid":{"rendered":"http:\/\/blog.nillsf.com\/?p=1752"},"modified":"2026-01-09T15:14:50","modified_gmt":"2026-01-09T23:14:50","slug":"ai-is-increasing-leverage-faster-than-its-creating-sustainability","status":"publish","type":"post","link":"https:\/\/nillsf.com\/index.php\/2026\/01\/09\/ai-is-increasing-leverage-faster-than-its-creating-sustainability\/","title":{"rendered":"AI is increasing leverage faster than it\u2019s creating sustainability"},"content":{"rendered":"\n

I came across two very contrasting posts this week from founders. One was from TailwindCSS<\/a>, and the other from The Browser Company<\/a>. The TailwindCSS founder shared how the company is struggling despite increased adoption, while The Browser Company shared how they are rethinking hiring due to Claude Code.<\/p>\n\n\n\n

Both posts show the real-world impact of AI. On one hand, it\nhighlights the fragility of the open-source ecosystem; on the other, it shows\nhow designers and product managers can prototype much faster and achieve more.<\/p>\n\n\n\n

AI is not fixing fragile open-source business models<\/h1>\n\n\n\n

I am an open-source enthusiast. Much to my own chagrin, I\nhave made fewer contributions than I would have liked, but I have built part of\nmy career around open-source tools like Terraform and Kubernetes.<\/p>\n\n\n\n

The world of open source has been struggling with business models since before generative AI. Multiple projects like MongoDB, ElasticSearch, Redis, Grafana, Terraform, and others have changed their licenses from \u201ctrue\u201d open-source licenses to licenses more friendly<\/a> to the commercial companies behind the projects<\/a>; with mixed reactions by the community. Even before AI, usage and sustainability in open source were not always aligned.<\/p>\n\n\n\n

The post from TailwindCSS shows a different form of struggle with the business model of open source. Because LLMs are so good at generating TailwindCSS code, the founder saw traffic to the documentation drop by 40% and revenue drop by 80%. The documentation for TailwindCSS is the main funnel into their commercial offering, and by seeing less traffic, their revenue dropped. This finally led to them having to let go of 75% of their software engineers. This is, however, counter to the actual adoption of TailwindCSS itself, which is still growing.<\/p>\n\n\n\n

When AI can explain, generate, and contextualize results\nwithout sending anyone back to the source, usage and sustainability decouple.\nMore people benefit from the tool itself and can create value, without that\nvalue necessarily flowing back to the people and companies behind it.<\/p>\n\n\n\n

AI is accelerating experimentation<\/h1>\n\n\n\n

The job posting by The Browser Company paints a completely different picture. It shows AI as a huge lever on the productivity of both designers and engineers. Designers no longer have to wait for an engineer to build their prototype, while engineers can do more experimental work without sacrificing their core responsibilities.<\/p>\n\n\n\n

What they are not saying is that they are launching vibe-coded features into the wild. In a reply to the post on X<\/a>, the CEO shares that Claude Code is helping with prototypes and experiments, which don\u2019t end up in the final product in that way.<\/p>\n\n\n\n

This makes total sense, and it\u2019s something I\u2019ve heard in\nother places as well. Semi-technical designers can now use tools like Claude\nCode to build a working prototype instead of spending their time mocking up how\na new feature would look. This helps both accelerate the iterative design\nprocess and makes it easier for other stakeholders to try out new design ideas.<\/p>\n\n\n\n

Same Shift, Different Outcomes<\/h1>\n\n\n\n

I read both stories in the same week, and both stuck with\nme. Both companies are impacted by the same shift in technology, but the\noutcomes are completely different.<\/p>\n\n\n\n

AI is increasing leverage at the individual level and can make individuals much more productive. However, the outcomes of that leverage might not be positive for everyone. In the case of TailwindCSS, it is clearly a negative. In the case of The Browser Company, it sounds like a positive.<\/p>\n\n\n\n

This is why narratives like \u201cAI is destroying everything\u201d\nand \u201cAI is pure upside\u201d both feel incomplete. These statements require context\nand don\u2019t apply to every situation.<\/p>\n\n\n\n

I don\u2019t have answers. But \u201cAI increases productivity\u201d is actually the least interesting part of these two stories. They raise a more important question: who gets paid when AI does the work? Until we have better answers, we will keep seeing cases where value creation rises while the people and companies behind them struggle to sustain themselves.<\/p>\n\n\n\n

<\/p>\n\n\n\n

This blog was written by myself, with inspiration and review by Microsoft Copilot and ChatGPT. The heading image was generated using Adobe Express.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

I came across two very contrasting posts this week from founders. One was from TailwindCSS, and the other from The Browser Company. The TailwindCSS founder shared how the company is struggling despite increased adoption, while The Browser Company shared how they are rethinking hiring due to Claude Code. Both posts show the real-world impact of […]<\/p>\n","protected":false},"author":1,"featured_media":1754,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[45,16],"class_list":["post-1752","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-ai","tag-open-source"],"jetpack_featured_media_url":"https:\/\/nillsfblog.blob.core.windows.net\/media\/2026\/01\/Untitled.png","_links":{"self":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts\/1752","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/comments?post=1752"}],"version-history":[{"count":2,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts\/1752\/revisions"}],"predecessor-version":[{"id":1755,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts\/1752\/revisions\/1755"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/media\/1754"}],"wp:attachment":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/media?parent=1752"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/categories?post=1752"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/tags?post=1752"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}