18 October 2026 · 9 min read · AI Operations
The best Claude prompts for small business: 10 copy-paste prompts for inbox triage, SOPs, follow-ups and planning. Save them once, reuse them weekly.
The short answer: the best Claude prompts for small business owners are the ones that handle your repeat admin: inbox triage, turning brain dumps into tasks, drafting SOPs, writing follow-ups and planning your week. Below are 10 copy-paste prompts for exactly that. Save them once in a Claude Project and you stop starting from a blank box every Monday.
Claude is the AI assistant made by Anthropic. It is very good at the boring middle bit of running a business, the part between "I know what needs doing" and "it is done". But most founders I talk to use it like a search engine. They type a vague question, get a vague answer, and decide AI is overrated.
The fix is not a smarter tool. It is a better prompt, saved somewhere you can find it.
Each prompt below has three parts: what it is for, the prompt itself, and a tip for adapting it. Anything in [square brackets] is yours to fill in.
A useful prompt gives Claude context about your business, a clear task and the format you want back. Anthropic's own guidance says to treat Claude like "a brilliant but new employee who lacks context on your norms and workflows" (Anthropic prompting best practices). If a new hire would be confused by your instructions, Claude will be too.
That is why every prompt here tells Claude who it is helping, what good looks like and how to lay out the answer.
What it is for: getting from 60 unread emails to a short list of what needs you today.
I'm a small business owner. Below are the emails from my inbox today. Sort them into three groups:
1. Needs my reply or decision today
2. Can wait until later this week
3. FYI only, no action needed
For group 1, give me one line per email: who it's from, what they want, and a suggested next step. Keep the whole summary under 200 words.
[Paste emails here]Tip: add a line about who your priority clients are ("Anything from [client names] goes in group 1"). Claude cannot guess which relationships matter most.
What it is for: turning a rambling voice memo (transcribed) into something you can actually act on.
Here's a transcript of me thinking out loud. It's messy. Pull out every task, idea and decision. Then:
- List the tasks as clear actions starting with a verb
- Group them by project or area
- Flag anything with a deadline
- Put loose ideas in a separate "parking lot" list so they don't clutter the tasks
Don't add tasks I didn't mention.
[Paste transcript]Tip: if your brain does not do linear (mine included), this is the one to save first. Tell Claude your project names so the grouping matches your task manager.
What it is for: documenting a process you already do, without sitting down to write it from scratch.
Below is a transcript of me walking through how I [name the process]. Turn it into a standard operating procedure for a new team member. Include:
- Purpose (one sentence)
- When this process happens
- Tools needed
- Numbered steps, one action per step
- Common mistakes to avoid
- What "done" looks like
Where the transcript is unclear or skips a step, write [CHECK: question] instead of guessing.
[Paste transcript]Tip: the [CHECK] instruction is the important bit. It stops Claude filling gaps with plausible fiction. For what a good SOP needs to include, see how to write an SOP your first hire can actually follow.
What it is for: follow-ups that sound like you, not like a robot that has read too many sales books.
Write a follow-up email to [client name] after [meeting/proposal/delivery]. Context: [two or three sentences on what happened and what you want next].
My writing style: [e.g. warm, direct, short sentences, no corporate jargon, signs off with "Speak soon"]. Here are two emails I've written that sound like me:
[Paste examples]
Keep it under 120 words with one clear next step.Tip: the examples do most of the work. Anthropic calls examples "one of the most reliable ways to steer Claude's output format, tone, and structure". Paste in real emails you were happy with.
What it is for: a Monday reset that turns a long list into a realistic week.
Here's everything on my plate this week, plus my fixed commitments.
Tasks: [paste list]
Fixed commitments: [meetings, school run, etc.]
Hours I realistically have for focused work: [number]
Help me pick my top 3 priorities for the week. For each, explain in one line why it matters. Then suggest which day to do each, and tell me honestly what should be dropped, delegated or moved to next week.Tip: the "tell me honestly" line matters. Without it, Claude tends to help you squeeze everything in. If you are unsure what to hand off, AI or a person? How to decide who gets each task covers the thinking.
What it is for: making sure the call actually leads somewhere.
Below are my notes (or the transcript) from a meeting with [who]. Give me:
1. A three-sentence summary
2. Decisions made
3. Action items in a table with columns: Action, Owner, Due date
4. Open questions nobody answered
If an owner or due date wasn't mentioned, write "Not agreed" rather than assuming.
[Paste notes]Tip: follow up with "Now draft a short recap email to the attendees using this." Two prompts, one finished job.
What it is for: getting more than one outing from something you have already written.
Here's a blog post / newsletter / talk transcript I wrote. Repurpose it into:
- 3 LinkedIn posts (each under 150 words, each with a different angle)
- 5 short Instagram caption ideas
- 1 email to my list (under 250 words)
Keep my voice. Don't invent stats, stories or claims that aren't in the original.
[Paste content]Tip: the "don't invent" line protects you. Name your audience too ("for overwhelmed founders" lands differently to "for HR managers").
What it is for: a first draft of a proposal you then edit, rather than staring at an empty document.
Help me draft a proposal for [client type] who needs [problem]. My offer: [what you'll deliver]. My price: [amount]. Timeline: [timeline].
Structure it as: the client's problem in their words, what I'll do, what's included and not included, timeline, investment, and next step. Keep it to one page. Ask me up to three questions first if anything important is missing.Tip: "ask me questions first" turns Claude into a thinking partner rather than a guesser. Always check the numbers yourself before anything goes to a client.
What it is for: having calm, ready answers to the questions you hear on every sales call.
I sell [offer] to [audience]. Here are the questions and objections I hear most often:
[List them]
For each one, write a short, honest answer (under 80 words) that I could say on a call or put on my sales page. Don't overpromise. Then suggest three more questions my audience is probably wondering about but not asking.Tip: run the output past a real client or two. Claude can draft the answer, but only your customers can tell you whether it lands.
What it is for: getting a stuck decision out of your head and onto the page.
I'm trying to decide between [option A] and [option B]. Context: [your situation, constraints, goals].
Give me:
- Pros and cons of each in a table
- The questions I should answer before deciding
- What I'd need to believe for each option to be the right one
- Your honest read, with reasoning
Challenge my assumptions if they seem shaky.Tip: Claude is not making the decision. It is helping you see it clearly. The "what would I need to believe" line is where the useful thinking usually shows up.
Write your own Claude prompts by covering four things: context, role, task and format. Once you have those, you can turn almost any repeat job into a reusable prompt.
| Part | What to include | Example |
|---|---|---|
| Context | Who you are, who it's for, why it matters | "I run a two-person bookkeeping practice for cafés." |
| Role | Who Claude should act as | "Act as an experienced operations manager." |
| Task | One clear job, starting with a verb | "Turn these notes into a client onboarding checklist." |
| Format | Length, structure, what to avoid | "Numbered list, under 15 items, no jargon." |
Anthropic's guidance backs this up: setting a role "focuses Claude's behavior and tone", and explaining why an instruction matters helps Claude "deliver more targeted responses" (source).
The simplest way to save prompts in Claude is a Project: a workspace with its own chats, uploaded files and instructions. According to Anthropic's help centre, Projects are available on all plans, and Free accounts can create up to five (What are projects?).
Here is how I would set it up:
There is also an account-wide setting called Instructions for Claude, found under Settings, which applies to all your conversations (Understanding Claude's personalization features). Use that for things that are true everywhere, like how you like answers laid out. Use project instructions for things that are true for one area of the business.
Menus change, so if something has moved, check that help page for the current location.
Yes, the prompts themselves work on any plan. Free accounts can also create a small number of Projects to keep them organised. Paid plans give you more usage, which matters if you run several of these every day.
The principles are the same: context, a clear task and a defined format. Most of these prompts will work in other assistants with little or no change. I use Claude daily, so that is what they are written and tested around.
As long as it needs to be for a new employee to understand it, and no longer. A few clear sentences plus your pasted material is usually enough. If Claude keeps misunderstanding, add context rather than more rules.
Be thoughtful. Check your plan's privacy settings and Anthropic's privacy policy before pasting in client data, and remove anything you don't need, such as full contact details. When in doubt, anonymise names and figures first.
Tell it, specifically. "Too formal, cut it by half and drop the first paragraph" works far better than starting a fresh chat. Then update your saved prompt so the fix sticks next time.
Start with whichever job you avoid most. For many founders that is the brain dump to task list or the weekly planner, because they make everything else easier to see.
If you would rather not build your prompt library alone, that is exactly what Claude 101 is for. It is $99 for 60 minutes one-to-one, and you leave with a working Claude setup: your Project, your context files and prompts that fit how your business actually runs.
If you want a wider look at where AI fits in your operations, the AI Operations Audit gives you a 90-minute session, the recording and a written Priority Action Plan. You can also read more on my Claude for business page, see the best tools for small business owners who want their time back, or learn how to delegate as a founder once Claude has cleared some space.
Not sure where to start? Book a free call.