--- title: What Business Processes Should You Automate with AI? (2026) description: Automate the lookup pile first — not tax, capture, or labels. McKinsey found 62% experimenting with agents and 23% scaling; reuse the published ~$791/mo AgentCore floor at 50K sessions. url: https://www.factualminds.com/blog/what-business-processes-to-automate-with-ai-2026/ datePublished: 2026-08-31T00:00:00.000Z dateModified: 2026-08-31T00:00:00.000Z author: palaniappan-p category: AI Agents tags: ai-agents, ecommerce, operations --- # What Business Processes Should You Automate with AI? (2026) > Automate the lookup pile first — not tax, capture, or labels. McKinsey found 62% experimenting with agents and 23% scaling; reuse the published ~$791/mo AgentCore floor at 50K sessions. [McKinsey's State of AI 2025](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai) found **62%** of organizations at least experimenting with AI agents and **23%** scaling an agentic system in at least one function. That is not a reason to automate "everything repetitive." It is a reason to pick the processes an agent can take a **first pass** on — and leave the ones that already have a correct template alone. **On June 17, 2026**, Amazon Bedrock AgentCore Harness reached general availability ([What's New](https://aws.amazon.com/about-aws/whats-new/2026/06/amazon-bedrock-agentcore-harness-generally-available/)). **Agents Classic** is in maintenance for new customers after **July 30, 2026**. Those dates made a first production loop cheaper to host. They did not change which business processes are agent-shaped. This is part 1 of **AI Agents for Business** — five executive notes for operators who have not built an agent yet. The 64-part [eCommerce field guide](/resources/ecommerce-ai-agents/) is the library. [The commercial hub](/ai-agents/) is the door after this post. > **First-party signals we reuse (not client KPIs)** — Gateway server-side tools cut median tool round-trip **~180 ms → ~95 ms** on a B2B CRM assistant (12 tools, ~8k turns/day) — [Gateway post](/blog/amazon-bedrock-agentcore-gateway-server-side-tool-execution-2026/). Support-style AgentCore at **50K sessions/mo ~$791/mo** platform + model ([decision guide](/blog/aws-bedrock-agentcore-vs-amazon-q-enterprise-decision-guide-2026/)). Treat **~$791/mo** as a platform cost floor, not as savings a store booked. > **Reproduce this** — Score the process on [`ai-agent-readiness-checklist.md`](https://www.factualminds.com/examples/architecture-blog-2026/ecommerce-ai-agents-series/ai-agent-readiness-checklist.md) (0/1/2 per row, total **/30**). Below **16**: do not attach write tools this quarter. Series folder: [`ecommerce-ai-agents-series/`](https://www.factualminds.com/examples/architecture-blog-2026/ecommerce-ai-agents-series/README.md). **Opinionated take:** automate the **lookup pile** first — order status, policy, a reorder risk brief — not tax, capture, or labels. Trade-off: the first agent will not "close the ticket end-to-end." The alternative is an unsupervised write on a process that already had a correct answer. ## The filter: agent-shaped vs already-solved A process is agent-shaped when **all four** are true: 1. A human already does a first pass every week (tickets, a queue, a spreadsheet). 2. The facts live in named systems (OMS, WMS, help center, ERP) — not in one person's head. 3. The first pass is messy language or incomplete evidence, not a fixed formula. 4. Someone can own a wrong answer (a named queue, not "the AI team"). A process is **already-solved** when a template or state machine is correct: cancel windows, tax, payment capture, allocation, carrier labels. [Agents vs workflow automation](/blog/ai-agent-vs-workflow-automation-ecommerce-2026/) is the build note. This post is the executive cut: do not replace those paths. FactualMinds is an AWS Select Tier Services Partner. We help commerce teams find the first workflow worth an agent — after the filter, not instead of it. There are **no published AI-agent case studies** on this site. Proof is the field guide and the first-party platform numbers above. ## Five families, one first process The [AI Agents hub](/ai-agents/) groups work into five families. Pick **one process** inside one family — not a fleet. | Family | First process that is usually agent-shaped | Leave on the workflow | |--------|--------------------------------------------|------------------------| | [Customer support](/ai-agents/customer-support/) | WISMO and policy reads | Auto-refund, address change, chargeback language | | [Sales](/ai-agents/sales/) | Quote or reorder from **contract** price | List-price PDP as the quote | | [Operations](/ai-agents/operations/) | Daily priority brief | Warehouse rewrite, unsupervised PO send | | [Inventory](/ai-agents/inventory/) | Reorder **risk** brief | Sending the PO without a buyer | | [Knowledge](/ai-agents/knowledge/) | Join keys and catalog quality | A generic "research agent" with no store systems | > **What broke** — Teams that swapped a working carrier-status email template for a chat agent that "sounded helpful." The bot invented clock-time ETAs when `getShipment` and the carrier page disagreed. Detection: shoppers quoting ETAs that were not in the OMS. Recovery: cite tool evidence or escalate; do not average timestamps. The support control-plane note is [post 2 of the field guide](/blog/ai-customer-support-agent-ecommerce-2026/). ## Named substitutes when "automate it with AI" is the wrong brief - **Already a correct template** → keep the template; add search if people cannot find it. - **Fixed state machine (refund window, tax, capture)** → keep the workflow; agent returns a structured decision only. - **FAQ search with no tools** → that is a [chatbot](/blog/ai-agents-vs-chatbots-2026/), not an agent. Ship search. - **No named APIs, no owner, no approval queue** → stop. Run the [readiness assessment](/blog/ecommerce-ai-agent-readiness-assessment-2026/) before a model bake-off. ## If You Only Do One Thing List the ten processes that ate last week's calendar. Cross out every row that already has a correct template. Score the rest on the [readiness checklist](https://www.factualminds.com/examples/architecture-blog-2026/ecommerce-ai-agents-series/ai-agent-readiness-checklist.md). Take the highest-scoring **read** process to the [hub](/ai-agents/) — not a refund tool. ## What to Do This Week 1. Name one owner (ops or support) and one engineering counterpart. No owner → no agent. 2. Confirm the process has a named API or admin export. "We can screenshot Shopify" is not a tool. 3. Write the stop rule: what the agent must **not** do in week one. 4. Open the matching family page on [the hub](/ai-agents/). If you are still choosing among families, use [where to start](/blog/where-to-start-with-ai-agents-2026/). ## What This Post Doesn't Cover It does not score your org /30 — that is the [readiness post](/blog/ecommerce-ai-agent-readiness-assessment-2026/). It does not compare agents to chatbots in depth — that is [part 3](/blog/ai-agents-vs-chatbots-2026/). It does not publish a client "hours saved" number. We have not run a new first-party process census for this note; the Gateway latency and **~$791/mo** floor are the published benchmarks we are willing to reuse. AWS how-to stays in the field guide. **Primary next step:** [AI Agents hub](/ai-agents/). ## FAQ ### When should you NOT automate a process with an AI agent? Do not replace a process that already has a correct template or state machine — cancel windows, tax calculation, payment capture, allocation, and carrier label creation. Keep the workflow. Add an agent only at the messy decision point, such as ambiguous ticket text or incomplete evidence. ### What could go wrong if you automate money movement first? The model can call refund, cancel, or create-return with a bad amount, on a delivered order, or twice in one turn. Prompt instructions are not authorization. Return a structured decision to the workflow; put a human on anything that moves money. ### Is this the same as replacing Shopify Flow or an OMS? No. Hybrid is the default. Rules own money movement. The agent returns a decision. See the field-guide note on agents vs workflow automation — this post is the executive filter, not that build note. ### Does McKinsey's 62% mean we are late if we have no agent yet? No. The same survey puts scaling at 23% in at least one function. Most organizations are still experimenting. Being late to a chatbot on Admin API keys is not the same as being late to a governed first agent. ### Which process should a store pick first? Usually the lookup pile — WISMO and policy reads — if tickets repeat and the OMS API is named. Inventory reorder briefs are second when ATP is trustworthy. Do not start with merchandising writes or unsupervised refunds. --- *Source: https://www.factualminds.com/blog/what-business-processes-to-automate-with-ai-2026/*