ChatGPT Prompts for Small Business Owners: 50 Tested Examples

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for ChatGPT Prompts for Small Business Owners: 50 Tested Examples.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for ChatGPT Prompts for Small Business Owners: 50 Tested Examples.

The best ChatGPT prompts for small business owners are specific: they give your business context, the customer's situation, the format you want and a length limit. The 50 below are grouped by job, from enquiries and quotes to money, staff and planning, and each comes with what it returns and how to adapt it for your trade.

One habit matters more than any single prompt: tell ChatGPT who you are once, then reuse it. Put a short business profile in a Project's instructions (prompt 50 builds it for you) so every answer starts from your services, prices, tone and rules. Before pasting anything about customers, switch off "Improve the model for everyone" under Settings, Data controls on personal plans, or use a Business plan, which doesn't train on your data by default.

Follow me on Instagram@sagnikteaches

Four habits that make any of these prompts better

Every prompt in this list follows the same pattern, and it's worth knowing why, because you'll write your own soon enough.

Connect on LinkedInSagnik Bhattacharya
  • Context first. "We're a five-person landscaping firm; most customers are homeowners with medium gardens" changes every answer that follows. Without it you get generic copy that could come from anyone.
  • Square brackets for what changes. Everything in [brackets] is a slot you fill in each time. Keep the rest fixed, so results stay consistent from one week to the next.
  • Ask for questions before answers. "Ask me up to three questions first" stops ChatGPT inventing details it doesn't have, which is the most common reason drafts need rewriting.
  • Say what to leave out. "No exclamation marks, no discounts, don't promise dates" saves more editing than any amount of "make it professional".

What not to paste, on any plan: card numbers, bank logins, alarm or key-safe codes, and anything a customer told you in confidence that the task doesn't need. Replace names with [first name] where the answer doesn't depend on them. If you want a fuller routine for this, anonymising client data before you paste it covers it step by step.

Subscribe on YouTube@codingliquids

Enquiries and customer emails (prompts 1 to 7)

These save the most time for most owners, because customer emails arrive every day and follow a handful of patterns.

1. Reply to an enquiry that's missing details

We're a [business type]. A customer sent this enquiry:
[paste enquiry]
Write a friendly reply under 120 words that thanks them and
asks only for the details we need to quote: [list, e.g. photos
of the area, rough size, preferred dates]. No prices yet.
  • Returns: a short reply with a numbered list of questions, which customers answer more completely than a paragraph.
  • Adapt it: keep a fixed list of "details we need" per job type, so the office asks the same questions every time.

A sample result for a removals enquiry (illustrative): "Thanks for getting in touch about your move on the 14th. To give you an accurate quote, could you tell us: 1. how many bedrooms the current property has; 2. whether there's parking outside both addresses; 3. if you'd like us to pack, or just move; 4. any large items like pianos or wardrobes that don't dismantle." What to fix: it assumed the date was confirmed. Change "your move on the 14th" to "your planned move" unless the customer said it was fixed.

2. Turn a rambling voicemail transcript into a job sheet

Turn this voicemail transcript into a job sheet with these
fields: name, contact, address given (Y/N), problem, urgency
(emergency/this week/flexible), access notes, questions to
ask on callback. Don't guess missing fields; write "not given".
[paste transcript]
  • Returns: a clean form you can paste into your job system, with gaps clearly marked.
  • Adapt it: match the field names to your job management software so staff can copy them straight across.

3. Calm down an angry customer email

A customer sent this complaint: [paste]. Our view of what
happened: [facts]. Draft a reply that acknowledges their
frustration without admitting fault we haven't established,
states what we'll do next and by when, and stays under 150
words. Plain language, no corporate phrases.
  • Returns: a measured reply with a concrete next step.
  • Watch: it tends to over-apologise. Remove any apology for things you didn't do, and never let it offer refunds you haven't decided on.

Here's the kind of draft it produces for a cleaning complaint (illustrative): "I'm sorry the kitchen wasn't up to standard after Tuesday's clean, and thank you for sending photos. I've shared them with the supervisor, and we'd like to send the team back on Thursday morning to put it right at no charge. Could you confirm that time works?" The edit it needed: "at no charge" is a decision, not wording. Keep it only if you've agreed it, and check Thursday is actually free.

4. Explain a technical problem in plain English

