Business Process Automation Examples: 15 Workflows Taken Apart

About the author

Joey Glyshaw is the founder of AlgoFuse, where he builds the shared AI layer that lets Claude and ChatGPT work from a company’s own data and procedures. He has sold on Amazon since 2015 and runs ZonFlip, an Amazon and TikTok Shop agency in Michigan, along with a small 3PL for Amazon sellers whose warehouse software he built himself with Claude.

Monday morning. Someone exports the weekend ad report, pastes it into a sheet, checks stock by hand, and messages the warehouse about two products running low. Each of those steps is a business process automation example waiting to be built.

The good ones share one shape: a clear trigger, plain rules for most steps, AI only where the input is messy, and a person at the judgment call. I run an Amazon agency and a small 3PL (third-party logistics warehouse), and ours run that way. Here are 15, split step by step, so you can copy the pattern.

TL;DR

  • Most good automations are plain rules; AI handles only messy reading and writing.
  • Put a person at the step where a wrong output costs money.
  • Start with weekly, high-volume work that already has a written procedure.
  • Every automation needs a named owner and a weekly check.
  • Price the manual hours at your loaded labor rate before you build anything.

Not sure which of these fits your week first?

Book a call, and we will map the two or three workflows worth building first. The plan is yours to keep, whichever way you go.

Book a call →

How to Read Each Example

Every example below is broken into the same five parts, so you can compare them and copy the parts that fit.

Each step inside a workflow gets one of three labels:

Rule
What it means
A fixed if-then step with one right answer
Example step
If stock covers fewer than 14 days of sales, alert the buyer
AI
What it means
An LLM (large language model, such as Claude or ChatGPT) reads or writes something unstructured, and a person can check the result
Example step
Pulling line items out of a PDF invoice
Person
What it means
Money, a customer relationship, or a legal question is on the line
Example step
Approving a refund above your limit

The five parts are the trigger, what runs, what gets logged, who checks, and what usually breaks it. I build in that order on purpose. When an output has to be exact, I use a code step, because, as I said on one of my livestreams, “if I use an LLM node for that output, it could be wrong.”

15 Examples at a Glance

Scan this first, then jump to the team that eats the most hours in your business.

1Supplier invoice capture and three-way match
Team
Finance
Trigger
Invoice email arrives
Mostly rule, AI, or person
AI reads, rule match
Good first build
Yes, if invoices are steady
2Daily payout reconciliation
Team
Finance
Trigger
Morning schedule
Mostly rule, AI, or person
Rule
Good first build
Yes
3Expense receipts coded to accounts
Team
Finance
Trigger
Receipt sent in
Mostly rule, AI, or person
AI suggests, rule applies
Good first build
Yes
4Overdue invoice reminders
Team
Finance
Trigger
Due date passes
Mostly rule, AI, or person
Rule
Good first build
Yes
5Inbound lead routing and enrichment
Team
Sales
Trigger
Form submitted
Mostly rule, AI, or person
Rule, AI summary
Good first build
Yes
6Post-purchase and win-back emails
Team
Marketing
Trigger
Order or 90 quiet days
Mostly rule, AI, or person
Rule
Good first build
Yes, with consent checked
7Weekly client reporting
Team
Agency
Trigger
Schedule or client question
Mostly rule, AI, or person
Rule pull, AI summary
Good first build
Yes
8Proposals and contracts from the CRM
Team
Sales
Trigger
Deal reaches proposal stage
Mostly rule, AI, or person
Rule fill, AI draft
Good first build
Later
9Order tagging and routing
Team
Ecommerce ops
Trigger
New order
Mostly rule, AI, or person
Rule
Good first build
Yes
10Low-stock alerts and PO drafts
Team
Ecommerce ops
Trigger
Daily after-sales sync
Mostly rule, AI, or person
Rule, person approves
Good first build
Yes
11Stockout guard for ads
Team
Ecommerce ops
Trigger
Stock or listing change
Mostly rule, AI, or person
Rule
Good first build
Yes
12Daily PPC anomaly alerts
Team
Ecommerce ops
Trigger
Morning schedule
Mostly rule, AI, or person
Rule flag, AI note
Good first build
Later
13Support ticket triage and draft replies
Team
Support
Trigger
New ticket
Mostly rule, AI, or person
AI tag and draft, person sends
Good first build
Later
14Return requests checked against policy
Team
Support
Trigger
Return requested
Mostly rule, AI, or person
Rule, person on exceptions
Good first build
Yes
15New hire onboarding and access
Team
People
Trigger
Offer signed
Mostly rule, AI, or person
Rule
Good first build
Yes

