free guides, playbooks & real talk
Simplifying AI for my non-techy friends.
Showing 16 guides
I was running too many things from one chat window and my own head. So I gave myself one weekend to put my business and my life into one system with Claude: an AI brain, an org chart, an AI COO, a workflow and five skills on top. Here's the whole thing in order, with my prompts, skills and templates in one free download so you can do it too.
Everyone is showing off how many AI agents they've built and which tools they use. I've been saying all year that none of that matters without the foundation underneath, and Anthropic's own guidance points the same way. Here's the foundation my AI employees run on - the AI brain with its memory and emotional intelligence, the workflow manager and the connectors - and how to set up yours.
Everyone online is talking about AI agents, writing skills, connecting them to Claude and setting up routines. Almost no one is talking about the workflow, and that's the piece that made everything else make sense for me. Here's the strategy behind it, and my ClickUp template so you can set it up yourself.
If you run a business and feel like everyone else has worked out AI while you're still using it to tidy up emails, Claude Code is where that changes. It isn't just for developers. Here's what it is in plain English, why I use it over the chat, and the business jobs it runs for me every week.
I built an AI operating system with 204 AI employees, and very quickly realised it was way too much. Humans are multi-skilled, so why can't my AI be? Here's the team I actually run now, the seven I'd recommend you start with, and a free kit to install each one.
I got caught up in the AI bug and built every skill and employee I could, and ended up with twenty-five skills I didn't know how to use. Now I work with one AI COO, a small team of employees and one shared library of skills, set up with the Incuv8or AI Framework. Here's how, in order, with the prompts.
All you see online are huge AI operating systems, with dashboards, dozens of agents and code, and it looks like that's the only way to have an AI team. It isn't. I run my business with the Incuv8or AI Framework: build your AI brain, map your org, build a COO, add employees only when they pass a test, hand out the work from your task manager and add routines where they're needed. Here's the whole thing, in the order to set it up.
I've been giving my AI employees an identity and an index of skills all year, and it's the same direction Anthropic is pointing everyone in now. A toolkit isn't anything fancy. It's a folder with an agent file that says who the employee is, what it connects to and which skills it pulls from, and here's how to build your first one.
A skill is one process, written down once so Claude does it your way every time. There are three types of skill, they're built differently, and here's how to build each - plus how the AI employees that use them are built.
Every time you want AI to do something new, it's tempting to build another agent. Anthropic's own guidance says to start with one and add more only when you have a reason. Here's what Anthropic actually says, the four-part test I use before I create any new AI employee, and the prompts to run it on your own jobs.
We've all been chasing the AI agent hype, building every agent and downloading every skill and hoping our systems get better. The first thing you actually need to do is the boring stuff: map your AI org chart. Install my AI Org Mapper skill and it interviews you, then maps your COO, your departments, the employees you actually need and the skills each one uses.
I started with ten AI directors and a pile of employees. Now I run one COO, a small team split into departments, and one shared library of skills. Here's how my AI team is set up today, what an AI employee actually is, and how work moves between them.
A skill is how a job gets done. A routine is what wakes it up on a schedule. Here's what a routine is, the three kinds worth building, and the exact template for each - ending with the one that runs an AI employee on its own.
Your AI employees know the job. But they don't know what to work on, where to put it, or when to stop and ask you. That's the workflow - and it's your task manager. Here's the exact setup, and where it fits once your COO and first employees are built.
If you're curious about AI employees but overwhelmed by all the skills and pieces you'd need, build one employee first: a COO. Give it your org chart, let it draft the rest of your team with you, then hand it work from ClickUp. Here's how to set it up, step by step, with the COO template and the prompts.
Once you know which AI employees you need, they need somewhere to read your business from. I keep mine in Obsidian, and every AI I use reads from the same folder. Here's why I chose it over Notion, Google Drive and plain files, how to set it up, and the folder structure I use.
