The Agentforce license doesn’t make an org ready; the org makes the agent trustworthy. An agent inherits the estate exactly as it is — automation quirks, identity fragmentation, access sprawl — and amplifies whatever it finds. The readiness work is ordinary org work; the agent is why it finally gets funded.
The four prerequisites, in order of leverage
1. Automation on one engine. Agent actions compose with Flow. Logic still living in Workflow Rules and Process Builder is behavior the agent can trip over and you cannot easily extend. Migrate per object so save order survives.
2. Identity the agent can be grounded on. The same customer under three Accounts means the agent answers confidently from whichever record it hits — the failure mode that looks like success. Duplicate and matching rules on core objects come before any grounding conversation.
3. Access as the agent’s specification. The agent acts through a user context; whatever that context can reach, the agent can be induced to touch. Least privilege stops being hygiene and becomes the operating envelope.
4. Platform currency. Components below the API retirement line and UI still leaning on Aura and Visualforce decide whether the org can adopt agent capability on Salesforce’s cadence rather than its own backlog’s.
All four are measurable today — Horus Eye measures them as findings, with fix paths, rather than as an invented readiness score. And once the runway is cleared, the agent conversation starts from evidence.