Finance and Back-Office Examples

Back-office work is where the hours tend to hide. In Fortune’s coverage of MIT’s 2025 report on generative AI in business, MIT’s researchers saw the strongest payoff from automating back-office work, while more than half of generative AI budgets went to sales and marketing tools.

1. Supplier Invoice Capture and Three-Way Match

Supplier invoices arrive as PDFs in a shared inbox, and someone types them into the books.

  • Trigger: a new email with an attachment lands in the accounts payable inbox.
  • What runs: AI reads the PDF and pulls the vendor, line items, and totals. A rule compares them with the purchase order (PO) and the receiving record, which is the three-way match.
  • Logged: one row per invoice with the extracted fields, the match result, and a link to the source file.
  • Person checks: any invoice where quantity or price differs from the PO, plus anything above your approval limit.
  • What breaks it: a vendor redesigns its invoice, or a new vendor shows up with no PO on file.

2. Daily Payout Reconciliation Across Sales Channels

Amazon, Shopify, and your payment processor each pay out on their own schedule, net of their own fees.

  • Trigger: a schedule, every morning.
  • What runs: a rule pulls the settlement report from each channel, matches every deposit to the bank feed, and flags any gap over a threshold you set. No AI is needed anywhere in this one.
  • Logged: matched and unmatched lines, with the dollar difference on each.
  • Person checks: the unmatched list only, which is usually a handful of lines.
  • What breaks it: an expired access token on one channel. The sync stops, and nobody notices until the books are off.

3. Expense Receipts Coded to the Right Account

Receipts pile up in phones and inboxes until someone spends a Friday matching them to card charges.

  • Trigger: a receipt photo sent to a dedicated email address or Slack channel.
  • What runs: AI reads the merchant, date, and amount and suggests a category. A rule applies the category on its own for merchants it has already seen twice.
  • Logged: the receipt image, the suggestion, and who approved it.
  • Person checks: first-time merchants and anything over your spending limit.
  • What breaks it: a replaced company card, after which charges stop matching receipts.

4. Overdue Invoice Reminders for Clients

Agencies and service businesses lose real cash to invoices nobody chased.

  • Trigger: an invoice passes its due date in your accounting tool.
  • What runs: a rule sends a templated reminder at 3, 10, and 20 days past due. AI drafts a personal note only for accounts you have flagged as sensitive.
  • Logged: each reminder sent and any reply.
  • Person checks: the last step. Someone calls the client before a third email goes out.
  • What breaks it: a client pays by wire, the invoice never gets marked paid, and the reminders keep coming.

Sales and Marketing Examples

These automations touch customers directly, so the human checks carry more weight here than anywhere else on this list.

5. Inbound Lead Routing and Enrichment

A demo request sits in a shared inbox for a day because nobody knows whose it is.

  • Trigger: a form submission or a booked call.
  • What runs: a rule checks the required fields and removes duplicates against the CRM (customer relationship management system). AI reads the company’s website and the form answers and writes a three-line summary for the rep. A second rule assigns the lead by region or deal size.
  • Logged: the lead, the summary, the owner, and the timestamp.
  • Person checks: the rep reads the summary before the first call, and someone reviews disqualified leads once a week.
  • What breaks it: a new field added to the form that the mapping quietly drops.

