Agent swarm, in plain English: several AIs working at once on narrow jobs, with one coordinating the others, the way a job site has a foreman and trades.

When it's real, the work is split up, every handoff gets checked, and the expensive model only touches the judgment calls. When it's a pitch, "swarm" often just means "our product makes more than one AI call." That's not a swarm, that's software.

The test: ask what happens when one of the steps is wrong. A real setup has a checkpoint, a log, and a defined stop.

Full version in this week's issue: https://manual.praxisx.co/p/models-are-hires-the-system-is-the-company

Which part still doesn't click? Ask here. The follow-ups shape next week's Translation.

My mornings used to start with 45 minutes of opening things. Five Gmail inboxes, 20+ Slack channels, calendar, meeting notes, task list, texts. Just to find out what the day held.

Now one skill runs that whole sweep at 4:45 AM, before I'm up, and leaves one page: what needs me today, what's on fire, what can wait. It drops a note in Slack when it's done, so the first thing I see is a message saying the work is finished, not an inbox full of other people's priorities.

One line I drew on purpose: it reads everything and decides nothing. No replies sent, no tasks moved. I kept the judgment and the send button.

What's the sweep you still do by hand every morning? That's usually the first thing worth automating.

Who I am: Marc Kleinmann, based in New York. I write The Company Builder's Manual and I run Praxis, an applied AI studio building production workflows for small and mid-market companies. Before this: visual effects in the 90s, a design-build firm in Dallas I founded and ran for 15 years, a venture-backed construction-tech startup, and two AI studios. The through-line is putting new technology into a real business and training the people who run it.

What I build: AI systems that do a company's actual work. Morning briefings that run before anyone wakes up, intake automation, content pipelines. What I write about in the newsletter is what I ship for clients.

Team size: one. Me, plus a lot of automation. Rule 3 applies to me too.

Your turn. Three lines is plenty: who you are, what you build, how big your team is.

Three rules. That's it.

1. No pitching. This is the promise in the community description and it's the one rule with teeth. Don't pitch your product, your agency, or your services, in a post or in a DM. Answering "what do you use for X" with a tool you happen to sell is fine if you say you sell it. Cold-pitching someone's DMs is the fastest way to get removed.

2. Specifics over takes. "We cut invoice processing from 6 hours to 40 minutes, here's how" is worth ten posts of AI opinion. Numbers, screenshots, the thing that broke. If you're asking, say what you already tried.

3. Say what size you are. Advice that works at 8 people breaks at 80. Put your headcount in your intro so answers can be aimed at your actual company.

That's the whole rulebook. Break rule 1 and you'll hear from me once. Spam and you won't.
One paid room, four free ones. The Drafting Room is for members of the Company Builders membership. Everything else here is free and stays free. Nothing that is open today gets walled off later.

Cohort members land here too. A seat in the Company Builders Cohort includes the first month of the membership, so cohort people arrive in the Drafting Room on day one. Say hello to them, they are usually mid-build.