# Ali Arsanjani

Ali Arsanjani writes and speaks about enterprise AI, with a focus on agentic systems that can carry out business and technical workflows. His posts discuss agent architecture, security, governance, and how AI connects to tools and enterprise software.

- Profile: https://b2binfluencer.marketing/creators/ali-arsanjani/
- LinkedIn: https://www.linkedin.com/in/ali-arsanjani
- LinkedIn followers: 28,596
- Median of last 8 posts: 26 reactions, 1 comments (checked 2026-11-02)
- Topics: artificial-intelligence, agentic-ai, enterprise-ai
- Based on 9 dated posts, latest 2026-10-02

## Summary

Ali Arsanjani is most useful for explaining enterprise agent architecture, controls, and integration in practical terms.

- Best for: Enterprise AI platform or technical content briefs about agentic systems and governance.
- Not for: Consumer brand campaigns, sponsorship products, or briefs needing verified performance claims.
- Check first: Confirm audience demographics, sponsorship terms, and any verified performance evidence before contacting.

### Takeaways

- A plugin includes skills, MCP servers, rules, lifecycle hooks, and custom subagents.
- Agent Compute Engine uses agent gateway, registry, SPIFFE identity, and OpenTelemetry observability.
- Governance should be built into the agent runtime, not added as policy.

## Main ideas

- **Reliable long-horizon agents are the real frontier, not bigger models**: Ali Arsanjani argues that the hardest architectural problem is moving from single-turn reasoning to reliable autonomous work over long horizons. Earlier models handled text, vision, and audio, but production uses such as autonomous code refactoring and live defensive cybersecurity were held back by context degradation, compound error cascades, and brittle verification loops. The direction Ali Arsanjani points to is directed test-time computation, continuous context coherence, and closed-loop domain verification instead of raw parameter scale.
- **Governance belongs inside the agent runtime**: Ali Arsanjani argues that giving agents access to enterprise content cannot be handled by bulk indexing, because that creates blind spots in permissions, auditability, and retention. Governance has to be architected into the agent runtime. The alternative Ali Arsanjani describes is typed, auditable, least-privilege retrieval with active access controls, retention rules, and provenance enforced while the agent runs.
- **Interoperability should be named, not assumed**: Rather than saying systems are integrated, Ali Arsanjani names the connective standards. The posts cover Model Context Protocol servers with built-in OAuth and scoped permissions, Agent2Agent connectivity that lets specialised agents discover and work with each other, and systems such as ServiceNow's Action Fabric that bridge boundaries for end-to-end execution. The reasoning is that agents only collaborate across vendors when the connection method is explicit.
- **Translate agentic AI into changed work for specific functions**: Ali Arsanjani tends to describe what changes inside a named function instead of making a general platform claim. In the ServiceNow and Google Cloud post, helpdesk agents triage incidents, evaluate change risk, and route tickets; site reliability engineers investigate alert storms and configuration dependencies; employees resolve service and HR requests through guided self-service; and industry workflows cover retail, telecom, and CRM from quote-to-cash to network inventory. The reasoning is that buyers need to see the changed job, not just the model.
- **Make agent integration a packaged, versioned object**: Ali Arsanjani argues that wiring an agent into production tools was too fragmented: teams manually configured Model Context Protocol endpoints, environment variables, custom skills, and config files across repositories. The fix is to package integrations as versioned plugins. Each plugin is defined by a plugin.json manifest with five parts: skills loaded through progressive disclosure, MCP servers, rules as persistent guardrails, lifecycle hooks that run outside the model loop, and custom agents with isolated contexts.
- **Machine fluency is not understanding, and that has governance consequences**: In one argumentative post, Ali Arsanjani says the central risk is not that machines fail to become intelligent. It is that people, seduced by fluent generated text, confuse machine fluency with internalised understanding. Skipping the messy, iterative work of synthesis and problem formulation removes the cognitive capacity needed to understand, direct, and govern the systems being deployed.
- **Sessions should teach a decision, not just announce a talk**: Ali Arsanjani promotes speaking sessions by naming the decision problem and stating what attendees will learn. The Oracle AI World post gives the date, venue, and session title, 'Ask Your Data Anything: Oracle AI Database Agent Across Every Cloud Assistant'. The governance session lists three takeaways: integrating Google Cloud's agent stack with Box through A2A and MCP, moving from bulk indexing to typed and auditable retrieval, and enforcing access controls, retention rules, and provenance at runtime.

## Work to read

