Claude Prompt Library

16 Claude Prompts for Small Business Owners

16 copy-paste prompts

Chase invoices, write quotes and plan next month's cash in minutes. Copy a prompt, fill in the brackets, and Claude does the first draft.

In short: This page contains 16 copy-paste ready prompts, organized into 4 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Drafted with AI writing assistance and checked against our editorial policy.

Louis Corneloup
By Louis Corneloup ยท Founder, Techpresso
Last updated ยทDrafted with AI assistance (how we make prompts)

Getting Paid

3 prompts

Chase an Unpaid Invoice

1/16

โœจ What it does

Claude writes a firm, friendly reminder for [invoice number, amount, what it was for] to [client name and contact person], plus a firmer follow-up to send 7 days later. Add how overdue it is and any late fee, then send the first email today.

<context> My business: [business name and what we do] Client: [client name and contact person] Invoice: [invoice number, amount, what it was for] Due date: [original due date] (now [number] days overdue) Reminders sent so far: [none / one friendly email on date / etc.] Relationship: [new client / long-standing client I want to keep] </context> <task> 1. Write a payment reminder email that is firm and clear but keeps the relationship intact 2. State the invoice number, amount, due date and how to pay in the first three lines 3. Ask for a specific payment date, not a vague "soon" 4. Offer one easy way out if they have a problem (a call, or splitting the payment) 5. Write a second, firmer follow-up email to send in 7 days if there is no reply, naming the next step I will take </task> <constraints> - Polite, plain and short: under 150 words per email - No guilt, no sarcasm, no "just checking in" - Assume a genuine mistake in the first email; be direct in the follow-up - Only mention late fees or next steps that I list here: [late fee or next step, or "none"] </constraints>

๐Ÿ’ก

Pro tip: Save the client and invoice details in a Claude Project. Next time an invoice slips, you only paste the new number, amount and date.

Write a Quote

2/16

โœจ What it does

Claude turns [describe the work, materials and anything included] and [total price, or my rates and hours] into a clean quote with scope, price, payment terms and a validity date. Check the "not included" list, then send it.

<context> My business: [business name and what we do] Customer: [customer name and what they asked for] The job: [describe the work, materials and anything included] My price: [total price, or my rates and hours so you can add it up] Payment terms: [deposit, when the balance is due, accepted payment methods] How long the quote is valid: [e.g. 30 days] </context> <task> 1. Write a clear quote with: a one-line summary of the job, a scope section, a price breakdown, payment terms and a validity date 2. List what is included and what is not included, so there are no surprises later 3. Add any assumptions the price depends on (access, materials, number of revisions) 4. End with one simple next step for the customer to accept </task> <constraints> - Use only the prices and rates I give you; do not invent numbers - Plain language a customer can read in two minutes - If the scope I describe is vague, list the questions I should ask before sending </constraints>

๐Ÿ’ก

Pro tip: Ask Claude to "format this as a table I can paste into my invoicing tool" so the line items drop straight in.

Plan Next Month's Cash

3/16

โœจ What it does

Claude lays out next month's cash week by week from [cash in the bank today], [money I expect in next month] and [money going out next month], finds the low point and suggests what to move. Run it at the start of each month.

<context> My business: [business name and what we do] Cash in the bank today: [amount] Money I expect in next month: [list invoices or sales with expected dates and amounts] Money going out next month: [rent, wages, suppliers, tax, loan payments, with dates and amounts] Anything uncertain: [late payers, a big order that might not happen] </context> <task> 1. Build a simple week-by-week table for next month: cash in, cash out, and the running balance at the end of each week 2. Point out the low point: the week my balance is lowest and how low it gets 3. If the balance gets tight, suggest what I could move: payments to chase early, bills I could pay later, spending to pause 4. Show a "bad case" line where the uncertain money does not arrive </task> <constraints> - Use only the numbers I give you and show your sums - Keep it to one table and a short list of actions - Flag any date or amount that looks missing </constraints>

๐Ÿ’ก

Pro tip: Paste an export from your bank or accounting tool instead of typing the list. Claude can sort the dates and amounts for you.

XML tags are just the start. Learn the full Claude workflow.

A growing library of hands-on AI tutorials covering Claude, ChatGPT, and many other tools. New tutorials are added regularly.

Start 7-Day Free Trial

Hiring and Reputation

2 prompts

Draft a Job Post

4/16

โœจ What it does

