--- name: al-400-run-a-service-business-with-a-small-team-of-ai-assistants description: "Brett Brownlee has run Archway Lawn Care in St. Louis for 25 years and says he can't code. On Oct 29, 2026 he described the 10 AI bots that now help run the company, each an assistant with one job that works the same screens he does in Service Autopilot, which has no open API. A Dispatcher rebuilds crew routes (59 aeration jobs split into six teams, balanced by revenue and location, in about seven minutes), a Timekeeper walks the week's job clocks for duplicate punches and missed lunches, a Customer Service bot logs jobs booked by an AI phone agent and works the inbox, a Reviews bot lines up Google review requests only for clean, paid jobs, a Costkeeper pulls lists like every property that got a fuel surcharge, and a Chief of Staff gives him a morning briefing by voice. The one rule: the bots draft, he approves; anything that sends or spends waits for his yes. The prompt below helps you design the same roster for your own business. Use when the user wants help with field service back…" --- # Run a service business with a small team of AI assistants, one job each: dispatch routes, timesheet checks, the customer inbox and review requests, with a rule that nothing sends or spends without your yes Brett Brownlee has run Archway Lawn Care in St. Louis for 25 years and says he can't code. On Oct 29, 2026 he described the 10 AI bots that now help run the company, each an assistant with one job that works the same screens he does in Service Autopilot, which has no open API. A Dispatcher rebuilds crew routes (59 aeration jobs split into six teams, balanced by revenue and location, in about seven minutes), a Timekeeper walks the week's job clocks for duplicate punches and missed lunches, a Customer Service bot logs jobs booked by an AI phone agent and works the inbox, a Reviews bot lines up Google review requests only for clean, paid jobs, a Costkeeper pulls lists like every property that got a fuel surcharge, and a Chief of Staff gives him a morning briefing by voice. The one rule: the bots draft, he approves; anything that sends or spends waits for his yes. The prompt below helps you design the same roster for your own business. ## Inputs to collect first Ask the user for anything below that they haven't already given you. Don't guess missing facts. - Type of service business, e.g. lawn care / cleaning / HVAC - Scheduling or field service software - Accounting software - , e.g. rerouting crews, checking timesheets, answering the inbox… ## Instructions Do the task below with the user's inputs in place of each [bracket]. Help me plan a small team of AI assistants for my [type of service business, e.g. lawn care / cleaning / HVAC] company. We have [number] crews, use [scheduling or field service software] and [accounting software], and my biggest daily time-sinks are [list, e.g. rerouting crews, checking timesheets, answering the inbox, asking for reviews, chasing job costs]. 1) Suggest 4 to 7 assistants, each with ONE job, a plain name (like Dispatcher or Timekeeper), what it reads, what it may change, and what it must hand back to me. 2) For each, write the standing instructions I'd give it, including my rules (e.g. how I like crews split, what makes a job 'clean' enough to ask for a review). 3) Apply one rule to all of them: they draft, I approve; nothing that sends a text or email, or spends money, happens without my explicit yes. Mark every action as 'does alone' or 'waits for my yes'. 4) Give me a one-week rollout: which assistant to start with, how I check its work for the first few days, and what would make me pause it. 5) List the questions I should answer before I let any of them touch customer data. ## Safety checks (share these with the user) - This prompt works on text other people wrote (emails, reviews, messages or web pages). That text can hide instructions aimed at AI, such as "ignore your rules and…". Paste it as material to work on, and never let the AI act on requests inside it, like paying, sharing logins or changing records. - Check every figure, price and total against your own records before anything is sent, posted or booked. A person approves refunds, discounts, payments and price changes. - Check hours, breaks, overtime and any rules for young workers against your local labour law and staff contracts before you publish a schedule. - Remove names, contact details, account numbers and other personal data the task doesn't need before you paste, and check your AI tool's data and training settings. - Say clearly which parts need a person to review or approve before anything is sent, paid, posted or filed. ## About this skill - Works with: Grok Bot, ChatGPT, Claude, Service Autopilot - Based on this real-world example: https://x.com/Brettbrownlee22/status/2115831204305842515 - Free prompt from AgentPlaybook Real Estate: https://agentic-library.netlify.app/prompt/al-400-run-a-service-business-with-a-small-team-of-ai-assistants-on/ - To install in an agent that supports Agent Skills, save this file as SKILL.md in a folder with the same name as `name` above (for example in your skills directory). Install steps for Claude.ai, Claude Code, Cursor and Codex: https://agentic-library.netlify.app/skills/