6. Post-Purchase and Win-Back Email Flows

Most stores already have the data for these and send them by hand, or not at all.

  • Trigger: an order, a delivery confirmation, or 90 days without a repeat purchase.
  • What runs: rules pick the flow and the timing. AI can draft subject line variants that a person approves once, before the flow goes live.
  • Logged: sends, opens, clicks, and unsubscribes.
  • Person checks: the copy before launch and the suppression list every month.
  • What breaks it: a list import that adds people who never signed up.

Marketing email carries legal duties. The FTC’s CAN-SPAM compliance guide says opt-out requests have to be honored within 10 business days, and the law covers business-to-business email too. Email only people who opted in, and check your own obligations with counsel, since none of this is legal advice.

7. Weekly Client Reporting for Agencies

Plenty of agencies still send a client spreadsheet on Friday built from numbers pulled on Wednesday.

  • Trigger: a schedule, or a client asking a question in Slack.
  • What runs: a rule pulls ad, sales, and inventory numbers into one database. AI writes a short summary of what moved and the likely reasons. The client dashboard refreshes on its own.
  • Logged: the time of each data pull, the summary text, and the version the client saw.
  • Person checks: the account manager reads every summary before it goes out, especially any sentence that explains why a number moved.
  • What breaks it: a platform renames a report column, and the summary starts describing a metric that is now blank.

8. Proposals and Contracts From the CRM

Copying a client’s name, scope and price into a template is slow, and one wrong number ends up in a signed contract.

  • Trigger: a deal moves to the proposal stage.
  • What runs: a rule fills the template with the client name, scope, and pricing from the deal record. AI drafts the scope paragraph from the call notes.
  • Logged: the generated document, the version sent, and the signature status.
  • Person checks: pricing and scope language before anything goes out, on every deal.
  • What breaks it: a price change made in the template that never reached the CRM fields.

Want to watch workflows like these get built first?

The AlgoFuse community on Skool is a paid group where I build them in the open, step by step.

Join the community →

Ecommerce Operations Examples

These four are the work I see every week at the agency and the 3PL.

9. Order Tagging and Routing

Every order needs a warehouse, a shipping method, and sometimes a hold, and doing that by eye does not scale.

  • Trigger: a new order.
  • What runs: rules tag the order (international, high value, fragile, possible fraud), pick the warehouse, and hold anything flagged.
  • Logged: each tag and the rule that applied it.
  • Person checks: held orders, ideally within the hour.
  • What breaks it: a new SKU (stock keeping unit) added with no weight or warehouse assigned.

On Shopify, the free Shopify Flow app watches the store for events and runs workflows built from triggers, conditions and actions, so most of this needs no custom code.

10. Low-Stock Alerts and Purchase Order Drafts

Running out costs you sales. Over-ordering ties up cash in boxes.

  • Trigger: daily, after the sales sync finishes.
  • What runs: a rule works out days of cover from recent sales velocity, current stock, and inbound units. Under your threshold, it drafts a PO at the supplier’s minimum order quantity.
  • Logged: the velocity it used, the days of cover, and the draft PO.
  • Person checks: the buyer approves every PO, since promotions and seasonality are a person’s call.
  • What breaks it: a stock count that is wrong at the source. The rule will trust it.

11. Stockout Guard for Ads on Unbuyable Listings

Zombie ads are ads that keep spending on listings that are out of stock or cannot be bought.

  • Trigger: a change in inventory or listing status.
  • What runs: a rule pauses ads on any listing that runs out of stock or becomes unbuyable, then turns them back on once shoppers can buy it again.
  • Logged: every pause and restart, with the reason.
  • Person checks: the daily list of paused ads, in case a listing needs a fix instead of a wait.
  • What breaks it: a change on the ads API (application programming interface) side that stops the pause from going through.