Claude writes a job post for [job title, hours, pay] from [the main tasks in a normal week], plus a short screening scorecard and phone questions. Post it, then score every applicant the same way.

<context> My business: [business name, what we do, where we are] Role: [job title, hours, pay] What the person will actually do: [the main tasks in a normal week] Must-haves: [skills, licences, experience] Nice-to-haves: [extras] What makes us a good place to work: [real reasons, e.g. flexible hours, small team] </context> <task> 1. Write a job post with a clear title, a short intro, the main tasks, must-haves, pay and how to apply 2. Keep the must-haves to the ones that really matter 3. Write a short screening scorecard: 4 to 5 criteria, each scored 1 to 3, with what a good answer looks like 4. Suggest three quick screening questions to ask by phone </task> <constraints> - Plain, friendly language; no "rockstar" or "ninja" - Include the pay if I give it - Fair to all candidates: no requirements about age, gender or anything unrelated to the job </constraints>

๐Ÿ’ก

Pro tip: Ask Claude to "cut the must-haves to the three that matter most". Shorter lists bring in more good applicants.

Reply to a Bad Review

5/16

โœจ What it does

Claude writes a calm public reply to [paste the review word for word] plus a private follow-up offering [refund, redo, a call, nothing]. Post the public reply within a day.

<context> My business: [business name and what we do] The review: [paste the review word for word] Where it was posted: [Google, Trustpilot, Facebook, etc.] What actually happened: [my side of the story, honestly] What I can offer: [refund, redo, a call, nothing] </context> <task> 1. Write a short public reply that thanks them, owns any real mistake, and shows other readers we care 2. Write a private follow-up message to the customer that offers a way to put it right 3. If the review contains something untrue, show how to correct it politely without arguing </task> <constraints> - Public reply under 80 words; calm, never defensive - Do not share private customer details in the public reply - Do not offer anything I have not listed </constraints>

๐Ÿ’ก

Pro tip: Write down what happened before you paste the review. Claude gives a fairer reply when it has both sides.

Winning Work

3 prompts

Price a New Service

6/16

โœจ What it does

Claude works out a floor price for [what it is and who it is for] from [hours per job] and [materials, software, travel], then suggests three price options. Pick one and test it on your next few customers.

<context> My business: [business name and what we do] New service: [what it is and who it is for] Time it takes me: [hours per job] Direct costs per job: [materials, software, travel] What similar businesses charge: [prices I have seen, or "not sure"] What I want to earn per hour: [amount] </context> <task> 1. Work out the minimum price that covers my costs and my target hourly rate 2. Suggest three price options (basic, standard, premium) with what each includes 3. Explain which option most customers are likely to pick and why 4. Write a one-line way to describe each option to a customer </task> <constraints> - Show the sum behind the minimum price - Do not guess competitor prices; use only what I give you - Keep it practical for a small business, not a pricing theory lesson </constraints>

๐Ÿ’ก

Pro tip: Ask Claude "what would make the premium option worth it to a customer?" to find extras that cost you little.

Follow Up a Lead

7/16

โœจ What it does

Claude writes a follow-up to [name, company, how they found us] about [their enquiry or what we discussed], asking for [a call, a site visit, a signed quote], plus a second nudge for a week later. Send the first one today.

<context> My business: [business name and what we do] Lead: [name, company, how they found us] What they asked about: [their enquiry or what we discussed] Last contact: [date and what happened] What I want next: [a call, a site visit, a signed quote] </context> <task> 1. Write a short follow-up email that picks up where we left off 2. Remind them of the one thing they cared about most 3. Ask for one clear next step with two time options 4. Write a shorter second message for a week later if they do not reply </task> <constraints> - Under 120 words per message - No pressure tactics, no fake deadlines - Sound like a real person, not a sales template </constraints>

๐Ÿ’ก

Pro tip: Paste their original enquiry word for word. Claude will mirror their language, which makes the reply feel personal.

Ask for a Review

8/16

โœจ What it does

Claude writes a short review request to [customer name and what we did for them] with your [review link], plus a gentle reminder. Send it within a day of finishing the job.

<context> My business: [business name and what we do] Customer: [customer name and what we did for them] Where I want the review: [Google, Trustpilot, Facebook, etc.] and the link: [review link] How I am asking: [email / text message / in person] </context> <task> 1. Write a short review request that thanks them for something specific 2. Make leaving the review take one click 3. Suggest two or three things they could mention, without writing the review for them 4. Write a one-line reminder to send 5 days later </task> <constraints> - Under 80 words for email, under 40 words for a text message - No incentives in exchange for reviews - Warm and personal, not a form letter </constraints>