Explain to a homeowner with no technical knowledge why
[problem, e.g. their boiler keeps losing pressure] happens,
what we recommend, and what it costs to leave it. Under 150
words, no jargon, one short analogy at most.
  • Returns: a clear explanation you can reuse in quotes and follow-ups.
  • Watch: check every technical claim yourself. It explains confidently whether or not it's right, and customers will quote it back to you.

5. Follow up a quote that went quiet

We sent this quote [date] and heard nothing: [summary].
Write three follow-ups: day 3 (helpful, answers likely
questions), day 10 (offers a call), day 21 (polite close,
door left open). Each under 80 words. No pressure tactics,
no fake deadlines.
  • Returns: a three-step sequence you can schedule in your email or CRM.
  • Adapt it: add the most common reason quotes stall in your trade (price, timing, a partner who needs to agree) and ask it to address that in message one.

6. Turn down a job politely and refer it on

We can't take this job: [reason, e.g. outside our service
area / not work we do]. Write a short, warm reply that
explains why in one sentence and suggests what kind of
business to contact instead. Don't name competitors.
  • Returns: a courteous refusal that leaves the customer with somewhere to go, which protects your reputation more than silence does.
  • Adapt it: keep two or three standard reasons (area, job size, specialism) so the office can send these in seconds, and log the refusals; a pattern of the same request is a hint about a service you could add.

7. Build an FAQ from past emails

Here are 30 customer questions from our inbox this year
[paste, names removed]. Group them into the 10 most common
questions and draft a short answer to each from the facts
below. Mark any answer you had to guess with [CHECK].
[our facts: prices, hours, policies]
  • Returns: a first FAQ page or chatbot knowledge sheet, with guesses flagged.
  • Watch: every [CHECK] needs a human answer. Those are exactly the questions where a wrong answer causes disputes.

Quotes, pricing and proposals (prompts 8 to 13)

ChatGPT is good at the words around a price and at spotting what's missing. It is bad at the price itself, because it doesn't know your costs, so every prompt here keeps the numbers in your hands.

8. Turn site notes into a quote cover letter

Write a quote cover letter from these site notes: [notes].
Price: [total]. Include what's included, what isn't, how long
it takes, and what happens next. Under 200 words. Use the
customer's own words for the problem where possible.
  • Returns: a tidy letter that reads as though you listened, because it reuses the customer's description.

A sample opening for a roofing quote (illustrative): "You mentioned water coming through the ceiling in the back bedroom after heavy rain. On our visit we found three slipped tiles and a cracked lead flashing above that room. This quote covers replacing both, clearing the gutter on that side and checking the rest of the rear roof while the scaffold is up." What to fix: it added "checking the rest of the rear roof", which wasn't in the notes. Delete anything the site notes don't support, because customers hold you to the letter, not the notes.

9. Check a quote for forgotten items

Here's a quote for [job type]: [paste line items]. List items
that jobs like this often need but this quote doesn't mention,
e.g. waste disposal, access equipment, making good. Questions
only; don't add prices.
  • Returns: a checklist of possible omissions to consider before you send.
  • Adapt it: save the useful suggestions as a permanent checklist for that job type.

10. Explain a price increase to regular customers

We're raising [service] from [old price] to [new price] from
[date] because [real reasons]. Write a short message to
regular customers: honest reason, the new price, when it
starts, and thanks for their custom. No apology spiral.
  • Returns: a respectful notice that states the change plainly.

Illustrative output for a window-cleaning round: "From 1 March, a standard three-bed clean will be $32, up from $28. Fuel, insurance and equipment costs have all risen over the past year, and this is our first increase in two years. Nothing else changes: same team, same day. Thank you for being a regular customer." Before sending, check "first increase in two years" is true. ChatGPT will cheerfully write a reassuring detail you never gave it.

11. Compare supplier quotes side by side

Put these three supplier quotes into a table: supplier, items,
unit prices, delivery, payment terms, anything unusual in the
small print. Then list questions to ask each one.
[paste quotes]
  • Returns: a comparison table and a question list.
  • Watch: check each figure against the original. Table-building is where copied numbers slip.

12. Write good, better and best options

For [job], write three options for a quote: essential,
recommended and premium. For each: what's included, the
benefit to the customer in one line, and a placeholder for
the price. Recommended should be the obvious sensible choice.
  • Returns: a tiered structure that helps customers choose rather than haggle.
  • Adapt it: fill in prices yourself; the value is in the descriptions.

13. List the costs you might be forgetting

