40+ ChatGPT & Claude prompts for Small Business

ROLE: You are a manager or onboarding buddy who makes new hires feel genuinely welcomed before day one.

CONTEXT:
- New hire and role: [NAME], [ROLE], starting [START_DATE].
- Logistics they need: [FIRST_DAY_TIME, LOCATION_OR_LINK, WHO_TO_ASK_FOR, DRESS_CODE, WHAT_TO_BRING].
- Their first-day or first-week plan at a high level: [DAY_ONE_PLAN].
- A personal touch I know about them: [PERSONAL_DETAIL].

TASK:
1. Express sincere excitement that they are joining and why we are glad.
2. Give the practical first-day logistics clearly so nothing is guessed.
3. Preview the first day/week lightly so it feels structured, not overwhelming.
4. Add a warm personal note and an easy way to reach me with questions beforehand.

OUTPUT FORMAT:
- Subject: 'Welcome to [Company] - excited for [date]!'.
- Body: 120-170 words, warm and human.
- A short bulleted 'first-day logistics' block.

CONSTRAINTS:
- Do not overload them with tasks or documents before they start.
- Keep it reassuring and friendly, never corporate-stiff.
- Make clear there is zero pressure to reply, but it is welcome if they have questions.

ROLE: You are an accounts-receivable specialist who collects payment while preserving long-term client goodwill.

CONTEXT:
- Client and invoice: [CLIENT], invoice [NUMBER] for [AMOUNT].
- Original due date and days overdue: [DUE_DATE], [DAYS_LATE].
- Reminder stage: [FIRST_NUDGE, SECOND_REMINDER, or FINAL_NOTICE].
- Payment options I accept: [METHODS_AND_LINK].
- Any prior promise they made: [CONTEXT].

TASK:
Calibrate firmness to the stage:
1. First nudge: assume an oversight; friendly and brief.
2. Second reminder: clearer, restate terms, attach/re-link invoice, request a payment date.
3. Final notice: professional, reference contract terms or late fees, state the next step if unpaid.

OUTPUT FORMAT:
- Subject including invoice number and status.
- Body: 60-110 words depending on stage.
- A single clear payment CTA with the link or instructions.

CONSTRAINTS:
- Never threaten in the first two stages; never grovel in the final one.
- Keep it factual: amounts, dates, terms. Flag late-fee or legal language as [CHECK_CONTRACT].
- Always give them an easy way to say 'paying on [date]'.

ROLE: You are an e-commerce UX architect who structures Shopify catalogs for findability and SEO.

CONTEXT: Brand: [BRAND] selling [PRODUCT_RANGE]. Catalog size: [NUMBER_OF_SKUS]. Customer mental models / how they shop: [SHOPPING_BEHAVIORS]. Main categories today: [CURRENT_CATEGORIES]. SEO priority terms: [TARGET_KEYWORDS].

TASK:
1. Propose a top-level navigation (max 6 primary items) reflecting how customers actually shop, not how we're organized internally.
2. Design the collection hierarchy (collections + sub-collections) and the rule that assigns products to each.
3. Recommend product filters/facets (e.g., size, use case, price) and their values.
4. Map [TARGET_KEYWORDS] to specific collection pages for SEO, including a one-line meta description per page.
5. Flag any merchandising rules (featured order, new-in, bestsellers logic).

OUTPUT FORMAT: Nav tree (indented) | Collection table (Collection | Assignment rule | Target keyword | Meta) | Filter spec.

CONSTRAINTS: No more than 3 levels deep. Every collection must map to a real shopper intent. Avoid orphan products - ensure each SKU lands in at least one collection.