The Agent Governance Gap: One Job Description, Two Different Careers
Sequoia co-led a $25 million round into Cymphony last week, a company whose entire pitch is that AI agents create new enterprise security risks.
Every ERP roadmap I have read this year has agents somewhere in it. Almost none name the person accountable for the risk.
Microsoft now describes Dynamics 365 as an agent-ready platform, with more than 650,000 MCP actions exposed across sales, finance, supply chain, HR, field service, customer service and project operations.
Agents operate inside the transaction layer of the business application, using the same data models, rules, permissions, security guardrails, and audit trails as any user of the system. That in itself is pretty dang powerful, and it is also a brand new area that very few organizations have actually staffed.
The roles I’m seeing this year now include responsibilities that simply were not on an ERP org chart two years ago. Some, but not all, include enterprise ontology and semantic layer ownership, agent and prompt governance, vector stores and retrieval architecture, and AI cost forecasting, which is now a real budget line item now.
Where I think this actually goes wrong is the job description. When a company finally writes it, deep Dynamics or NetSuite architecture experience lands on one side and enterprise ontology, knowledge graphs, and agentic frameworks land on the other.
Those two populations barely overlap today. After 25 years in this channel, I can tell you the person who has genuinely done both is rare enough that a search built on finding them will sit open for months.
I think it lands much better to split the role. Put the platform depth in one position, put the AI and data architecture in another, and make one of them accountable for agent governance in writing. Let them work with each other and learn from each other for the next couple of years, and then let’s talk. My answer will be different in 2028, I’m sure.
So I am curious. If your ERP roadmap includes agents over the next 12 months, who owns governance today, and is that written down anywhere?
If you are staring at that gap right now, I would genuinely love to talk it through with you, whether or not you ever choose to use our recruiting services.
Sources:
TechCrunch, “Sequoia doubles down on Cymphony as AI agents create new enterprise security risks,” September 9, 2026
Microsoft, “Microsoft Dynamics 365: An agent-ready business applications platform,” July 23, 2026 hashtag#MicrosoftDynamicshashtag#D365hashtag#NetSuitehashtag#ERPhashtag#AIAgentshashtag#NetSuiteRecruitinghashtag#MicrosoftDynamicsRecruiting
Every ERP roadmap I have read this year has agents somewhere in it. Almost none name the person accountable for the risk.
Microsoft now describes Dynamics 365 as an agent-ready platform, with more than 650,000 MCP actions exposed across sales, finance, supply chain, HR, field service, customer service and project operations.
Agents operate inside the transaction layer of the business application, using the same data models, rules, permissions, security guardrails, and audit trails as any user of the system. That in itself is pretty dang powerful, and it is also a brand new area that very few organizations have actually staffed.
The roles I’m seeing this year now include responsibilities that simply were not on an ERP org chart two years ago. Some, but not all, include enterprise ontology and semantic layer ownership, agent and prompt governance, vector stores and retrieval architecture, and AI cost forecasting, which is now a real budget line item now.
Where I think this actually goes wrong is the job description. When a company finally writes it, deep Dynamics or NetSuite architecture experience lands on one side and enterprise ontology, knowledge graphs, and agentic frameworks land on the other.
Those two populations barely overlap today. After 25 years in this channel, I can tell you the person who has genuinely done both is rare enough that a search built on finding them will sit open for months.
I think it lands much better to split the role. Put the platform depth in one position, put the AI and data architecture in another, and make one of them accountable for agent governance in writing. Let them work with each other and learn from each other for the next couple of years, and then let’s talk. My answer will be different in 2028, I’m sure.
So I am curious. If your ERP roadmap includes agents over the next 12 months, who owns governance today, and is that written down anywhere?
If you are staring at that gap right now, I would genuinely love to talk it through with you, whether or not you ever choose to use our recruiting services.
Sources:
TechCrunch, “Sequoia doubles down on Cymphony as AI agents create new enterprise security risks,” September 9, 2026
Microsoft, “Microsoft Dynamics 365: An agent-ready business applications platform,” July 23, 2026
hashtag#MicrosoftDynamics hashtag#D365 hashtag#NetSuite hashtag#ERP hashtag#AIAgents hashtag#NetSuiteRecruiting hashtag#MicrosoftDynamicsRecruiting