I'm pricing [job type] for [business type]. List every cost
category I should include, including hidden ones like travel
time, waste, callbacks and admin. Don't give figures; I'll
add my own.
  • Returns: a cost checklist. Many owners find two or three categories they've been absorbing for free.
  • Adapt it: run it once per job type and turn the answer into a costing template; a roofer's list and a cleaner's list share little beyond travel and admin.

Marketing, social posts and your website (prompts 14 to 20)

These work best when you feed them real jobs. ChatGPT with nothing to go on writes the same posts as everyone else in your trade.

14. A month of post ideas from real jobs

Here are the jobs we did this month: [list with one detail
each]. Suggest 12 social posts: 4 before-and-after, 4 useful
tips, 2 behind-the-scenes, 2 customer questions answered. One
line each, plus the photo we'd need.
  • Returns: a posting plan tied to work you've actually done, with a shot list for the team.

15. Caption a before-and-after photo

Write an Instagram caption for a before-and-after of [job].
Detail: [what made it tricky]. Under 60 words, one practical
tip for homeowners, up to 3 relevant hashtags. No emojis.
  • Returns: a short caption with a tip, which gets saved and shared more than "another happy customer".
  • Watch: Instagram caps hashtags at five per post, so keep the request at three to five.

16. Rewrite a web page for one type of customer

Rewrite this service page for [customer type, e.g. landlords
with several properties]. Keep every fact; change emphasis,
examples and the questions answered. Under 400 words.
[paste page]
  • Returns: a version that speaks to one audience, useful for landing pages and ads.
  • Watch: compare facts line by line. "Keep every fact" reduces invention but doesn't eliminate it.

17. Write a Google Business Profile update

Write a Google Business Profile post about [news/offer/job].
Under 100 words, one clear call to action, nothing that
sounds like an advert for a competitor's product.
  • Returns: a short update in the right length for the profile.
  • Adapt it: add a real photo from the job and one concrete detail, such as the type of work or the problem solved; generic updates get skipped.

18. Turn recent jobs into a customer newsletter

Write a short email newsletter from these notes: [3-4 jobs,
one seasonal tip, one reminder]. Subject line under 45
characters, 250 words max, friendly and practical.
  • Returns: a ready-to-edit newsletter and subject line.
  • Watch: ask for three subject lines and pick the plainest. Models love a pun, and puns rarely get opened.

19. Draft a page for a new service

We're adding [new service]. Ask me 5 questions about how we
deliver it, then draft a service page: what it is, who it's
for, how it works step by step, what it costs to find out.
  • Returns: questions first, then a page built on your answers, which is far better than a page built on nothing.
  • Adapt it: answer the questions in rough bullet points; the rougher and more specific your answers, the less the page sounds like everyone else's.

20. Write ad headline variations

Write 10 search ad headlines under 30 characters for [service]
aimed at [customer]. Vary the angle: speed, price clarity,
reliability, expertise. No claims we can't prove: [our facts].
  • Returns: options to test. Delete any that claim "best" or "cheapest" unless you can prove it.

Reviews and reputation (prompts 21 to 25)

21. Reply to a positive review

Reply to this review in under 50 words. Mention one specific
detail they raised, thank them, no sales pitch.
[paste review]
  • Returns: a short, specific thank-you that doesn't read like a template.
  • Watch: if you reply to many reviews in one sitting, ask for varied openings, or every reply starts with the same thank-you line and readers notice.

22. Reply to a negative review

Draft a public reply to this negative review: [paste]. Facts
from our side: [facts]. Calm, brief, no arguing detail in
public, invite them to contact [name/role] directly. Under
80 words.
  • Returns: a measured public reply that moves the discussion offline.

For a locksmith, a typical draft reads (illustrative): "Thank you for the feedback. I'm sorry the wait on Saturday was longer than the time we gave you; that's not the service we aim for. I'd like to understand what happened and put it right, so please call me directly on [number]." Little needs changing, but check the wait really was longer than quoted before you agree with it in public. A reply that concedes a fact you later dispute is hard to walk back.

23. Ask for a review, the compliant way

Write a short text message asking a customer to leave a
review after [job]. No incentive, ask every customer the same
way, and don't ask them to mention any staff member by name.
Include [review link].
  • Returns: a request that fits Google's current rules, which ban incentives and review gating and, since April 2026, asking for reviews that mention specific content such as a staff member's name.

24. Find themes in your reviews

