Find the idea.
Understand the evidence.
Research perspectives and practical workflow proposals across industries. Explore what has been studied, what is still uncertain, and how to test a useful first project.
Before you build an agent team, define one good workflow.
A practical way to choose between fixed workflows, tool-using agents, and specialist teams—starting with a decision your business can actually verify.
Read the perspectiveAgent architecture
Scroll to explore
Operations blueprint
Scroll to explore
Procurement agents should build the evidence before the shortlist.
How to turn quotes, delivery constraints and approval policies into a traceable comparison—without letting a model invent the winning supplier.
A healthcare scheduling agent needs a state machine, not a promise.
A careful administrative blueprint for proposed appointments, resource checks and staff confirmation, grounded in the FHIR scheduling model.
Commerce agents have to respect inventory truth.
Why available stock, reserved units and location matter more than a convincing sales reply—and how to design an exception workflow around them.
Let a solver plan routes. Let an agent explain the exceptions.
A logistics blueprint that separates constraint solving from conversational coordination, so proposed plans remain feasible and inspectable.
Running a pilot in your own cloud: exactly what IT has to do
Network paths, secrets, SSO, logging, data residency, and roll-back when ProcureAI or FinanceAI workers run in your account instead of a public trial.
Research to practice
Scroll to explore
From language to robot action: the boundary that matters.
What OpenVLA shows about learned robot policies, and why a first business pilot should separate task planning from physical execution.
Research agents should make hypotheses easier to challenge.
What Co-Scientist and ChemCrow suggest about tool-assisted research, and a proposed evidence workflow that preserves uncertainty and expert review.
Connected systems
Scroll to explore
Manufacturing agents need machine context before machine control.
A read-only incident-assistance blueprint that joins equipment signals with manuals and maintenance history, while keeping control boundaries clear.
Adding agents next to Coupa without re-platforming
Which Coupa objects to read first, where ProcureAI agents sit in the AP loop, what buyers see during a pilot, and how to scope read-only access before any write-back.
Read-only first: connecting agents to SAP S/4HANA
How to scope OData read access, stage sandbox mapping, run a batch pilot, and defer hold codes or invoice blocks until your AP organisation signs off.
Healthcare finance teams: agents that never touch the EHR
How hospital AP and shared services use ProcureAI on supplier invoices and POs today, what data stays out of clinical systems, and what a future clinical-adjacent agent would still refuse to do. HIPAA compliance is not offered by Stellitron today.
From the analysis archive
Research summary · sources listed
These earlier research summaries remain available for exploration. Sources and publication notes are on each article page; claims belong to the original authors. Proposed workflows are illustrations to evaluate, not customer deployments.
The analysis archive is temporarily unavailable. The research perspectives above are available to read.