Agentforce Readiness 47-Point Checklist (2026)

70% of Salesforce orgs fail Agentforce readiness on first scan. The same patterns show up across mid-market and enterprise: empty Lead.Rating, 14 Integration Users with admin profile, 282 automations stacked on Opportunity, Process Builder rules from 2019 still firing.

This is the checklist top teams run before they commit to an Agentforce launch budget. Four dimensions, 47 specific checks. Skim in 15 minutes. Run the free Agentforce readiness audit if you want all 47 scored automatically with a 24-hour fix plan.

The four dimensions to score

The benchmarks

• Industry average: 38/100 across the 1,000+ orgs we scan
• Top 25% threshold: 71/100 (the bar most teams should aim for)
• Top 10% threshold: 84/100 (orgs that ship Agentforce with zero remediation)

Above 70 is the minimum for a smooth launch. Below 50, pause the rollout by 30-60 days and run a remediation sprint first.

Dimension 1: Data Quality (30% weight)

The largest weight because empty fields cause agents to hallucinate the values they need.

1. Lead.Rating populated above 70%. Median is 45%. Below 70%, lead routing agents stop working reliably.
2. Account.Industry above 80%. Territory and routing depend on this. Blank on 31% of accounts typical.
3. Opportunity.NextStep populated on all open Opps. Pipeline agents depend on this string.
4. Contact.Email validated and unique. Email agents misbehave with malformed or duplicate emails.
5. Required fields enforced via Validation Rule, not just page layout. Layout-only requirements bypass via API.
6. Duplicate Contact rate below 2%. Above 2%, agents pick the wrong record to act on.
7. Duplicate Account rate below 2%. Same risk on parent record.
8. Field utilization above 60% for every agent-touched custom field. Below 60% means dead field.
9. Picklist values cleaned and standardized. No "Closed Won" vs "ClosedWon" vs "closed_won".
10. Stale record rate below 10% (created or modified > 18 months ago without updates).
11. Data Cloud grounding fields above 90% populated. If using Data Cloud, agent grounding requires this.
12. No orphan records. Contacts without AccountId, Cases without ContactId, etc.

Dimension 2: Process Clarity (25% weight)

A process humans navigate ambiguously is one an agent cannot navigate at all.

13. Every Opportunity stage has explicit entry criteria. Documented, not "the AE knows".
14. Every Opportunity stage has explicit exit criteria.
15. Stage skip rate below 15%. If 31% of deals skip Needs Analysis, the agent learns to skip too.
16. Rework rate below 20%. Loop-backs from later stages confuse pipeline forecasting.
17. Documented owner for every active Flow. Not "Admin". A named person.
18. Documented purpose for every active Flow. One sentence of what it does and why.
19. Lead Qualification has a single defined entry point. Not "wherever the rep wants".
20. Renewal handoff from Sales to Success documented. Agents working renewals need the trigger.
21. Case escalation criteria documented and enforced. Support agents need unambiguous escalation rule.
22. No undocumented flow exceptions. "Except when the customer is enterprise" must be in the flow.

Dimension 3: Permission Hygiene (20% weight)

The agent inherits whatever permissions its runtime user has. Most orgs fail this dimension on first scan.

23. Profile count below 25. Sprawl correlates with permission leakage.
24. No more than 2 Integration Users with System Administrator profile. Median is 14.
25. Agent runtime user has a least-privilege custom profile. Not "Standard User", not "System Administrator".
26. Permission sets used in place of profiles for one-off access. Profiles for baseline only.
27. Fewer than 5 stale permission sets (no users assigned in 12+ months). Median is 234.
28. No inactive users consuming licenses. Median is 62 inactive users still licensed.
29. MFA enforced on all human users.
30. API access scoped per integration user. Each integration has its own user with its own permissions.
31. Connected apps reviewed in the last 12 months.
32. Apex classes that bypass sharing (without sharing) reviewed and justified.
33. Sensitive fields (PII, financial) flagged and access-restricted.

Dimension 4: Automation Overlap (25% weight)

The #1 AI killer in our scoring engine. Agents cannot operate on top of conflicting automation.

34. No more than 5 active Flows on a single object. Median Opportunity has 14. The full 282-automation count includes Triggers, Workflow Rules, and Validation Rules.
35. No Workflow Rules firing on objects that also have active Flows. Pick one mechanism per object.
36. No Process Builder processes still active. Legacy. Migrate to Flow.
37. Apex triggers do not duplicate Flow logic. Race condition risk if both write same field.
38. One trigger per object (one-trigger framework pattern). Multiple triggers compound race risk.
39. Validation rules execute before Flows that depend on them.
40. No Flows in Draft status that should have been activated.
41. Subflow call depth below 4. Deep nesting is hard for the agent to reason about.
42. No silent Flow failures in the last 30 days. Check Flow error logs.
43. Apex governor limit headroom above 30% on all triggered automation.
44. No hardcoded IDs in Apex referenced by automation. They break on sandbox refresh.
45. No SOQL queries in for-loops. Governor limit risk pattern.
46. No DML in for-loops. Same risk category.
47. All flow paths tested via Apex unit test or sandbox dry-run.

How to score yourself

Each check passes (1 point) or fails (0 points). Total possible: 47. Then:

The orgs that score 40+ are the orgs that ship Agentforce on time. The orgs that score below 24 are the orgs that hit blockers mid-deployment and miss the launch date.

Run it automatically

The 47 checks above are what we score in the free Agentforce Readiness Audit. You can do it manually, or let the agent score it in 10 minutes via read-only OAuth. Either way, do not commit to an Agentforce rollout date until you have it cleared.

For the day-by-day workflow on lifting a failing score from 41 to 78 in 7 days, see How efficient Salesforce teams audit their org in 7 days.