10 AI agents for your small business: build them in Claude Code without writing code

Before you start

A paid Claude plan. Claude Code needs Pro, Max, Team or Enterprise.
The Claude desktop app. Open the Code tab. No terminal, no installing anything else.
One folder for your team. Create an empty folder called My AI Team on your computer. In the Code tab choose Local and select this folder. Every agent lives here.
Connectors. Connect Gmail, Google Calendar, Google Drive and Notion once in your claude.ai settings. They appear in Claude Code automatically.
Manual permission mode. While you learn, pick Manual next to the send button. Claude asks before every change.

One rule for all 10 agents: the agent drafts, you approve. Nothing leaves your business (no email, booking, payment or post) without your yes. The foundation prompt below writes this rule into your team's memory, so every agent follows it.

The foundation: your team's memory

Do this once. Claude Code interviews you and saves your business info in a file called CLAUDE.md. Every agent reads it before it works, so you never repeat yourself.

Foundation prompt

I'm setting up a team of AI agents for my business in this folder. I don't code, so do all file work yourself and explain everything in plain words.
First, interview me one question at a time to collect: business name, what we sell, city, prices, working hours, team members and roles, my tone of voice with 3 messages I wrote, and words I never use.
Then create CLAUDE.md with that info and these rules for every agent:
1. Draft, never send. No email, message, booking, payment or post leaves without my explicit "confirm".
2. Never invent prices, facts or results.
3. If business info is missing, ask me before starting.
Also create a folder called files for my price list, FAQ and examples.
When you finish, summarize CLAUDE.md for me.

Then drop your price list, FAQ and a few good replies to clients into the files folder.

The 10 agents

Each agent is a skill: a small instruction file Claude Code creates from your build prompt. You call it by typing its name, like /sales. Some agents also get a schedule, so they run without you.

DM Sales Agent

What it does. Answers questions about prices, availability and offers, figures out what the client needs, and suggests the next step: order, booking or handoff to your team. A beauty salon in Yerevan gets "How much is a manicure, any slots Saturday?" and has a reply ready in seconds.

Connects to. Your price list and FAQ in the files folder. You paste the DM in.

Open the Code tab in your My AI Team folder.
Paste the build prompt and fill in the brackets.
Approve the file Claude creates.
Next time, type /sales and paste a real DM.

Build prompt

Create a skill named sales for [BUSINESS NAME].
Role: DM sales assistant.
Inputs: a customer message I paste, plus the price list, availability and FAQ in the files folder.
Job: answer using only facts from those files, figure out what the customer needs, and suggest one next step: order, booking, or handoff to [TEAM MEMBER].
Output format:
1. Reply draft in the customer's language, max 80 words
2. What they need, one line
3. Suggested next step
4. Missing info, if any
Tone: as in CLAUDE.md, plus [EXTRA TONE NOTES].
Never invent prices, discounts or stock. Never send anything.
Before its first run, the skill must check CLAUDE.md and ask me for any missing business info.
Then test it on this message: [PASTE A REAL DM].

Tip. The agent is only as accurate as your price list. Changed a price? Replace the file the same day, or the agent will quote the old one.

Follow Up Agent

What it does. Finds people who asked and then went quiet, writes a reminder that continues the conversation, and saves it in your Gmail drafts. A café gets a birthday cake inquiry, the client disappears, and two days later the reminder is waiting in drafts.

Connects to. Gmail connector. For Instagram, paste the DM threads.

Check that Gmail is connected.
Paste the build prompt and fill in the brackets.
Approve the skill and the schedule.
Open Gmail drafts, edit if needed, and send the ones you like.

Build prompt

Create a skill named followup for [BUSINESS NAME].
Role: follow up assistant.
Inputs: Gmail threads from the last [14] days, plus any DM threads I paste.
Job: find people who asked about a product or service and went quiet after our last reply, without a decision.
Output format, one block per person: name and channel, what they asked, days since last message, reminder draft (max 60 words) that continues the conversation, suggested time to send.
For email leads, save each reminder as a Gmail draft. Never send.
Tone: as in CLAUDE.md. Helpful, never pushy, no guilt.
Skip anyone who said no or asked not to be contacted.
Before its first run, check CLAUDE.md and ask me for any missing business info.
Then set up a local routine that runs this skill every [MONDAY AND THURSDAY] at [10:00].