๐Ÿ’ก

Pro tip: Ask Claude for both an email and a text message version. Text messages often get a faster reply from local customers.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. The library keeps growing.

Try AI Academy Free

Running the Business

8 prompts

Write a Supplier Email

9/16

โœจ What it does

Claude writes an email to [supplier name and what they supply] asking for [a lower price / longer payment terms / a bulk discount], using [other quotes, order volume, paying on time]. Decide your fallback before you hit send.

<context> My business: [business name and what we do] Supplier: [supplier name and what they supply] What I want: [a lower price / longer payment terms / a bulk discount / faster delivery] Our history: [how long we have bought from them and roughly how much] My leverage: [other quotes, order volume, paying on time, or "none"] </context> <task> 1. Write a polite, direct email asking for what I want 2. Give one or two reasons that make it easy for them to say yes 3. Suggest a middle option in case they cannot agree to the full ask 4. Ask for a reply by a specific date </task> <constraints> - Under 150 words - Keep the relationship friendly; I still need this supplier - Do not invent competitor quotes or volumes </constraints>

๐Ÿ’ก

Pro tip: Ask Claude to "play the supplier and reply to this email" so you can see their likely pushback before it arrives.

Plan a Promotion

10/16

โœจ What it does

Claude plans a promotion for [product or service] from [start and end] to hit [your goal], with the offer, a day-by-day schedule and the copy for each channel. Check the sums, then schedule the first post.

<context> My business: [business name and what we do] What I want to promote: [product or service] Goal: [more bookings in a quiet week / clear stock / win new customers] Budget: [amount, or "none"] Dates: [start and end] Where my customers are: [email list, Instagram, shop window, local paper] </context> <task> 1. Suggest the offer itself, and check I can afford it at my margin: [margin or cost per sale] 2. Plan what goes out and when, day by day 3. Write the main message for each channel 4. Name one number to track so I know if it worked </task> <constraints> - Keep it doable by one person alongside normal work - No fake urgency or "only 2 left" claims that are not true - Show the sum behind the offer so I can see it still makes money </constraints>

๐Ÿ’ก

Pro tip: Ask Claude to write the messages in your own voice by pasting two or three of your past posts or emails first.

Onboard a New Hire

11/16

โœจ What it does

Claude plans the first week for [name, role, start date] from [tools, tasks, customers, rules], with a welcome message, a set-up list and an end-of-week check-in. Send the welcome message the week before.

<context> My business: [business name and what we do] New hire: [name, role, start date] What they need to learn: [tools, tasks, customers, rules] Who will help them: [me, a colleague] What "doing well" looks like after week one: [a few specific things] </context> <task> 1. Plan their first week day by day: what they do, who they meet, what they learn 2. Write a short welcome message I can send before day one 3. List what I need to set up before they arrive (logins, keys, kit) 4. Write five questions to ask them at the end of the week </task> <constraints> - Realistic for a small team where I am also doing my normal job - Mix learning with real, simple work from day one - Keep the plan to one page </constraints>

๐Ÿ’ก

Pro tip: Save the plan as a document in a Claude Project. For the next hire, you only update the name, role and dates.

Write a Refund Policy

12/16

โœจ What it does

Claude writes a short refund policy from [refund window, exchanges, store credit, conditions] and [what I do not refund], plus a two-line version for receipts. Check the flagged points for [country], then publish it.

<context> My business: [business name and what we sell] How I sell: [online, in person, by appointment] What I want to allow: [refund window, exchanges, store credit, conditions] What I do not refund: [custom work, used items, missed appointments] My country: [country, so the policy can note local consumer rights] </context> <task> 1. Write a clear, short refund policy customers can read in one minute 2. Cover: how long they have, what condition items must be in, how to ask, and how long refunds take 3. Note where local consumer rights may apply, and flag anything I should check with an adviser 4. Write a two-sentence version for receipts or a checkout page </task> <constraints> - Plain language, no legal jargon - Fair to the customer and to me - Do not state legal requirements as certain; flag them for me to check </constraints>

๐Ÿ’ก

Pro tip: Ask Claude to "list the questions customers are most likely to ask about this policy" and add the answers as a short FAQ.

Answer a Customer Complaint

13/16

โœจ What it does

Claude writes a reply to [paste their message] that owns the problem, offers [refund, discount, redo, replacement] and says when it will happen. Send it the same day.

