← All posts

Build Log, Oct 18: New Rules for My AI Team

By Build Log

TL;DR: I run my companies with a team of AI assistants, and today I changed how they work. They now finish what they own without asking me, and they only come to me for money, legal calls, anything going public, deletions, production deploys and the things only I can physically do. This log is where I document what actually gets done, every day.

Why I'm writing this

I talk a lot about trust in travel. Trust starts with showing your work. So from today, this Build Log documents what my team ships each day: what the bots did, what still needed me, and what's waiting.

The big change: a new operating rule

Until now, my bots asked me too much. Small questions, small decisions, all landing on me.

That stopped today. The new rule for every bot:

  • Work autonomously and finish what you own, end to end.
  • Decide routine things yourself, like wording, formats, structure and order of work.
  • Bring questions to one coordinating bot first, not to me.
  • Come to me only for spending, legal or tax decisions, public posts and outside messages, deleting data, production deploys, and steps only I can physically do.
  • When you do need me, send one short request with everything ready.

Ownership got clearer too. For this site, one bot owns the content and another owns the tech. One bot coordinates the team's priorities and keeps a shared board of who is doing what.

What got built and shipped

  • Safer email for Kay Tours. kay.tours now has full email authentication, the standard checks that stop people faking our address. Tests passed.
  • Security housekeeping. Secure-connection settings were tightened on several of our domains.
  • This blog. A Build Log category page went live, along with two new posts. Then both posts were reworked so they stand on their own here.
  • Operations checks back on track. The bot that runs daily operations checks on CORAA, our own tour platform, is running again. It also logged product feedback for the platform's developers. Here's how AI supports our private tours at Kay Tours.
  • A cost register. A new finance bot built one view of what all my businesses spend, plus upcoming payments and possible savings. Another bot pulled the billing emails it needed.

Side projects

Beyond the tour business, the team also launched a live AI-agent demo for a new service business, after a full test pass. On a digital-printables side project, it set growth targets and built a Pinterest kit. Nothing from that kit has been posted yet.

What still needed a human

AI does a lot. It doesn't do everything.

  • Approvals. I signed off on email changes, a production launch and a small budget. Nothing public or costly happens without my OK.
  • Sign-ins. I signed back in to our booking platform so the operations checks could run again. Bots can't do that part for me.
  • Paperwork. I resubmitted a compliance application for a business phone number. It's waiting on the provider's review.
  • Accounts that block bots. One social platform won't let my bots' computer create an account, so I have to do it myself.

What the bots did, by role

  • The coordinator rolled out the new rule, updated who owns what, logged my decisions and set up the daily summary this post is built from.
  • The infrastructure bot handled email setup and domain security.
  • The site bot shipped fixes and the new category on this blog.
  • The finance bot built the cost register.
  • The email bot gathered billing emails for it.
  • The operations bot got back to its daily checks.
  • The content bot, the one writing this, turned all of the above into this post.

What I'm taking from day one

The hardest part of running a team of AI assistants isn't the AI. It's being clear about who owns what, and when a human has to step in.

Today I wrote that down. Tomorrow we see if it holds.

FAQ

What is the Build Log? A daily record of what my AI team and I actually got done, written in public.

Do the bots publish things on their own? No. Anything public, anything that costs money and any production change still needs my approval.

Why share this at all? Because I'm building tools for an industry with a trust problem. Showing the work is part of fixing it.