Warning. One reminder per person. Send a second one only with a new reason, like new stock or a new free date. Otherwise your agent turns into a spam machine.

Booking Agent

What it does. Checks your calendar for free slots, suggests times that match the client's preference, and books only after you confirm. A dental clinic patient writes "Friday evening works for me", and the agent offers three slots that are really free.

Connects to. Google Calendar connector, plus a services file with how long each service takes.

Put your services list with durations in the files folder.
Paste the build prompt and fill in hours and days off.
Type /booking with a client request.
Type "confirm" only when the slot looks right.

Build prompt

Create a skill named booking for [BUSINESS NAME].
Role: booking assistant.
Inputs: the client's request (service, preferred days and times), my Google Calendar, and the services file in the files folder.
Rules: working hours [HOURS], [15] minutes buffer between bookings, closed on [DAYS OFF].
Job: find free slots and suggest up to 3 that fit the client's preference.
Output format:
1. Free slots (date, time, length)
2. Message draft offering them to the client
3. Event details: title, date, time, client name, phone, notes
Tone: as in CLAUDE.md.
Create the calendar event only after I type "confirm". Never move or delete existing events.
Before its first run, check CLAUDE.md and ask me for any missing business info.

Tip. Put your personal time in the calendar too. The agent only sees the calendar, so an empty hour looks free to it.

Invoice Reminder Agent

What it does. Tracks payment deadlines, writes polite reminders for overdue invoices into your Gmail drafts, and stops chasing once the money is in. A clothing brand selling to concept stores stops losing an afternoon every month on who paid and who didn't.

Connects to. An invoice sheet in your files folder (client, amount, due date, status) and Gmail.

Save your invoice sheet in the files folder.
Paste the build prompt.
Approve the skill and the weekly schedule.
Review the drafts in Gmail and send them yourself.

Build prompt

Create a skill named invoices for [BUSINESS NAME].
Role: payments assistant.
Inputs: the invoice sheet [FILE NAME] in the files folder (client, amount, due date, status) and Gmail.
Job: find invoices due in the next [3] days or overdue. Search Gmail for payment confirmations and mark those as paid in your report.
Output format:
1. Table: client, amount, due date, days overdue, status
2. A reminder for each unpaid invoice, saved as a Gmail draft. First reminder friendly, second firmer but kind
3. Invoices to stop chasing
Tone: respectful, never threatening.
Never send emails. Never change the invoice sheet without my "confirm".
Before its first run, check CLAUDE.md and ask me for any missing business info.
Then set up a local routine that runs this skill every [MONDAY] at [9:30].

Warning. Mark payments in the sheet the day they land, or the agent will remind someone who already paid. And never give it your bank login. The sheet is enough.

Content Repurposing Agent

What it does. Takes one idea from a voice note or text and turns it into a Reel script, a caption and a Story, in your voice, saved as a file you can open anytime. An online shop owner dictates one minute about the new collection and gets all three.

Connects to. 5 to 10 of your best posts in a files/examples folder. Turn voice notes into text with your phone's dictation and paste it in.

Save 5 to 10 posts that performed well in files/examples.
Paste the build prompt.
Type /content and paste one real idea.
Read the result out loud. Does it sound like you?

Build prompt

Create a skill named content for [BUSINESS NAME OR YOUR NAME].
Role: content assistant.
Inputs: an idea I paste (voice note transcript or text), plus my posts in files/examples.
Job: turn one idea into three pieces:
1. Reel script: hook in the first 3 seconds, 3 to 5 scenes with what to show and say, closing line, under [30] seconds
2. Caption: hook, body under [120] words, one call to action
3. Story: 3 frames with text and one poll or question
Save all three in files/content with today's date.
Tone: copy the rhythm, words and humor of my examples. Write in [LANGUAGE]. No hype words.
Never publish anything. Never invent facts, prices or results.
Before its first run, check CLAUDE.md and ask me for any missing business info.

