Choose by the output you need to make

ChatGPT Prompts for Small Business Owners

Local and online business owners creating operating, service, marketing, and support copy.

Where ChatGPT helps this role

  • Turn rough notes into a reviewable asset for a customer, employee, applicant, or local buyer.
  • Convert a recurring small business owners workflow into a reusable prompt sequence.
  • Ask ChatGPT for clarifying questions before committing to tone, format, or evidence.
  • Create a quick version for routine work and a deeper version for high-stakes work.
  • Review an existing answer against privacy, accuracy, and role-specific constraints.
  • Rewrite output for a different audience without changing the underlying facts.
  • Build a checklist that makes the human review faster and less subjective.

Main Risks

  • Prompts should fit the real business model and avoid legal, tax, or hiring advice as final judgment.
  • A broad prompt can hide missing source material, so small business owners should name the exact evidence before asking for output.
  • Over-polished wording can make weak assumptions look finished; every page links the prompt to a review step.
  • Copying the same prompt across tasks weakens results because small business owners need different inputs for planning, review, outreach, and explanation work.

Recommended Workflow

  1. Pick the task page that matches the decision, not just the closest job title.
  2. Prepare the source notes, audience, constraints, and forbidden assumptions before copying a prompt.
  3. Run the prompt once for structure, then run a review prompt against facts, tone, and missing context.
  4. Save the final prompt with the human review checklist so the workflow can be reused without becoming automatic.

Choose the first task by situation

Start with Sketch business plans when the user has source notes but does not yet know the right output structure, then move to Plan local marketing or Write customer service replies only after the audience and review owner are clear.

Choose by situation

  • Choose Sketch business plans when the main problem is shaping raw context into something a customer, employee, applicant, or local buyer can inspect.
  • Choose Plan local marketing when the user already has a first version and needs the next artifact in the same small business owners loop.
  • Choose Write customer service replies when the risk is quality control, review consistency, or a clearer handoff to another person.
  • Open the role guide when the user cannot name the task yet and needs to decide whether to create, revise, review, or sanitize context first.

Avoid starting with

  • Do not start from a broad role prompt when the user already knows the concrete task.
  • Do not start from a writing prompt when the missing piece is source material or reviewer approval.
  • Do not reuse a small business owners prompt across unrelated tasks without changing inputs, constraints, and review checks.

Small Business Owners pages are organized by the decision a person is trying to make, not by a long list of clever prompt phrases. The role page should help the user pick the first useful task, then the task page should carry the details: source material, variable fill, example, stronger prompt, and human review boundary.

Pick the workflow by decision

Sketch business plans

Use when the next decision is the shape, review path, or reuse rule for a business plan outline.

Sketch business plans needs business model, customer, offer, costs, channels, risks, and near-term milestone; its review lens is business plan outline quality, customer and offer, and customer-ready action, not a generic writing pass.

Plan local marketing

Use when the next decision is the shape, review path, or reuse rule for a local marketing plan.

Plan local marketing needs service area, customer segment, local channels, offer, budget, and calendar; its review lens is local marketing plan quality, service area and local channel, and customer-ready action, not a generic writing pass.

Write customer service replies

Use when the next decision is the shape, review path, or reuse rule for customer service replies.

Write customer service replies needs customer message, order or service context, policy, tone, and resolution options; its review lens is customer service replies quality, customer issue and policy boundary, and customer-ready action, not a generic writing pass.

Write SOPs

Use when the next decision is the shape, review path, or reuse rule for a standard operating procedure.

Write SOPs needs process trigger, owner, tool access, step order, exceptions, and quality checks; its review lens is standard operating procedure quality, trigger and owner, and customer-ready action, not a generic writing pass.

Write hiring posts

Use when the next decision is the shape, review path, or reuse rule for a hiring post.

Write hiring posts needs role scope, required skills, schedule, compensation range, culture notes, and screening rules; its review lens is hiring post quality, role outcomes and must-have criteria, and fairness and policy fit, not a generic writing pass.

