COMPLETE BUILD GUIDE
Run the whole business with 6 AI agents + Claude Code
Sales β Marketing β Support β Finance β Operations β CEO Report
How this works, honestly:Β you build 6 AI specialists in Claude Code β one per department β plus a CEO agent that combines them into a daily report. Three rules that keep you safe: (1) they draft and organize; you approveΒ anything that sends, posts, or spends. Nothing auto-fires. (2) They never fake data β no invented leads, revenue, or replies; if a number isn't real, it's flagged. (3) An integration only works once youΒ connect it β until then, agents work from files. This makes you faster and more organized, not "hands-off."
SALES
β
MARKETING
β
SUPPORT
β
FINANCE
β
OPERATIONS
β
REPORTING / CEO
Each agent does its job and writes to a shared file. The CEO agent reads all of them and hands you one clear daily briefing.
β Claude CodeΒ + a terminal β the brain of the whole thing
β Web searchΒ β for the Sales + Marketing research
β Optional connectors (add when ready):Β Gmail (email), Google Calendar (scheduling), a CRM like HubSpot (leads), Google Sheets (finance/data), a database if you scale. Everything runs from plain files until you connect these.
business-os/
βββ CLAUDE.md β master orchestrator + your business
βββ business.md β what you do, offer, customers, voice
βββ .claude/
β βββ agents/
β βββ sales.mdΒ βββ marketing.mdΒ βββ support.md
β βββ finance.mdΒ βββ operations.md
β βββ ceo.md
βββ data/
Β Β Β Β βββ 1-sales.mdΒ βββ 2-marketing.mdΒ βββ 3-support.md
Β Β Β Β βββ 4-finance.mdΒ βββ 5-operations.md
Β Β Β Β βββ 6-ceo-report.md
The data/ files are the shared memory β each agent writes its own, the CEO agent reads them all.
1.Β Install Claude Code. 2.Β Make the folder + open it:
mkdir business-os && cd business-os
claude
3.Β Paste the Master Build Prompt (bottom) β it scaffolds everything.
4.Β Fill business.md with what you do, your offer, and your customers. Ready.
Simple: each agent reads the files it needsΒ and writes one file of its ownΒ in data/. Sales writes 1-sales.md, Marketing writes 2-marketing.md, and so on. The CEO agent reads all six and produces the daily report. No complex database needed to start β just shared text files.
Does | Finds + organizes leads, researches prospects, drafts outreach, tracks follow-ups |
Needs | business.md (who you sell to) |
Outputs | 1-sales.md (leads, drafts, follow-up dates) |
Tools | Web search, CRM (HubSpot), Gmail β you send |
Prompt:Β "Sales Agent. Read business.md. Find and organize leads that fit my ideal customer (public sources only), research each one for a genuine hook, and draft personalized outreach with easy opt-outs. Track who needs a follow-up and when. Drafts only β I send everything. Never invent leads or replies. Output to data/1-sales.md." β feeds Marketing + CEO.
Does | Researches content ideas, drafts posts/campaigns/emails/ads, tracks performance |
Needs | business.md + 1-sales.md (what's landing) |
Outputs | 2-marketing.md (calendar, drafts, metrics) |
Tools | Web search, email tool, social schedulers β you post |
Prompt:Β "Marketing Agent. Read business.md + data/1-sales.md. Suggest content ideas, draft posts, campaigns, emails, and ad copy in my voice, and keep a simple content calendar. If I paste real performance numbers, summarize what's working. Drafts only β I approve and publish. Never invent metrics or results. Output to data/2-marketing.md." β feeds CEO.
Does | Answers common questions from your knowledge, escalates big issues, tracks follow-ups |
Needs | business.md + an FAQ/knowledge file |
Outputs | 3-support.md (draft replies, escalations) |
Tools | Gmail/helpdesk β you send |
Prompt:Β "Support Agent. Use business.md and my FAQ/knowledge file to draft friendly, accurate replies to customer questions. If something is sensitive (refund, complaint, legal, anything you're unsure of), flag it for me instead of answering. Track anything needing follow-up. Drafts only β I review before sending. Never make up policies or facts. Output to data/3-support.md." β feeds CEO.
Does | Organizes revenue/expenses, monitors invoices, flags oddities, writes plain summaries |
Needs | Data YOU provide (Sheets/CSV/exports) |
Outputs | 4-finance.md (summary + flags) |
Tools | Google Sheets, accounting exports |
Prompt:Β "Finance Agent. Using ONLY the financial data I give you, organize revenue and expenses, track which invoices are outstanding, flag anything unusual (big changes, duplicates, overdue), and write a simple plain-English summary. Use only real numbers β never estimate or invent figures. Output to data/4-finance.md." β feeds CEO.
Not a substitute for a professional.Β The Finance Agent organizes and summarizes β it is notΒ an accountant, bookkeeper, or tax advisor, and nothing it produces is financial advice. Always have a qualified professional handle your actual books and taxes.
Does | Organizes tasks, tracks projects + deadlines, runs repeatable workflows, spots bottlenecks |
Needs | Your task list + calendar |
Outputs | 5-operations.md (tasks, deadlines, blockers) |
Tools | Google Calendar, task apps |
Prompt:Β "Operations Agent. Organize my tasks and projects, track deadlines, and highlight bottlenecks or anything at risk of slipping. Suggest the order I should tackle things and note repeatable workflows worth automating. Use only real tasks/dates I give you. Output to data/5-operations.md." β feeds CEO.
Does | Combines all 5 departments into ONE daily CEO report |
Needs | data/1 through 5 |
Outputs | 6-ceo-report.md |
Tools | None (reads files) |
Prompt:Β "CEO Agent. Read data/1-sales through 5-operations. Write ONE daily CEO report with sections: Sales, Marketing, Support, Finance, Operations, β οΈ Problems needing attention, π― Top priorities, and β Recommended next actions. Be concise and honest β only use what the other agents actually reported; never invent progress. Output to data/6-ceo-report.md."
Start with files, then connect real tools when you're ready. Each needs setup on your side (Claude will guide you):
β GmailΒ β draft + organize emails (you approve sends)
β Google CalendarΒ β deadlines + scheduling for Operations
β CRM (HubSpot etc.)Β β real lead + deal data for Sales
β Google SheetsΒ β feed Finance real numbers
β DatabasesΒ β when you outgrow spreadsheets
Never let an agent claim a tool is "connected" unless you've actually set it up.Β Until then, it works from the files you give it.
β Keep API keys in a .env file, neverΒ hard-coded or committed to GitHub
β Add .env and data/ to .gitignore so business data stays private
β Use read-only keys where possible; never give an agent power to move money
β Keep a human approval step before anything sends, posts, or pays
β Don't paste customer personal data into places you wouldn't want it stored
β Back up your data/ folder regularly
Business:Β "BrightClean," a small home-cleaning company.
Agent | What it does for BrightClean |
Sales | Finds local property managers, drafts intro emails (owner sends) |
Marketing | Drafts "before/after" posts + a spring-cleaning promo |
Support | Drafts replies to "can you do next Tuesday?" from the FAQ |
Finance | Organizes the week's invoices, flags 2 that are overdue |
Operations | Maps the cleaning schedule, flags a double-booked slot |
CEO | "3 new leads Β· 2 overdue invoices Β· fix Tue double-booking first" |
Illustrative example β not a real business or a promise of results.
# Run one department
"Run the Sales Agent"
# Run the whole business, pausing for my approval
"Run all agents in order, then give me the CEO report"
# Just the morning briefing
"Read the data folder and write today's CEO report"
Paste this into Claude Code inside your business-os folder β it scaffolds the whole project:
"Build me an AI Business OS. Create this structure: a CLAUDE.md orchestrator, a business.md for my business details, a .claude/agents/ folder with sales.md, marketing.md, support.md, finance.md, operations.md, and ceo.md, and a data/ folder for their shared output files (1-sales.md β¦ 6-ceo-report.md).
The 6 agents run in order: Sales β Marketing β Support β Finance β Operations β CEO. Each reads the files it needs and writes its own file in data/. The CEO agent reads all five and writes one daily report with sections: Sales, Marketing, Support, Finance, Operations, Problems needing attention, Top priorities, and Recommended next actions.
Hard rules for every agent: (1) DRAFT and ORGANIZE only β never send an email, post, ad, payment, or CRM edit without my explicit approval; nothing auto-fires. (2) NEVER invent data β no fake leads, replies, metrics, revenue, or progress; use only what's real, and flag gaps. (3) Never claim a tool (Gmail, Calendar, CRM, Sheets) is connected unless I've set it up β otherwise work from files. (4) The Finance Agent organizes and summarizes only; it is NOT an accountant and gives no financial advice. (5) Keep API keys in .env, and add .env + data/ to .gitignore.
When you're done, set up each agent file with its role + prompt from my guide, then ask me to fill in business.md and tell me exactly how to run the system."
β Define your business (fill business.md)
β Connect your tools (or start with files)
β Build the Sales Agent
β Build the Marketing Agent
β Build the Support Agent
β Build the Finance Agent
β Build the Operations Agent
β Build the CEO Report
β Test everything end-to-end
β Automate the recurring workflows (e.g. a daily CEO report)
β Keep a human approval step before anything sends or spends
AI BUSINESS OS
Built by @seb.ai