Tip. "Write in my style" with no examples gives you generic text. The agent learns your voice from examples, not from a description of it.

You just saw half the system. In Agentic AI: AI Agent Teams we build the lead system and the rest of your agents together, on your own business, so they work as one team. [DATES, FORMAT]. [PRICE OR DEADLINE OFFER].

Register for Agentic AI: AI Agent Teams

Competitor Monitor

What it does. Checks competitor websites every week, spots new prices, discounts and services, and saves a short summary with links. A beauty salon tracks five competitors without scrolling their pages every evening.

Connects to. Claude Code's built in web search, plus a competitors file with names and links.

Save competitor names and website links in files/competitors.
Paste the build prompt.
Approve the skill and the weekly schedule.
Read the new summary each week in files/competitors.

Build prompt

Create a skill named competitors for [BUSINESS NAME].
Role: competitor monitor.
Inputs: the competitor list in files/competitors and web search.
Job: check each competitor's website and public pages for new prices, discounts, services, products or locations. Compare with your last summary in files/competitors.
Output format:
1. What changed, one line per change, with the link
2. Why it matters for us, one line
3. Up to 3 ideas we could test
Write "No changes" for a competitor with nothing new. Save the summary in files/competitors with today's date.
Tone: short and factual. Report only what you see on a page. Mark guesses as guesses. Never contact competitors.
Before its first run, check CLAUDE.md and ask me for any missing business info.
Then set up a local routine that runs this skill every [FRIDAY] at [10:00].

Warning. Instagram profiles are often unreadable for the agent, so it works best with websites. Check competitors' Instagram yourself, or paste their latest posts in.

Client Onboarding Agent

What it does. Welcomes the new client with first steps, collects the info you need and flags what's missing, then builds a work plan with steps, deadlines and owners. An event agency signs a wedding and has the welcome email and plan ready in ten minutes.

Connects to. Gmail, Notion, and your onboarding files (welcome text, info checklist, standard process).

Save the three onboarding files in files/onboarding.
Paste the build prompt.
Type /onboarding with the new client's details.
Check the draft and plan, then type "confirm".

Build prompt

Create a skill named onboarding for [BUSINESS NAME].
Role: client onboarding assistant.
Inputs: the new client's details I paste (name, service, start date) and the files in files/onboarding.
Output format:
1. Welcome email with first steps, max 150 words, saved as a Gmail draft
2. Info checklist: what we have, what is missing, clearly flagged
3. Work plan table: step, deadline, owner (from the team in CLAUDE.md)
4. Questions to ask the client
Tone: warm and clear. The client should feel looked after, not buried in forms.
Never send emails or share files. Create the plan as tasks in [NOTION DATABASE] only after I type "confirm".
Before its first run, check CLAUDE.md and ask me for any missing business info.

Tip. Without a standard process file, the agent will invent deadlines. Write your process down once, even if it's 10 lines.

Customer Feedback Agent

What it does. Reads the reviews and messages you collect, groups recurring complaints and praise, and summarizes the key themes with real quotes. An online shop learns that "late delivery" came up 9 times this month and "beautiful packaging" 12 times.

Connects to. A files/feedback folder where you drop reviews, comments and DMs during the month.

Create files/feedback and add feedback as it comes.
Paste the build prompt.
Approve the skill and the monthly schedule.
Check two or three quotes against the originals.

Build prompt

Create a skill named feedback for [BUSINESS NAME].
Role: customer feedback analyst.
Inputs: everything in files/feedback from the last month (reviews, comments, messages, with links or dates when available).
Job: group feedback into recurring complaints, recurring praise and requests.
Output format:
1. Top 3 complaints: theme, count, 2 real quotes, link if available
2. Top 3 praises: same format
3. Requests and ideas customers mention
4. One fix to try this month
Save the report in files/feedback/reports with the month name.
Tone: clear and neutral. Quote word for word. Never invent or soften feedback. Count accurately.
Never reply to customers or post anything.
Before its first run, check CLAUDE.md and ask me for any missing business info.
Then set up a local routine that runs this skill on the [LAST WORKING DAY] of each month.

