Where Should a Business Start with AI Agents? (2026)

Most businesses should start with one read-only agent on one workflow, after a readiness score, not with a fleet and a keynote. McKinsey’s State of AI 2025 put 62% of organizations at least experimenting with agents and 23% scaling in at least one function. Experimenting is not a starting plan. A score and a single family is.

On June 17, 2026, AgentCore Harness reached GA (What’s New). That date is a hosting fact. It is not a green light. Agents Classic is in maintenance for new customers after July 30, 2026.

This is part 4 of AI Agents for Business. The interactive picker is Which eCommerce agent first?. The org-wide score is the readiness assessment.

First-party signals we reuse (not client KPIs) — Gateway ~180 ms → ~95 ms on a B2B CRM assistant (12 tools, ~8k turns/day) — Gateway post. Support-style AgentCore at 50K sessions/mo ~$791/mo platform + model (decision guide). Treat ~$791/mo as a floor to plan against, not savings.

Reproduce this — Fill ai-agent-readiness-checklist.md. Score each row 0/1/2. Total /30. Below 16: no write-capable agent this quarter. Then walk the decide tree. Interactive readiness: Agentic commerce readiness checker.

Opinionated take: if the score is under 16/30, start by fixing join keys, named APIs, and a human queue — not by picking a model. Trade-off: you delay the demo. You avoid a chatbot that refunds from a prompt.

The starting order we recommend

1. Score readiness /30 — data, integration, process, governance, priority. Flagship write-up: readiness assessment.
2. Pick one family — support, sales, operations, inventory, or knowledge — on the hub or the decide tree.
3. Week-one reads only — especially support. See how agents reduce support work.
4. One write later — after Policy, evals, and a named owner. Not a supervisor swarm.

FactualMinds is an AWS Select Tier Services Partner. We have no published AI-agent case studies. The decide tree and the checklist are the artifacts we can point at.

Default first family (and when to override)

What broke — Teams treated a shopping-agent PDP/API score as org readiness and attached writes. Detection: no owner, no goldens, no escalation on the first bad createReturn. Recovery: run the /30 checklist; stay on reads until 16+. That counter-case is published in the readiness post.

Named substitutes

• Score under 16/30 → fix data and ownership; readiness post. No writes.
• Cannot choose among families → decide tree, not a five-agent program.
• Want cost math before a family → how to evaluate opportunities and the ROI calculator.
• Want the automation map → 15 automations in the field guide — not this executive note.

If You Only Do One Thing

Open the decide tree after you have a /30 score. If you skip the score, you will pick the family that looked good in a vendor demo.

What to Do This Week

1. Fill the readiness checklist with one ops lead and one engineer in the same hour.
2. If the total is under 16, schedule data/API work. Do not book a write-capable build.
3. If the total is 16+, walk the decide tree and open one family page.
4. Write the week-one stop rule before anyone creates a harness.

What This Post Doesn’t Cover

It does not replace the decide tree’s branching questions. It does not score shopping-agent PDP readiness — that is a different field-guide post. It does not recommend a model or a vendor bake-off. We have not published a new “first family” census; 16/30, 62%/23%, ~180→95 ms, and ~$791/mo are the published figures we reuse.

Primary next step: Which eCommerce agent first?.