Reply to reviews

Use when the next decision is the shape, review path, or reuse rule for a review reply.

Reply to reviews needs review text, customer sentiment, service facts, tone, and escalation boundary; its review lens is review reply quality, service recovery and customer retention, and recipient-safe next step, not a generic writing pass.

Write pricing pages

Use when the next decision is the shape, review path, or reuse rule for pricing page copy.

Write pricing pages needs offer tiers, customer segment, proof, objections, inclusions, and limits; its review lens is pricing page copy quality, tier logic and inclusions, and scope and value-risk check, not a generic writing pass.

Write email newsletters

Use when the next decision is the shape, review path, or reuse rule for an email newsletter.

Write email newsletters needs audience segment, topic, offer, links, timing, and voice; its review lens is email newsletter quality, audience segment and editorial hook, and recipient-safe next step, not a generic writing pass.

Open a prompt workbench

Review-first run

Sketch Business Plans: avoid unsupported financial, market, or outcome claims

A prompt set for business plans that keeps a business plan outline, customer, offer, revenue logic, cost assumptions, and milestone risk, and the final human check tied to the same source note. business plans stays close to a customer-facing workflow where service boundaries and trust matter, which keeps ChatGPT from drifting into generic advice.

Turn business model, customer, offer, costs, channels, risks, and near-term milestone into a business plan outline for a customer, employee, applicant, or local buyer.

Bring first
Need sections for customers, offer, pricing assumptions, costs, operations, risks, milestones, and questions for accountant. No fake projections. plan outline with risk and milestone rows needs the source note, output shape, and review owner in the same pass. The answer should protect the real constraint before polish. a business plan outline should use the note as its source. Before small business owners run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if
Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Ready-to-run path

Plan Local Marketing: check service area and local channel

A focused prompt path for small business owners: gather context, create a local marketing plan, repair weak answers, and save only the reusable parts. local marketing needs a human pass that can replace polished filler with source-backed lines inside a local marketing plan before the answer is reused.

Turn service area, customer segment, local channels, offer, budget, and calendar into a local marketing plan for a customer, employee, applicant, or local buyer.

Bring first
Need Google Business Profile ideas, email, flyers, referral offer, review ask, budget-light plan, and tracking notes. Small Business Owners need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The first answer should make the review path obvious. a customer, employee, applicant, or local buyer should still see the note while a local marketing plan is being built. Plan Local Marketing works better when the context is in named fields, because each variable can be checked before copying.
Reject if
Stop before sharing if it cannot show proof, numbers, or authority that the user did not provide.

Ready-to-run path

Write Customer Service Replies: prep customer, employee, applicant, or local buyer handoff

This customer service replies workflow helps small business owners copy the right prompt, inspect the answer, and hand off only what the source supports. customer service replies examples stay close to a customer-facing workflow where service boundaries and trust matter, so the prompt has a real work setting.

Turn customer message, order or service context, policy, tone, and resolution options into customer service replies for a customer, employee, applicant, or local buyer.

Bring first
Need response examples, tone rules, refund boundary, escalation trigger, and what staff should not promise. reply set with policy and resolution path would be weak without the source details, so the evidence has to stay attached. The saved version should keep the one-time details editable. Small Business Owners should use the note as the base for customer service replies. Before small business owners run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if
Do not use the answer if it hides unsupported claims about source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.

Review-first run

Write Sops: check trigger and owner

For small business owners, this page turns sops into a repeatable prompt process with source notes, examples, and a reviewer checkpoint. sops needs a human pass that can replace polished filler with source-backed lines inside a standard operating procedure before the answer is reused.

Turn process trigger, owner, tool access, step order, exceptions, and quality checks into a standard operating procedure for a customer, employee, applicant, or local buyer.

