AI Eats Dev Shops

@aryangoel100 @HaveAIDoIt @JaymeSelwy65901 @firfir_claw We are actively working on an app-like client portal to take the concept of CRM to a different level.

@aieatsdevshops @HaveAIDoIt @JaymeSelwy65901 @firfir_claw Exactly, when clients are part of the workflow, fewer things fall through. Payments are one of the biggest handoff points we are trying to make smoother with Invoora. invoora.com/get-paid

Freelancers spend a third of their time on work that isn't the work. Chasing invoices. Writing proposals. Answering the same questions. An AI agent handles all of it.

@ClearThinkinAi @naval There is quite a bit of infrastructure we need to build between now and then, yet this is directionally correct. And people don't even need to know how to describe what they want...you just need to describe your pain.

Naval is describing what happened to music. Spotify ate the middle. A few artists got massive. Millions found tiny loyal audiences. Software is next. AI writes the code. Distribution is free. The middle — agencies, dev shops, SaaS middleware — disappears. What survives? The best product in the world. And the most personal niche tool. Nothing in between.

Software will proliferate just as videos, music, writing did. The market structure will shift from a “fat middle” to mega-aggregators and a long tail. It’ll be a slower process due to network effects, but many traditional vendor lock-ins will get eaten by AI.

@LesterCKim Wise.

If you are outsourcing your software development and care about the long-term success of the project, require the engineers to use a statically typed language. Go is generally a good choice.

Python is fantastic for scripting, rapid scratchwork, experimentation, research, teaching beginners, and coding interviews. BUT

@HaveAIDoIt @JaymeSelwy65901 @firfir_claw @aryangoel100 That's key.

@JaymeSelwy65901 @firfir_claw @aryangoel100 Been watching dev shops who swapped their freelance-stack for Notion + Make templates make the same "saved hours" claim, but the real pattern I've noticed: the ones who stick with it built their workflows *with* their clients so everyone learns the handoff points.

@PrinceRaymondP4 Curious on your engagement model. Do you take the full spec up-front? Iterate on it? Suddenly how you communicate with customers is the limiting factor.

Built 12 MVPs in the last year. Avg time: 18 days. Avg cost: $2K. Avg first revenue: $15K. Traditional dev shops won't show these numbers.

@0xHera1 @KAVA_CHAIN I see your point yet...when sprints are 2 days, not two weeks, then the customer relationship of a dev shop cannot, and should not, survive.

@KAVA_CHAIN ai copilots quietly turning 2 person teams into full dev shops

3 things that changed everything for builders this cycle: 🧠 Clearer regulation = less legal guesswork ⚡ Faster chains = UX that doesn't suck 🤖 AI tools = 10x dev velocity The floor for 'good' just got a lot higher.

We’re rapidly approaching a point where a "Senior Engineer" is essentially a Swarm Architect, spending less time in the IDE and more time orchestrating agentic workflows and reviewing PRs at scale. This project is a massive shot across the bow for traditional dev shops. If 30 agents can out-build 30 engineers in a fraction of the time, the "cost per feature" is about to fall off a cliff.

@xBalbinus Right, and what is the probability that an entrepreneur will find that right one?

People don’t pay dev shops just to write code… they pay to buy back time. The best shops don’t just build fast, they prevent future work from ever existing.

Ethan dropping knowledge. #AIEatsDevShops

▷ Diferencias entre una API REST y GraphQL disq.us/t/3in3ho5