The new Agent Operators episode with Karsten Stinis is live. Karsten installs managed AI agents for businesses in Belgium. His offer is €2,750 for the setup, then €250 a month for support. The part I'd pay attention to is what happens during the installation: he watches the client work, finds a recurring task, and aims to have something useful waiting for them the next morning. Before you install the agent, decide what it will finish. A morning briefing is a good example: meetings, open tasks, and unanswered emails worth following up on. The person can open it, check the sources, and decide whether it helps. Whether you're building for yourself or a client, try scoping one overnight job: 1. The job: choose one recurring task. 2. The inputs: name the inbox, calendar, or task list it needs. Connect the accounts and check access. 3. The result: decide where the output should appear and when it should be ready. Make it easy to trace back to its sources. 4. The review: choose who checks it. Keep outgoing messages as drafts for the first run, and have a person approve them. Run it once. Read the output with the person who will use it. Use their corrections to improve the next run before adding another job. In the episode, Karsten walks through Hermes on Orgo, Composio for connecting business tools, Honcho for memory, and how he monitors usage and incidents. Keeping the workflow working is part of the service. He also reports one client's agent setup being built in 22 minutes. Humans still handle the tool and account connections. Watch the full conversation: How He Sells AI Agents for €2,750 + Monthly Support https://www.youtube.com/watch?v=Y8MJG3iDtSo What would you want your agent to have ready tomorrow morning? Share the job below.

Most multi-agent demos stop at "look, two agents can talk." In a client business, the hard part is knowing who owns the work, whether it was actually done, and what happens when an agent stalls. For Episode 3 of Agent Operators, I sat down with Jason Myers of AppLayer. He built Tango after realizing he had become the human copy-paste layer between his agents. We connected Hermes to a shared task list, watched workers claim jobs, and dug into audit trails, task leases, and recovery. Then I showed how Orgo cloud computers let you see and control the work when an agent needs a real desktop. In the conversation: • 04:19 — Hermes creates a task in Tango • 19:56 — Preventing two agents from doing the same job • 21:16 — Recovering stalled tasks • 30:25 — Agents working on Orgo cloud computers Watch the full 36-minute episode: https://youtu.be/LKCZXIGmrY4 If you’re deploying agents for clients, where do your handoffs still depend on you?

I just built a full AI employee from scratch in this video. Everyone’s hyped on agents but barely anyone’s actually showing how to build ones that can really work inside a business. Here’s the entire stack I spun up live (no holding anything back): • Cloud computer running Hermes on Orgo • Its own email (AgentMail) • Its own phone number (AgentPhone + iMessage) • Telegram as the main chat interface • Every tool & connector hooked up through Composio • Credit card so it can actually spend money • Obsidian vault as its knowledge base / second brain • Latitude for observability so I know when shit breaks I made one main orchestrator agent (named it Hubert) that stays in charge 99% of the time and just hands tasks off to specialized sub-agents underneath it. One giant bloated agent is a nightmare to debug. This way everything stays clean and purpose-built. Full live build, every prompt I pasted, every terminal I opened… it’s all in there. And I’m giving away the complete templates for the orchestrator + every sub-agent I build going forward. I'm giving you actual employees that can do real work. Watch the whole thing here: PS - the template is free here on Github: https://github.com/nickvasilescu/nicks-stack