Bring first
Need SOP with timing, supplies, responsible role, quality check, exception handling, and closing handoff note. Small Business Owners need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. A useful run should keep the approval moment in view. a customer, employee, applicant, or local buyer should still see the note while a standard operating procedure is being built. Write Sops works better when the context is in named fields, because each variable can be checked before copying.
Reject if
Stop before sharing if it cannot show proof, numbers, or authority that the user did not provide.

Ready-to-run path

Write Hiring Posts: avoid the wording fair, job-related, and reviewed

Build a hiring post from role scope, required skills, schedule, compensation range, culture notes, and screening rules, then inspect source notes, examples, constraints, and reviewer judgment and the handoff before it reaches a customer, employee, applicant, or local buyer. hiring posts stays close to a customer-facing workflow where service boundaries and trust matter, which keeps ChatGPT from drifting into generic advice.

Turn role scope, required skills, schedule, compensation range, culture notes, and screening rules into a hiring post for a customer, employee, applicant, or local buyer.

Bring first
Need job post with duties, schedule, pay range note, must-haves, nice-to-haves, application steps, and inclusive wording. role post with scope and screening notes needs the source note, output shape, and review owner in the same pass. The prompt run should carry the rough note forward. a hiring post should use the note as its source. Before small business owners run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if
Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Ready-to-run path

Reply to Reviews: work from public reply that has to help

A practical reviews workflow for small business owners, with variable prompts, a messy-note example, quality checks, and next-step links. reviews treats reply version with escalation and public-tone limits as the asset to check, not as decorative output.

Turn review text, customer sentiment, service facts, tone, and escalation boundary into a review reply for a customer, employee, applicant, or local buyer.

Bring first
Need public reply under 90 words, acknowledge wait, thank customer, invite direct contact, no excuses, no coupon promise. In reply to reviews, the rough note has to lead because role-level advice would flatten the situation. A useful handoff should preserve the evidence before improving tone. Carry the reply to reviews note into a review reply. For reply to reviews, paste the source as bullets, constraints, and audience notes so the model has enough shape for a ready-to-edit message with subject line, body, tone notes, and review checklist.
Reject if
Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.

Review-first run

Write Pricing Pages: turn notes into pricing page copy

A working prompt pack for small business owners who need pricing page copy backed by real notes, clear limits, and reviewable output. pricing pages should only be saved after someone can replace polished filler with source-backed lines inside pricing page copy.

Turn offer tiers, customer segment, proof, objections, inclusions, and limits into pricing page copy for a customer, employee, applicant, or local buyer.

Bring first
Need package descriptions, who each fits, what is included, what costs extra, FAQ, and no tax or legal advice promise. a customer, employee, applicant, or local buyer can be misled by polished wording, so the reviewer check needs to stay visible. The copied prompt should keep the rough-note evidence intact. Treat write pricing pages as first-pass evidence for pricing page copy. Write Pricing Pages works better when the context is in named fields, because each variable can be checked before copying.
Reject if
Discard the answer if it cannot trace which details came from the source and which details were inferred.

Ready-to-run path

Write Email Newsletters: check audience segment and editorial hook

Small Business Owners can start email newsletters from real notes, copy a ready prompt, and check email newsletter quality, audience segment and editorial hook, and recipient-safe next step before using the result. email newsletters needs a human pass that can replace polished filler with source-backed lines inside an email newsletter before the answer is reused.

Turn audience segment, topic, offer, links, timing, and voice into an email newsletter for a customer, employee, applicant, or local buyer.

Bring first
Need subject lines, intro, three tips, workshop CTA, product mention, and local weather caveat. Friendly but not too salesy. Small Business Owners need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. The answer should start from the supplied details. a customer, employee, applicant, or local buyer should still see the note while an email newsletter is being built. Write Email Newsletters works better when the context is in named fields, because each variable can be checked before copying.
Reject if
Stop before sharing if it cannot show proof, numbers, or authority that the user did not provide.