Day 7: Building the Machine Behind the Curtain

Quick Summary

The Context

Day 7 of the Infinite Leverage Blueprint. The team was coming at 10 AM, so I had a few hours alone to knock out things that needed focus. After the team arrived, we had an eight-hour sprint building agent infrastructure that will keep running long after anyone walks away from their desk.

This was the day it stopped feeling like an experiment and started feeling like a company.

The Solo Morning Build

Three tools shipped before the team arrived. First, a certification program calculator live at ai-officer.com where businesses can price out the cost of certifying their team members. Tiered pricing that updates in real time based on group size. It gives people agency. It answers the question before they even think to ask it.

Second, a retreat planning calculator. Different tool, different purpose. This one helps potential retreat attendees see what the experience looks like at different group sizes and configurations.

Third, a visual CRM dashboard. Not a spreadsheet pretending to be a CRM. An actual visual interface for tracking leads, conversations, and pipeline across properties.

I also worked on the homepage, applying the design system so everything feels consistent, and updating the team section to include photos of Dave Brooks and David Nielsen. Small things. But the kind of details that signal: this is real, these are real people, we care about how this looks.

Want to see what these tools actually look like? Reach out and I will send you screenshots of the certification calculator, retreat planner, and CRM dashboard. All built by one person before breakfast.

Infrastructure Day

When the team arrived, we had a list. We started by watching a video together on advanced Claude usage: best practices, how to get the most out of it when you are building real systems, not just asking questions.

From there, we built a global CLAUDE.md setup. A templatized project configuration file that sets variables for GitHub, Supabase, and the shell environment in one pass. Our engineer TRAC had built a setup style that lets you run it once and have everything wired. That alone saved hours of repetitive setup work.

Getting the Project Manager Right

We realized we had not been doing a good job of coordinating the agent layer with the human layer, and in some cases had not really set it up at all. We needed a daily process that worked in the right order.

First: check what humans want to accomplish. Then check agent daily jobs. Add anything extra, align, send a summary. We hooked it into Telegram so by 9 AM every morning, everyone on the team gets a summary of what is happening.

The Marketing Workflow

Building the marketing team took longer than expected, mostly because we had to get the folder structure right before anything else would work. Agents are virtual. They spin up fresh each time. So if you want them to actually function, every folder needs to have the right context and the right skills packed in, without burning a ton of tokens on every run.

Once we got that organized, we figured out the full content workflow. Tuesday the writer agent runs. Wednesday and Thursday is a 48-hour human review window. Thursday the designer agent runs. The following week everything goes live on schedule.

The campaign manager role stays human for now. We want to feel this out for a couple of months before we hand that off. But the sourcing is organized: four content categories, all the source material indexed and ready to go.

What We Actually Shipped

The compact version. No hero lap, no drama, just the list.

What's Next

Edge 8 website rebuild. Fresh content queued for Monday. The writer agent gets its first real run. Day 8 is going to be interesting.