How I work
I built my own AI system. It made my work 10x better.
AI agents check every client account every day, catch what's off, and bring each fix to a human before anything goes live. My team and I spend our time on judgment, not busywork. Nothing depends on one person's memory, and nothing slips through the cracks. I call the whole system the village. This page shows how it's built. I build the same kind of system for local service businesses.

The problem with traditional marketing agencies.
Most marketing agencies run the same play. The owner sells you on the call. Then your account goes to junior staff, often offshore, who juggle dozens of clients at once. It keeps the agency's margins high. It trades away your results.
I saw it from the inside. So I went the other way. I spent years turning the way I run an account, down to the small details, into systems. Then I put my knowledge and systems inside a team of AI agents. They get smarter every day, and they run everything through me, so the quality and detail never slip. Your account gets my level of detail every day, not a junior's.
The village at work
Every agent works from one brain: what my agency knows.
- 1The village knows my agency
Clients, accounts, rules, and the record.
- 2An agent pulls what it needs
Only the facts for its job.
- 3The job gets done
Live changes wait for my yes first.
The framework
How the village is built, part by part.
I built my agency like a small town. Every building is a real part of the system. Every name is a real agent with its own instructions.
The whole idea in one breath: agents do the work, every job proves it ran, nothing live happens without my yes, and everything gets written down. The four sections below show how.
01Who decides
What waits for my yes, and what doesn’t.
The short version: the agents can prepare anything. They cannot spend, publish, or contact a customer without me.
No part can both do the work and approve it. The teams prepare, the Keymaster holds the keys, I say yes, and the Record Office writes it all down.
- Everything lives in the client’s own accounts: every login, every file.
- Passwords are typed by me, where they’re used. Never in a chat, never stored by an agent. Agents never see one.
- Anything a customer will see is a draft until I send it.
- Spending money needs my yes, with the amount read from the live account, not from memory.
- Anything that touches the outside world happens in three steps: proposed, approved, then confirmed. Each step is written down, and the record is never edited.
- A live change counts only after the real account is checked again to confirm it.
- If it can’t do something, it says so and stops. A number it can’t read shows as unknown, never as zero.
Waits for my yes
- Spending money, or changing a budget.
- Any change to a client’s live account.
- Anything that reaches a customer or goes public: a text, a post, a published page.
- Connecting a new tool or account.
- Putting a new agent on live client work.
- Approving new research as the rules the teams work from.
It just tells me
- Building inside the village: new departments, new teams, draft skills.
- Breaks, and the fixes that stay inside the village.
- The short version of each day, and an alert when something breaks.
02The map
Every part of the village.
The short version: every job, check and decision has a building and a name, so I can see where things happen. Start with the three marked.
The Mayor is the one agent that talks to me. It sits in the middle with my phone. Everything else is grouped by what it does. Open any part to see how it works and what breaks without it.
In the middle
who decides, and how word travelsStart hereTown Hall the Mayor The Mayor plans the work and brings me the big questions. How it works
- Only the Mayor talks to me. Workers report to their team lead, and team leads report to the Mayor.
- The Mayor reviews the whole village twice a day: new results, new breaks, and anything I sent. It also checks for my messages every few minutes.
- It may approve building inside the village on its own: new departments, new teams, draft skills. That is the one place it does more than propose.
- It never touches a live client account, spends money, publishes, or messages anyone outside. Each of those becomes a yes-or-no question for me. When unsure, it asks.
Without itI would get every little question, or none of the big ones.
Joey’s phone me Where the village reaches me: the big questions, the daily news, and the orders I send back. How it works
- The village asks before anything that spends money, reaches a customer, or changes something live. Each ask is one plain question I can answer yes or no.
- Asks arrive as a short numbered list, so I can answer by number from wherever I am.
- Orders go the other way too. One text to the Mayor can start a whole new team.
- A yes in a chat is not enough by itself. It counts once it is written in the Record Office, next to the order it approves.
Without itThe village would either act without me, or sit and wait until I got to a desk.
Question it answers: MAY · Is it allowed?
Herald’s Tower the Herald Sends me the short version of each day, so I am never buried in alerts and never left guessing. How it works
- The Mayor writes the message. The Herald carries it to my phone word for word. It never rewords, filters, or decides anything.
- My replies travel back to the Mayor the same way, word for word.
- The daily text goes out only when something changed: a new ask, an ask that went away, or a reply of mine that was handled. No news means no text.
- If a message does not get through, the Herald says so. A failed delivery is reported, never dropped.
Without itI would drown in alerts, or hear nothing at all.
Runs the work
where the daily work happensStart hereWork Hall the desk workers Every desk is one job that runs on its own schedule. When it is time, the job runs. Nobody presses a button. How it works
- Each desk is one job, done by one worker, on a set schedule: every few minutes, daily, weekly or monthly. A timer wakes it.
- A job counts as done only if it ends by reporting
RESULT: OK. If it crashes, freezes, gets signed out, or skips that line, it is marked as failed. - Every run goes into a run log with its start, its end and its result, so a missed or failed run is easy to see.
- A job that keeps failing gets slowed down instead of retried forever. One success puts it back on its normal pace.
Without itWork only happens when someone remembers.
Example desk: Pip runs the 6 AM daily check-up on every client’s ads, without changing anything, so I hear about a drop the same morning.
Question it answers: DO · Did it really happen?
Client teams Max, Sage, Vesta, and two newer teams The teams that do the work: Google Ads, Google Maps, Reactivation, Facebook Ads, and Growth, which finds new clients for my own agency. How it works
- Each team has a lead and a few specialists, each with one clear job. The lead turns their evidence into one recommendation.
- Every team has a Measurement & Outcomes specialist, whose job is to check what really happened after the work.
- Teams prepare the work. Anything live waits for my yes.
- Each team has its own Professor in the Academy and its own desks in the Work Hall.
- Google Ads team, led by Max. Runs clients’ Google ads, and blocks the searches that waste money.Specialists: Search & Experience, Measurement & Outcomes. Account and budget changes wait for my yes.
- Google Maps team, led by Sage. Gets clients found on Google Maps and in search, without paying per click.Specialists: Local Presence & Reputation, Site & Content, Measurement & Outcomes. Anything published under a client’s name waits for my yes.
- Reactivation team, led by Vesta. Texts a client’s old customers and brings them back.Specialists: Audience & Rights, Offer & Message, Measurement & Outcomes. No text goes to a customer without my yes.
- Facebook Ads team. Runs Facebook and Instagram ads. Built from one text, in about half an hour.Specialists: Creative & Audience, Measurement & Outcomes. No live ad account is connected and nothing is spent until I approve.
- Growth team, the newest. Finds businesses that fit and drafts the outreach, for my own agency.Specialists: Prospect Research, Channel & Outreach. No message goes out without my yes.
Without itClients’ phones would go quiet.
Market where clients meet the village Where clients see their leads and results. How it works
- Each client sees their own leads and results. The Market also keeps the approved file on each client: goals, priorities and limits. A new fact goes in only once it is approved.
- Reports keep two things apart: what the village did, and what happened in the business afterward.
- Every “what we did” line points to an entry in the record. No claim goes in without a receipt behind it.
- A number the village cannot get is shown as unknown, never as zero.
Without itClients would have to ask me what is going on.
Question it answers: KNOW · Is it true?
Keeps it safe
checks, keys and the recordWatchdog the Watchdog Checks every 30 minutes that each job really ran. If one did not, it raises the alarm. How it works
- It runs a plain health check with no AI in it: did each job run, did it pass, is anything stuck. So it keeps working even when the AI is down or signed out.
- It alerts my phone when the list of problems changes, reminds me every 6 hours while something stays broken, and tells me once when it clears.
- It never repairs anything. Finding is its job. Fixing belongs to the Brigade.
Without itA job that stopped would look exactly like a quiet day.
Brigade Station the Marshal and the Responders When a job breaks, they find the cause, fix it, check the fix worked, and write down the lesson so it does not break the same way again. How it works
- Every morning the Marshal patrols with the same health check the Watchdog uses, opens one incident for each new failure, and hands it to a Responder.
- The Responder confirms the failure is real, pins down the one real cause, and fixes that cause, not the symptom.
- Then it proves the fix by running the same check again. A fix that reports “success” is not trusted until the check agrees.
- It does not change live systems alone. A fix to a shared script, a password, or anything a customer sees goes to its owner for approval.
- Every incident ends with a guard: a test, a check, or a louder alarm, so the same break shows up sooner or cannot happen at all.
Without itSmall breaks pile up until a client notices.
The Brigade fixes the village’s machinery, not the teams’ judgment. A bad call on an ad account goes to the Academy instead.
Question it answers: LEARN · What did we learn?
Keymaster Gate the Keymaster Every new tool gets tested before it is trusted. Passwords stay locked away. Agents never see them. How it works
- Each agent gets a key that opens only what its job needs, and nothing more.
- Passwords never pass through an agent or the Keymaster. When a tool is connected, I sign in myself, and the password stays where it lives.
- A connection counts as working only after it actually pulls real data. Nothing is marked working on faith, and every check is dated.
- It keeps one list of every connection and its true state: working, needs sign-in, broken, or retired. It also flags any key left sitting in a file or a link where it should not be.
Without itOne bad tool could reach every client’s account.
Question it answers: MAY · Is it allowed?
Start hereRecord Office Eve Every job, decision and mistake is written down. I can check any step, any day. How it works
- The record only grows. Entries are added, never edited. A mistake is fixed by a new entry that points back at the old one.
- One event, one entry: an order approved, a job done, an incident opened. Each is saved on its own, with only the files it changed.
- Work that skips the record does not count. An approval is real only once it is written here, not in the chat that carried it.
Without itNobody could check what happened, or why.
Question it answers: DO · Did it really happen?
Gets smarter
what the village knows and teachesAcademy the Professor The Professor studies each subject, checks every fact against the source, and writes the lessons and the tests. How it works
- There is one department for each client team. Each has its own Professor, who researches the subject once a week.
- Tests are blind. The answers stay locked, and a test is never reused once an agent has seen it. A case used to teach is never used to test.
- Pass the tests, then do one real job while the team watches. Only then does an agent touch client work, and even then it prepares work for approval.
- Once agents do real work, the Professor grades it. What went well and what went wrong becomes a new lesson for everyone.
Without itUntested agents would practice on real clients.
Question it answers: CAN · Is it proven?
Library the Librarian The village’s book. Every checked fact and written skill is kept once, so every agent works from the same truth. How it works
- Each fact is tied to the source it came from, with the date it was checked. Where sources disagree, the book says so.
- New research comes in as a numbered set. I approve each set before the teams work from it, and then it is locked.
- The Academy teaches from approved sets, so what agents learn and what they use at work match.
- Missing evidence is written down as missing. Nobody fills a gap with a guess.
Without itEach agent learns alone, they disagree, and the same mistake repeats.
Question it answers: KNOW · Is it true?
Grows the village
new teams and toolsBuilder’s Lot the Builder Builds new teams and tools. When a client needs something new, the village grows. How it works
- It builds from saved blueprints, so every new team has the same shape: a Professor in the Academy, a lead and specialists on the team, and desks in the Work Hall.
- It checks for approved orders every few minutes. Nobody has to start it.
- On its own it only builds inside the village. Connecting a live account, spending, or launching waits for my yes.
- Each order it claims, finishes, or gets stuck on is written in the record as it happens.
Without itEvery new service would mean weeks of me building it by hand.
The Facebook Ads team went from the Mayor’s order to built in about half an hour.
Every part reports up to the Mayor. Only the Mayor talks to me.
03Five questions
Five questions every agent asks, in order.
The short version: these habits matter more than any single agent. They are why the village can be trusted with real accounts.
Before any agent does a job, it works through these five questions. Every agent learns them first, before it learns its own job. They are the same habits I give away as skills.
-
KNOW
Is it true?
Check the number before trusting it. A zero might just mean the counter is broken.
Agents work from checked facts, not memory. Every fact in the Library is tied to its source and dated, and each client’s facts live in the Market. A number that cannot be read is written down as a gap, never guessed and never turned into zero.
-
CAN
Is it proven?
An agent touches client work only after blind tests and one real job under watch. Even then it prepares the work. It does not push anything live on its own.
-
MAY
Is it allowed?
Before changing anything, ask: can it be undone, and how much could it break? When in doubt, ask instead of guessing.
Each agent gets a key that opens only what its job needs. No agent ever has a password. Anything that spends money, reaches a customer, or changes something live waits for my yes. Being able to do something never means being allowed to.
-
DO
Did it really happen?
Jobs run on their own schedule. A job counts as done only when it reports that it finished, and a live change counts only after the real account is checked again to confirm it. Every step gets its own entry in the record.
-
LEARN
What did we learn?
Fix the cause, not the symptom. The symptom is a clue to what really went wrong.
Every break ends with a written lesson and a guard against a repeat. The Professor grades real work and turns it into new lessons and tests. When an agent gets something wrong, it doesn’t patch itself. It saves the example, works out which part went wrong, and proposes the smallest fix to whoever owns that part. The fix is tested on a different example before it goes in.
04Real examples
Three real days, step by step.
The short version: in each one I answered yes or no a couple of times. The village did everything else.
Three things that really happened, step by step. Each step names the part of the village that did it. Yellow dots mark where the work stopped for my yes.
Real: the 11% question came from the village’s daily check-up. The client’s name is hidden.
From the 6 AM check-up to my yes, and on to the evening
One client’s cost per lead went up 11% in a week. Here is the whole day, from the first read of the account to the short version on my phone, and the two places it stopped for me.
-
6:00 AM: the check-up runs
A timer wakes the check-up desk. Nobody presses a button. It reads every client’s ad account, read-only, and leads with one question: is the client’s money coming back toward their goal?
-
Each account gets sorted
Each account gets a short plan, and anything odd gets flagged. Nothing reacts to a single bad day. Today one client’s cost per lead is up 11% this week. The number comes from the live account, not from memory. Anything it could not read is listed as a gap, never as zero.
-
One question, in plain words
The Mayor turns the jump into one question, with the client’s name hidden. The Herald carries it to my phone, word for word. I say yes.
A client (name hidden): cost per lead up 11% this week. Take a look?
-
Judged case by case, not by a cutoff
Max’s team looks at the searches behind the clicks. A search that has been costing money with no leads gets judged: does it match a service we sell, what was the person trying to do, did Google send it to the right ad. The finding: searches that never turn into customers. One of them ate a big chunk of the budget with zero calls.
-
One ask, with the reasoning
The answer is “block it.” That changes a live ad account, so the ask comes to me with the reasoning attached. Nothing moves until I tap yes.
-
Applied, then double-checked
On my yes, the block list goes in. Then the account is checked again to confirm every block really took. The change, my yes and the check each get their own entry in the record.
-
All day: every 30 minutes
The Watchdog checks that each job really ran. If one did not, it raises the alarm, and the Brigade takes it from there.
-
Evening: the short version
The Mayor reviews the whole village and writes what it did and what is waiting on me. The Herald sends the short version, and I read it on my phone.
What this shows: the village finds the problem and writes the fix. I answer yes or no. Two yeses from me that day, and it wrote everything down. In its first week, this check-up found about $550 a month of wasted spend on one account.
Real: this happened on Sept 2.
A false alarm, fixed for good
Four job runs were marked FAILED even though each one had done its work. Here is how the Brigade found out why, and made sure it would not break the same way again.
-
Four runs marked FAILED
By the morning of Sept 2, four runs of different jobs had been marked FAILED in the run log. One of them was Pip’s morning check-up.
-
Read what the job actually did
The Brigade’s morning patrol opened one incident. The Responder read each job’s own log instead of trusting the FAILED mark. All four jobs had done real, correct work.
-
Name the root cause
Every job has to end with one exact line,
RESULT: OK, to count as done. One job wrote that line in bold, as**RESULT: OK**. The checker only recognized plain text, so a finished job looked like a crash. The other runs had left the line out.Two causes, kept apart: a checker that was too strict, and jobs that skipped the line.
-
A shared fix needs a yes
Every job in the Work Hall runs through that checker. The Brigade may not change a shared script on its own, so it wrote the exact fix and sent it for approval. Once I approved fixes of this kind, it went in.
-
Prove the fix
The fix was tested against the same saved logs. The bold line now passes. A log with no done line still fails, as it should. The fix ends the false alarm without hiding a real one.
-
Write down the lesson
The lesson went into the incident record: “I could not find the done line” is not the same as “the job crashed.” Read a job’s own log before trusting a FAILED mark. Jobs that still skip the line now get a stronger closing instruction, one job at a time, each checked after.
What this shows: it repairs itself, but never touches shared machinery without my yes. I was told, gave one yes, and that false alarm cannot happen again.
Real: the Builder set this team up in about half an hour. A few days later the Brigade caught one step that was missed.
One text, one new team
I texted the Mayor: “Let’s build a Facebook ads service.” Here is what each part of the village did with that one message.
-
The order
I texted the Mayor: “Let’s build a Facebook ads service.” I added one limit: build it inside the village for now, and connect no live ad account and spend nothing until I approve. The Herald carried it to the Town Hall word for word.
-
Split into orders
The Mayor matched the request to a saved blueprint for a new service. The blueprint splits it into orders: a new Academy department, a new team, and a connection to the ad accounts. Building inside the village needs no second yes, so the Mayor approved those orders itself. Touching a live account is never done alone, so that part waits for me.
-
Built in about half an hour
The Builder checks for approved orders every few minutes, so nobody had to start it. It built the new department and the new team: a lead, the specialists and their jobs. From the Mayor’s first order to the last one marked done: about half an hour. Each order was written in the record as it moved.
-
Research, checked
The team’s new Professor researches how Facebook ads work today and checks every claim against its source. The checked rules go into the Library as a numbered set. I approve each set before the team works from it.
-
Train and test
New agents train on those rules and take blind tests. Pass, then do one real job while the team watches. Only then do they touch client work.
-
Access, without passwords
Connecting a real ad account is its own step, done live with me. I sign in myself. The agents never see a password, and the connection counts only after a real read works.
-
Ready
New desks light up in the Work Hall: the new team’s weekly jobs. The Herald tells me the Facebook Ads team is ready.
-
The missing step
A few days later the Brigade’s patrol caught one step left undone: the new team’s weekly research job had been written but never switched on. Finding steps like that is the patrol’s job.
What this shows: a new service is one text and about half an hour. One order from me. The village did the rest.
For your business
The same shape works for other businesses.
Nothing here is special to marketing. Swap the teams and you have the same village for a roofing company, a landscaper, or a remodeler: agents that do the daily work, one place that writes everything down, and an owner who only answers yes or no.