Corey Ganim just had me back on the Build With AI podcast to break down exactly how I’m building and selling managed agents for $5K/month. The part that still feels like the future is that my agent, Dewey, now handles most of the fulfillment himself. He builds the client’s agent on Orgo, turns discovery calls and Slack context dumps into skills, onboards the agent into the client’s Slack, and handles customer support after launch. I’ll literally be out on a walk, watching Dewey solve client problems from my phone. Here are the biggest lessons from the system: 1. Agents building agents is already here. Dewey recently built a $5K/month client’s agent and onboarded it into their Slack himself. 2. Build is becoming commoditized. The valuable skill is knowing which questions to ask, understanding the client’s business, and pointing the agent at the right tools and problems. 3. Every agent should have its own identity and resources. Dewey has his own email, phone number, computer, memory, and card. He can sign up for software, pay for tools, communicate with clients, and complete work without waiting for me. 4. Customer support can become part of the agent’s job. Dewey sits inside iMessage and Slack conversations with clients. When something breaks, he can investigate and fix it directly. 5. The stack is simpler than people think. You need a harness like Hermes or OpenClaw, a strong model, an Orgo computer, Agent Mail, Agent Phone, Obsidian, Honcho for memory, Composio, and Latitude. The Agent Bundle packages the agent’s card, email, and phone for around $20/month. 6. Templatize once, deploy forever. Once you build your ideal agent stack, save it as an Orgo template. Then you can clone that exact infrastructure for every new client instead of rebuilding from scratch. 7. Nobody pays $5K/month for an agent just because it’s cool. The agent needs to make the client money. The strongest model I’ve found is helping a business build an agent they can resell to their own customers. That turns the offer from B2B into B2B2B—and makes it much harder to churn.

I have a question that has been bothering me for quite a while. I think the concept of Nick and the idea of virtual desktops is absolutely brilliant, but I still have my difficulties with the idea that a business owner should be willing to pay $5,000 to get it built. Maybe that's because of my advantage of knowledge knowing about the option to simply install a Claude Code or Claude Co-Work agent which anyone can do... How big the pain must be to solve it for a business owner to pay 5K/m? It's not enough just to sort emails. I'm interested in what you think coming from foreign countries maybe where the willingness to pay is different compared to the US.. What are your experiences? Have you ever won customers for such a project, and are they ready to pay? I would be very interested in your views on this topic 🤓

If you've ever stopped doing the work without knowing why, this is probably what's happening. I stopped posting. I stopped working. It was fear (subconscious fear). I was avoiding what I really had to do, without noticing it. Fear that my first potential client says no. Fear that it means the idea is bad. Fear that it means I'm a failure. And on top of that, I kept telling you guys I was going to contact him and never did. I didn't want you to think I was a loser so I just... disappeared. I had no idea what was happening. A week went by like nothing. I was just keeping myself busy with other stuff. So that's why I'm posting this: If you're in this place right now, not moving, not sure why, thinking maybe you should just start a new project, it's not that. It's fear. And the only way out is through. I'm not giving up. This project is too good to abandon to a feeling. I'm still here. Still going. Doing it anyway.

Part 7 was about turning trusted knowledge into repeatable work through SOP prompts. Once those workflows existed, I needed a simple way to find them and start the right one without remembering internal names or digging through setup notes. The final piece I added was a Skill Command Registry. It is a small, human-facing reference that gives each approved workflow a plain-English activation phrase. It can also record an optional shortcut, what the workflow does, its current status, and any reminders about verification or human review. In practice, it acts like a control panel, but there is no dashboard or complicated interface. I can intentionally start a workflow by using a phrase I am likely to remember. For example, second brain capture (SBC) starts the workflow that extracts and routes source material into my Second Brain. Capturing something does not make it trusted or approved. Human review still decides what happens next. Hermes capability builder (HCB) shows me the current top three capability candidates and starts planning for the one I choose. Choosing a candidate does not authorize the build. Building still requires separate approval. That distinction matters. A memorable command starts a workflow. It does not give the workflow new powers or remove its existing safeguards. The registry does not authorize publishing, sending, spending, destructive changes, or work outside the scope I approved. Each workflow still carries its own verification steps and human approval gates. The Skill Command Registry simply makes those workflows easier to find and use intentionally. It improves the interface between me and the system, not the correctness of the result. This closes the eight-part series. It started with making an organically grown vault easier to understand. From there, I added source mapping, capture and review, confidence labels, structural validation, and SOP prompts for recurring work. The Skill Command Registry became the final human-facing layer that ties those workflows together.

Hey everyone, I've created a little schematic by deriving whatever I understood from Nick's YouTube video and I think it just lays it out in a nice illustration. Hope you guys enjoy it. Super happy to be part of the community. Super happy to be building and working on this and looking forward to meeting and networking with you all. Special shout out to Nick and Eric for the awesome video and the awesome text that @Nick Vasilescu Thank you for making this wondeful community - I Want to add a voice ai agent and digital avatar twin into the mix . Think that could handle the ingest and post follow ups looms . Orgo V2? I build stuff like this : mansoor.ai and teerya.com - voice agents - figured i could embed these suckers into the stack