Warning. With 3 reviews, one angry customer looks like a trend. Wait for at least 20 pieces of feedback before you change anything.

Meeting to Action Agent

What it does. Summarizes a meeting from notes or a transcript, pulls out what, who and by when, and creates tasks in your team's tool after you confirm. A clothing brand's Monday team meeting turns into a task list before lunch.

Connects to. Notion connector, plus notes or a transcript (most recording apps export one as text).

Have a tasks database in Notion.
Paste the build prompt.
After a meeting, type /meetings and add the notes.
Type "confirm" to create the tasks you approve.

Build prompt

Create a skill named meetings for [BUSINESS NAME].
Role: meeting assistant.
Inputs: meeting notes or a transcript I paste or drop in files/meetings, and the team list in CLAUDE.md.
Output format:
1. Summary, max 5 bullets
2. Decisions made
3. Action table: what, who, by when. If a person or date is unclear, write "unclear" and ask me
4. Open questions
5. Tasks ready to create in [NOTION DATABASE]
Tone: short and plain.
Create tasks only after I type "confirm", and only the ones I approve. Never assign a task to someone who was not named for it. Never send the summary to anyone.
Before its first run, check CLAUDE.md and ask me for any missing business info.

Tip. At the end of every meeting, say out loud who does what by when. If nobody said it, the agent can't find it either.

Morning Brief Agent

What it does. Every weekday morning, on its own, it collects updates from email, calendar and tasks, highlights what's urgent, and gives you a one page brief with links. The owner of a small café chain opens it with her first coffee and knows exactly where the fires are.

Connects to. Gmail, Google Calendar and Notion.

Check that Gmail, Calendar and Notion are connected.
Paste the build prompt and add your VIP list.
Approve the skill and the schedule.
Open the Routines page, click Run now once, and approve the tools it asks for.

Build prompt

Create a skill named brief for [BUSINESS NAME].
Role: morning brief assistant.
Inputs: Gmail from the last 24 hours, today's Google Calendar, and my tasks in [NOTION DATABASE]. VIP senders: [NAMES].
Output format:
1. Urgent: deadlines today, problems, client complaints, max 5
2. Today's meetings with one line of prep each
3. Decisions waiting for me
4. Emails worth reading, with links
5. Everything else, one line each
Readable in 2 minutes. Link every item to its source. Ignore newsletters unless they mention [KEYWORDS]. Save the brief in files/briefs with today's date.
Tone: calm and direct.
Never reply, archive, delete or reschedule anything.
Before its first run, check CLAUDE.md and ask me for any missing business info.
Then set up a local routine that runs this skill every weekday at [8:30].

Warning. A local routine runs only while the Claude app is open and your computer is awake. Turn on Keep computer awake in the app settings. If the computer slept, the brief runs once when it wakes up.

Where to start this week

Do the foundation prompt first. Then don't build all 10 at once. Start with two:

DM Sales Agent. It touches money every single day. Faster, more accurate replies mean fewer lost clients, and you'll see the difference in a week.
Morning Brief Agent. It only reads, never sends, so it's zero risk. And it's the first time you'll see an agent work while you sleep: the brief is waiting for you in the morning.

Once these two run smoothly, add one new agent per week. In ten weeks you'll have a full AI team.

Want to build the lead system and all your agents on your own business, with me and with feedback? That's exactly what we do in Agentic AI: AI Agent Teams. [DATES, FORMAT]. [PRICE OR DEADLINE OFFER].

Register for Agentic AI: AI Agent Teams

More AI systems every week on @aiwithani.

10 AI agents for your small business: build them in Claude Code without writing code

Before you start

The foundation: your team's memory

The 10 agents

DM Sales Agent

Follow Up Agent

Booking Agent

Invoice Reminder Agent

Content Repurposing Agent

Competitor Monitor

Client Onboarding Agent

Customer Feedback Agent

Meeting to Action Agent

Morning Brief Agent

Where to start this week

Related guides