Here are our last 50 reviews [paste, names removed]. List the
5 things customers praise most and the 5 complaints that
recur, with how often each appears. Quote short examples.
  • Returns: a summary you can act on and use in marketing.
  • Watch: spot-check the counts; models are loose with tallies across long lists.

25. Turn a complaint into a process fix

This complaint happened: [summary]. Our current process:
[steps]. Suggest 3 changes to the process that would prevent
it, each with who does it and how we'd know it's working.
  • Returns: practical process changes, not just a better apology.
  • Adapt it: give it the last three similar complaints rather than one; patterns across several are more useful than a fix for a one-off.

Operations, checklists and processes (prompts 26 to 31)

26. Turn a voice note into a written procedure

Here's a transcript of me explaining how we [task]. Turn it
into a numbered procedure a new starter could follow, with
a "check before you leave" list at the end. Flag any step
that seems to be missing.
  • Returns: a written procedure from knowledge that previously lived only in your head.

For an HVAC annual service, a typical result (illustrative) has nine steps and one flag: "You mention recording the flue gas reading but not where it's recorded. Add the form or system." That flag is the value. One edit: it wrote "test the appliance" as one step; break vague steps into the actual checks your engineers do.

27. Build a job-type checklist

Create a checklist for [job, e.g. end-of-tenancy clean of a
two-bed flat], grouped by room, with the items inspectors
most often fail. Tick-box format, one line per item.
  • Returns: a printable checklist you can refine after each job.
  • Watch: remove items that don't apply to how you work; an over-long checklist gets ticked without being read.

28. Untangle a scheduling puzzle

Help me plan next week. Jobs: [list with durations]. Staff:
[names, skills, days off]. Rules: [e.g. two people for heavy
lifts]. Propose a schedule and list any rule you couldn't meet.
  • Returns: a draft rota with conflicts named.
  • Watch: it doesn't know travel times between jobs unless you give them. Treat the output as a first draft, not the plan.

29. Create a van or kit checklist

List the tools, materials and paperwork a [trade] van should
carry for [job types], grouped by "every job", "most jobs"
and "occasional". Flag items that expire or need servicing.
  • Returns: a stock list that cuts return trips for forgotten parts.
  • Adapt it: ask engineers which items they drove back for last month and add them; the AI's list is a starting point, their memory is the real one.

30. Write up an incident from notes

Write a factual incident report from these notes: [notes].
Headings: what happened, when, who was involved, immediate
action, follow-up needed. No opinions or blame; facts only.
  • Returns: a neutral record, useful if an insurer or customer asks later.
  • Watch: write the notes as soon as possible after the event and paste them unedited; the model should tidy wording, not fill gaps from imagination.

31. Turn meeting notes into actions

Turn these rough meeting notes into: decisions made, actions
(who, what, by when), and open questions. If an action has
no owner, list it under "needs an owner".
[paste notes]
  • Returns: a clean action list, and the "needs an owner" section alone usually justifies it.

Money: invoices, costs and cash flow (prompts 32 to 37)

Keep bank details and card numbers out of every prompt here. Category totals and anonymised lists are enough for all of these jobs.

32. Write a three-stage invoice reminder

Write three payment reminders for an overdue invoice of
[amount], due [date]: gentle (day 3), firm (day 14), final
(day 30, mentions next steps per our terms: [terms]). Each
under 90 words, polite throughout.
  • Returns: a reminder sequence you can load into your accounting software.

Stage two came out like this (illustrative): "Invoice 1043 for $1,280, due on 2 May, is now 14 days overdue. If it's already been paid, thank you, and please ignore this. If not, could you let us know when we can expect payment? You can pay by bank transfer using the details on the invoice." It's good as it stands; just add your own terms line (late fees or next steps) only if your terms actually include them.

33. Explain a spreadsheet you've exported

I've uploaded our monthly income and costs for the past year
(CSV, names removed). Summarise the trends in plain English,
show which months were tight, and list 3 questions I should
ask my accountant.
  • Returns: a plain-English read of your numbers, with a chart if you ask for one.
  • Watch: check any figure you'll act on against the original file. If spreadsheets are where you spend your time, the guide to using ChatGPT with Excel goes much further.

34. Find subscriptions worth cancelling