12. Daily PPC Anomaly Alerts to Slack

PPC (pay-per-click) accounts drift overnight, and the person who catches it is usually checking by hand.

  • Trigger: a schedule, every morning.
  • What runs: a rule compares yesterday’s spend, clicks, and ACoS (advertising cost of sales, which is ad spend divided by ad-attributed sales) by campaign against the trailing average and flags outliers. AI writes a short note on each flag, such as a search term that spiked or a budget that capped by noon.
  • Logged: the flags, the notes and what the team did about each one.
  • Person checks: bid changes wait for a person to approve them before the tool writes them to Amazon Ads.
  • What breaks it: an expired token that leaves the report quietly empty.

Amazon Ads put its MCP server into open beta in February 2026, giving Claude, ChatGPT, and similar tools one connection to Amazon Ads API functions. MCP (Model Context Protocol) is an open standard for connecting AI to outside tools and data, and Amazon limits the beta to Ads partners with active API credentials. In my own setup, the PPC actions live as folders of skill files behind one MCP server, so when a client runs PPC differently, I edit the skill file once, and every person’s Claude uses the new version.

Customer Support and People Examples

Support and hiring are full of repeat work, but each one has a moment where only a person should decide.

13. Support Ticket Triage and Draft Replies

Much of a support inbox is the same handful of questions, and someone answers each one from scratch.

  • Trigger: a new ticket by email or chat.
  • What runs: AI reads the message and tags the intent (order status, return, damaged item, wholesale). A rule pulls the order record. AI then drafts a reply from your support SOP (standard operating procedure) and the order data.
  • Logged: the tag, the draft, the final reply and who sent it.
  • Person checks: every draft for the first few weeks, then refunds, complaints, and anything outside your five most common intents.
  • What breaks it: a policy change that never makes it into the SOP the drafts read from.

14. Return Requests Checked Against Policy

Most return requests are clear yes-or-no cases, and a few need someone to think.

  • Trigger: a customer submits a return request.
  • What runs: a rule checks the order date, the return window and the condition rules, approves the clear cases and sends the label.
  • Logged: the decision and the rule behind it.
  • Person checks: anything outside policy, plus refunds above a dollar limit you choose.
  • What breaks it: an extended holiday return window set in the store and never in the rule.

15. New Hire Onboarding and Account Access

A new hire’s first day goes better when the logins work and the calendar is already full.

  • Trigger: a signed offer in your HR (human resources) tool.
  • What runs: a rule creates the accounts, adds the person to the right Slack channels and shared drives, sends the checklist, and books the first-week meetings.
  • Logged: every account created and who has access to what.
  • Person checks: the manager confirms access levels before day one.
  • What breaks it: the reverse flow never gets built, and a former contractor keeps a login for months.

The Math Behind Picking One

Before you build any of these, price the manual version.

The formula is simple: hours per week, times 52, times your fully loaded hourly cost. For a public anchor, the Bureau of Labor Statistics reported on September 9, 2026, that private industry employers spent an average of $46.89 per hour worked on total compensation in June 2026, counting wages and benefits.

The hours below are placeholders. Replace them with what your team logs.

Payout reconciliation
Hours per week (your number)
3
Hours per year
156
Cost at $46.89 an hour
$7,314.84
Weekly ad report
Hours per week (your number)
2
Hours per year
104
Cost at $46.89 an hour
$4,876.56
Support replies
Hours per week (your number)
6
Hours per year
312
Cost at $46.89 an hour
$14,629.68

Subtract the tool subscriptions and the hours someone spends checking and maintaining the automation. Whether a build pays back depends on how many hours of repeat work your team does today, so run the math on your own hours first. If the number left over is small, keep doing it by hand.

Where to Start With Your First Automation

Six steps, in order, take you from a list of chores to one automation that keeps working.

Step 1: List the Work That Repeats Every Week

