Staff of Agents

The AI Staff Playbook · Coming soon

How one person created a business on his iPhone with $100 budget and a team of AI agents.

Staff of Agents: The AI Staff Playbook

The job descriptions, skills, routines, and rules I use to run a team of 20-plus AI agents from my iPhone, by voice and text. Written for founders and creators who don't code. Set yours up in seven days.

The story

At 10:49 on a Tuesday night in October, I picked up my iPhone and asked my AI assistant to come up with a product people need right now. Then build it with the rest of my agent team, and handle the marketing.

It pitched two ideas. I picked one. At 11:00 PM, eleven minutes after I started, the first full draft of this playbook existed, with a sales page and launch posts beside it.

It was a first draft, and I'm editing it, the way I review everything my agents write. But I never opened a laptop to get there, and I'm not going to for this whole project. I'm building it from my phone, on voice calls, voice notes, and chat. My agents have their own computer in the cloud. I have a phone.

Two rules keep it honest. The project has a hard budget cap: it has to start for under $100. And the build log is public, timestamped from that first message, so you can watch what I asked for, what the agents did, and what went wrong. There's no revenue to report yet. When there is, it goes in the log, along with the misses.

I built the agent team itself the same way, from my phone, one conversation at a time. The morning before, I was driving into town and remembered I hadn't booked a desk at my coworking space. I tapped the voice button and said, “Can you set up a desk for me at WeWork for today?” About fifteen seconds later the agent said it was booking my usual location, full day, on membership credits. I told it, “Until further notice, that will always be the case. So you don't need to ask.” The next morning it didn't ask me anything.

That booking was safe because of rules I'd set up earlier, also by talking to my phone. Credits only. If the site asks for a card, stop before the card screen and ask me. Never cancel or change a booking. When I say “always,” save it as a default.

I'm not a developer. I run three newsletters, work with galleries and artists, and build apps without writing the code myself. A team of more than 20 AI agents handles a lot of that work now. One sweeps roughly 20 mailboxes every morning and tells me only about money, deadlines, and replies only I can write. One acts as my chief of staff and keeps my morning briefing to one screen. One drafts my photography newsletter every week, and I approve it before anything goes out. When Google Drive on my MacBook stalled for hours, an agent found the cause on the Mac remotely, and I did my part of the fix on a voice call from my phone.

This playbook is that setup, written down so you can copy it.

What's inside

  1. Before you startA business built from a phone.The experiment behind this book: the 10:49 PM start, the $100 cap, the public build log, and what you need (a phone and an agent app).
  2. Chapter 1A desk booked from the car.Why a non-developer can run an AI staff now, what it costs you in time and attention, and what a normal week looks like.
  3. Chapter 2The org chart.My full roster, why one chief of staff matters more than any other agent, the naming system I use (and the rename that confused half my team), and how work moves between agents.
  4. Chapter 3The job description.The eight parts of a persona file, plus my real email agent's file, lightly redacted, with notes on why each line is there.
  5. Chapter 4Skills.How to turn a task you keep repeating into a saved procedure any agent can run. The real example is my weekly photography newsletter, broken into six steps, with the note I used to pass it to my newsletter agent the night before an issue was due.
  6. Chapter 5Routines.My weekly rhythm (morning briefing, inbox sweep, news brief, newsletter build, weekly review) and the rules that keep them to one screen. Includes a real inbox sweep: what it caught, what it got wrong, and how it failed safe.
  7. Chapter 6Guardrails and approvals.Draft, don't send. Stop before the card. Never delete. Never cancel a booking. Separate accounts. A 12-line rules block you can paste into any agent.
  8. Chapter 7Big jobs for coding agents.How two cloud agents built contact databases overnight (554 photographers and 8,643 art organizations) under budget caps, using one rule: validate 5 to 10 samples first, then scale. Plus how an agent fixed my Mac's stalled Google Drive (about 196,000 files it was trying to back up) while I stayed on my phone.
  9. Chapter 8The nightly question.“Where did I block you?” The one-question review that cuts the time you spend on your agents, adapted from Nat Eliason's work with his agent Felix.
  10. Chapter 9Your first seven days.One to two hours a day. By day seven you have four agents, a rules block, two skills, and three routines running.
  11. Chapter 10Templates.Persona file, skill file, rules block, six routine prompts, a handover note, a big-job brief for coding agents, and a banned-words list for writing agents. Copy, fill in the brackets, paste.

Format: PDF, plus the templates as plain-text files.

Who this is for

Who it's not for

Questions

Can I really do this from just a phone?

I am. I set up my agent team from my iPhone, and everything in this project has been done by voice and text from it. The agents do their computer work on their own cloud machine. You can use a laptop if you'd rather.

What does the $100 cap cover?

The cost of starting this project: things like the domain and the first tools. It doesn't include the agent app I already pay for. The running total is in the public build log.

Do I need to use the same app you use?

No. I run my team in the Grok Bot app on my iPhone. Everything in the book works in any agent tool that gives each agent standing instructions, saved procedures, and a schedule.

Do I need to code?

No. I don't. When a job needs code, I describe it in plain English and give it to a coding agent with a sample gate and a budget cap. Chapter 7 shows how.

How much time does this take?

Plan on one to two hours a day for the first week. After that, I spend most days reviewing drafts and answering a few questions. That time shrinks as you save more standing defaults.

What will it cost to run?

It depends on your tools, and prices change often, so I don't quote numbers. The book shows you how to start with one paid tool and add only when an agent is stuck without something.

Is it safe to give an AI my email?

It's as safe as your rules. Mine can't send, delete, or reply without my approval, can't type my passwords, and must leave anything it can't classify unread. You get the full rules block.

Will this work if I only have one business?

Yes. Start with four agents. Most people won't need twenty.

Is this written by AI?

My agents helped draft it, the same way they help with everything else, and I reviewed and edited every page. The examples come from my own setup.

Not on sale yet

Staff of Agents: The AI Staff Playbook is being finished now, in public.

Checkout isn't open yet. If you'd like a note the day it launches, send me an email and I'll write back when it's ready.

Email me when it launches

This opens your email app and goes straight to my inbox.

Your first agent will take about an hour to set up, and you can do it from your phone. The book has the job description, the rules, and the first routine ready for you to copy. The build log is public at staffofagents.com/log if you want to watch the rest of this business get built.

I'm Chris Davies. I'm in Los Angeles, I'm not a developer, and I'm writing this from my phone.