Who Owns a Custom AI Agent Project? Business, IT, and Compliance RACI

The Owner of a custom AI Agent project is the person Accountable for scenario ROI, voice/policy, and go-live gates—not “whoever knows the model best” or “whoever signed the PO.” Unclear ownership shows up as stale knowledge, unsigned boundary tables, and finger-pointing on incidents. This post gives a RACI across business, IT, compliance, and vendor, plus failure modes. Artifacts: /blog/custom-agent-delivery-artifact-checklist. Boundary tables: /blog/custom-agent-scope-boundary-in-contract. GeonAI delivers governable Agents; /agents are capability references only (not a public trial of 363+ presets). Email [email protected].

Why name an Owner first

• Knowledge and scripts change: without A/R, voice drifts within weeks
• Accounts and network sit with IT: business can decide, yet access never opens
• Red lines sit with compliance: veto-only roles leave boundary tables empty
• Vendors can deliver—they cannot forever make your business decisions

Recommended accountability model

Business Owner (primary Accountable) owns scenario ROI, user-facing voice, and scale decisions. IT owns platform, accounts, security, and observability. Compliance sets and samples red lines. The vendor delivers, hands over, and covers on-call only as contracted. Small teams may merge roles, but Accountable name and decision cadence must appear in the kickoff memo.

Sample RACI (paste into kickoff)

Legend: A=Accountable, R=Responsible, C=Consulted, I=Informed. Multiple R is fine; keep a single A—dual Owners often mean no Owner. Pilot metrics: /blog/custom-agent-30-day-pilot-metrics.

Three failure modes

• IT-only Owner: stable platform, business rejects voice and never updates KB → frontline bypasses the Agent
• Vendor-only Owner: black-box delivery, no enterprise takeover → paralysis when the contract ends
• Compliance veto-only: oral red lines, unsigned tables → go-live gate forever deferred

If sourcing already shows “no ops owner + no KPIs,” pause a large buy—see /blog/ai-agent-project-red-flags.

Minimum decision cadence

1. Kickoff week: name business Owner, backup, and weekly slot
2. Weekly: business reviews KB change queue; IT reports integration/incidents; compliance samples red-line cases
3. Gate nodes: business A signs before scale; IT/compliance R check tech and red-line boxes
4. After handover: vendor drops from A/R to C or contracted R; enterprise A stays put

How to brief GeonAI

Name the business Owner, decision cadence (e.g. “Tue 30 min”), and IT/compliance contacts. Email [email protected], /pricing, or Live chat. We align delivery to your RACI—we do not replace your Accountable.