Here's a list of our monthly software and subscription costs
[name, cost, who uses it]. Group them, flag overlaps and
anything nobody uses, and suggest what to check before
cancelling each.
  • Returns: a tidy list with overlaps flagged. Plenty of small firms find two tools doing the same job.
  • Watch: check notice periods and annual renewal dates before cancelling anything; the saving isn't real if you're locked in for another year.

35. Work out a break-even point

We're considering [a second van / a new hire]. Monthly cost:
[figure]. Average profit per job: [figure]. Show how many
extra jobs a month we'd need to break even, with the working
shown, and what assumptions would change the answer.
  • Returns: a worked sum you can check line by line, which is the point of asking for the working.

36. Turn costs into a price list

Our costs for [service]: [labour hours, materials, travel,
overhead per job]. Target margin: [x]%. Build a simple price
table for small, medium and large jobs, showing the working.
  • Returns: a starting price table based on your own numbers.
  • Watch: check the maths yourself; ask it to show each step so errors are visible.

37. Offer a payment plan kindly

A customer owes [amount] and has said they're struggling.
Draft a message offering a payment plan of [terms], kind in
tone, clear about amounts and dates, and asking them to
confirm in writing.
  • Returns: a humane message that still sets clear terms.
  • Adapt it: agree the plan's figures before drafting, then ask for a short schedule table with dates and amounts that the customer can keep.

Staff, hiring and training (prompts 38 to 43)

38. Write a job advert from a messy description

Turn this into a job advert: [notes about the role, pay,
hours, what the job is really like]. Sections: the role, a
typical week, what we need, what we offer, how to apply.
Honest about the hard parts. Under 350 words.
  • Returns: an advert that describes the real job, which tends to attract applicants who stay.

Illustrative excerpt for a cleaning supervisor role: "A typical week: you'll run two teams of three across about 30 domestic and office cleans, check quality on site, handle the Monday rota and be the person clients call when something isn't right." The fix: it described the pay as "competitive". Replace it with the actual figure; adverts with real pay get more serious applicants.

39. Prepare interview questions and a scoring sheet

Write 8 interview questions for [role] that test [skills],
including 2 that ask about a real past situation. For each,
describe a weak, good and strong answer. Nothing about age,
family plans, health or background.
  • Returns: questions plus a scoring guide, so interviews are fairer and easier to compare.

40. Plan a new starter's first week

Create a day-by-day first week for a new [role]: who they
shadow, what they learn, what they do on their own by Friday,
and a 15-minute check-in agenda for the end of the week.
  • Returns: an onboarding plan that stops new staff spending day one waiting around.
  • Adapt it: include which AI tools they'll use and the rules for them, so good habits start in week one rather than after the first mistake.

41. Announce a rota change without grumbles

Write a short team message about this rota change: [change,
reason, date]. Acknowledge the inconvenience, explain why in
one sentence, and say who to talk to about problems.
  • Returns: a clear message that heads off most of the questions.
  • Watch: send it where the team actually reads messages, and give a date by which people should raise problems.

42. Prepare for a difficult conversation

I need to talk to a team member about [issue, facts only].
Help me plan: how to open, the facts to state, questions to
ask, what I want agreed by the end. This isn't a formal
disciplinary; I'll follow our policy if it becomes one.
  • Returns: a structure for the conversation.
  • Watch: for anything formal, follow your written procedure and take HR advice; don't paste the employee's personal details.

43. Turn a procedure into a training quiz

Write a 10-question quiz from this procedure [paste], mixing
multiple choice and "what would you do if" scenarios. Include
the answers separately.
  • Returns: a quick way to check that a procedure has been read and understood.
  • Adapt it: base the scenarios on real mistakes from the past year; a question about something that actually went wrong teaches more than a textbook case.

Planning and decisions (prompts 44 to 50)

44. Think through a decision properly

I'm deciding whether to [decision]. Before answering, ask me
5 questions about my situation. Then give the strongest case
for, the strongest case against, and what I'd need to believe
for each to be right.
  • Returns: a structured argument rather than a verdict, which is what you want from a tool that doesn't know your business as well as you do.

45. Run a pre-mortem on a new idea

Imagine it's a year from now and our new [service/idea]
failed. List the 8 most likely reasons, and for each, one
early warning sign we could watch for in the first 90 days.
  • Returns: the risks you'd otherwise discover the expensive way.

Illustrative output for a landscaper adding a garden maintenance plan included "customers cancel in winter when there's little visible work" with the warning sign "more than 10% of plans paused by November". What to fix: it suggested a 12-month minimum contract as a solution; that's a business decision with consumer-law implications, so treat suggestions as questions to research, not advice.

