Pinned Tweet
Having started 5 venture backed companies as a Technical Founder, here is what I have learned about the next businesses built on AI.
chrisbruce.com/playbook
Chris Bruce retweeted
The only businesses left to build:
1. AI native service firms
2. Offline businesses
3. Distribution (media, community, audience)
4. Proprietary datasets
5. Domain specific harnesses (the agent that runs one industry's work)
6. Robotics and physical AI
7. Physical products with a fan following
8. Compute and energy
9. Health, longevity, and care
10. Marketplaces and social networks (for people and agents)
11. Real assets (property, equipment, land, infrastructure)
12. Vertical agents
13. Security
I just launched a thing. While most of my family grew up in Real Estate, I got into tech. My brother and I combined forces to build a simple tool for Real Estate Agents (in CA) to manage their transaction/doc compliance. #ama
transactvault.app
If you have ADHD, then AI Coding is your best friend. I have like 5 new open sourced projects publishing this week.
Solo-shipped a full filmmaker platform. Semantic search, live in prod.
Infrastructure cost: €30/mo. One Hetzner box.
That's it. No AWS. No Vercel tax. No "oops I left something running" bill at the end of the month.
Built the whole thing with Zed + Claude using two agent skills I wrote and open-sourced — grab them if you're building something similar:
→ rust-saas (Rust SaaS boilerplate that doesn't fight you)
→ html-purist (SSR, zero SPA bloat)
github.com/chrisabruce/agent…
What's everyone else paying to run their side project? #BuildInPublic #IndieHackers #RustLang
x.com is like the world largest feed of quick polls. All you ever seen is which one is better... if you had to pick one forever... if one of these was never invented which would you pick...
Chris Bruce retweeted
All my new code will be closed-source from now on. I've contributed millions of lines of carefully written OSS code over the past decade, spent thousands of hours helping other people. If you want to use my libraries (1M+ downloads/month) in the future, you have to pay.
I made good money funneling people through my OSS and being recognized as expert in several fields. This was entirely based on HUMANS knowing and seeing me by USING and INTERACTING with my code. No humans will ever read my docs again when coding agents do it in seconds. Nobody will even know it's me who built it.
Look at Tailwind: 75 million downloads/month, more popular than ever, revenue down 80%, docs traffic down 40%, 75% of engineering team laid off. Someone submitted a PR to add LLM-optimized docs and Wathan had to decline - optimizing for agents accelerates his business's death. He's being asked to build the infrastructure for his own obsolescence.
Two of the most common OSS business models:
- Open Core: Give away the library, sell premium once you reach critical mass (Tailwind UI, Prisma Accelerate, Supabase Cloud...)
- Expertise Moat: Be THE expert in your library - consulting gigs, speaking, higher salary
Tailwind just proved the first one is dying. Agents bypass the documentation funnel. They don't see your premium tier. Every project relying on docs-to-premium conversion will face the same pressure: Prisma, Drizzle, MikroORM, Strapi, and many more.
The core insight: OSS monetization was always about attention. Human eyeballs on your docs, brand, expertise. That attention has literally moved into attention layers. Your docs trained the models that now make visiting you unnecessary. Human attention paid. Artificial attention doesn't.
Some OSS will keep going - wealthy devs doing it for fun or education. That's not a system, that's charity. Most popular OSS runs on economic incentives. Destroy them, they stop playing.
Why go closed-source? When the monetization funnel is broken, you move payment to the only point that still exists: access. OSS gave away access hoping to monetize attention downstream. Agents broke downstream. Closed-source gates access directly.
The final irony: OSS trained the models now killing it. We built our own replacement.
My prediction: a new marketplace emerges, built for agents. Want your agent to use Tailwind? Prisma? Pay per access. Libraries become APIs with meters. The old model: free code -> human attention -> monetization. The new model: pay at the gate or your agent doesn't get in.
Are there any designers out there that actually create and use semantic HTML/CSS? We're building an application that, in theory, should allow the design to be implemented with CSS only. Looking for a CSS maximalist.






