We're running our weekly team syncs (The Quest, Units, Engine) meet on Tuesdays. We're using the 90 minute, EOS L10 format. We'll go through each QUEST each person is on, and trouble shoot everyones problems together. I thought this could be two diff meets, one for the Q&A, but I'll do is answer Q&A and run the formal weekly team meets. So if you have a QUEST you are working on, I'll see you there. You should be able to update or at least have an answer for each area of QUEST.

Approach specific communities, and offer to "scale" their systems. We do this first with an audit, mapping out their current business, and once they see that you understand their business "maybe better than them", then they trust your judgement. This could be not just a GTM motion like their content or dm or sales process, but can also just be the main thing they sell. For example, I was working with one of those faceless pages. We went from $0k and maxed out at $6000/mo. The "core work" of making faceless pages, the thing they sold, was a 40-hour per week job, but after applying the MAP framework, we saw we could boil it down to 3 workers, at a combined $10/hour TOTAL working full time could produce 5X more output... thats more quality content on their faceless pages. What is the value of doing this? Its not just making a business 5X more revenue... but removing the $10/hour tasks that business owner was spending (what was $10/hour work). The offer is sound as fuck. "I help you scale and 2X your revenue by using the increase of revenue fund itself."

Running an AI Agent isn’t enough. Having alerts if anything breaks is a must have but most people stop there. Having continuous monitoring over agents’ performance is what truly moves the needle. Just like a healthy business always knows everything about employees’ performance, same should happen with AI Agents. With the only difference that you can’t know the real-time performance of employees (their metrics are always lagging) but you can know that of AI Agents. You don’t even need a fancy dashboard. For some simple multi-agent systems you can use a chat interface like Telegram as we did with this one. Fast and effective.

There are different types of QUEST engines I use. They are known as factory plant layouts. This is literally the skeleton of productivity. Without it, you're just a smart guy with knowledge, but with it, you can model the flows of work, can solve, and one step closer to being giga. The easiest engine layout is just a simple straight line that you might see at a sandwich shop. To admin and run these engines, you start with a single leader, usually an expert in the work. For example, lets look at youtube content at scale. Making content is complicated, but orderly and not the invisible chaos. You can map out everything in iso 9001 format, but group each "main workflow" under one routine that you check once a day to see if it was made. Theres a few high level stages that you can model in a task management board view. Scripting -> Recording -> Editing -> Promote We just have a simple routine under each stage -- EZ, aligned to the output goal of the engine. Did you script one new script today? Did you record one new video today? Did you edit one new video today? Did you promote one video today? If not, then do the work to move from each stage. Zooming out as an outsider its complicated but once its explained... its obvious and clear, almost simple... and zooming in you're just doing the work itself. You've seen a simple value-chain diagram. Its just describing the habit chain , and then building a simple, daily, recurring task to go into each area. Thats it. Then its just habits or time management, to clear out the routine. A person if well-balanced, might see "hey yo, it takes 8 hours to produce one video. For example, it Might take 2 hours to write and record a video, but take 6 hours on editing. A full work day for one. But that leader can scale could get a few editors (8 hour day for 80 hours a week total), and the scriptwriter recorder can output more by balancing the load. What most teams do is they just fucking get one editor, buy back the "6 hours of work" and leave it at that. But if a engine produces economic value... revenue or profit, it can be refunneled back into to max it out until it no longer is a constraint.

Acquition.com launched a pocket Alex Hormozi that I picked up for $6k for lifetime use. I think he sold $110M of this a few months ago. Its absolutely giga brain and completely based. Its essentially an ChatGPT AI trained on Alex Hormozi's PKM of notes, how to solve problems, best practices, etc, and his playbooks. If you'd like to use it, let me know, and we'd use it over a call. You need to have a setup Obeya board first. This can be your Kata/mentoring partner. I use it to tell me what to do. And its delivered as direct, no BS how-tos.