Help me start the right Small Business Owners workflow.
Task to use: Sketch Business Plans: make plan outline with risk and milestone rows reviewable.
Paste current work: 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..
Audience and constraints: Local and online business owners creating operating, service, marketing, and support copy..
Who checks it: Assign the business plan outline check to someone who understands business plan outline quality, customer and offer, and customer-ready action; they compare the answer with the source note before a customer, employee, applicant, or local buyer sees it..
Before writing, ask for anything missing that would change the sketch business plans: make plan outline with risk and milestone rows reviewable output.
Return: The reusable version should keep the fields, rejection rules, and review lens while removing one-time details.
Stop if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
After the first answer
Save what came back, what needs fixing, and the next prompt change before moving to another task.
0No role notes yet
Run the prompt once, check the answer, then save the problem and next try here.
Nothing saved yet
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
Pick the task page that matches the work to finish, not just the closest job title.
Prepare the source notes, audience, constraints, and forbidden assumptions before copying a prompt.
Run the prompt once for structure, then run a review prompt against facts, tone, and missing context.
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 named human check.
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 choice a person is trying to make, not by a generic prompt collection. 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 the work in front of you
Sketch business plans
Use when the next useful output is a business plan outline and the answer needs a sequenced plan with stages, owners, timing, and choice checkpoints.
Sketch business plans needs business model, customer, offer, costs, channels, risks, and near-term milestone; the check focuses on business plan outline quality, customer and offer, and customer-ready action, not a generic writing pass.
Plan local marketing
Use when the next useful output is a local marketing plan and the answer needs a local marketing plan arranged as a working version, check questions, and next steps.
Plan local marketing needs service area, customer segment, local channels, offer, budget, and calendar; the check focuses on 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 useful output is customer service replies and the answer needs customer service replies with named sections, action bullets, and a final reviewer pass.
Write customer service replies needs customer message, order or service context, policy, tone, and resolution options; the check focuses on customer service replies quality, customer issue and policy boundary, and customer-ready action, not a generic writing pass.
Write SOPs
Use when the next useful output is a standard operating procedure and the answer needs a standard operating procedure arranged as a working version, check questions, and next steps.
Write SOPs needs process trigger, owner, tool access, step order, exceptions, and quality checks; the check focuses on standard operating procedure quality, trigger and owner, and customer-ready action, not a generic writing pass.
Write hiring posts
Use when the next useful output is a hiring post and the answer needs a hiring post split into reader-ready copy, open questions, and reviewer notes.
Write hiring posts needs role scope, required skills, schedule, compensation range, culture notes, and screening rules; the check focuses on 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 useful output is a review reply and the answer needs a ready-to-edit message with subject line, body, tone notes, and review checklist.
Reply to reviews needs review text, customer sentiment, service facts, tone, and escalation boundary; the check focuses on 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 useful output is pricing page copy and the answer needs copy options grouped by angle, audience, supporting detail, and revision note.
Write pricing pages needs offer tiers, customer segment, support, objections, inclusions, and limits; the check focuses on 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 useful output is an email newsletter and the answer needs a ready-to-edit message with subject line, body, tone notes, and review checklist.
Write email newsletters needs audience segment, topic, offer, links, timing, and voice; the check focuses on email newsletter quality, audience segment and editorial hook, and recipient-safe next step, not a generic writing pass.
The business plan outline prompt set keeps a business plan outline, customer, offer, revenue logic, cost assumptions, and milestone risk, and the final check tied to the same source note. It is built to reduce polished but unsupported answers.
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.
The local marketing plan prompt path asks for service area, customer segment, local channels, offer, budget, and calendar, creates a local marketing plan, and marks what still needs a person. It is meant for a customer, employee, applicant, or local buyer, not for one-click publishing.
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 support, numbers, or authority that the user did not provide.
Use this customer service replies workflow when small business owners need to move from source notes to a shareable answer without losing the original limits. It keeps customer service replies quality, customer issue and policy boundary visible before reuse.
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 provided context, examples, hard constraints, and the final human check or treats uncertainty as fact.
Repeat sops work from the original notes instead of from a saved generic prompt. The page links examples, reject rules, and a reviewer pass for standard operating procedure quality, trigger and owner, and customer-ready.
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 support, numbers, or authority that the user did not provide.
Use this hiring post workflow when the raw material is role scope, required skills, schedule, compensation range, culture notes. It turns that material into a hiring post split into reader-ready copy, open questions and keeps the pasted notes, concrete examples, hard limits, and reviewer in front of the person checking the answer.
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.
Use this when review reply has real source material but still needs review. The page turns review text, customer sentiment, service facts, tone, and escalation boundary into a review reply and shows what to keep, question, revise, or discard.
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 review reply work, 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 source note into a review reply. For review reply work, 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.
The pricing page copy setup gives small business owners a working prompt pack backed by real notes, clear limits, and reviewable output. It centers pricing section copy with plan-fit checks, not generic advice. It also names the objection language a customer may raise about price, value, or plan fit.
Turn offer tiers, customer segment, support, 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 the rough request 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.
Bring audience segment, topic, offer, links, timing, and voice into the email newsletter workflow and keep audience segment, editorial hook, offer placement, and click path visible from the first run. small business owners can check email newsletter quality, audience segment and editorial hook before sharing the result.
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 support, numbers, or authority that the user did not provide.