<context> My business: [business name and what we do] Customer: [name and how long they have been a customer] Their complaint: [paste their message] What went wrong, as far as I know: [the facts] What I can offer: [refund, discount, redo, replacement] </context> <task> 1. Write a reply that acknowledges the problem in their words 2. Explain briefly what happened, without excuses 3. Offer a clear fix and say when it will happen 4. Suggest one change I could make so it does not happen again </task> <constraints> - Under 150 words - Warm and direct; apologise once, not three times - Only offer what I have listed </constraints>

๐Ÿ’ก

Pro tip: If you are angry, ask Claude to "make this calmer" before you send. Then sleep on any reply over 150 words.

Summarise My Monthly Numbers

14/16

โœจ What it does

Claude turns [this month's numbers] and [last month's numbers] into a plain summary: profit, what changed, the line to watch and two actions. Read it before you plan next month.

<context> My business: [business name and what we do] Month: [month and year] This month's numbers: [paste sales, costs, profit, bank balance, number of customers] Last month's numbers (or the same month last year): [paste them] </context> <task> 1. Write a plain-English summary: did we make money, and how much 2. Show what changed versus last period and the likely reason, as a question if you are not sure 3. Point out the one cost or income line that needs my attention 4. Suggest two actions for next month </task> <constraints> - Use only the numbers I give you and show any sums - Under 250 words plus one small table - If something looks wrong in the numbers, say so </constraints>

๐Ÿ’ก

Pro tip: Paste the same figures in the same order each month, and save this prompt in a Claude Project, so the summaries stay comparable.

Write a Proposal

15/16

โœจ What it does

Claude writes a proposal for [client name and their situation] that leads with [what they want to fix or achieve], then sets out the work, timeline and [total or price per phase]. Read it as the client would, then send it.

<context> My business: [business name and what we do] Client: [client name and their situation] Their problem or goal: [what they want to fix or achieve] What I will do: [the work, in phases if possible] Timeline: [start date and key dates] Price: [total or price per phase] Why us: [relevant experience or past results] </context> <task> 1. Open with their problem in their own words 2. Explain my approach in clear phases with what they get at each step 3. Set out the timeline and the price 4. Add a short "why us" section with real examples I gave you 5. End with the next step to say yes </task> <constraints> - Under two pages - Use only facts, prices and results I give you - No jargon; write for the person who signs the cheque </constraints>

๐Ÿ’ก

Pro tip: After the draft, ask Claude "what question will this client ask before saying yes?" and add the answer to the proposal.

Plan My Week

16/16

โœจ What it does

Claude sorts [paste everything on my mind] into what matters this week and fits it around [appointments, jobs, deliveries with times], with time for [goal]. Run it every Monday morning.

<context> My business: [business name and what we do] My hours this week: [days and hours I can work] Fixed commitments: [appointments, jobs, deliveries with times] To-do list: [paste everything on my mind] The one thing that would make this a good week: [goal] </context> <task> 1. Sort my to-do list into: must do this week, can wait, can hand off or drop 2. Put the must-dos into a day-by-day plan around my fixed commitments 3. Block time for the one goal early in the week 4. Leave a buffer each day for the unexpected </task> <constraints> - Do not fill more than 80% of my hours - Group similar tasks (calls, admin, emails) together - One page, easy to glance at </constraints>

๐Ÿ’ก

Pro tip: Paste last week's plan with notes on what slipped. Claude will plan this week more realistically.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free โ†’

Frequently Asked Questions

No. Every prompt works on the free Claude plan. A paid plan gives you more messages per day and Claude Projects, which let you save your business details once so you do not have to retype them.
They are the parts you fill in: your business, your customer, your numbers. Replace each one with your own details before you send the prompt. The more specific you are, the better the result.
Claude can sort, add up and explain the numbers you give it, and spot things that look wrong. It does not connect to your bank and is not a substitute for an accountant on tax or legal questions. Always check the sums before you act on them.
Share only what the task needs. You can use first names or initials instead of full customer details, and leave out card numbers and passwords entirely. Check your own data rules if you handle sensitive information.
Create a Claude Project and add a short note about your business: what you sell, your prices, your payment terms and your tone. Then each prompt only needs the new details, such as this invoice or this customer.

Prompts are the starting line. Tutorials are the finish.

A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.

Start 7-Day Free TrialCancel anytime.
Explore AI tutorials for Business