Speaking twice at Dreamforce · Sept 15-17 →
Agentic systems layer

AI stack · Agentic systems

Agents that plan, call tools, and stop.

Agentforce when the work lives in Salesforce. A code agent or SDK when it does not. MCP and A2A so the pieces talk without a custom API each time. The first week is in the org, reading what already exists.

Get the written assessment

Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks

  1. 01Models · Claude, Gemini, OpenAI, Bedrock
  2. 02Agents · Agentforce, CrewAI, ADK, A2A
  3. 03Memory · Neo4j, Cognee, RAG
  4. 04Identity · IndyKite, SSO, entitlements
  5. 05Governance · policy, audit, human override

Questions

What buyers ask us.

Agentforce or a custom agent?
Agentforce when the records, the permissions and the people already live in Salesforce. A custom agent on an SDK when the seat is Slack, WhatsApp or another system. Many programs run both, with a control plane in front.
Do we need MCP or A2A?
MCP when an agent needs governed access to tools and data. A2A when agents from different vendors must hand work to each other. Neither is required for a first agent on one process.
How do you stop an agent doing something wrong?
Limits on steps and tools, an identity that inherits the user permissions, and a person on any write that commits the firm. Every run is logged so a reviewer can see why it acted.

The brief

Send the situation.

Name the process. We tell you which layer is missing.