AI Workflows for Small Business: 12 Templates a One-Person Business Can Actually Use
AI workflows for small business are most useful when they turn repeatable work into a clear process: gather the right inputs, paste a specific prompt, review the output, and turn it into a real business action.
That is what Jivaro’s AI Workflow Library for One-Person Businesses is for. It is a free workflow pack for solo founders, freelancers, consultants, creators, coaches, independent service providers, tiny online shops, and one-person agencies that need practical AI prompts instead of another generic AI productivity list.
Free download: get the workflow pack directly from Jivaro. This link goes directly to the free ZIP file.
Use these as reviewed workflows, not autopilot. AI can draft, summarize, organize, clean up, and check work. It should not replace your final judgment, customer policy, legal advice, accounting advice, medical advice, hiring decisions, or business accountability.
Quick answer: what is inside the AI Workflow Library?
The free AI Workflow Library contains 12 workflow templates for the tasks a one-person business repeats all the time:
- Invoice follow-up
- Meeting summary
- Customer FAQ update
- Product description rewrite
- Source-checking
- Blog outline
- Support triage
- Transcript cleanup
- Spreadsheet analysis
- Contract question list
- Weekly planning
- SOP drafting
Each workflow below includes the business problem, required inputs, expected output, QA checks, and a copyable prompt. The download link gives you the pack as a reusable file set, but the article is also useful on its own.
Why one-person businesses need workflows instead of random prompts
A random prompt is easy to write once and hard to trust later. A workflow is different because it includes the task, inputs, output format, review checklist, and next action.
That matters when you are the whole team. In a one-person business, the same person may handle invoices, client calls, website copy, customer questions, spreadsheets, contracts, planning, and operations. AI can help with the first draft or the first pass, but the owner still needs a clear review process.
Inputs first
Start with the real invoice details, transcript, message batch, spreadsheet, or process notes. The prompt should not invent the facts.
Output format second
Ask for a specific output: email options, FAQ entries, a triage table, a source-check table, or an SOP.
Human review last
Check names, dates, prices, policies, customer details, claims, calculations, and legal or financial language before using the output.
Preview table: 12 AI workflow templates
| Workflow | User problem | Required inputs | Expected output | QA check |
|---|---|---|---|---|
| Invoice Follow-Up Email | Use when an invoice is due soon, due today, or overdue and you need a professional reminder. | Invoice details, client relationship, invoice status, payment terms, tone, and context to include. | Three reminder options, subject lines, payment-details checklist, and a human review checklist. | Verify the amount, due date, invoice number, payment link, client name, and contract terms before sending. |
| Meeting Summary and Action Items | Use after client calls, sales calls, coaching sessions, vendor calls, or planning sessions. | Rough notes or transcript text, meeting type, participants, follow-up style, deadlines, and sensitivity rules. | Decisions, action items, owners, deadlines, risks, open questions, and a follow-up email draft. | Confirm that decisions and deadlines were actually stated. Mark unclear items as needs confirmation. |
| Customer FAQ Update | Use when the same customer questions keep repeating across email, chat, DMs, forms, calls, or comments. | Customer questions, business type, known policies, answer style, page destination, and sensitive-data rules. | Grouped FAQ entries, concise answers, missing-policy questions, page-placement ideas, and QA notes. | Do not let AI invent refund terms, shipping timelines, pricing, warranties, guarantees, health claims, or legal terms. |
| Product Description Rewrite | Use when a product, service, download, or digital asset description is vague, too feature-heavy, or hard to scan. | Current description, audience, product facts, constraints, proof points, tone, and SEO target. | Revised copy, benefit bullets, best-fit notes, not-ideal-fit notes, SEO fields, and trust cautions. | Verify every feature, compatibility note, promise, price, policy, and outcome claim before publishing. |
| Source-Checking | Use before publishing a draft that contains claims, citations, statistics, comparisons, or factual statements. | Draft text, source list, claim type, risk level, citation style, and output format. | Claim-check table, unsupported-claim flags, evidence-quality notes, source gaps, and rewrite suggestions. | Open the sources yourself. Treat AI as an organizing assistant, not proof that the claim is true. |
| Blog Outline | Use before writing a blog post, tutorial, comparison, resource page, or asset launch article. | Topic, audience, goal, search intent, internal links, examples, angle, and constraints. | Article brief, outline, FAQ ideas, examples to gather, internal-link ideas, and QA checks. | Reject generic sections and verify that the outline has a real angle, useful examples, and no unsupported claims. |
| Support Triage | Use when support messages, forms, reviews, comments, or chat logs pile up. | Message batch, known policies, categories, urgency rules, reply tone, and escalation rules. | Triage table, priority order, response drafts, missing-info requests, and escalation flags. | Personally review refund disputes, privacy requests, safety issues, legal threats, payment problems, and angry customers. |
| Transcript Cleanup | Use for client calls, interviews, webinars, voice notes, podcasts, research calls, or screen-share narration. | Raw transcript, content type, speaker labels, cleanup level, output need, tone, and sensitive-data rules. | Cleaned transcript sections, summary, key points, quotes to verify, action items, and reuse ideas. | Verify quotes, speaker intent, names, and sensitive information before publishing or sending. |
| Spreadsheet Analysis | Use when pasted rows or exported data need a plain-English readout. | Data table, data type, analysis goal, column definitions, date range, and business context. | Data-quality issues, summary metrics, patterns, risks, questions, and suggested next steps. | Verify formulas, totals, rows, dates, categories, and financial conclusions outside the AI output. |
| Contract Question List | Use before professional review of a contract, vendor agreement, NDA, licensing term, sponsorship agreement, or service term. | Contract type, excerpt with identifiers removed, jurisdiction if known, business role, concerns, output style, and risk level. | Plain-English clause summary, questions for professional review, unclear terms, and review checklist. | Do not use AI to decide whether to sign. Use it to prepare questions for a qualified professional. |
| Weekly Planning | Use at the start of the week or whenever the task list feels overloaded. | Task list, available hours, fixed commitments, weekly goals, energy pattern, and priority method. | Priority list, weekly blocks, must-do tasks, defer list, risks, and review prompts. | Make sure the plan does not overload the week, invent deadlines, or ignore fixed commitments. |
| SOP Drafting | Use when a repeated task should become a reusable process, checklist, or handoff document. | Process name, current notes, tools used, future user, quality standard, known edge cases, and SOP format. | SOP with purpose, trigger, inputs, tools, steps, QA checks, edge cases, owner, frequency, and improvement notes. | Test the SOP against a real task before delegating, automating, or treating it as final. |
How to use a workflow card
Use each workflow card as a small operating process:
- Pick the closest workflow. Use invoice follow-up for payment reminders, transcript cleanup for raw recordings, support triage for customer batches, and SOP drafting for repeatable operations.
- Prepare the inputs. Put the facts in one place before pasting the prompt.
- Remove sensitive data. Replace customer names, invoice IDs, account numbers, payment links, contract names, private metrics, and credentials with placeholders.
- Paste the prompt. Use the copyable prompt under the relevant workflow card below.
- Review before using. AI output should be checked before it is sent, published, billed, filed, or used in a business decision.
The 12 copyable AI workflows
1. Invoice Follow-Up Email Workflow
User problem: Use when an invoice is due soon, due today, or overdue and you need a professional reminder.
Required inputs: invoice details, client relationship, invoice status, payment terms, tone, and context to include.
Expected output: three reminder options, subject lines, payment-details checklist, and a human review checklist.
QA check: Verify the amount, due date, invoice number, payment link, client name, and contract terms before sending.
Copy the workflow prompt
ROLE
Act as a careful accounts-receivable writing assistant for a one-person business.
GOAL
Draft polite, clear invoice follow-up emails that preserve the client relationship while making the payment request specific.
WHEN TO USE THIS
Use when an invoice is unpaid, approaching due, just overdue, or overdue enough to need a firmer follow-up.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return three email options: gentle reminder, standard overdue follow-up, and firm final reminder. Include subject lines, payment details checklist, and a human review checklist.
RULES
- Do not threaten legal action unless the user explicitly asks and provides policy language.
- Do not invent invoice numbers, amounts, due dates, or payment links.
- Use placeholders for sensitive client details.
- Keep tone professional and calm.
- Check your invoice records before sending.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
BUSINESS_TYPE:
<Freelancer, Consultant, Coach, Creator, Local service provider, One-person agency, Other>
CLIENT_RELATIONSHIP:
<New client, Repeat client, Long-term client, Difficult client, Unknown>
INVOICE_STATUS:
<Due soon, Due today, 1-7 days overdue, 8-30 days overdue, 30+ days overdue>
INVOICE_DETAILS:
<Invoice number, amount, due date, payment link, project name, placeholders if sensitive>
TONE:
<Friendly, Professional, Firm, Very concise, Warm but direct>
PAYMENT_TERMS:
<Due on receipt, Net 7, Net 14, Net 30, Custom terms>
CONTEXT_TO_INCLUDE:
<Previous reminder sent, Work delivered, Payment issue known, No prior contact, Other>2. Meeting Summary and Action Items Workflow
User problem: Use after client calls, sales calls, coaching sessions, vendor calls, or planning sessions.
Required inputs: rough notes or transcript text, meeting type, participants, follow-up style, deadlines, and sensitivity rules.
Expected output: decisions, action items, owners, deadlines, risks, open questions, and a follow-up email draft.
QA check: Confirm that decisions and deadlines were actually stated. Mark unclear items as needs confirmation.
Copy the workflow prompt
ROLE
Act as a meeting-notes editor for a one-person business.
GOAL
Turn rough notes or transcripts into clear decisions, action items, open questions, and follow-up messages.
WHEN TO USE THIS
Use after client calls, sales calls, project check-ins, coaching calls, vendor calls, or internal planning sessions.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return a structured meeting summary with decisions, action items, owners, deadlines, risks, open questions, and a follow-up email draft.
RULES
- Do not invent decisions that are not in the transcript or notes.
- Mark unclear items as “needs confirmation.”
- Separate facts from assumptions.
- Keep client-sensitive details private and use placeholders where needed.
- Keep raw notes or transcript text separate from the final summary.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
MEETING_TYPE:
<Client call, Sales call, Project check-in, Coaching session, Vendor call, Planning session, Other>
RAW_NOTES_OR_TRANSCRIPT:
<Paste notes or transcript text>
PARTICIPANTS:
<Names, roles, or placeholders>
FOLLOW_UP_STYLE:
<Short recap, Detailed recap, Friendly, Formal, Action-focused>
DEADLINE_FORMAT:
<Exact dates, Relative deadlines, No deadlines, Unknown>
OUTPUT_NEEDED:
<Summary only, Summary + email, Action list only, Client-ready recap>
SENSITIVE_DATA_RULE:
<Use placeholders, Remove names, Keep internal only, Other>3. Customer FAQ Update Workflow
User problem: Use when the same customer questions keep repeating across email, chat, DMs, forms, calls, or comments.
Required inputs: customer questions, business type, known policies, answer style, page destination, and sensitive-data rules.
Expected output: grouped FAQ entries, concise answers, missing-policy questions, page-placement ideas, and QA notes.
QA check: Do not let AI invent refund terms, shipping timelines, pricing, warranties, guarantees, health claims, or legal terms.
Copy the workflow prompt
ROLE
Act as a customer-support content editor for a one-person business.
GOAL
Turn repeated customer questions into clear FAQ entries, help-center copy, and website-ready answers.
WHEN TO USE THIS
Use when customers keep asking the same questions by email, chat, social DMs, forms, calls, or comments.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return grouped FAQ questions, concise answers, recommended page placement, missing-policy questions, and a QA checklist.
RULES
- Do not invent policies, prices, shipping times, refund terms, health claims, legal terms, or guarantees.
- Flag missing information instead of guessing.
- Make answers customer-friendly but accurate.
- Prepare web-ready formatting only after verifying policies and facts.
- If the source questions are long, split them into smaller batches before analysis.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
BUSINESS_TYPE:
<Online shop, Consultant, Coach, Creator, Local service provider, SaaS/tool, One-person agency, Other>
CUSTOMER_QUESTIONS:
<Paste questions, emails, chat logs, reviews, or support snippets>
CURRENT_POLICIES:
<Refund policy, shipping policy, booking policy, support hours, pricing notes, placeholders if unknown>
FAQ_LOCATION:
<Product page, Service page, Help page, Checkout page, Blog post, Email template, Other>
TONE:
<Friendly, Clear, Premium, Casual, Direct, Technical>
RISK_AREAS:
<Refunds, Health claims, Legal claims, Financial claims, Delivery promises, Privacy, None>
OUTPUT_FORMAT:
<FAQ table, Website copy, Help-center entries, Draft + missing-info list>4. Product Description Rewrite Workflow
User problem: Use when a product, service, download, or digital asset description is vague, too feature-heavy, or hard to scan.
Required inputs: current description, audience, product facts, constraints, proof points, tone, and SEO target.
Expected output: revised copy, benefit bullets, best-fit notes, not-ideal-fit notes, SEO fields, and trust cautions.
QA check: Verify every feature, compatibility note, promise, price, policy, and outcome claim before publishing.
Copy the workflow prompt
ROLE
Act as an ecommerce and digital-product copy editor for a one-person business.
GOAL
Rewrite product descriptions so they are clearer, more specific, and more useful without making unsupported claims.
WHEN TO USE THIS
Use for digital products, templates, prompt packs, services, downloads, physical products, or app-related product pages.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return a revised product description, benefit bullets, “best for / not ideal for,” usage notes, trust cautions, and SEO fields.
RULES
- Do not invent features, compatibility, prices, guarantees, refund terms, certifications, or outcomes.
- Separate features from benefits.
- Keep claims specific and verifiable.
- Do not overhype AI, health, finance, or income claims.
- Mention page placement only when the product page destination is provided.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
PRODUCT_TYPE:
<Digital template, Prompt pack, Tool kit, App resource, Physical product, Service, Other>
CURRENT_DESCRIPTION:
<Paste current copy or rough notes>
FEATURES_CONFIRMED:
<List confirmed files, formats, features, limits, compatibility, and requirements>
TARGET_BUYER:
<Freelancer, Creator, Student, Researcher, Small business owner, Investor, Other>
SEO_KEYWORD:
<Primary keyword or Auto>
CLAIMS_TO_AVOID:
<Guaranteed income, Medical claims, Legal claims, Financial advice, Unsupported savings, Other>
OUTPUT_FORMAT:
<Short product page, Long product page, Product listing, SEO snippet, All>5. Source-Checking Workflow
User problem: Use before publishing a draft that contains claims, citations, statistics, comparisons, or factual statements.
Required inputs: draft text, source list, claim type, risk level, citation style, and output format.
Expected output: claim-check table, unsupported-claim flags, evidence-quality notes, source gaps, and rewrite suggestions.
QA check: Open the sources yourself. Treat AI as an organizing assistant, not proof that the claim is true.
Copy the workflow prompt
ROLE
Act as a source-verification assistant for a solo publisher or one-person business.
GOAL
Check whether claims are supported by the provided sources and flag unsupported, outdated, vague, or risky statements.
WHEN TO USE THIS
Use before publishing blogs, product pages, reports, newsletters, educational content, research summaries, or social posts.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return a claim-check table with claim, source support, evidence quality, citation note, rewrite suggestion, and risk level.
RULES
- Do not browse unless the user asks and the tool is available.
- Use only the sources pasted by the user unless instructed otherwise.
- Do not invent citations or page numbers.
- Flag claims that need current verification.
- Separate “source says” from “reasonable interpretation.”
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
DRAFT_TEXT:
<Paste the draft section, article, product copy, or report excerpt>
SOURCE_LIST:
<Paste links, excerpts, PDFs, notes, or citations to check against>
TOPIC_TYPE:
<Health, Finance, AI, Science, Technology, Legal-adjacent, General business, Other>
CLAIM_RISK_LEVEL:
<Low, Medium, High, YMYL, Regulated, Current facts needed>
CITATION_STYLE:
<Natural links, Footnotes, Inline citations, Source table, Other>
OUTPUT_DETAIL:
<Critical issues only, Standard, Detailed>
REWRITE_NEEDED:
<Yes, No, Only risky claims>6. Blog Outline Workflow
User problem: Use before writing a blog post, tutorial, comparison, resource page, or asset launch article.
Required inputs: topic, audience, goal, search intent, internal links, examples, angle, and constraints.
Expected output: article brief, outline, FAQ ideas, examples to gather, internal-link ideas, and QA checks.
QA check: Reject generic sections and verify that the outline has a real angle, useful examples, and no unsupported claims.
Copy the workflow prompt
ROLE
Act as an SEO blog strategist and editor for a one-person business.
GOAL
Turn a topic idea into a useful, search-intent-matched article outline with original assets, examples, and internal-link opportunities.
WHEN TO USE THIS
Use before writing a blog post, tutorial, comparison, resource page, or asset launch article.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return a blog brief with title options, search intent, reader problem, outline, table ideas, FAQ, examples to gather, and QA checks.
RULES
- Do not create a generic outline that could fit any website.
- Include an original angle, workflow, template, calculator, example, or checklist where possible.
- Do not invent rankings, search volume, or traffic.
- Do not recommend duplicate content unless there is a clear unique angle.
- Suggest a repeatable drafting workflow when relevant.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
TOPIC:
<Describe the blog topic>
WEBSITE_OR_BRAND:
<Business site, Personal site, Client site, Other>
TARGET_AUDIENCE:
<Beginners, Professionals, Small business owners, Researchers, Investors, Technical users, Other>
PRIMARY_GOAL:
<Traffic, Authority, Leads, Sales, Internal links, Product launch, Education, Other>
EXISTING_RELATED_PAGES:
<Paste related URLs or say unknown>
ASSET_TO_INCLUDE:
<Template, Prompt pack, Spreadsheet, Checklist, Tool, Calculator, None, Other>
OUTPUT_DEPTH:
<Quick brief, Standard outline, Detailed editorial brief>7. Support Triage Workflow
User problem: Use when support messages, forms, reviews, comments, or chat logs pile up.
Required inputs: message batch, known policies, categories, urgency rules, reply tone, and escalation rules.
Expected output: triage table, priority order, response drafts, missing-info requests, and escalation flags.
QA check: Personally review refund disputes, privacy requests, safety issues, legal threats, payment problems, and angry customers.
Copy the workflow prompt
ROLE
Act as a support-triage assistant for a one-person business.
GOAL
Sort support messages by urgency, category, needed action, missing information, and suggested reply draft.
WHEN TO USE THIS
Use when inboxes, forms, comments, reviews, or chat logs pile up and the owner needs a response plan.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return a triage table, priority order, reply drafts, escalation flags, and policy questions to verify before responding.
RULES
- Do not promise refunds, replacements, legal outcomes, medical results, or policy exceptions.
- Flag angry customers, payment issues, privacy issues, safety issues, and legal threats for human review.
- Do not infer facts not in the message.
- Use placeholders for customer data.
- Keep tone calm and practical.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
MESSAGE_BATCH:
<Paste support messages, emails, comments, reviews, or chat snippets>
BUSINESS_TYPE:
<Online shop, Service business, Creator, Coach, Consultant, App/tool, Other>
KNOWN_POLICIES:
<Refunds, delivery, warranty, support hours, privacy, pricing, placeholders if unknown>
TRIAGE_CATEGORIES:
<Billing, Technical issue, Refund, Pre-sale question, Complaint, Feature request, Spam, Other>
URGENCY_RULES:
<Same day, 24 hours, 48 hours, Low priority, Custom>
REPLY_TONE:
<Friendly, Professional, Empathetic, Firm, Concise>
ESCALATION_RULES:
<Legal threat, Safety issue, Payment dispute, Privacy request, Medical/financial/legal claim, Other>8. Transcript Cleanup Workflow
User problem: Use for client calls, interviews, webinars, voice notes, podcasts, research calls, or screen-share narration.
Required inputs: raw transcript, content type, speaker labels, cleanup level, output need, tone, and sensitive-data rules.
Expected output: cleaned transcript sections, summary, key points, quotes to verify, action items, and reuse ideas.
QA check: Verify quotes, speaker intent, names, and sensitive information before publishing or sending.
Copy the workflow prompt
ROLE
Act as a transcript cleanup editor for a one-person business.
GOAL
Turn messy transcripts into readable notes, summaries, quotes, action items, and reusable content snippets without changing meaning.
WHEN TO USE THIS
Use for call transcripts, podcast drafts, interviews, voice notes, webinars, client calls, research interviews, or screen-share narration.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return cleaned transcript sections, summary, key points, quotes to verify, action items, and content repurposing ideas.
RULES
- Do not add facts that are not present.
- Do not fabricate quotes.
- Mark unclear audio or uncertain wording.
- Preserve speaker intent while improving readability.
- If the transcript is long, split it into smaller sections before cleanup.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
TRANSCRIPT_TEXT:
<Paste raw transcript text>
CONTENT_TYPE:
<Client call, Podcast, Interview, Webinar, Voice note, Research call, Other>
SPEAKER_LABELS:
<Known speakers, Unknown speakers, Single speaker, Use placeholders>
CLEANUP_LEVEL:
<Light punctuation, Standard cleanup, Heavy readability cleanup, Summary only>
OUTPUT_NEEDED:
<Clean transcript, Summary, Action items, Quotes, Blog notes, Social snippets, All>
TONE:
<Neutral, Editorial, Professional, Casual, Technical>
SENSITIVE_DATA_RULE:
<Remove names, Remove company data, Keep placeholders, Internal use only, Other>9. Spreadsheet Analysis Workflow
User problem: Use when pasted rows or exported data need a plain-English readout.
Required inputs: data table, data type, analysis goal, column definitions, date range, and business context.
Expected output: data-quality issues, summary metrics, patterns, risks, questions, and suggested next steps.
QA check: Verify formulas, totals, rows, dates, categories, and financial conclusions outside the AI output.
Copy the workflow prompt
ROLE
Act as a spreadsheet analysis assistant for a one-person business.
GOAL
Analyze pasted spreadsheet data or summaries to identify patterns, anomalies, missing fields, questions, and next actions.
WHEN TO USE THIS
Use for sales logs, invoices, expenses, content calendars, product lists, customer feedback, inventory, lead lists, or campaign tracking.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return a plain-English analysis with data-quality issues, summary metrics, notable patterns, risks, questions, and suggested next steps.
RULES
- Do not invent rows, totals, dates, or categories.
- State when calculations cannot be verified from the pasted data.
- Do not provide personalized financial, tax, or accounting advice.
- Ask for column definitions when unclear.
- Suggest cleaning CSV or JSON formatting when relevant.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
DATA_TABLE:
<Paste CSV, table, spreadsheet sample, or summary>
DATA_TYPE:
<Sales, Expenses, Invoices, Leads, Content, Product catalog, Customer feedback, Inventory, Other>
ANALYSIS_GOAL:
<Find trends, Find errors, Summarize, Compare categories, Prioritize actions, Prepare dashboard, Other>
COLUMN_DEFINITIONS:
<List columns and meanings or say unknown>
DATE_RANGE:
<This week, This month, Quarter, Year, Custom, Unknown>
BUSINESS_CONTEXT:
<Describe the business and what decisions the data supports>
OUTPUT_FORMAT:
<Narrative summary, Table, Action list, Dashboard ideas, All>10. Contract Question List Workflow
User problem: Use before professional review of a contract, vendor agreement, NDA, licensing term, sponsorship agreement, or service term.
Required inputs: contract type, excerpt with identifiers removed, jurisdiction if known, business role, concerns, output style, and risk level.
Expected output: plain-English clause summary, questions for professional review, unclear terms, and review checklist.
QA check: Do not use AI to decide whether to sign. Use it to prepare questions for a qualified professional.
Copy the workflow prompt
ROLE
Act as a contract-reading assistant that creates questions for a professional review, not legal advice.
GOAL
Turn a contract excerpt into a plain-English list of clauses to understand, risks to ask about, missing terms, and questions for a lawyer or qualified professional.
WHEN TO USE THIS
Use before signing client contracts, vendor agreements, contractor agreements, licensing terms, sponsorship agreements, or service terms.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return a clause summary, plain-English questions, unclear terms, negotiation points to consider, and a professional-review checklist.
RULES
- Do not give legal advice or say whether to sign.
- Do not interpret law for a jurisdiction unless a qualified source is provided.
- Do not rewrite clauses as enforceable legal language.
- Flag ambiguous, one-sided, missing, or high-stakes terms for lawyer review.
- Use placeholders for names and confidential contract terms.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
CONTRACT_TYPE:
<Client service agreement, Vendor contract, NDA, Contractor agreement, Licensing agreement, Sponsorship agreement, Terms of service, Other>
CONTRACT_EXCERPT:
<Paste excerpt or summarized clauses with sensitive details removed>
JURISDICTION_IF_KNOWN:
<United States, State/country, International, Unknown>
BUSINESS_ROLE:
<Service provider, Buyer, Seller, Contractor, Client, Licensor, Licensee, Other>
MAIN_CONCERNS:
<Payment, Scope, IP ownership, Confidentiality, Liability, Termination, Renewal, Non-compete, Data/privacy, Other>
OUTPUT_STYLE:
<Simple questions, Detailed review checklist, Negotiation prep, Professional-review brief>
RISK_LEVEL:
<Low, Medium, High, Unknown>11. Weekly Planning Workflow
User problem: Use at the start of the week or whenever the task list feels overloaded.
Required inputs: task list, available hours, fixed commitments, weekly goals, energy pattern, and priority method.
Expected output: priority list, weekly blocks, must-do tasks, defer list, risks, and review prompts.
QA check: Make sure the plan does not overload the week, invent deadlines, or ignore fixed commitments.
Copy the workflow prompt
ROLE
Act as a weekly planning assistant for a one-person business.
GOAL
Turn a messy list of tasks, deadlines, client work, admin work, and personal constraints into a realistic weekly plan.
WHEN TO USE THIS
Use at the start of each week or whenever the owner feels overloaded and needs priority sequencing.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return a priority list, weekly schedule blocks, must-do tasks, defer list, delegation/automation ideas, risks, and end-of-week review prompts.
RULES
- Do not overload the schedule.
- Separate urgent from important.
- Preserve personal constraints and energy limits.
- Do not invent deadlines.
- Suggest tools only when they are explicitly named by the user or clearly needed.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
TASK_LIST:
<Paste tasks, projects, deadlines, errands, admin work, content work, client work>
AVAILABLE_HOURS:
<5, 10, 20, 30, 40, Custom>
FIXED_COMMITMENTS:
<Meetings, appointments, delivery dates, personal constraints, travel, Other>
BUSINESS_GOALS_THIS_WEEK:
<Revenue, Client delivery, Marketing, Product build, Admin cleanup, Learning, Other>
ENERGY_PATTERN:
<Morning best, Afternoon best, Evening best, Variable, Unknown>
PRIORITY_METHOD:
<Impact/effort, Deadline first, Client first, Revenue first, Balanced>
OUTPUT_FORMAT:
<Daily plan, Priority board, Time blocks, Checklist, All>12. SOP Drafting Workflow
User problem: Use when a repeated task should become a reusable process, checklist, or handoff document.
Required inputs: process name, current notes, tools used, future user, quality standard, known edge cases, and SOP format.
Expected output: SOP with purpose, trigger, inputs, tools, steps, QA checks, edge cases, owner, frequency, and improvement notes.
QA check: Test the SOP against a real task before delegating, automating, or treating it as final.
Copy the workflow prompt
ROLE
Act as an operations documentation assistant for a one-person business.
GOAL
Turn a repeated task into a clear standard operating procedure that can be reused, delegated, automated, or improved.
WHEN TO USE THIS
Use for invoicing, content publishing, customer onboarding, support responses, file naming, product uploads, podcast editing, research workflows, or monthly reporting.
TASK
Use the inputs at the end to create the requested business output. If critical information is missing, ask only the minimum questions needed. If the input is enough, proceed and state any assumptions.
OUTPUT REQUIRED
Return an SOP with purpose, trigger, required inputs, tools, steps, quality checks, edge cases, owner, frequency, and improvement notes.
RULES
- Do not assume hidden steps.
- Ask clarifying questions if the process is incomplete.
- Keep steps concrete and testable.
- Include QA checks and failure points.
- Mention tools only when they are explicitly named by the user or clearly needed.
FINAL CHECK
Before finishing, verify that the output is specific, usable, factual, and ready for a human business owner to review. Flag anything that needs confirmation before it is sent, published, billed, or acted on.
INPUTS
PROCESS_NAME:
<Invoice sending, Blog publishing, Customer onboarding, Support reply, Product upload, Research workflow, Monthly report, Other>
CURRENT_PROCESS_NOTES:
<Paste rough notes, steps, voice notes, transcript, checklist, or examples>
TOOLS_USED:
<Google Sheets, Email, CMS, Calendar, Notes app, Project tool, Other>
OUTPUT_USER:
<Just me, Future contractor, Assistant, Client-facing team, Other>
QUALITY_STANDARD:
<Fast and simple, Thorough, Client-ready, Compliance-sensitive, Other>
EDGE_CASES_KNOWN:
<Missing info, Rush jobs, Refunds, Errors, File issues, Client changes, Other>
SOP_FORMAT:
<Checklist, Step-by-step, Table, Training doc, All>Quality-control rules before you use AI output
The workflow pack is built around human review. Keep these rules close:
- Do not send AI-written emails without checking names, dates, amounts, links, and tone.
- Do not publish AI-written copy without verifying product details, pricing, policies, sources, and claims.
- Do not treat AI spreadsheet analysis as verified accounting, tax, or financial advice.
- Do not treat AI contract notes as legal advice.
- Do not let AI invent customer policies, refund exceptions, shipping timelines, legal terms, medical claims, or guarantees.
- Do not use AI output as final judgment for high-stakes business decisions.
- Do keep a reusable QA checklist for each workflow you use often.
A useful AI workflow should make review easier. It should not remove review.
Privacy and sensitive-data cautions
Before pasting business material into any AI assistant, remove sensitive details unless you are using an approved business account and you understand the data policy.
Replace or remove:
- customer names, emails, phone numbers, and addresses
- invoice numbers, payment links, account IDs, and order IDs
- private contract terms and confidential client work
- employee, contractor, medical, legal, financial, or compliance details
- private business metrics, API keys, passwords, tokens, and credentials
Use placeholders like:
[CLIENT_NAME]
[INVOICE_NUMBER]
[PAYMENT_LINK]
[CONTRACT_EXCERPT_WITH_IDENTIFIERS_REMOVED]
[CUSTOMER_MESSAGE_1]
[PRIVATE_METRIC_REMOVED]For legal, accounting, medical, compliance, employment, and tax-related material, use AI only to create drafts, summaries, questions, and checklists. Final decisions should stay with the business owner and qualified professionals.
Where this free workflow pack fits in your business
This pack is not an app directory and it does not require any specific Jivaro tool. It fits into the tools you already use: email, notes, spreadsheets, documents, your CMS, your calendar, and your customer inbox.
| Business area | Best matching workflows | How to use the output |
|---|---|---|
| Billing and admin | Invoice Follow-Up, Weekly Planning, SOP Drafting | Draft reminders, organize payment follow-up, and document repeatable admin steps. |
| Client communication | Meeting Summary, Transcript Cleanup, Support Triage | Turn messy notes and messages into summaries, follow-ups, and response priorities. |
| Website and content | Customer FAQ Update, Product Description Rewrite, Blog Outline, Source-Checking | Create clearer website copy, article briefs, FAQ entries, and claim-review tables. |
| Operations | Spreadsheet Analysis, Contract Question List, Weekly Planning, SOP Drafting | Find data issues, prepare professional-review questions, plan the week, and document processes. |
Who this workflow library is for
This free workflow library is a good fit if you are:
- a freelancer who sends invoices, handles client calls, and writes your own proposals
- a consultant who needs meeting summaries, SOPs, and source-checked content
- a creator turning transcripts, ideas, and notes into publishable material
- a coach managing calls, client follow-ups, FAQs, and planning
- a one-person agency juggling client delivery, admin, support, and content
- a tiny shop owner improving product descriptions, FAQs, and support replies
It is also useful if your main problem is not “which AI tool should I use?” but “what should I ask AI to do in a way I can reuse and verify?”
Who this workflow library is not for
This pack is not a replacement for:
- a lawyer
- an accountant
- a clinician
- a financial advisor
- a trained employee
- a customer-support policy
- a real source-checking process
- final business judgment
It is also not built for unattended AI agents making business decisions on your behalf. These workflows are designed for controlled AI assistance with human review.
Download the free workflow pack: use the ZIP when you want the files saved locally, or copy individual prompts from the workflow cards above.
FAQ
What are AI workflows for small business?
AI workflows for small business are repeatable prompt-based processes for tasks such as invoice follow-up, meeting summaries, FAQs, support triage, blog outlines, spreadsheet analysis, and SOP drafting.
How is an AI workflow different from a prompt?
A prompt is the instruction. A workflow includes the whole process around it: when to use it, what inputs to gather, what output to expect, what to verify, and what to do next.
Is the AI Workflow Library free?
Yes. This article uses the direct Jivaro download link for the free workflow pack, and each workflow card also includes a copyable prompt.
Can AI handle invoice follow-up for me?
AI can draft invoice reminder options, but you still need to verify the client name, invoice number, amount, due date, payment link, tone, and payment terms before sending.
Can AI review contracts for a one-person business?
AI can summarize clauses and create questions for professional review. It should not decide whether you should sign, negotiate, or accept legal terms.
How do I protect customer privacy when using AI workflows?
Remove sensitive details before pasting anything into an AI assistant. Use placeholders for names, emails, invoice IDs, payment details, contract terms, and private business data unless you have an approved business AI setup and data policy.
