[
  {
    "id": "inbox-priority-review",
    "title": "Triage your inbox without automatically replying",
    "description": "Separate messages needing a decision from reference material and low-priority mail.",
    "category": "Customer service",
    "tool": "Muse",
    "toolUrl": "https://muse.ai/",
    "level": "Beginner",
    "evidence": "Editorial adaptation",
    "output": "A source-linked inbox review with action items, deadlines, and unsent reply drafts.",
    "inputs": [
      "A limited date range or mailbox label",
      "Your priority rules and examples of messages that matter"
    ],
    "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.",
    "prompt": "For my small business, review [mailbox scope] using [priority rules]. Return messages requiring my decision, deadlines explicitly stated in the email, unanswered questions, and optional unsent reply drafts. Link to the original message and distinguish an explicit commitment from an inference. Do not send, archive, delete, unsubscribe, or change labels. Ask for clarification when the sender's intent is unclear.",
    "steps": [
      "Connect only the mailbox access you intend Muse to use, or provide approved exports.",
      "Define the time range and examples of high-priority messages.",
      "Compare the first brief to the original messages, including excluded items.",
      "Adjust rules and use an approval step for any later actions."
    ],
    "review": "Check deadlines, recipients, commitments, and any message the assistant may have missed.",
    "limits": [
      "Mail access and available actions depend on your configured account.",
      "A large inbox demonstration does not prove reliable triage for every mailbox."
    ],
    "measure": "Missed important messages, false priorities, and corrections to draft replies.",
    "sources": [
      {
        "title": "Muse email demonstration",
        "url": "https://x.com/Muse/status/2097440088812662803",
        "author": "Muse, featuring Casey and Hal",
        "note": "September 8, 2026. Official demonstration of working with a large email history. Our priority rubric and draft-only prompt are editorial additions. This guide adapts the idea for a small-business owner; any reported outcome belongs to the original tool and source.",
        "kind": "Vendor example"
      },
      {
        "title": "Introducing Muse",
        "url": "https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/",
        "author": "Meta",
        "note": "Official introduction of the personal agent. Connector access, account availability, and action permissions still need to be configured.",
        "kind": "Official documentation"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "prospect-research-sheet",
    "title": "Research a small prospect list with evidence",
    "description": "Build account briefs you can verify before using them for outreach.",
    "category": "Sales",
    "tool": "Muse",
    "toolUrl": "https://muse.ai/",
    "level": "Beginner",
    "evidence": "Editorial adaptation",
    "output": "A spreadsheet-ready account list with fit evidence, sources, and unsent outreach ideas.",
    "inputs": [
      "Your customer profile and exclusion criteria",
      "A small approved account list or research scope"
    ],
    "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.",
    "prompt": "For my small business, research [accounts or bounded search scope] against [customer profile]. Return company name, domain, relevant public facts, dated source URLs, and fit reasoning. Use unknown for missing details. Deduplicate records and separate factual evidence from an outreach hypothesis. Draft an optional short opener only for reviewed accounts. Do not guess private contact information or send messages.",
    "steps": [
      "Specify company-level criteria and excluded categories.",
      "Start with a small research batch that can be manually checked.",
      "Review source URLs and company identity before exporting results.",
      "Have the owner approve any outreach and separately verify contact details."
    ],
    "review": "Check company matches, source dates, fit reasoning, and every personalized claim before use.",
    "limits": [
      "The creator’s CSV report does not prove research completeness.",
      "Website access or third-party enrichment may require separate tools and subscriptions."
    ],
    "measure": "Verified fields, duplicate records, and reviewer-accepted account briefs.",
    "sources": [
      {
        "title": "Prospect research with Muse",
        "url": "https://x.com/smallchris/status/2098373287453601935",
        "author": "Chris Small",
        "note": "September 11, 2026. Reports account research, CSV enrichment, and outreach drafts. The public excerpt does not establish completeness or accuracy. This guide adapts the idea for a small-business owner; any reported outcome belongs to the original tool and source.",
        "kind": "Practitioner report"
      },
      {
        "title": "Introducing Muse",
        "url": "https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/",
        "author": "Meta",
        "note": "Official introduction of the personal agent. Connector access, account availability, and action permissions still need to be configured.",
        "kind": "Official documentation"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "supplier-comparison",
    "title": "Compare supplier quotes before you order",
    "description": "Put prices, lead times, minimum orders, and missing terms in one comparison.",
    "category": "Purchasing",
    "tool": "Muse",
    "toolUrl": "https://muse.ai/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A component sourcing table with exact part identifiers, supplier URLs, stock, quantity, cost and unresolved substitutions.",
    "inputs": [
      "Bill of materials with exact part identifiers and required quantities",
      "Approved suppliers, delivery destination, budget, and deadline"
    ],
    "connections": "User-provided bill of materials and approved supplier websites; procurement and payments require explicit approval.",
    "prompt": "For my small business, research [bill of materials] against [approved suppliers and requirements]. For each line, list exact manufacturer and part number, supplier URL, quantity available, unit and extended cost, shipping and tax assumptions, lead time, and return terms. Separate exact matches from proposed substitutes and flag unclear specifications. Reconcile quoted quantities to the original list. Do not create supplier accounts, disclose confidential design details, place orders, or make payments. Return a sourcing table and unresolved questions for approval.",
    "steps": [
      "Normalize part identifiers, specifications, and quantities in the bill of materials.",
      "Find exact supplier matches and record time-sensitive stock and prices.",
      "Compare landed cost assumptions, lead times, and any proposed substitutions.",
      "Have the project owner review compatibility and approve procurement separately."
    ],
    "review": "A technically qualified owner verifies component compatibility, authenticity, stock, quantities, and shipping constraints.",
    "limits": [
      "The visible X excerpt reports research and procurement across 14 suppliers but is truncated. Do not claim transaction verification details or achieved time savings without the full source. This is a personal report, not a reproduced test.",
      "The prompt, setup steps, and review criteria are editorial adaptations; this directory has not reproduced the reported outcome."
    ],
    "measure": "Exact matches sourced, uncertain substitutes identified, and missing or duplicated line items.",
    "sources": [
      {
        "title": "Compare suppliers for a hardware bill of materials — original X report",
        "url": "https://x.com/justinbojarski/status/2099630878993387556",
        "author": "Bojo.io",
        "note": "2026-09-14. Verified original author and public excerpt via X oEmbed on 2026-10-12. The visible X excerpt reports research and procurement across 14 suppliers but is truncated. Do not claim transaction verification details or achieved time savings without the full source. This is a personal report, not a reproduced test. Guide prompt and steps are editorial additions. This guide adapts the idea for a small-business owner; any reported outcome belongs to the original tool and source.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "business-expense-audit",
    "title": "Find questions worth asking in business expenses",
    "description": "Group recurring spend and flag anomalies without calling every expense waste.",
    "category": "Finance",
    "tool": "Grok Bot",
    "toolUrl": "https://grok.com/",
    "level": "Beginner",
    "evidence": "Editorial adaptation",
    "output": "An expense-review table with source rows, owner questions, and possible investigation areas.",
    "inputs": [
      "Redacted expense export for a defined period",
      "Known vendors, cost centers, and contract context"
    ],
    "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.",
    "prompt": "For my small business, review [expense export] for [period]. Preserve source row IDs and reconcile totals. Group vendors consistently, identify duplicate-looking charges, recurring commitments, unusual changes, and missing descriptions. Treat each as a question for the owner, not proof of waste or fraud. Do not change accounting records, cancel contracts, move money, or infer tax treatment. Return a discrepancy list and the reconciliation.",
    "steps": [
      "Choose a reporting period and remove unnecessary payment details.",
      "Reconcile the imported rows to the accounting export total.",
      "Review grouped vendors and exceptions with the relevant budget owners.",
      "Document confirmed findings and handle accounting changes through the normal approval process."
    ],
    "review": "Finance checks duplicate assumptions, currencies, refunds, timing differences, and contractual commitments.",
    "limits": [
      "Different transaction dates may represent legitimate installments.",
      "This is an investigation aid, not an audit opinion or tax classification."
    ],
    "measure": "Reconciled totals and exceptions confirmed or dismissed by owners.",
    "sources": [
      {
        "title": "Weekend bot wins supplied by the site owner",
        "url": null,
        "author": null,
        "note": "The pasted report mentions bill, shopping, subscription, expense, and travel tasks. Original author, date, and post URL are unverified; no savings are treated as established results. This guide adapts the idea for a small-business owner; any reported outcome belongs to the original tool and source.",
        "kind": "User-supplied report"
      },
      {
        "title": "Grok Bot overview",
        "url": "https://docs.x.ai/grok-bot/overview",
        "author": "xAI",
        "note": "Official overview of the bot environment, browser, files, connectors, and approvals. It does not validate the reported savings in the supplied anecdote.",
        "kind": "Official documentation"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "commitment-tracker",
    "title": "Track commitments across Slack, Notion, and email",
    "description": "A reviewable commitments register with owner, due date, source link, and completion evidence.",
    "category": "Operations",
    "tool": "Grok Bot",
    "toolUrl": "https://grok.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A reviewable commitments register with owner, due date, source link, and completion evidence.",
    "inputs": [
      "Selected Slack channels, Notion pages, and email date range",
      "Rules for what counts as a commitment and who owns each item"
    ],
    "connections": "Read access to explicitly selected Slack channels, email scope, and Notion pages. Notion writes require separate review and permission.",
    "prompt": "For my small business, review [approved message and task scope] for commitments I explicitly made during [date range]. Return a table with task, owner, stated deadline, original quote or source link, status, and evidence of completion. Distinguish promises from ideas or requests. Deduplicate repeated discussions. Mark unclear owners and dates as unknown. Do not message colleagues, assign work, or write to Notion yet; show the proposed changes for review.",
    "steps": [
      "Choose a narrow source scope and date range.",
      "Extract commitments with links to the original messages.",
      "Review uncertain wording, duplicates, owners, and deadlines.",
      "Approve any Notion updates separately and close items only when completion evidence exists."
    ],
    "review": "Check whether the user actually committed, whether the deadline was explicit, and whether a later message changes the obligation.",
    "limits": [
      "One practitioner report; no measured accuracy or time saved. A Notion integration is reported by this user, not verified as universally available.",
      "The prompt, setup steps, and review criteria are editorial adaptations; this directory has not reproduced the reported outcome."
    ],
    "measure": "Missed commitments, false task detections, duplicates, and unsupported completion marks.",
    "sources": [
      {
        "title": "Track commitments across Slack, Notion, and email — original X report",
        "url": "https://x.com/samlambert/status/2099584402045210992",
        "author": "Sam Lambert",
        "note": "2026-09-14. Verified original author and public excerpt via X oEmbed on 2026-10-12. One practitioner report; no measured accuracy or time saved. A Notion integration is reported by this user, not verified as universally available. Guide prompt and steps are editorial additions. This guide adapts the idea for a small-business owner; any reported outcome belongs to the original tool and source.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "subscription-review",
    "title": "Review recurring software and service costs",
    "description": "List business subscriptions, renewal dates, owners, and questions before deciding what to keep.",
    "category": "Finance",
    "tool": "Grok Bot",
    "toolUrl": "https://grok.com/",
    "level": "Beginner",
    "evidence": "Editorial adaptation",
    "output": "An inventory of possible subscriptions with evidence, renewal details, and an owner decision column.",
    "inputs": [
      "Redacted recent statements or approved billing exports",
      "Known subscriptions and services you want to keep"
    ],
    "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.",
    "prompt": "For my small business, review [billing exports] for possible subscriptions. Group repeated merchants, preserve source rows, and distinguish confirmed recurring charges from guesses. List amount, frequency, latest charge, known renewal date, and what needs checking. Create keep, investigate, and possible-cancel columns without making the decision for me. Do not log in, send cancellation requests, or change services without separate approval.",
    "steps": [
      "Use a small set of redacted statements and retain unchanged originals.",
      "Match recurring merchant patterns to actual service accounts.",
      "Check renewal, cancellation, refund, and business-dependency details.",
      "Decide service by service and verify any later cancellation confirmation."
    ],
    "review": "Confirm the service owner, renewal terms, shared users, and whether cancellation removes data or access.",
    "limits": [
      "Merchant names do not always identify the service correctly.",
      "A recurring charge can be necessary or shared; low usage is not proof it should be canceled."
    ],
    "measure": "Subscriptions correctly identified, uncertain charges resolved, and confirmed decisions.",
    "sources": [
      {
        "title": "Weekend bot wins supplied by the site owner",
        "url": null,
        "author": null,
        "note": "The pasted report mentions bill, shopping, subscription, expense, and travel tasks. Original author, date, and post URL are unverified; no savings are treated as established results. This guide adapts the idea for a small-business owner; any reported outcome belongs to the original tool and source.",
        "kind": "User-supplied report"
      },
      {
        "title": "Grok Bot overview",
        "url": "https://docs.x.ai/grok-bot/overview",
        "author": "xAI",
        "note": "Official overview of the bot environment, browser, files, connectors, and approvals. It does not validate the reported savings in the supplied anecdote.",
        "kind": "Official documentation"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "x-lead-discovery",
    "title": "Find people on X asking for what your product does",
    "description": "Review a short list of recent buying signals every four hours, with direct post links, fit reasons, and helpful reply drafts.",
    "category": "Sales",
    "tool": "Grok Bot",
    "toolUrl": "https://grok.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "reviewed": "2026-10-17",
    "output": "A ranked shortlist of posts from the last 24 hours, with author handles, intent labels, relevance scores, and reply drafts. Each report ends with “What needs my attention?” and up to three strongest opportunities.",
    "inputs": [
      "Product description, target customer profile, and clear exclusions",
      "Competitor names, customer problem phrases, and examples of relevant and irrelevant posts",
      "A persistent log of previously reported post IDs and handles, a report destination, and a timezone for the four-hour schedule"
    ],
    "connections": "Requires a configured Grok Bot environment with authorized X search access, a persistent deduplication log, and a report destination. Set up the recurring four-hour schedule separately after reviewing a manual sample. This directory does not schedule runs or connect your X account.",
    "prompt": "For my small business, act as a lead discovery agent for [PRODUCT].\nProduct description: [WHAT YOUR PRODUCT DOES]\nTarget customers: [WHO YOUR PRODUCT HELPS]\nCompetitors and exclusions: [COMPETITORS, GEOGRAPHY, AND EXCLUSIONS]\n\nFor each run of a separately configured four-hour schedule, search X for posts published within the last 24 hours. Record the run time and timezone. Focus on five types of posts:\n1. Requests for recommendations for products like mine.\n2. Complaints about problems my product solves.\n3. Frustration with competitors or requests for alternatives.\n4. Descriptions of workflows my product could improve.\n5. Explicit requests for help with something my product does.\n\nFor every relevant post, provide the original post text available to you and its direct link, the author's X handle, publication time, a specific fit reason tied to the product description, intent (actively looking, exploring alternatives, or expressing frustration), a relevance score from 1–10 with a one-line reason, and a suggested natural reply that helps the person. If no intent label fits, say unclear rather than forcing one. Reply drafts must make only supported product claims and must not imply that I am an unaffiliated customer.\n\nPrioritize explicit requests for a solution over general conversation. Use 8–10 for an explicit need and strong customer fit, 5–7 for a relevant problem with uncertain purchase intent, and 1–4 for weak fit; scores are judgment calls, not purchase probabilities. Exclude promotions, apparent bots, irrelevant mentions, and posts older than 24 hours. Bot detection is uncertain; flag ambiguous cases rather than claiming certainty. Never invent posts, links, user details, or quoted text. If the original cannot be verified, leave it out of the lead shortlist and note the access limitation.\n\nCheck [PERSISTENT REPORTED-LEAD LOG] before reporting. Do not repeat previously reported posts or leads. Group multiple posts from the same author into one opportunity. Record post IDs, handles, source times, and report times for leads included in a successfully delivered report. If the log cannot be read or written, disclose that and do not claim deduplication worked.\n\nKeep the report short, with a maximum of [10] new opportunities, highest intent first. A small or empty report is acceptable; do not pad it. End with “What needs my attention?” and highlight up to three most promising opportunities, or state that no qualifying new opportunities were found. Report incomplete searches or failed runs separately from zero matches.\n\nDo not reply, follow, DM, or otherwise contact anyone. I will review each opportunity and decide whether to respond.",
    "steps": [
      "Define your product, customer profile, exclusions, and search phrases for all five signal types; choose a small report limit.",
      "Run one manual search and check each post, timestamp, fit reason, and reply draft against the original context.",
      "Set up a persistent reported-lead log and confirm that a repeated sample run does not resend the same posts or people.",
      "Configure the four-hour schedule and report destination in your own environment. Review the report before any response and inspect failures or empty runs."
    ],
    "review": "Open each original post before acting. Check that the request is current, the product actually fits, and the draft offers useful help without unsupported claims or disguised affiliation. A relevance score does not prove buying intent. All replies, follows, and DMs remain manual decisions.",
    "limits": [
      "The excerpt’s author, original URL, and publication date are unverified. It describes an experiment and a suggested prompt, not measured lead or revenue results.",
      "X search coverage and account access can be incomplete. Freshness depends on checking post timestamps, not when a search engine indexed the page.",
      "A prompt alone does not create a scheduler or durable memory. Reliable deduplication requires a persistent log across runs.",
      "Intent scoring and bot detection are fallible. A complaint or workflow description is not necessarily a purchase request.",
      "X search is not assumed to be available in every agent. Provide verified post links or configure a supported search tool first."
    ],
    "measure": "New opportunities accepted after review, duplicate and stale-post rates, unsupported fit claims, and conversations that progress after a human chooses to respond.",
    "sources": [
      {
        "title": "X lead-discovery prompt — user-supplied excerpt",
        "url": null,
        "author": null,
        "kind": "User-supplied report",
        "note": "The supplied excerpt proposes four-hour X searches across five buying-signal types, a 24-hour freshness window, relevance scoring, deduplication, helpful reply drafts, and human review before any contact. The original author, URL, and date are not verified. This guide adapts the prompt and adds implementation checks; no conversion or revenue outcome has been established. This guide adapts the idea for a small-business owner; any reported outcome belongs to the original tool and source."
      }
    ]
  },
  {
    "id": "job-note-invoice-draft",
    "title": "Turn a job-site voice note into an invoice draft",
    "description": "Capture completed work while it is fresh, then check the customer, rates and totals before billing.",
    "category": "Finance",
    "tool": "AI by Zapier + accounting software",
    "toolUrl": "https://zapier.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "An invoice draft with a transcript, matched customer, itemized work and missing-information list.",
    "inputs": [
      "A voice note or transcript describing completed work",
      "Approved customer records, rate card and invoice template"
    ],
    "connections": "An approved recording or upload workflow plus an accounting connection. Begin with draft creation only; publishing invoices requires a separate approved action.",
    "prompt": "Turn [job note] into a draft invoice using [approved customer records, rates and template]. Extract the work date, customer, completed tasks, quantities and explicitly stated charges. Link each item to the transcript. Flag unclear customer matches and missing rates instead of guessing. Calculate totals from confirmed inputs and mark tax fields for review. Show the full draft for approval before creating records, sending an invoice or changing accounting data.",
    "steps": [
      "Record the completed work and retain the original note.",
      "Match the customer and service items against approved records.",
      "Prepare the invoice draft and highlight missing or ambiguous fields.",
      "Review the customer, quantities, rates and totals before approving any accounting write or delivery."
    ],
    "review": "The owner checks that billed work was completed, customer details are correct and the approved pricing applies.",
    "limits": [
      "A voice transcription may confuse quantities, names or dates.",
      "The cited implementation is a vendor-reported customer example; this adaptation has not been reproduced and does not promise the same outcome."
    ],
    "measure": "Drafts accepted without correction, missing fields resolved and duplicate invoices prevented.",
    "sources": [
      {
        "title": "How a small gardening business automates invoicing and expenses with AI",
        "url": "https://zapier.com/blog/how-danny-richman-automates-invoicing-expenses-with-ai/",
        "author": "Grace Miller / Zapier",
        "note": "The 2024 customer story describes Wee Beastie Gardens using recorded requests, transcription and Zoho Books. Our draft-first checks are editorial additions; older model and pricing details are not current setup instructions.",
        "kind": "Vendor example"
      },
      {
        "title": "Zapier Agents is now AI by Zapier",
        "url": "https://zapier.com/blog/zapier-agents-is-now-ai-by-zapier/",
        "author": "Ruchira Kulkarni / Zapier",
        "note": "October 6, 2026 product announcement establishes the current AI by Zapier naming and migration of agent capabilities into Zap steps.",
        "kind": "Official documentation"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "supplier-invoice-review",
    "title": "Check supplier invoices before they reach bookkeeping",
    "description": "Extract the important fields and flag duplicate-looking bills, missing references and mismatched totals.",
    "category": "Finance",
    "tool": "AI by Zapier + accounting software",
    "toolUrl": "https://zapier.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A source-linked invoice register and exception queue for a bookkeeper to review.",
    "inputs": [
      "A bounded batch of supplier invoices",
      "Approved vendor list and relevant purchase orders or receiving records"
    ],
    "connections": "Approved document uploads or an invoice mailbox, with a separately configured bookkeeping integration if reviewed entries will later be written.",
    "prompt": "Review [invoice batch] against [vendor list and purchase records]. Extract invoice ID, vendor, currency, dates, line items, tax as stated and total, retaining a reference to each source page. Flag possible duplicates, missing purchase references and arithmetic differences. Do not treat a similarity as proof of duplicate billing. Return a review table and exception queue. Ask for approval before writing accounting records, contacting vendors or initiating any payment.",
    "steps": [
      "Choose a reporting batch and retain unchanged invoice files.",
      "Extract fields with page references and reconcile each invoice total.",
      "Compare candidate duplicates and purchase references without deleting entries.",
      "Have the bookkeeper resolve exceptions and approve any later writeback."
    ],
    "review": "Check currencies, credit notes, installments and vendor identity before accepting an exception or posting a bill.",
    "limits": [
      "Scanned documents and inconsistent layouts can cause extraction errors.",
      "Matching an invoice to a purchase order does not prove goods were received or authorize payment."
    ],
    "measure": "Correctly extracted invoices, confirmed exceptions and bookkeeping corrections required.",
    "sources": [
      {
        "title": "Your guide to automating invoicing",
        "url": "https://zapier.com/blog/streamline-invoicing-with-zapier/",
        "author": "Zapier",
        "note": "Describes invoice extraction, routing and accounting connections. The specific duplicate checks and approval table here are our proposed workflow, not a measured customer result.",
        "kind": "Official documentation"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "support-answer-handoff",
    "title": "Answer routine customer questions with a clear handoff",
    "description": "Use approved answers for repeat questions and send uncertain cases to a named person.",
    "category": "Customer service",
    "tool": "Intercom Fin",
    "toolUrl": "https://www.intercom.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A tested support flow with answer sources, escalation rules and an owner for unresolved requests.",
    "inputs": [
      "Current approved FAQs, policies and service information",
      "Sample customer questions and the team's escalation contacts"
    ],
    "connections": "A configured Intercom workspace with the required Fin and workflow access. Other agents need their own support integration; this guide does not install one.",
    "prompt": "Design a support pilot from [approved content] and [sample questions]. For each question, draft a sourced answer or identify the information needed. Route policy exceptions, account-specific uncertainty and requests for a person to [support owner]. Include a concise handoff summary without unnecessary personal data. Test the flow privately and show all proposed configuration changes for approval before publishing it, replying to customers, issuing refunds or changing accounts.",
    "steps": [
      "Select a small set of supported topics and update their source material.",
      "Define the human handoff owner and the cases the agent must escalate.",
      "Preview answers and handoffs using ordinary, ambiguous and frustrated-customer examples.",
      "Approve a limited launch, then review actual unresolved conversations and correct the source material."
    ],
    "review": "Confirm that answers match current policy and that escalation reaches an available person with enough context.",
    "limits": [
      "A support agent can give a plausible answer from incomplete or stale material.",
      "Fin's documented handoff controls are product-specific and should not be assumed to exist in another agent."
    ],
    "measure": "Correct answers in the test set, successful handoffs and customer-reported unresolved cases.",
    "sources": [
      {
        "title": "Use Fin AI Agent in Workflows",
        "url": "https://www.intercom.com/help/en/articles/10032299-use-fin-ai-agent-in-workflows",
        "author": "Intercom",
        "note": "Documents workflow previews, follow-up and handover configuration. Our bounded pilot and evaluation checklist are editorial additions, not a claim of achieved resolution rates.",
        "kind": "Official documentation"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "customer-call-followup",
    "title": "Prepare the follow-up after a customer call",
    "description": "Turn the actual conversation into a reply draft, open questions and proposed CRM notes.",
    "category": "Sales",
    "tool": "ChatGPT Work",
    "toolUrl": "https://chatgpt.com/",
    "level": "Beginner",
    "evidence": "Editorial adaptation",
    "output": "A customer email draft and internal next-step list linked to the meeting record.",
    "inputs": [
      "An approved meeting transcript or contemporaneous notes",
      "Customer identity, existing proposal and relevant prior commitments"
    ],
    "connections": "Uploaded notes can support the first pass. Reading live Zoom, email or CRM context requires each supported connection and its permissions.",
    "prompt": "Use [meeting record] and [approved account context] to prepare a follow-up for [customer]. Separate agreed scope from proposals, identify open questions, and list explicit owners and dates without inventing either. Draft a short customer email and separate internal CRM notes. Preserve references to the supporting transcript or notes. Keep internal concerns out of the customer draft. Show both for approval before sending messages, creating tasks or updating any record.",
    "steps": [
      "Choose the exact customer meeting and relevant account context.",
      "Extract agreements, unresolved questions and stated next steps.",
      "Draft a customer reply separately from internal notes.",
      "Check the record and approve each intended message or system update."
    ],
    "review": "Verify names, commitments, dates and any price or scope mentioned in the reply.",
    "limits": [
      "Transcripts can omit context or misidentify speakers.",
      "A suggested next step is not a commitment accepted by the customer."
    ],
    "measure": "Follow-ups reviewed, commitments correctly captured and corrections needed before sending.",
    "sources": [
      {
        "title": "Turn meetings into follow-ups",
        "url": "https://learn.chatgpt.com/use-cases/zoom-meeting-follow-ups",
        "author": "OpenAI",
        "note": "Official ChatGPT workflow covers transcript-based email drafts, account plans and proposed CRM updates. This service-business version and its prompt are original adaptations.",
        "kind": "Official documentation"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "weekly-owner-report",
    "title": "Explain this week's sales and operating changes",
    "description": "Give the owner a short report with reconciled numbers, changes worth reviewing and unanswered questions.",
    "category": "Finance",
    "tool": "ChatGPT Work",
    "toolUrl": "https://chatgpt.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A one-page operating report with a source table and review questions.",
    "inputs": [
      "Sales, cost and operating exports for comparable periods",
      "Metric definitions, targets and owner notes explaining known events"
    ],
    "connections": "Start with approved files. Live refreshes require separately connected data sources and a confirmed schedule.",
    "prompt": "Prepare a weekly owner report from [approved exports] using [metric definitions]. Reconcile source totals before comparing periods. Show the few material changes in sales, costs and operations, with a source reference for every number. Separate explanations supported by owner notes from hypotheses to investigate. List missing data and inconsistent definitions. Return a draft and supporting calculations; ask for approval before sharing the report, editing source records or creating a recurring update.",
    "steps": [
      "Choose comparable reporting periods and agree on metric definitions.",
      "Reconcile imported totals and identify missing or inconsistent fields.",
      "Draft the material changes with source references and clearly labeled hypotheses.",
      "Have the owner verify the calculations and approve distribution or a recurring schedule."
    ],
    "review": "Check period cutoffs, refunds, accrual versus cash figures and whether an apparent change comes from a data-definition change.",
    "limits": [
      "A weekly change may be seasonal or caused by incomplete data.",
      "An agent-generated explanation is not proof of causation or a reliable forecast."
    ],
    "measure": "Figures reconciled, unsupported explanations removed and decisions informed by verified changes.",
    "sources": [
      {
        "title": "Prepare a business review",
        "url": "https://learn.chatgpt.com/use-cases/monthly-business-review-narrative",
        "author": "OpenAI",
        "note": "Describes preparing source-backed business reviews from workbooks, KPI definitions and owner notes. This smaller weekly owner report is an editorial adaptation, not a tested performance claim.",
        "kind": "Official documentation"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "morning-owner-brief",
    "title": "Start the day with the customer work that needs attention",
    "description": "Bring deadlines, unanswered customer messages and today's appointments into one short briefing.",
    "category": "Operations",
    "tool": "ChatGPT Work",
    "toolUrl": "https://chatgpt.com/",
    "level": "Beginner",
    "evidence": "Editorial adaptation",
    "output": "A dated priority list with source links, missing context and optional reply drafts.",
    "inputs": [
      "Approved inbox, calendar and job-tracker sources",
      "Business hours, priority rules and escalation preferences"
    ],
    "connections": "Connect the specific supported email, calendar and tracker tools needed. A schedule is active only after it has been saved and confirmed.",
    "prompt": "Review [approved sources] for today's customer work in [time zone]. Return no more than five items needing attention: appointments to prepare for, customer replies, deadlines at risk and decisions waiting on me. Check latest replies so resolved work is not repeated. Link each item to evidence and name unavailable sources. Draft replies where helpful, but ask for approval before sending, changing appointments or updating jobs. Propose a recurring schedule only after this first brief is reviewed.",
    "steps": [
      "Choose the exact sources and define which issues deserve attention.",
      "Prepare one briefing using a bounded date range.",
      "Review missing sources, duplicate items and priority judgments.",
      "Approve a schedule and notification rules after the trial brief is useful."
    ],
    "review": "Confirm the brief reflects the latest replies and does not treat tentative appointments as confirmed work.",
    "limits": [
      "Disconnected tools and private threads can leave gaps in the briefing.",
      "A reminder does not complete the underlying task or guarantee a deadline will be met."
    ],
    "measure": "Relevant items surfaced, resolved items wrongly repeated and missed commitments found in review.",
    "sources": [
      {
        "title": "Set up a work chief of staff",
        "url": "https://learn.chatgpt.com/use-cases/daily-work-brief",
        "author": "OpenAI",
        "note": "Official workflow describes recurring cross-tool briefings and draft replies. Our customer-work focus and five-item limit are editorial choices; no time savings are claimed.",
        "kind": "Official documentation"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "after-hours-phone-intake",
    "title": "Capture after-hours callers and prepare the morning callback list",
    "description": "Give a caller a clear next step when the shop is closed, then pass the request to the right person.",
    "category": "Customer service",
    "tool": "AI phone agent + Quo",
    "toolUrl": "https://www.quo.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A tested call-intake script, escalation rules and a callback list with the caller’s stated request.",
    "inputs": [
      "Business hours, service area, approved FAQs and callback policy",
      "Examples of common calls, staff handoff contacts and the information needed to return a call"
    ],
    "connections": "A phone service that supports the intended AI answering flow, with routing configured separately. Start with test calls; an ordinary chat prompt does not answer the shop phone.",
    "prompt": "Design an after-hours intake pilot for [business] using [hours, service area and approved answers]. Greet callers as an automated assistant, explain when a person will return their call, and collect only [required callback fields]. Confirm the callback number and summarize the request in the caller's words. Give answers only from the approved material. For urgency, uncertainty or a request for a person, follow [handoff policy]; do not invent an available appointment, diagnosis or price. Produce a call-flow draft, a callback-list format and ten test conversations including interruptions, unclear addresses and out-of-area requests. Show configuration changes for review before activating call routing.",
    "steps": [
      "List the questions the assistant may answer and the requests a person must handle.",
      "Write the intake flow and decide where unanswered calls and failed handoffs should go.",
      "Run test calls from a separate phone; compare the captured details with what the caller actually said.",
      "Have the shop manager approve routing, callback ownership and a limited after-hours trial.",
      "Review every trial conversation and callback outcome before expanding coverage."
    ],
    "review": "Check phone numbers, the promised callback window, emergency handling and whether the person responsible can see the request.",
    "limits": [
      "Speech recognition can miss names, numbers and background speech; a transcript alone is not a verified booking.",
      "Phone routing, recording settings and handoff behavior depend on the selected service and account setup."
    ],
    "measure": "Calls with usable callback details, missed handoffs, incorrect answers and callbacks completed within the stated window.",
    "sources": [
      {
        "title": "Capture after-hours callers and prepare the morning callback list — original X example",
        "url": "https://x.com/ryanmchenoweth/status/2097802727514677663",
        "author": "@ryanmchenoweth",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The supplied source describes an auto repair shop using AI to answer after-hours calls on Quo/OpenPhone. It does not establish call accuracy or recovered revenue. The prompt, setup and checks are original editorial additions. The directory has not reproduced the reported deployment or results.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "service-quote-first-draft",
    "title": "Draft a service quote from a complete job request",
    "description": "Turn the request and your price book into a quote the owner can check before sending.",
    "category": "Sales",
    "tool": "Claude",
    "toolUrl": "https://claude.ai/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A quote draft with priced line items, source references, assumptions and unanswered scope questions.",
    "inputs": [
      "Customer request, site notes, measurements and photos where useful",
      "Current price book, minimum charges, exclusions and examples of accepted quotes"
    ],
    "connections": "Approved files or pasted job details are enough for a first draft. Sending a quote or writing to estimating software requires a separately configured connection.",
    "prompt": "Prepare a quote draft for [job request] using only [approved price book and scope rules]. Itemize quantity, unit, rate, subtotal and the source of each rate. Check arithmetic and minimum charges. Separate customer-provided measurements from estimates. Put missing scope, site-access constraints and ambiguous quantities in a questions section instead of making them up. Mark items needing an estimator's decision. Include stated exclusions and the quote-validity rule from the supplied policy. Return the draft and a source table; do not send it, discount it, promise a start date or accept a contract.",
    "steps": [
      "Define the minimum information needed to price a job and request any missing measurements.",
      "Provide the current price book and one representative approved quote.",
      "Generate the draft and reconcile quantities, rates, minimums and totals.",
      "Have the estimator resolve uncertain scope and approve the final price.",
      "Send through the normal quoting process and record when the customer received it."
    ],
    "review": "Check site conditions, quantities, rate validity, exclusions, taxes as specified by the business and any proposed work date.",
    "limits": [
      "A faster quote may help response time, but it does not prove AI caused a sale.",
      "Photos and descriptions may omit work that needs an on-site inspection."
    ],
    "measure": "Time from a complete request to an approved quote, pricing corrections and quote outcomes tracked separately.",
    "sources": [
      {
        "title": "Draft a service quote from a complete job request — original X example",
        "url": "https://x.com/JaredDHardin/status/2108211608996741266",
        "author": "@JaredDHardin",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The author reports already drafting quotes with Claude, with substantial supervision. He says more than half of converted quotes were sent within 48 hours, not that more than half were AI-drafted. Feeding a recorded site walkthrough into AI is a proposed next step. The quote-checking workflow here is an editorial adaptation, not a reproduced performance result.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "field-text-job-cards",
    "title": "Turn crew messages into draft job cards",
    "description": "Keep completed work, equipment issues and follow-up questions attached to the right job.",
    "category": "Operations",
    "tool": "Grok Bot",
    "toolUrl": "https://grok.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "Draft job-card updates and an exception list, each linked to the crew message that supports it.",
    "inputs": [
      "A bounded set of field messages and the current job register",
      "Job identifiers, status definitions and equipment escalation contacts"
    ],
    "connections": "Use exported or pasted crew messages for the pilot. Live message access and writes to the job tracker require separate permissions and setup.",
    "prompt": "Review [crew-message batch] against [job register] for [date]. Match each message to an existing job only when the identifier or location is unambiguous. Propose job-card updates for work stated as completed, materials used, next steps and equipment issues. Preserve message time and source reference. Keep reported completion separate from supervisor acceptance. Flag conflicting updates, unknown jobs and missing quantities for review. Put equipment faults in a separate queue for [responsible person]. Do not infer payment status from field chatter or assign a new job without approval. Return proposed changes before writing records or notifying anyone.",
    "steps": [
      "Give each active job a consistent ID and define what each status means.",
      "Import a single day of messages while retaining the originals.",
      "Generate proposed job-card changes and inspect unmatched or contradictory messages.",
      "Ask the supervisor to confirm completion and route equipment issues.",
      "Apply approved updates, recording the source message and reviewer."
    ],
    "review": "Confirm job identity, actual completion, quantities and whether an equipment issue affects safe operation.",
    "limits": [
      "Crew shorthand, reused addresses and delayed messages can attach work to the wrong job.",
      "A text mentioning an invoice is not evidence of the current accounts-receivable balance."
    ],
    "measure": "Correct job matches, supervisor corrections, unresolved messages and equipment issues reaching the assigned owner.",
    "sources": [
      {
        "title": "Turn crew messages into draft job cards — original X example",
        "url": "https://x.com/TherealWitty22/status/2103699084221747308",
        "author": "@TherealWitty22",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The source describes a ground-spraying business using Grok Bot with crew texts and daily reporting. The draft-only job-card process here narrows that reported workflow. The prompt, setup and checks are original editorial additions. The directory has not reproduced the reported deployment or results.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "vendor-credit-reconciliation",
    "title": "Find supplier credits that have not been applied",
    "description": "Match returns and credit notes to supplier statements, then prepare questions for the vendor.",
    "category": "Finance",
    "tool": "AI assistant (source does not name tool)",
    "toolUrl": null,
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A reconciliation of expected credits, applied credits and unresolved differences with document references.",
    "inputs": [
      "Supplier invoices, credit notes, return authorizations and statements for the same period",
      "Vendor account identifiers and the business’s record of returns or disputed charges"
    ],
    "connections": "Begin with document exports. Supplier portals, accounting writes and outbound vendor messages need separate access and approval.",
    "prompt": "Reconcile supplier credits for [vendor/account] over [period]. Extract invoice, return and credit-note identifiers, dates, currencies and amounts with source-page references. Match credits to invoices only when identifiers or other evidence support the match. Separate issued credits, credits visible on statements, returns awaiting a credit note and uncertain matches. Check statement cutoffs and partial credits. Reconcile the totals without treating every difference as money owed. Draft a short vendor question for each unresolved item, including the supporting references. Do not post an accounting adjustment, claim a refund is due or send the inquiry.",
    "steps": [
      "Gather the statement and supporting documents for one supplier and one period.",
      "Extract identifiers and amounts, preserving original files and page references.",
      "Match issued credits to statements and isolate partial or uncertain matches.",
      "Have the bookkeeper inspect cutoff dates and confirm unresolved discrepancies.",
      "Approve vendor inquiries and record each resolution in the reconciliation."
    ],
    "review": "Check account identity, tax and currency treatment, partial returns and whether a credit appears on a later statement.",
    "limits": [
      "An approved return does not always mean the supplier has issued a credit.",
      "A missing match may reflect posting delays or incomplete documents rather than an unapplied credit."
    ],
    "measure": "Credits reconciled, confirmed unresolved amounts, false exceptions and time required to close each inquiry.",
    "sources": [
      {
        "title": "Find supplier credits that have not been applied — original X example",
        "url": "https://x.com/ryanmchenoweth/status/2097439081579848064",
        "author": "@ryanmchenoweth",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The source reports an auto repair shop finding unapplied vendor credits with AI. Any dollar amount in that report is a practitioner claim, not a projected saving for this workflow. The prompt, setup and checks are original editorial additions. The directory has not reproduced the reported deployment or results.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "product-catalog-cleanup",
    "title": "Prepare product listings and catch catalog inconsistencies",
    "description": "Create a review sheet for missing descriptions, inconsistent variants and unsupported product claims.",
    "category": "Marketing",
    "tool": "Claude",
    "toolUrl": "https://claude.ai/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A proposed catalog-change sheet with source-backed descriptions and a separate list of missing product facts.",
    "inputs": [
      "A small catalog export with stable product and variant IDs",
      "Supplier specifications, approved product photos, category rules and brand-writing examples"
    ],
    "connections": "CSV exports and approved images can support the first pass. A live storefront connection and publication process must be configured separately.",
    "prompt": "Review [catalog batch] using [approved specifications, photos and category rules]. Preserve every product and variant ID. Flag duplicate-looking records, missing fields, inconsistent units and category mismatches. Draft concise descriptions using only supported attributes; do not infer materials, compatibility, certifications or included accessories from a photo. Keep suggested edits separate from unchanged fields. For every edit provide old value, proposed value, supporting source and reason. Use unknown when a fact is missing. Return an import-ready draft plus questions; do not change prices, remove branding or publish listings.",
    "steps": [
      "Export a small product batch and save the unmodified file.",
      "Specify required fields, category rules and facts that need a supplier source.",
      "Generate the change sheet and check variant relationships and product IDs.",
      "Have a merchandiser verify claims and approve individual changes.",
      "Test the approved import on a small batch and inspect the storefront before expanding."
    ],
    "review": "Check variant mappings, measurements, product claims, accessibility text and whether descriptions match the actual item.",
    "limits": [
      "A product image rarely establishes exact material, size or compatibility.",
      "Storefront imports may overwrite fields or variant relationships if identifiers are wrong."
    ],
    "measure": "Accepted edits, unsupported claims removed, variant errors and missing fields resolved.",
    "sources": [
      {
        "title": "Prepare product listings and catch catalog inconsistencies — original X example",
        "url": "https://x.com/DavisPaipa/status/2079551762877292880",
        "author": "@DavisPaipa",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The post describes Shopify merchant tasks with Claude and also promotes Shoptank and Libautech products. Treat it as a promotional practitioner example, not a neutral comparison or proof of ranking gains. The export-and-review process, prompt and checks here are original editorial additions; no built-in Shopify connection is promised.",
        "kind": "Promotional practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "content-performance-review",
    "title": "Review which posts brought useful attention",
    "description": "Compare your own posts against a defined goal and choose a small experiment for next week.",
    "category": "Marketing",
    "tool": "Claude",
    "toolUrl": "https://claude.ai/",
    "level": "Beginner",
    "evidence": "Editorial adaptation",
    "output": "A weekly content review with checked metrics, format comparisons and one or two proposed experiments.",
    "inputs": [
      "Platform analytics export with post IDs, dates and comparable observation windows",
      "The goal for each campaign, posting calendar and any tracked leads or purchases"
    ],
    "connections": "Upload a platform export for the first review. Recurring collection requires supported analytics access and a saved schedule; the prompt alone does not activate either.",
    "prompt": "Review [content analytics] for [period] against [campaign goals]. Verify what each metric means and keep posts with different observation windows separate. Identify the strongest and weakest posts by the relevant metric, not by likes alone. Show denominators for rates and flag missing data or small samples. Distinguish reach, engagement, profile visits and attributable inquiries. Suggest at most two changes to test next week with a clear comparison and success measure. Do not claim a format caused sales without attribution evidence or publish new content. Return the calculations, source post IDs and a short recommendation.",
    "steps": [
      "Choose one business goal and export the metrics relevant to it.",
      "Check metric definitions, post age, paid promotion and missing rows.",
      "Compare similar posts and inspect the underlying content before interpreting a pattern.",
      "Select a small test with a defined metric and comparable review window.",
      "Review the next period and keep conclusions proportionate to the sample."
    ],
    "review": "Check rate calculations, paid versus organic distribution, observation windows and whether inquiries can actually be traced to a post.",
    "limits": [
      "A successful post may reflect timing or audience distribution rather than its format.",
      "Platform analytics may not connect an interaction to a sale outside the platform."
    ],
    "measure": "Correctly calculated metrics, experiments completed and relevant inquiries where attribution is available.",
    "sources": [
      {
        "title": "Review which posts brought useful attention — original X example",
        "url": "https://x.com/ashrodriguezugc/status/2105663260426998245",
        "author": "@ashrodriguezugc",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The author describes a recurring Instagram-insights review using what she calls Claude Coworker. The retrieved text is truncated and refers to a video; it does not provide the complete setup or establish measured growth. The prompt, calculations and evaluation steps here are original editorial additions.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "loyalty-program-prototype",
    "title": "Write and test the rules for a customer loyalty program",
    "description": "Define earning, redemption and exception rules before building a custom rewards app.",
    "category": "Operations",
    "tool": "Google Antigravity + Claude",
    "toolUrl": null,
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A loyalty-program specification, sample customer journeys and a prototype tested with fictional accounts.",
    "inputs": [
      "Reward economics, eligible purchases, expiration policy and redemption rules",
      "Existing checkout process, staff roles and examples of returns or mistaken stamps"
    ],
    "connections": "Begin with a local prototype and synthetic customer records. Wallet passes, checkout integrations and customer messaging each require separate service setup.",
    "prompt": "Help specify a loyalty program for [business] using [approved rules]. Define how customers earn and redeem rewards, how refunds affect balances, who can correct a mistake and how every balance change is recorded. Calculate the reward cost from the provided margins without inventing missing costs. Design minimal data fields and staff permissions. Create test cases for duplicate purchases, repeat scans, refunds, lost access and concurrent redemptions. Build only a prototype with fictional accounts. Treat Apple Wallet or point-of-sale support as integration requirements to validate, not completed features. Return the specification, test results and unresolved decisions before any production launch.",
    "steps": [
      "Agree on reward rules and calculate their cost using real product margins.",
      "Map the checkout and redemption steps for customers and staff.",
      "Create a prototype using fictional accounts and a transaction history.",
      "Test duplicate scans, mistaken credits, returns and simultaneous redemptions.",
      "Have the owner approve the rules and validate payment or wallet integrations before handling real customers."
    ],
    "review": "Confirm reward economics, permissions, duplicate protection, balance history and a workable correction process.",
    "limits": [
      "A working demo does not establish that wallet or checkout integrations are production-ready.",
      "Rewards can create unexpected costs if stacking, refunds or repeat redemptions have not been specified."
    ],
    "measure": "Test cases passed, incorrect balances found, time to redeem and reward cost per eligible purchase.",
    "sources": [
      {
        "title": "Write and test the rules for a customer loyalty program — original X example",
        "url": "https://x.com/canoCloudX/status/2012467590107467884",
        "author": "@canoCloudX",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The author reports building a coffee-shop loyalty app using Google Antigravity and Claude Opus 4.5, including Apple Wallet and gifting features. These integrations are practitioner claims, not independently tested capabilities. This guide proposes a specification and prototype. The prompt, setup and checks are original editorial additions; the directory has not reproduced the deployment.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "monthly-bookkeeper-handoff",
    "title": "Prepare a monthly document pack for your bookkeeper",
    "description": "Collect the statements, receipts and unresolved questions before month-end review.",
    "category": "Finance",
    "tool": "Grok Bot",
    "toolUrl": "https://grok.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A document index, reconciled intake checklist and draft bookkeeper email with unresolved items.",
    "inputs": [
      "Statements and receipt files for a specified month and business entity",
      "The bookkeeper’s required document checklist and approved category definitions"
    ],
    "connections": "Start with downloaded files and selected deposit emails. Live email or bank access is optional and must be configured separately; no payment access is needed.",
    "prompt": "Prepare the [month] handoff for [business entity] using [approved files] and [bookkeeper checklist]. Index each document by source filename, account, date range and currency. Identify missing statement periods and duplicate-looking receipts without deleting anything. Match receipts to transactions when evidence supports it and mark uncertain matches. Keep transfers, refunds and deposits distinct; do not call every deposit revenue. Summarize unresolved questions and draft a short email to the bookkeeper. Do not decide tax deductibility, change accounting records or send the email. Return the document index and reconciliation for review.",
    "steps": [
      "Confirm entity, month, accounts and the bookkeeper’s required files.",
      "Collect unchanged source documents and create a consistent document index.",
      "Match receipts where possible and list missing documents or uncertain transactions.",
      "Have the owner review the pack for completeness and unnecessary personal information.",
      "Send the approved pack through the bookkeeper’s normal channel and retain the resolved questions."
    ],
    "review": "Check period coverage, transfers between accounts, currencies, duplicate files and every total against the statements.",
    "limits": [
      "An assistant cannot establish tax deductibility from a merchant name or receipt alone.",
      "Email notifications may omit transactions or differ from the final posted amount."
    ],
    "measure": "Missing documents found before handoff, reconciliation differences and follow-up requests from the bookkeeper.",
    "sources": [
      {
        "title": "Prepare a monthly document pack for your bookkeeper — original X example",
        "url": "https://x.com/RICOSAIZ1/status/2104409270557012141",
        "author": "@RICOSAIZ1",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The source reports Grok Bot gathering receipts and statements and preparing a bookkeeper email. Tax suggestions in the source are not adopted here; classification decisions remain with the bookkeeper. The prompt, setup and checks are original editorial additions. The directory has not reproduced the reported deployment or results.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "staff-roster-draft",
    "title": "Draft a staff roster that respects availability and coverage",
    "description": "Compare a proposed schedule with the shifts, skills and constraints the manager provides.",
    "category": "Operations",
    "tool": "ChatGPT Work",
    "toolUrl": "https://chatgpt.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A draft roster, coverage checks and an exception list for the manager to resolve.",
    "inputs": [
      "Staff availability, approved time off and role or skill requirements",
      "Opening hours, demand estimates, shift rules and manager-provided scheduling constraints"
    ],
    "connections": "A spreadsheet is enough for a trial roster. Calendar writes, payroll exports and staff notifications need separate configuration and approval.",
    "prompt": "Draft [week] staffing for [business] from [availability and coverage requirements]. Use only the constraints provided by the manager, including role coverage, approved time off, maximum hours and breaks. Do not infer availability or preferences. Show each person's proposed hours and any uncovered interval. If constraints conflict, explain the conflict and present options rather than silently breaking a rule. Keep demand assumptions visible and separate from confirmed bookings. Return the roster, constraint checks and questions. Do not publish shifts, contact staff or change payroll records.",
    "steps": [
      "Collect current availability and write down coverage and shift constraints.",
      "Create a first roster from the supplied data and calculate hours per person.",
      "Check each interval for role coverage, availability conflicts and uncovered work.",
      "Have the manager resolve exceptions and review the distribution of shifts.",
      "Publish the approved roster through the usual system and track subsequent corrections."
    ],
    "review": "Confirm availability, local scheduling requirements supplied by the manager, required skills and any last-minute changes.",
    "limits": [
      "A schedule is only as current as the availability and coverage assumptions provided.",
      "The assistant does not determine employment rules; the manager must supply the applicable constraints."
    ],
    "measure": "Coverage gaps, rule violations caught before publication, changes after publication and manager review time.",
    "sources": [
      {
        "title": "Draft a staff roster that respects availability and coverage — original X example",
        "url": "https://x.com/tuanle6618/status/2079424730696929289",
        "author": "@tuanle6618",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The supplied coffee-shop example mentions ChatGPT Work for scheduling, waste tracking and staff training. It does not isolate the effect of scheduling or establish savings for this guide. The prompt, setup and checks are original editorial additions. The directory has not reproduced the reported deployment or results.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "coffee-shop-waste-review",
    "title": "Find repeat patterns in a shop’s waste log",
    "description": "Compare prep, sales and discarded stock before changing how much the team makes.",
    "category": "Operations",
    "tool": "ChatGPT Work",
    "toolUrl": "https://chatgpt.com/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A waste-review table with unit checks, recurring patterns and a small proposed prep experiment.",
    "inputs": [
      "Dated prep, sales and waste records with item identifiers and units",
      "Recipe yields, stock adjustments, opening hours and known events affecting demand"
    ],
    "connections": "Use spreadsheet exports for the first review. POS and stock-system connections require separate setup; this workflow does not change ordering automatically.",
    "prompt": "Review [prep, sales and waste logs] for [period]. Normalize units only where a conversion is supplied, retaining original values. Reconcile opening stock, production, sales, adjustments and closing stock where the records allow it. Separate recorded waste from unexplained differences. Compare like weekdays and note events, closures or stockouts. Identify repeated excess preparation and propose one bounded change to test, including service-level and waste measures. Do not infer food safety from the logs, recommend reusing unsafe items or change purchase orders. Return calculations, source rows and missing-data questions.",
    "steps": [
      "Choose a small set of high-waste items and define the units for each.",
      "Reconcile prep, sales, stock adjustments and discarded quantities.",
      "Review recurring patterns while separating event days and stockouts.",
      "Have the manager approve a limited prep change and retain existing food-handling rules.",
      "Compare waste and availability during the trial before changing the standard quantities."
    ],
    "review": "Check unit conversions, recipe yields, staff meals, transfers and whether a stockout suppressed recorded sales.",
    "limits": [
      "Missing waste entries can make unexplained losses look like ordinary demand.",
      "Historical averages alone do not predict a special event or establish safe food handling."
    ],
    "measure": "Recorded waste per item, unexplained inventory differences and stockouts during the trial.",
    "sources": [
      {
        "title": "Find repeat patterns in a shop’s waste log — original X example",
        "url": "https://x.com/tuanle6618/status/2079424730696929289",
        "author": "@tuanle6618",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The supplied coffee-shop report includes waste tracking alongside other ChatGPT Work tasks. This guide separates the waste review into its own proposed pilot and makes no time-saving claim. The prompt, setup and checks are original editorial additions. The directory has not reproduced the reported deployment or results.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "small-business-crm-prototype",
    "title": "Prototype a CRM around the way your business actually tracks work",
    "description": "Test the records and handoffs you need before replacing the system your team relies on.",
    "category": "Operations",
    "tool": "Claude Code",
    "toolUrl": "https://claude.com/product/claude-code",
    "level": "Advanced",
    "evidence": "Editorial adaptation",
    "output": "A CRM specification, a prototype using fictional records and a migration checklist with tested exports.",
    "inputs": [
      "Current CRM fields, workflow stages, reports and pain points",
      "Staff roles, integrations, record volumes and backup or retention requirements"
    ],
    "connections": "Develop in an isolated environment with synthetic records. Production hosting, identity, email, backups and data migration must be implemented and tested separately.",
    "prompt": "Design a small CRM prototype for [business workflow] using [current field definitions and stages]. First map contacts, companies, jobs or deals and the relationships between them. Preserve stable identifiers. Specify required fields, allowed stage changes, role permissions, activity history, import/export and backup recovery. Build the smallest prototype that supports [one workflow] using fictional records. Test duplicate imports, missing fields, unauthorized changes and restore from backup. List integration gaps and ongoing maintenance work. Do not migrate live customer data, replace the current CRM or claim the prototype is production-ready.",
    "steps": [
      "Map one complete workflow and identify which current CRM features it depends on.",
      "Define the data model, roles, activity history and import/export behavior.",
      "Build a small prototype with fictional records and test normal and failed updates.",
      "Test backup restoration and export readability before considering migration.",
      "Have the owner review maintenance responsibilities and run a limited parallel trial before replacing anything."
    ],
    "review": "Confirm access controls, record relationships, history, backups, restoration and the integrations the team uses every day.",
    "limits": [
      "Generating an app quickly does not remove security, hosting or maintenance work.",
      "A custom CRM may cost more to maintain than the subscription it replaces."
    ],
    "measure": "Workflow tasks completed correctly, failed permission checks, export completeness and successful restore tests.",
    "sources": [
      {
        "title": "Prototype a CRM around the way your business actually tracks work — original X example",
        "url": "https://x.com/ryanflorence/status/2078472215604129920",
        "author": "@ryanflorence",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The source is a second-hand account of a small-business owner building a CRM with Claude Code. It does not verify reliability, operating cost or suitability for another business. The prompt, setup and checks are original editorial additions. The directory has not reproduced the reported deployment or results.",
        "kind": "Second-hand report"
      }
    ],
    "reviewed": "2026-10-17"
  },
  {
    "id": "order-history-bundle-ideas",
    "title": "Find product bundles worth testing from order history",
    "description": "Separate products customers already buy together from combinations that only sound appealing.",
    "category": "Sales",
    "tool": "Claude-based custom workflow",
    "toolUrl": "https://claude.ai/",
    "level": "Intermediate",
    "evidence": "Editorial adaptation",
    "output": "A ranked list of bundle candidates with co-purchase counts, margin assumptions and a proposed small test.",
    "inputs": [
      "Order-line export with order IDs, product IDs, quantities, refunds and dates",
      "Product costs, inventory, shipping constraints and current bundle or promotion rules"
    ],
    "connections": "Start with a store export. A custom agent or scheduled Slack report requires separately built integrations; this guide does not install the reported SDK workflow.",
    "prompt": "Analyze [order-line export] for bundle ideas over [period]. Deduplicate orders, account for refunds and distinguish repeat units from distinct products. Count how often each candidate pair appears together and show both the count and its share of relevant orders. Flag small samples, existing promotions and unavailable stock. Estimate contribution only from supplied costs, clearly listing missing shipping or fee assumptions. Propose a small bundle test with an inventory limit and comparison metric. Do not present a forecast as guaranteed revenue, create a discount or publish a product. Return the supporting calculations and a decision sheet.",
    "steps": [
      "Export a defined period of orders and reconcile orders, refunds and line counts.",
      "Calculate co-purchase patterns and remove candidates driven by data errors or existing bundles.",
      "Check stock, margins, shipping and operational fit for a short list.",
      "Have the owner approve one limited offer and its measurement plan.",
      "Compare contribution and purchase behavior during the test before expanding it."
    ],
    "review": "Check whether an apparent pairing is common enough to matter and whether the offer still contributes profit after all known costs.",
    "limits": [
      "Products purchased together historically may not sell better as a discounted bundle.",
      "Small samples and prior promotions can produce misleading recommendations or revenue projections."
    ],
    "measure": "Candidate pairs with sufficient evidence, test contribution margin, stockouts and incremental performance against the chosen comparison.",
    "sources": [
      {
        "title": "Find product bundles worth testing from order history — original X example",
        "url": "https://x.com/victorpaycro/status/1975522228474180090",
        "author": "@victorpaycro",
        "note": "Source post and author checked through X public oEmbed on October 17, 2026. The supplied source describes a Claude SDK workflow producing Shopify bundle recommendations and reports. Revenue projections in that report are not validated results; this guide requires a measured trial. The prompt, setup and checks are original editorial additions. The directory has not reproduced the reported deployment or results.",
        "kind": "Practitioner report"
      }
    ],
    "reviewed": "2026-10-17"
  }
]