Review-first run
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
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
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
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
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
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
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
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.