Running 15+ bots
Nine habits that keep a big team organized, cheap and under your control.
What to add, and when
The sizes are a rule of thumb from experience, not a study. Your team may need structure sooner.
One lead bot
One bot has the final say. The others give input. A question goes to the lead once, and the lead decides.
Why: Bots arguing with each other burn usage and never finish.
One home per case
Each job has one note that holds its status. Every other note only points to it.
Why: Two notes saying different things is how work gets lost.
From running a large team of bots. Not a study.
Script before AI
Start every routine with a plain script that skips the run when there is nothing to do.
Why: Usage is one shared pool. Empty runs spend it for nothing.
From running a large team of bots. Not a study.
One board
A single page shows failing routines, stuck jobs, quiet bots and items waiting for your OK.
Why: With a big team, problems hide until you look for them.
From running a large team of bots. Not a study.
Size every job
Tag jobs small, medium or large. Run the large ones early in your usage week, while you are under pace.
Why: A heavy job late in the week can lock the whole team out.
From running a large team of bots. Not a study.
Batch bot notes
Bots send one combined note a day to each other, not one message per update.
Why: Every message can wake a bot, and every wake costs usage.
From running a large team of bots. Not a study.
Write each rule once
Keep rules in one folder. Give each bot only a short core, and fix a rule in one place.
Why: Copies drift. Ten bots end up following ten versions.
From running a large team of bots. Not a study.
Check before done
A job is done when you opened the result, not when the bot says so. A checker bot helps.
Why: Bots say done on half-finished work.
Your OK, every time
Sending, posting, buying and paying always wait for you. Another bot saying yes does not count.
Why: Only you can be held responsible for what goes out in your name.