Agentic AI Use cases

Twenty use cases, five chains, one way of building them.

Five end-to-end chains run a manufacturer, and in each the market is deploying three or four agentic use cases now.

END-TO-END CHAINUSE CASES THE MARKET IS DEPLOYING NOWON THE MAPOrder-to-CashCash application andmatchingCollections anddunningDisputes anddeductionsOrder intake andblocked orders161 more rolesdesigned, configurableProcure-to-PayInvoice matching andexceptionsSourcing andtail-spendnegotiationPO change andcancellationruns in productionSupplier risk and endof life116 more rolesdesigned, configurablePlan-to-ProduceShortage triage andclear-to-buildForecast exceptionsand biasSafety stock andparametersSchedule repair fromthe floor179 more rolesdesigned, configurableRecord-to-ReportReconciliations andclose tasksJournal entryanomaliesAccruals for goodsreceivedFlux and variancecommentary133 more rolesdesigned, configurableIdea-to-MarketRegression triage anddebugEngineering changeimpactComponent end of lifeLaunch readinesschecks163 more rolesdesigned, configurableagent blueprint · 20 worked use cases lit, and one of the twenty runs, in production · 752 additional roles dashed · designed, yet to be built
Five chains as rows. The lit cards are the twenty use cases with their own pages; one of the twenty runs, PO change and cancellation, marked in the figure, in production at a high-tech manufacturer. The dashed card at the right of each row counts the additional roles designed on the blueprint. Market evidence checked 23 September 2026.
20
worked use cases, three or four per chain, chosen on evidence checked 23 September 2026
dated source
5
end-to-end chains, from the order to the cash and from the idea to the launch
blueprint
1
agent in production: purchase order change and cancellation, at a high-tech manufacturer
production · anonymised
960
agent roles designed on the map, yet to be built; 752 of them are additional capability on the chain pages
blueprint · designed, yet to be built
One way of building them

A role on the map becomes an agent the same way every time

The chains differ; the parts an agent is configured from, and the week that builds one, are the same.

Lima’s agent blueprint is a design of 960 agent roles across five end-to-end chains. It is the map of what Juno can be configured to do, and the first agents are built from it one at a time, the way the PO cancellation agent was.

Every use-case page follows one shape: a moment in the day, the evidence, the six stages, who does what at which level, the settings you would make and the roles it would draw on. “Would” is the honest tense on nineteen of the twenty pages; the twentieth describes the agent that runs. blueprint

Five chains

Where the money and the pain are, chain by chain

One line on each chain from its research note, and the use cases it lights.

The chain page carries the market evidence, the four use-case pages and the additional capability by phase. Sources at the foot of the page.

The twenty

Every use case, with its page

Four pages per chain; the one labelled production is the PO cancellation agent of chapter 5.

The additional roles are designed and yet to be built; each chain page lists them by phase. blueprint

Where to start

Where to start, by role

The chair you sit in decides the first use case; the week runs the same way for all of them.

RoleFirst use caseWhy start there
Supply planner (L. Tan)Purchase order change, cancellation and confirmation chasingThe one agent that runs. Her policy sentence is the starting point; her Monday shrinks from 2.5 days to 38 minutes on the showcase estate.
Buyer (D. Okafor)Supplier risk, sanctions and end-of-life monitoringSupply continuity is the top procurement priority for 2026 (The Hackett Group, 17 March 2026); the roles would start at A1 and A2.
Finance lead (J. Harrison)Cash application and remittance matchingThe median company auto-matches 70% of payments (The Hackett Group, 11 August 2025); the A4 scene of the gamut, audited after the fact.
ControllerAccount reconciliations and close task automation55% of accounting teams name reconciliations their top automation opportunity, while 5% call them highly automated (FloQast, 11 August 2026).
Data lead (A. Novak)Engineering change impact across BOM, stock and ordersOne change touches PLM, two ERPs, the planning suite and the supplier portal; the map across them is hers to build in the first week.
IT architect (S. Iyer)Invoice matching and exception clearingThe best-measured cost per document in any chain; write-back through the ERP’s released interfaces after a confirmed test write.

