Most ChatGPT prompts for small business owners fail for a boring reason: they describe a job in general terms and never hand over the detail that makes the answer usable. “Write a follow-up email” gets you a follow-up email from nowhere, addressed to nobody. A prompt is a brief, not a wish.
Every prompt below is short on purpose and grouped by the job you are actually doing, each with a line on when to reach for it and what to change before sending. How these guides are put together is on the About page.
What makes ChatGPT prompts for small business owners different
A generic prompt asks the model to improvise a business. A working prompt hands over the business you already have, then asks for one piece of it back. Three things separate the two.
It carries your facts. Rates, exclusions, opening hours, the customer’s own words. Without them the model fills gaps with plausible text, and plausible is what you cannot check quickly.
It names the output. Not “a reply” but “under 90 words, one next step, no apology”. A named shape is something you can accept or reject in seconds.
It says what to do when information is missing. Tell it to write MISSING rather than guess. Guesses arrive fluent and wrong, the worst combination for an owner reading at nine at night.
That is the whole theory. The prompts below apply that pattern to jobs you already do.
Why generic prompts fail
Generic prompts fail quietly, which is why people conclude AI is overhyped rather than that their prompt was thin. Four failures account for most of it.
They ask for a category, not a job. “Help with marketing” has no finish line, so the answer wanders. “Turn this job into a three-paragraph case note using only these notes” does.
They let the model invent specifics. Ask for a quote and you get a number. Anything numeric you did not supply is fabricated, and looks reasonable.
They skip the audience. A reply to a customer who has paid twice for the same fault differs from one answering a question about opening hours.
They have no length constraint. Unconstrained output defaults to long, the opposite of what a busy owner needs.
The fix is not a longer prompt. It is a prompt with the right things in it.
The customisation recipe: context, constraints, format
Every prompt here is built from the same three parts. Once you can see them, you can fix any prompt that produces mush.
Context is what the model cannot know: trade, region, rates, policy, the customer’s message verbatim. Paste it rather than summarising, since your tidied version has lost the detail that matters.
Constraints are the guardrails: what not to invent, what to do when something is missing, whose voice to use. This is where money is protected.
Format is the shape you want back: word count, sections, a table, one line per item. Name it and stop reformatting.
[ROLE] You draft [DOCUMENT] for a [BUSINESS TYPE] in [REGION].
[CONTEXT] Use only the information between the markers below.
---INPUT---
[PASTE THE REAL THING: notes, email, quote, message]
---END INPUT---
[CONSTRAINTS]
- Do not invent prices, dates, names, quantities or timeframes.
- If a required detail is missing, write MISSING instead of guessing.
- Keep my wording where I have given it.
[FORMAT]
- [WORD COUNT] words maximum.
- [STRUCTURE: e.g. three short paragraphs, one line per item, a table].
- End with [WHAT YOU WANT NEXT: one question, one next step, nothing].Swap the three bracketed blocks and you have a new prompt in under a minute. The prompts below are this template with the thinking done.
Quoting and sales prompts
Quoting is where small businesses leak margin. It is also the job most improved by a prompt that refuses to invent numbers. For the full workflow, see writing quotes and estimates with AI.
Site notes to scope lines. Use it after a visit, before you price. Swap the trade and delete any surface you did not walk.
Turn these site notes into quote scope lines for a [TRADE] job.
One line per surface: verb, quantity, coverage. Flag gaps.Missing-information check. Before you price a vague enquiry. Paste the request as it arrived, typos included.
Read this job request and list what I must confirm before pricing.
One question per line. No advice, no estimate, no guessing.Vague line to clear scope. When a quote line reads like “repaint bathroom”. Replace the line, keep your price.
Rewrite this quote line so a customer can tell what is included:
"[LINE]". Do not add work or change the price.Exclusions list. Before any quote goes out. Swap trade and job, then delete the exclusions that do not apply.
List the exclusions to state on a [TRADE] quote for [JOB].
Use only what I give you. Do not add work I have not mentioned.Quote follow-up. Day four after sending. Change the number of days and the one next step you can honour.
Draft a follow-up email for a quote sent [X] days ago and not answered.
Neutral tone, no pressure, one next step. Under 90 words.Qualifying questions. When an enquiry is too thin to price. Paste the message, then cut questions you can answer yourself.
From this message, write the questions I need answered to quote
accurately. Ask only what changes price or schedule.Price pushback reply. When someone says it is more than expected. Change the smaller option to one you can genuinely deliver.
A customer said my quote is higher than expected. Draft a reply
restating what is included and offering one smaller option.Customer service prompts
Replies are the highest-volume writing job in most small businesses, and a bad draft costs trust immediately. Read each one before it goes out.
Complaint reply. Within the hour, not the day. Paste the complaint, then name only actions you will actually keep.
Draft a reply to this complaint. Acknowledge the specific problem, state
what we will do and by when. Do not admit or deny liability.Reusable answer. For a question you answer weekly. Paste both the question and your own rough answer.
Turn my rough answer into a polite reply I can reuse. Under 120 words.
Do not apologise for things that are not my fault.Running-late message. The moment you know, not after. Change the delay and the new time.
Write a short message saying we are running [DELAY] late. Give the new
time and one sentence of reason. No excuse-making.Policy explanation. When you have to decline something. Paste the request and check the policy wording yourself afterwards.
Explain in plain English what our [POLICY] covers for this customer.
Factual, calm, brief.Public review reply. Within 48 hours of a review. Swap the review, and never argue the facts in public.
Write a reply to this review. Thank them, address the specific point,
offer to continue privately. No defensiveness, no fake warmth.Review request. A day after finishing. Change the job and keep it to one ask.
Write a short message asking a customer to review a completed [JOB].
No incentive, no script, one link.Thread summary. Before replying to a long chain. Paste the whole thread oldest first, including your own replies.
Summarise this thread: what the customer asked, what we agreed, what is
still open. Three short sections, no opinion.Marketing and content prompts
Content prompts go wrong when asked to sound impressive. Aim for specific and plain, and the writing stops reading like a brochure.
Case note from a job. After work you are proud of. Paste notes, then cut any result you cannot evidence.
Turn these job notes into a three-paragraph case note: problem, what we
did, result. Use only facts in the notes.Local service page outline. For a service you want found in your town. Swap both, and fill the cost line honestly.
Outline a page for [SERVICE] in [TOWN]: who it is for, what is included,
how pricing works, common questions, how to book.Plain-English rewrite. When your copy sounds like a brochure. Paste one paragraph at a time, not the whole site.
Rewrite this website paragraph in plain English. Shorter sentences, no
jargon, keep every fact and my meaning.Photo captions. Same day as the job. Describe the photo yourself first, then change the tone words.
Write three captions for this job: one practical, one plain, one short.
No hashtags, no exclamation marks. The image shows: [DESCRIBE]Seasonal email. Six weeks before your busy period. Change the offer to one you can actually staff.
Draft a short email to past customers about [SEASON] availability. One
offer, one reason to book now, one line on opting out.FAQ page from real questions. When the same questions keep arriving. Paste question and answer pairs, not just questions.
Turn these real customer questions into an FAQ page. Answer each in
under 60 words, using only what I give you.Profile update. When hours, services or staff change. Swap what changed, then post it yourself.
Write a Google Business Profile update about [WHAT CHANGED]. Under 100
words, no links, no keyword repetition, no sales language.Admin and finance prompts
These save the most time per minute spent, provided you keep the checking habit. Anything touching money or contracts gets read twice. Our tools section covers what is worth paying for.
Overdue invoice reminder. First reminder around seven days. Change the days and amount, then check them against the invoice.
Draft a reminder for invoice [NUMBER], [X] days overdue. Firm but
courteous, restate amount and date, one way to pay.Bookkeeping descriptions. Before handing a batch to your bookkeeper. Paste descriptions only, never card numbers.
Write a one-line description for each transaction so my bookkeeper can
categorise it. Do not guess an account code or supplier name.Contract clause in plain English. Before signing anything unfamiliar. Paste one clause and still get real advice.
Explain this contract clause in plain English and list what to ask a
professional. Do not tell me whether to sign.Cash questions. Start of the month. Paste your own notes and answer the questions yourself.
List the questions to answer about my cash position this month, given
these notes. No forecasts, no figures I have not given you.Meeting notes to actions. Straight after the meeting. Paste verbatim notes and send the list the same day.
Turn these notes into actions: what, who, by when. Flag anything with
no owner or no date as unassigned.Procedure from your head. For a job only you know how to do. Describe it out loud first, then paste that.
Write a step-by-step procedure for [TASK] from the description below.
Number the steps, name who does each, note what could go wrong.Price change letter. Four weeks before it takes effect. Change the date and state the real reasons.
Draft a letter to existing customers about a price change from [DATE].
Plain reasons, what stays the same, what happens next.Hiring and onboarding prompts
Hiring is slow because the documents get written late and badly. Prompts help with the writing, never with judgement about people.
Job ad. Before you post anywhere. Swap role and size, and never leave pay vague.
Write a job ad for a [ROLE] in a [SIZE] [TRADE] business: real tasks,
hours, the pay range I give you, how to apply.Interview questions. Before the first interview. Change the role, then cut any question you cannot judge fairly.
Write eight interview questions for a [ROLE] about past work, not
hypotheticals. Add what a strong answer sounds like.Scoring sheet. Before you interview anyone. Paste requirements and score each candidate separately.
Turn these requirements into a scoring sheet for comparing candidates.
Five criteria, 1-4 scale, and what a 4 looks like.30-day onboarding plan. Once the offer is accepted. Change the role, then match it to your real week.
Write a 30-day onboarding plan for a new [ROLE]. Week by week: what they
learn, who they shadow, what they own by day 30.First-week task list. Day one. Swap the role and delete tasks needing certification they do not have.
List first-week tasks for a new [ROLE], in order, with who signs each
off. Assume they have never worked in this trade.Reference-check questions. Before you call a referee. Change the role, and listen more than you write.
Write six reference-check questions for a [ROLE] that get past "they
were fine". Ask for specific examples and dates.Paid trial task. Final stage only. Change the role, and pay for the work.
Design a short paid trial task for a [ROLE] that shows how they work.
Two hours maximum, no free labour, one clear deliverable.Suppliers and operations prompts
Operations prompts work best as a comparison or checklist, because that is what you need when deciding.
Supplier comparison. Before choosing. Paste both quotes in full and check the terms yourself.
Compare these two supplier quotes on price, lead time, what is included
and what is excluded. Put the differences in a table.Late delivery message. The day it is late. Change the stated impact to the real one.
Draft a message to a supplier about a late delivery: the order, the
promised date, the impact, what I need today.Reorder list. Weekly or monthly. Paste real counts and check stock before ordering.
Turn these usage notes into a reorder list: item, quantity used, suggested
order quantity. Do not invent stock levels.Recurring problem checklist. After the second occurrence. Describe the actual failure, then test the checklist.
This keeps recurring: [DESCRIBE IT]. Write a one-page checklist that
would stop it happening again, including an early-warning check.Subcontractor brief. Before they start. Change the job and agree it in writing.
Write a scope-of-work brief for a subcontractor on [JOB]:
deliverables, sequence, what each side provides, what counts as finished.Internal process note. Before the change lands. Change the date and name a real person to ask.
Write a short internal note on this process change: what changes, from
when, what the team does differently, who to ask.Capacity risks. Friday afternoon. Paste your real constraints, then assign an owner to each risk.
Given these constraints, list next week's operational risks with one
prevention step each. No assumptions I have not stated.How to keep a prompt library that stays useful
Forty-two prompts are useless in a browser tab. Keep them in a document, numbered by job. Three rules stop the library rotting.
Version each prompt with a date. One line above it: what changed and when. A prompt full of last year’s exclusions is worse than none.
Save the output that worked. One good example beside each prompt teaches the format faster than any description.
Record failures, not just wins. When an output was unusable, note why in five words: “invented a lead time”. That tells you which constraint is missing.
Start with three. The ones for the job that hurts most this week, written properly, beat forty copied from a list. That is the honest limitation of an article like this, and why our editorial policy says what we test and what we cannot.
Or generate the prompt instead
If you would rather fill in blanks than edit a template, the prompt builder covers seven recurring jobs, from chasing an invoice to replying to a complaint, and leaves placeholders wherever you have not supplied a detail.
Frequently asked questions
Do these prompts only work in ChatGPT?
No. Nothing here is specific to one product. They are written for ChatGPT because that is what most owners have open, but the same text works elsewhere. What travels is the structure: context, constraints, format. What does not is any assumption the tool knows your business.
How long should a prompt be?
As long as it takes to include the facts the model cannot know, and no longer. Most prompts here are three to five lines plus a pasted input, and the pasted part does the heavy lifting. If a prompt grows because you are explaining your business in prose, paste a real example instead.
Can I reuse the same prompt for every customer?
Yes. That is the point of the brackets: the template stays fixed, the pasted input changes. Revisit monthly the fixed part, meaning your rates, exclusions and policy wording. A reused prompt with stale facts produces confident, wrong, on-brand output.
What should I never paste into a prompt?
Card numbers, bank details, passwords, customer addresses you do not need, and anything medical or disciplinary about a named person. Replace sensitive details with placeholders, then fill them in yourself before sending.
How do I know a prompt is actually working?
Set the test before you run it. Write down what the output must contain and the two things that would make it unusable, then run it on a finished job so you have a right answer to compare against. If you still rewrite most of it, the prompt is missing context, and the fix is usually a pasted example.
Last reviewed and updated on November 10, 2026.
