Hey team — got a suggestion to hop on a call for some Q&A and a meet and greet. Good idea. Let's do it. Need a read on days and times that work for everyone. Drop your availability in the comments and I'll pick whatever lines up with the most people.

Big news dropped today. CMD & Conquer just got approved for the Anthropic Claude Partner Network. Here’s where you come in. To unlock the next milestone I need 10 members to complete the official Anthropic Academy learning path. This is literally what this community was built for. You’re already here learning to build with Claude — now you can get certified by Anthropic themselves and help push us toward official partnership status. First 10 to complete it become part of the foundation of what CMD & Conquer is growing into. Real credentials. Real opportunity to work alongside me on client engagements as we scale. Drop a comment if you want in and I’ll get you the details.

When you set your dev team up properly, you can build anything. Three weeks ago I got hired by an early-stage healthcare startup to run QA and production readiness on the software they're shipping. The screenshot below is from a real session I ran today as part of that work. Seven defined roles, each with their own discipline. Business analyst grounds findings in evidence. Technical writer turns complex concepts into structured docs. Product manager drives jobs-to-be-done. UX designer balances empathy with edge-case rigor. System architect favors boring tech for stability. Senior engineer enforces test-first discipline. Master test architect speaks in risk calculations. I asked the team to discuss a Definition of Done for production readiness. Four agents kicked off in parallel. The product manager reviewed the doc. The architect assessed technical gaps. The engineer validated against the actual codebase with 30 tool calls. The test architect evaluated testing readiness. Total runtime: 2 minutes 42 seconds. Nobody prompted "build me a SaaS." Nobody typed "you are an expert software team." The roles, the disciplines, the responsibilities, the handoff structure — all set up in advance. The output is what the structure produces. This is what BMAD-style orchestration looks like in practice. You're not chatting with AI. You're running a software team. The reason I got hired wasn't because I can prompt better than the next person. It's because I know how to set up the structure that makes the output reliable enough to ship in a regulated industry. That skill is rare right now, and the teams who need it are figuring out they need it. This is exactly what CMD & Conquer was built for. When I say I want to build the world's first army of agentic developers, this is the kind of work I'm talking about. Real structure, real teams, real software shipped to real users in real industries. I'm genuinely excited every one of you is here. We're early. Let's build.