46. Compare your website with a competitor's

Here's the text of our [service] page and a competitor's
[paste both]. Which questions does theirs answer that ours
doesn't? Suggest additions to ours; don't copy their wording.
  • Returns: gaps in your page, without borrowing their copy.
  • Watch: copying a competitor's wording creates problems of its own, so use the gaps as a to-do list and write the additions from your own experience.

47. Summarise a long document into questions

Summarise this [contract/tender/supplier terms] in plain
English: what we must do, what they must do, payment terms,
how either side can end it, and anything unusual. Then list
questions to ask before signing. Not legal advice.
  • Returns: a readable summary and a question list for the other side or your solicitor.
  • Watch: it can miss clauses. Use it to prepare questions, never as the reason to sign.

48. Build a 90-day plan

My goal for the next 90 days: [goal]. Constraints: [time,
money, staff]. Break it into weekly milestones, name the one
thing that matters most each month, and say what I should
stop doing to make room.
  • Returns: a realistic plan, and the "stop doing" list is the part most plans skip.
  • Adapt it: paste the plan into a Project and run prompt 49 against it each Friday, so the plan and the weekly review stay connected.

49. Run a weekly review

Ask me these one at a time, then summarise: What went well?
What went wrong? What did customers complain or rave about?
What's the one thing to fix next week? What am I avoiding?
  • Returns: a ten-minute Friday habit that builds a record of how the business is going.

50. Let ChatGPT interview you for your business profile

Interview me to build a business profile you'll use for
future tasks. Ask one question at a time about: what we do,
who our customers are, prices and policies, tone of voice,
words we never use, and rules you must follow. Then write the
profile in under 300 words.
  • Returns: the profile that makes every other prompt here better. Paste it into a Project's instructions so it applies to every chat in that Project; on business plans the Project can be shared with colleagues.

Keeping your best prompts where the team can find them

Once a few of these become weekly habits, store them somewhere other than your chat history: a shared document, or the instructions and files of a ChatGPT Project. Don't build custom GPTs for them. OpenAI is retiring custom GPTs, which stop running on 11 December 2026, and its migration turns them into plugins with skills; a Project or a shared document is simpler and moves easily between tools. The method for organising prompts across a team is set out in how to build a shared prompt library, and making the output sound like you rather than like ChatGPT is covered in writing AI prompts that sound like your business.

For multi-step jobs, such as researching three suppliers and producing a comparison spreadsheet, ChatGPT Work (which replaced the old agent mode in July 2026) can carry out several steps for you on Plus, Pro, Business and Enterprise plans. Check its work the same way you'd check a new starter's. And whichever prompts you use, remember what the sample outputs above had in common: nearly every one needed a fact checked or a promise removed. That is normal, and a sensible expectation for the accuracy of drafts is set out in how accurate ChatGPT is, task by task. The prompts save the writing; you still own what goes out.

Using these prompts: common questions

Do these prompts work on the free ChatGPT plan?

Most of them do, because they only need text in and text out. Prompts that analyse an uploaded spreadsheet, or that you want to reuse inside a Project, work best on a paid plan. OpenAI says ads may appear on the Free and Go plans, while Plus and above have none. Whatever the plan, check the privacy setting before pasting business information.

Will these prompts work in Claude, Gemini or Copilot?

Yes. Nothing in them is specific to ChatGPT; they rely on giving context, constraints and a clear output format, which every major assistant responds to. Wording of the replies will differ, and some tools are stronger at certain jobs, so run your most-used prompts in two assistants once and keep the one whose drafts need fewer edits.

Should I build a custom GPT for the prompts I use most?

No. OpenAI is retiring custom GPTs: they stop running on 11 December 2026, and OpenAI's replacement turns them into plugins with skills. For shared business context, put your business profile and standing rules in a ChatGPT Project's instructions, and keep your best prompts in a shared prompt library document.

Further reads

Sources: OpenAI help pages (Data controls FAQ; ChatGPT Business overview; custom GPT retirement FAQ); OpenAI pricing for ChatGPT plans; Google review policies for the review prompts. Checked September 2026. Sample outputs are illustrative.

Want prompts built around your own jobs?

On a 1:1 call we'll pick the tasks where prompts save your team the most time, build a shared set around your business, and decide which ones are worth turning into automations.

Book a 1:1 call with me