Whichever row is yours, the first week is the same: two source systems, one weekly decision, three people for two hours a day. The use case sets which tables are registered on the Monday, which question is asked on the Wednesday and which policy is written on the Friday.

In the story

Chapter 8 chooses the twenty; chapter 9 runs the week

Questions
Do the twenty use cases exist as agents today?

One does: purchase order change and cancellation, in production at a high-tech manufacturer. The other nineteen are designed on the blueprint; each would be configured from the same parts, simulated first and released at a level a manager signs.

Sources

Dated sources used on this page

  1. The Hackett Group, The Hackett Group Establishes AI World Class Finance Benchmarks (news release), 15 July 2026 (checked 23 September 2026) · https://www.thehackettgroup.com/the-hackett-group-establishes-ai-world-class-finance-benchmarks/
  2. WEX, What does it cost to process an invoice? AP benchmarks every finance team should know (citing Ardent Partners 2025), 20 July 2026 (checked 23 September 2026) · https://www.wexinc.com/resources/blog/what-does-it-cost-to-process-an-invoice-ap-benchmarks-every-finance-team-should-know/
  3. The Hackett Group, Supply Chain AI Adoption Becomes Pervasive as Cost and Modernization Pressures Intensify (2026 Supply Chain Key Issues Study), 14 May 2026 (checked 23 September 2026) · https://www.thehackettgroup.com/the-hackett-group-supply-chain-ai-adoption-becomes-pervasive-as-cost-and-modernization-pressures-intensify/
  4. AEMT (summarising the Siemens True Cost of Downtime 2024 report), The True Cost of Downtime 2024: A Comprehensive Analysis, 1 August 2024 (checked 23 September 2026) · https://www.theaemt.com/resource/the-true-cost-of-downtime-2024-a-comprehensive-analysis.html
  5. ISG (Ventana Research), Research Reveals the Importance of Technology in Shortening the Close, 12 December 2023 (checked 23 September 2026) · https://research.isg-one.com/analyst-perspectives/research-reveals-the-importance-of-technology-in-shortening-the-close
  6. Siemens Digital Industries Software (Verification Horizons blog), Why First-Silicon Success Is Getting Harder for System Companies, 3 September 2025 (checked 23 September 2026) · https://blogs.sw.siemens.com/verificationhorizons/2025/09/03/why-first-silicon-success-is-getting-harder-for-system-companies/
  7. Semiconductor Engineering (reporting the 2024 Siemens EDA and Wilson Research Group Functional Verification Study), First-Time Silicon Success Plummets, 27 March 2025 (checked 23 September 2026) · https://semiengineering.com/first-time-silicon-success-plummets/
  8. The Hackett Group, The Hackett Group Reports Rapid Progress in Procurement's AI Agenda (2026 Procurement Key Issues Study), 17 March 2026 (checked 23 September 2026) · https://www.thehackettgroup.com/the-hackett-group-reports-rapid-progress-in-procurements-ai-agenda/
  9. The Hackett Group, AI-Powered Software Is Solving the E-Payments Dilemma: The Hackett Group Reveals Top Cash Application Vendors (news release), 11 August 2025 (checked 23 September 2026) · https://www.thehackettgroup.com/ai-software-e-payments-hackett-cash-vendors/
  10. FloQast (via Yahoo Finance), FloQast Study Reveals Wide Gap Between the AI Ambitions of Accounting Teams and Their Ability to Execute, 11 August 2026 (checked 23 September 2026) · https://finance.yahoo.com/technology/ai/articles/floqast-study-reveals-wide-gap-130000189.html

Pick a use case, then book the week

Bring two source systems, one weekly decision and three people for two hours a day. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.