🏢Enterprise AI
Your Architecture Diagram Shows Parts Not Paths
When your AI system chooses its own path at runtime, a box-and-arrow diagram is just an expensive org chart. Here's what you're actually missing.
·8 min read
I design and build agentic AI systems for large enterprises — production software that runs on real data, makes real decisions, and holds up in production.
I work on Accenture's Advanced Technology Center team, embedded directly with client teams to turn ambiguous AI initiatives into working agentic systems across insurance, retail, financial services, and healthcare. I stay agnostic on framework and cloud provider seeking the "best of need" vs. the "best of breed" with something built well.
Agentic system architecture and enterprise AI application across industries
What you build around the model
From pilot to production across industries
Productivity, automation, and innovation
Recent writing on agentic architecture, enterprise AI, and production systems
My work centers on the gap between a promising model and a system a business can actually run: the context it draws on, the boundaries around what it's trusted to decide, the abstraction that keeps a solution portable across cloud providers, and the instrumentation that catches trouble before it reaches a customer.
As part of Accenture's Advanced Technology Center, I embed directly with client teams across insurance, retail, financial services, and healthcare to take an AI initiative from an open question to a system running in production. I try to stay agnostic about the tools: the best framework or hyperscaler is usually whatever the client already has in place.
This site is where I write about what I'm learning: the emerging trends, patterns, and ideas I see shaping enterprise AI, in my own words, independent of any client work.
Interested in what Accenture's Advanced Technology Center for Agentic AI does or want to explore a project together? Reach out to your local Accenture office.