Turns out sarcasm is now a legitimate technical architecture decision—Patrick discovered that giving Claude Opus 5 a snarky personality shaves hours off verbose outputs, and Morgan is staring down a four-day backend rewrite because Convex's real-time sync is just that tempting. If you missed the chief-of-staff agent deep dive, you missed the moment we realized the "assistant" model completely collapses at 2,000 licenses. 📞 HOW THE CALLS WORK The calls can run 2+ hours. We want to make sure we're respecting everyone's time. Especially those of you who actually show up. Here's the structure: 👉 Reply to this post with your questions before the call 👉 If you submit a question and you're on the call, you go first 👉 We work through questions in the order they came in 👉 Then we open it up for everyone else If you can't make the call but want your question answered, drop it in the comments. We'll get to it. But priority goes to people who are there. The goal is simple: if you're taking the time to show up, you shouldn't have to wait behind questions from people who aren't even on the call. Morgan is weighing whether to pull the trigger on that Convex migration before onboarding new schools, Patrick is cooking up separate Claude style templates to keep the chief of staff from drowning the implementer in chatter, and Scott will be back from holiday soon to demo his Mac coding workflow replacement. If any of those threads resonate—or if you're sitting on your own AI architecture puzzle—bring it to the call. 🔗 ZOOM LINK (save this) https://us06web.zoom.us/j/81995207847?pwd=Xe6u6LmIQOmCP5VTnOwWYjDBfZNKGB.1 📅 WHEN Tuesday August 18th at 6PM ET Looking forward to seeing you on the call!

📝 SUMMARY This week's call centered on the evolution from single AI assistants to "chief of staff" multi-agent architectures, with multiple members converging on similar two-tier systems where a coordinator agent delegates to an implementer via shared repositories. Patrick Chouinard detailed his enterprise rollout of 2000+ Claude licenses and the governance patterns required, while others shared strategies for managing model verbosity, measuring real ROI versus vanity metrics, and overcoming organizational resistance to AI coding. Additional discussions covered database migrations for real-time apps, personal assistant tooling, and enterprise adoption tactics. 💡 KEY INSIGHTS The "assistant" model collapses at scale. Patrick described how coordinating many Claude assistants eventually consumes more time than it saves, leading his team to create a two-tier architecture: Claude Cowork acts as "chief of staff" coordinating with Claude Code as "implementer" through a shared local Git ledger, reducing humans to pure decision-makers. Two agents talking directly is the real unlock. Patrick and Paul Miller independently arrived at architectures where coordinator and executor agents communicate and write status to each other without human message relay, freeing the human to act only as a decision-maker. Surface decisions and wins, not just noise. Ty Wells noted that showing only problems creates a demoralizing interface. Effective chief-of-staff agents should highlight progress and successes alongside escalations, not just raw agent output. Set explicit time budgets. Paul Miller emphasized that agent tasks without deadlines can silently balloon from one hour to four, cascading delays. Decisive time constraints prevent runaway context windows. Opus 5 requires verbosity management. Multiple attendees flagged Opus 5 as unusually chatty. Mitigations include Matt Pocock's "wait, what?" skill to detect confusing output and Patrick's discovery that sarcastic, personality-driven prompts naturally produce shorter, clearer responses.

AI Developer Accelerator — Coaching Call - August 11 VIEW RECORDING - 96 mins (No highlights) Meeting Purpose To share progress, discuss AI agent architectures, and strategize on enterprise adoption. Key Takeaways - Chief of Staff (CoS) Architecture: Multiple members are adopting a CoS model, shifting from reactive assistant use to a proactive coordinator that manages tasks, prioritizes work, and initiates agent sessions, freeing up human time for high-level decisions. - Enterprise Adoption Strategy: Overcoming developer skepticism requires proving ROI with direct performance comparisons (e.g., agentic vs. traditional dev delivery) and enforcing governance via mandatory skills and plugins, not just rules. - Convex.dev for Real-time Apps: Convex.dev is being considered for a carpool app to replace Supabase. Its native real-time sync simplifies architecture, but indexing queries is critical to manage costs and prevent bill shock. - New Business Models: AI enables new models like Juan's low-cost ($1.5k) AI photo booth, which may pivot from VC funding to a distribution partnership with event venues. Topics AI Agent Architectures - Problem: Managing multiple AI assistants becomes a bottleneck, consuming more time coordinating agents than doing the work itself. - Solution → Chief of Staff (CoS) Model:

AI Developer Accelerator — Coaching Call - August 04 VIEW RECORDING - 91 mins (No highlights) Meeting Purpose Review AI development projects and share business strategies. Key Takeaways - Ty Wells's "Terrain" system creates custom UIs for existing apps in minutes by applying a front-end skin over their APIs, enabling rapid, personalized user experiences without touching core code. - Morgan's Python driver revived a legacy Dymo printer in 2 hours, using AI to find the protocol and process print-test photos to auto-calibrate label boundaries. - Patrick's team knowledge system uses Git as an agentic memory, hiding complexity from users and using Claude for "Fastlane Merging" of knowledge artifacts. - Juan's AI photo booth is gaining traction, with an event coordinator becoming an impromptu salesperson; the immediate challenge is scaling operations and securing funding. Topics Business & Strategy - Juan Torres (Stetica Flux AI Photo Booth) - Event Success: A recent event generated high engagement, with an event coordinator becoming an impromptu salesperson for the booth. - New Lead: Secured a lead from a country club operations manager in Indio, CA. - Marketing: Finalized a promo video. - Scaling Challenges:

📝 SUMMARY This week's call featured live demos of a zero-backend-change UI reskinning system, strategies for reviving obsolete hardware with AI-written drivers, and a bottom-up approach to enterprise knowledge management using Git as "agentic memory." Members also strategized on consulting deal structures, fundraising tactics for AI photo booths, and hardware arbitrage opportunities. 💡 KEY INSIGHTS 🔹 Zero-Backend UI Reskinning: Build a separate frontend layer that consumes existing APIs to completely reskin applications without touching endpoints or ACLs. This allows multi-tenant products to show different complexity levels to different users (e.g., hiding technical details from basic users while showing dense data to power users). 🔹 AI Hardware Salvaging: Revive obsolete hardware like label printers by having AI reverse-engineer communication protocols and write fresh Python drivers in a half-day. Calibrate by showing the AI photos of physical output (e.g., a printed label) and asking it to adjust its own calculations rather than manual tuning. 🔹 Git as Agentic Memory: Use Git/Azure DevOps as "SharePoint for Agents"—a behavioral memory layer that feeds context into agent actions rather than serving as a queryable RAG database. Build bottom-up at the team level (20-30 people) before attempting corporate-scale systems. 🔹 Problem Description Over Solution Prescription: Avoid commitment bias by describing problems clearly rather than prescribing solutions. Heavily-specified prompts perform worse with Opus/Claude than allowing the model to determine its own approach. 🔹 Paid Proof-of-Concept Gating: Structure consulting engagements with a small paid POC phase before full projects to build trust with budget stakeholders and create easier approval pathways without giving away free work. 🔹 Operational Capability Assessment: Evaluate client operational readiness (support, process stability, team skills) beyond just the code deliverable. 🔹 Event Coordinator as Sales Channel: High-end venue coordinators can become viral sales agents after experiencing AI products firsthand; one showcase event can generate significant word-of-mouth.