Ask each person to write down what they do every week that follows the same steps. Note how long it takes and how often it goes wrong. The tasks that show up on two or three lists are your candidates.

Step 2: Trace Where the Data Comes From

For each candidate, name the system that holds the input and the system that needs the output. If the data lives in someone’s head or a private spreadsheet, fix that before any automation. I start every build with this question.

Step 3: Write the SOP Before Anything Runs

A workflow nobody has written down cannot be automated well. Write the steps, the exceptions, and what a good result looks like in a plain document. That file becomes the rulebook for the automation and, later, for the AI steps.

Step 4: Ship the Plain Version First

Build the rule-based version with no AI, and run it beside the manual process for two weeks. Most of the 15 examples above are mostly rules, and our own guide on which tasks deserve a simple rule goes deeper on that split. You will find the edge cases faster without a model in the way.

Step 5: Add AI Only Where a Person Can Check It

Add an AI step only where the input is unstructured, such as a PDF, an email or call notes. Put a person right after it until the drafts are reliably good. Keep that check permanently wherever money or a customer is involved.

Step 6: Name an Owner and a Weekly Check

Every automation needs one person who owns it and looks at its log once a week. Tokens expire, platforms rename fields, and policies change, which is why automations decay months after launch when nobody watches them. A ten-minute weekly review of the log catches most of it.

Processes to Keep Manual for Now

Some work looks automatable on paper and costs more once it runs on its own.

  • Low-volume tasks. If it happens once a quarter, a checklist beats an automation.
  • Undocumented processes. Automating a process nobody has written down locks in whatever the last person happened to do.
  • Pricing in competitive categories. One bad rule can cut margin across the whole catalog before anyone looks.
  • Legal and HR judgment calls. Disputes, terminations, and contract changes stay with a person.
  • Replies to angry customers. Keep a person on these until you have reviewed a few hundred AI drafts and trust them.

Skip the build entirely if no single repeat task takes more than a few hours a week. One line from my YouTube Shorts sums up the stance: “Full automation is not always the goal.”


Frequently Asked Questions

Short answers to the questions owners ask most before their first build.

Do I Need AI to Automate a Business Process?+

No. Most of the examples above run on plain rules in tools you may already pay for. AI earns its place only where the input is unstructured, such as a PDF invoice, a customer email, or a page of call notes.

What Is the Difference Between BPA and RPA?+

BPA (business process automation) is the umbrella term for the full workflow, start to finish. RPA (robotic process automation) is one tool inside it: software that clicks through screens the way a person would, usually for older systems with no API.

Which Business Process Should a Small Team Automate First?+

The one you do every week, already have written down, and can check cheaply. For most ecommerce teams, that means payout reconciliation, low-stock alerts, or the weekly ad report.

Can I Build These With Claude or ChatGPT?+

Yes, for many of them, once the model can reach your data through a connector or an MCP server. The rule steps still run in plain automation tools, and Claude or ChatGPT handles the reading and drafting.

Who Should Own the Automations Once They Are Built?+

You should. If an agency or a tool holds the logic and you cannot edit or export it, ask what happens on the day you stop paying.

Copy the Pattern and Keep the Logic Yours

Each of these 15 workflows follows the same pattern: a trigger, rules for most steps, AI where the input is messy, a log, and a person at the decision that matters. Pick one from the team that loses the most hours, write its SOP, and ship the plain version before adding anything clever.

The part that decides whether it lasts is who owns it. When we build the shared AI structure for a team, the data sits in the client’s own database, the SOPs live as skill files on their own server, and Claude reaches both through a custom MCP server. If they leave, the system goes with them and keeps working.

Ready to pick your first two workflows?

Book a call. We will look at where your team’s hours go, and you keep the plan whether or not we work together.

Book a call →

Book a call · 30 minutes

Want this running inside your business?

In 30 minutes we map where your data lives, the first thing worth automating with the hours and dollars behind it, and what 30 days would look like. You keep the plan either way.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *