We figured out how to build agents. Anyone can stand up an impressive single-team demo. The run is where it stalls: data that isn't ready, trust and governance left unresolved, integration that costs more than planned, and pilots that never become a live service.

Deployed is not the same as live. Live needs a named business owner, an accountable service owner, access and action boundaries, a support and rollback path, and a way to reassess when models, tools or context change. Those decisions can be named in advance, and that is where the bottleneck now sits: with us.

This session maps the run phase as an operating model. Choose the route first: adopt SaaS, combine it with shared context and controls, or build and resource a platform. Form and name the team that builds and the team that runs. Then run a shared agent platform with a named owner (identity, tool connections, runtime controls, evaluation, telemetry and cost, governed context) so the next squad inherits rather than rebuilds, with a Centre of Excellence feeding improvements back.

You'll leave with three steps to take one working pilot into live service.

Takeaways:
1. Name the business and service owners, with a mandate to act, before the build ends.
2. Agree what live use requires: business evaluation evidence, access controls, support, FinOps and rollback, and a process to reassess after change.
3. Make the next team easier to onboard: a shared platform with a named owner, and a Centre of Excellence that turns recurring needs into supported capabilities.

30 minutes (25 + 5 Q&A). Intermediate. For architects, platform and SRE teams, and engineering leads. Delivered at SREday London, 24 September 2026. Production operations session in the five-talk series.