Practitioner essays on building production software with AI agents.

Your product team spends 60% of their time on coordination that agents handle in minutes. Building is no longer the bottleneck, your customer's capacity to receive what you ship is. The operating model that wins is embarrassingly simple: talk to customers, figure out what to build, ship it, make sure it lands.

Your revenue team already exports pipeline data out of the CRM to do the real work somewhere else. You are not buying a strategic platform. You are paying $2.2 million a year for a database you already own, and four engineers could replace it in twelve weeks.

Your CFO should absolutely control the money. Your procurement team should absolutely manage the buying process. But neither of them should be deciding which AI capabilities your company adopts, because AI is not a printer.

You read Brooks. You read Fowler. You read The Phoenix Project and highlighted the good parts. Then you built something on Claude Code this weekend and realized your entire engineering organization is obsolete. Here is what building software actually looks like in 2026.

You waited on cloud. You waited on DevOps. You pushed out the people who tried to fix it. You still have a manual QA team. Your board is already comparing you to companies half your size shipping twice as fast. This isn’t about your team. It’s about you.

Every executive wants AI to magically modernize their 10 million line monolith. It won’t. Here’s what you actually need, and why you’ve been asking the wrong question for the last two years.

Your heaviest AI users are probably your best people. That’s the easy part. The harder question, the one that actually matters, is who still is not really using it. Go find out. It’s going to be an awkward conversation.