- [Announcing Gemini 4 Argon](https://www.linkedin.com/posts/ali-arsanjani_gemini-4-argon-inside-googles-frontier-activity-7511160374801399808-M46F)
- [Our earnings report: the core AI strategic takeaways](https://www.linkedin.com/posts/ali-arsanjani_our-earnings-report-the-core-ai-strategic-activity-7486339282316500992-_VUw)
- [Google Antigravity's Plugin Marketplace: what a plugin contains](https://www.linkedin.com/posts/ali-arsanjani_the-ai-workspace-for-people-agents-mondaycom-activity-7521838443405172737-vzFx)
- [ServiceNow and Google Cloud: agentic AI in everyday operations](https://www.linkedin.com/posts/ali-arsanjani_agenticai-servicenow-googlecloud-activity-7521568313559240704-lz6e)
- [Balancing governance with autonomous agents (Google Cloud and Box MCP)](https://www.linkedin.com/posts/ali-arsanjani_ready-to-balance-agent-autonomy-with-enterprise-activity-7522756806990036992-VqTx)
- [Google Cloud Agent Compute Engine: isolating agent sandboxes](https://www.linkedin.com/posts/ali-arsanjani_google-cloud-agent-compute-engine-ace-activity-7520518429611827201-GSSZ)
- [The central risk of our era is not machine intelligence](https://www.linkedin.com/posts/ali-arsanjani_the-central-risk-of-our-era-is-not-that-machines-activity-7516887846264356864-iM25)
- [Speaking at Oracle AI World: asking your data anything](https://www.linkedin.com/posts/ali-arsanjani_im-excited-to-speak-at-oracle-ai-world-on-activity-7515823982013468672-wZR5)

## Brand relationships

- **Google Cloud** (employment)
- **Oracle** (disclosed_partnership)
- **Box** (disclosed_partnership)
- **ServiceNow** (mention)

## Partnerships

No partnership or sponsorship offering is documented in the material reviewed for Ali Arsanjani. The nine posts read here contain no sponsor policy, rate card, media kit, audience specification for advertisers, or published route for brands to propose a paid collaboration. What the material does show is a working pattern that affects how a buyer should plan. Ali Arsanjani writes vendor-aligned technical commentary about Google Cloud products and partner integrations, including Antigravity plugins, Gemini, Agent Compute Engine, and a joint ServiceNow and Google Cloud agentic workflow announcement, and posts about Box and Thales work in the same vein. Ali Arsanjani also appears publicly as a conference speaker: an Oracle AI World session on an AI Database agent, October 25–28 at the Venetian in Las Vegas, and a Google Cloud and Box MCP session on governance for autonomous agents that carries a registration link. Those are speaking and co-marketing appearances, not a purchasable sponsorship product. A brand planning a technical content or speaking engagement should therefore expect to negotiate scope, deliverables, disclosure, and review terms directly and from scratch, rather than selecting from a published menu. Treat this as no documented offer in the reviewed material, not as a claim that sponsorships are never accepted.

## Alternatives

- Itai Tevet: Choose Itai Tevet when the audience is security operations leaders and the session has to connect autonomous AI to running security operations in production, not just to model capability. Both reviewed posts take the question a platform buyer asks right after a frontier release — if the labs keep shipping better defensive models, what does the security operations layer add? — and answer it with operational specifics: running on every alert rather than a demo set, decisions in seconds while the alert still matters, deterministic behaviour across thousands of investigations, and reviewable reasoning when someone asks why. The same post lists evidence a model cannot produce on its own, including memory and network forensics, file and code analysis, sandboxing and threat intelligence, then organisational context such as which asset matters and what normal looks like, plus a feedback loop back into detection engineering. The second post carries that into a regulated setting through a named customer conversation about low-severity alerts now analysed immediately, escalation within minutes, and continuous purple-team testing. For a buyer who needs proof that autonomous execution survives contact with a live queue, this is closer to the decision than a component walkthrough.
- Sundar Pichai: Choose Sundar Pichai when the campaign needs launch-scale announcements and a commerce or retail AI story. Both posts are first-person product announcements rather than analysis. One describes the Gemini 3 launch for developers and enterprise buyers, naming surfaces such as Vertex AI, Gemini Enterprise, the Gemini API, AI Studio, Antigravity and Gemini CLI, and naming early users including Replit, Shopify and Thomson Reuters. The other reports a retail keynote that introduced the Universal Commerce Protocol with named collaborators Shopify, Etsy, Wayfair, Target and Walmart, native checkout coming to Google surfaces including AI Mode in Search and Gemini, a new Gemini Enterprise for Customer Experience in preview, and drone delivery expansion with store counts, a launch city and a reach estimate. For a brief whose value is being attached to a major product moment and a partner ecosystem, and whose reader question is what the platform announced and who is behind it, this alternative delivers something Ali Arsanjani's posts do not attempt.
- Justin Hardy: Choose Justin Hardy when the brief shifts from an engineering audience to marketing and GTM leaders and the question becomes what autonomous, tool-using models let a marketing team do. The Argon post reframes a model release for marketers and names the applications directly: combining CRM, sales calls, product data and campaign performance into GTM intelligence; diagnosing funnels across objections, leaks and segment differences; mining webinars, interviews and long video for hooks and campaign angles; turning evidence into briefs, hypotheses and test plans; and keeping ICPs, brand rules, proof and pricing as reusable cached context. The second post gives the same audience an operating method rather than another opinion, with a first-party insight library defined field by field and a five-day collect, clean, cluster, prioritise, activate loop that ends in named outputs such as a post, landing-page copy, an FAQ and sales enablement. For a brief that wants a practitioner session on applying agentic AI to marketing decisions, this is the closest match in the set.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/