Salesforce keeps making it easier to turn on AI.
That does not mean your business is ready to use it.
The button is the easy part. The hard part is deciding what the AI should do, what information it can trust, what it is allowed to touch, what happens when it gets something wrong, and whether the result will be worth the time and cost.
This matters even more as Salesforce AI moves beyond suggesting an email or summarizing a record. An AI agent may retrieve information, update records, trigger a flow, answer a customer, or complete a series of actions. The more it can do, the less useful “Let’s turn it on and see what happens” becomes as an implementation strategy.
AI readiness is not a product setting. It is the business’s ability to give AI a clear job, reliable context, appropriate boundaries, and accountable ownership.
Before you enable another Salesforce AI feature or begin an Agentforce project, answer these seven questions.
1. What exact job are we asking AI to do?
“Help sales” is not a use case.
Neither is “improve productivity” or “use Agentforce.” Those are ambitions. A usable AI project begins with a specific job performed for a specific person at a specific point in a process.
For example:
- Summarize the last 90 days of account activity before a renewal call
- Draft a follow-up email after a discovery meeting using approved product information
- Answer a customer’s order-status question after verifying identity
- Identify inbound leads that meet agreed qualification criteria and route them to the right team
Now the business can evaluate what data the feature needs, what actions it should take, which exceptions matter, and how success will be measured.
The best first use case is often not the flashiest one. It is a narrow, repetitive task with enough volume to matter and an outcome you can verify. If the process is poorly defined, full of exceptions, or different every time, adding AI may only help the confusion move faster.
Ask: Can we describe the job, user, trigger, desired outcome, and stopping point in a few sentences?
2. Does the process work before AI gets involved?
AI does not remove the need for process design. It makes weak process design harder to ignore.
Imagine asking an agent to move an opportunity forward when nobody agrees what must happen before a deal changes stages. Or asking it to recommend a discount when pricing rules live partly in Salesforce, partly in a spreadsheet, and partly in a sales manager’s head.
The agent needs more than instructions that sound good in a meeting. It needs rules that hold up in real situations.
Map the current process. Identify who owns each decision, which inputs are required, what the normal path looks like, and where exceptions go. If the team cannot agree on those basics, the AI project is not ready for configuration. It is ready for a business-process conversation.
That is not a delay. It is the work that prevents an impressive demo from becoming an unreliable production tool.
Ask: If a capable new employee followed our documented process, would they know what to do without guessing?
3. Is the data fit for this use case?
Your entire Salesforce org does not need to be spotless before you begin. The data required for this particular job does need to be trustworthy enough for the decision or action you are handing over.
That distinction matters.
Salesforce defines AI-ready data as accessible, complete, contextual, compliant, and correct. In practical terms, that means asking whether the right records and documents exist, whether they are current, whether important context is missing, and whether the AI can distinguish an approved source from an outdated one.
A service agent grounded in old policy documents can answer confidently and still be wrong. A renewal assistant cannot reliably surface risk when contract dates are missing. A sales assistant cannot summarize the relationship accurately when half the meaningful activity lives outside Salesforce.
Do not begin by launching a vague, org-wide “data cleanup.” Start with the use case. Name the critical fields, records, knowledge articles, documents, and connected systems it requires. Then evaluate those sources against the actual consequence of an incorrect or incomplete answer.
Ask: What information must be correct for this feature to be useful, and how will we know when it is not reliable enough to proceed?
4. What can the AI see, and what can it do?
Access is not a setup detail to resolve at the end.
An AI feature may need to read a case, search knowledge, update an opportunity, send a message, call a flow, or reach into another system. Each additional source and action expands both its usefulness and its risk.
Salesforce describes Agentforce security as a shared responsibility. The platform supplies the foundation, but the customer is still responsible for configuring access, permissions, and agent-specific controls. The safest starting point is least privilege: give the AI only the data and actions required for the approved use case, not broad access just in case it becomes useful later.
Review object access, field access, record visibility, connected systems, available actions, and the identity under which those actions run. Pay special attention to sensitive customer data and actions that create, change, disclose, or delete information.
The important question is not merely, “Can the agent do this?” It is, “Under exactly which conditions should it be allowed to?”
Ask: If this feature used every permission we give it, would we still be comfortable with the result?
5. What could go wrong, and where does a human step in?
Every worthwhile AI use case has a failure mode.
The AI might use outdated information, misunderstand intent, expose something it should not, take an incorrect action, or produce an answer that sounds more certain than the source material deserves. The point of risk planning is not to imagine every bizarre possibility. It is to identify the failures that would matter most and design for them before launch.
Consider the people affected, the sensitivity of the data, the reversibility of the action, and the cost of being wrong. Drafting an internal call summary is not the same risk as changing a contract term or answering a customer about a refund.
Higher-impact uses need stronger controls. That may include approval before action, clear disclosure that AI is involved, confidence thresholds, restricted topics, audit trails, and a defined path to a qualified person. Salesforce’s responsible AI guidance specifically emphasizes human review for high-impact decisions and continued monitoring after deployment.
“Human in the loop” should not mean “someone will probably notice if things get weird.” Name the person, trigger, and response.
Ask: Which outcomes require review, escalation, correction, or an immediate stop?
6. Who owns the feature after launch?
AI is not a one-time configuration that can be handed a small plant and left alone near a sunny window.
Business rules change. Products change. Knowledge articles age. Users ask questions nobody anticipated. New failure patterns appear only after real people interact with the feature.
Someone needs to own business performance, not just technical uptime. That owner should review usage, task completion, escalations, incorrect answers, user feedback, data quality, and consumption. They also need the authority to update instructions, fix source content, adjust permissions, retrain users, or pause the feature.
Salesforce’s own agent-development guidance treats deployment as one stage in a larger lifecycle that includes testing, monitoring, analytics, and continuous refinement. That is a useful expectation to set with leadership before the pilot begins.
Choose the owner before launch. “Salesforce team” is a department, not an accountable name.
Ask: Who reviews performance, how often do they review it, and what can they change when the feature misses the mark?
7. What result would make this worth it?
AI ROI cannot be measured with enthusiasm.
Define the baseline before the feature changes it. How long does the task take today? How often does it happen? What does an error cost? How much work reaches completion? What is the current customer or employee experience?
Then choose a small set of measures tied to the job. That could include time saved per case, faster first response, fewer manual touches, improved completion rate, lower escalation volume, or better data capture. Pair efficiency with quality so the team does not celebrate faster work that creates more cleanup later.
Include the full cost. Agentforce offers several buying models, including usage measured through Flex Credits, and Salesforce provides near-real-time consumption information through Digital Wallet. Licensing or credits are only part of the investment. Add implementation, data preparation, testing, monitoring, maintenance, training, and the human time required to review exceptions.
A pilot does not need a perfect financial model. It does need a definition of success strong enough to support a continue, change, or stop decision.
Ask: What measurable improvement are we buying, what will it cost to operate, and when will we decide whether to scale it?
Readiness does not mean perfection
You do not need to solve every Salesforce problem before using AI. You do need enough clarity to understand which problems could affect the use case you selected.
If you can answer these seven questions, you are in a much better position to run a focused pilot:
- What exact job will AI perform?
- Does the underlying process work?
- Is the required data fit for purpose?
- What can the AI see and do?
- What are the material risks and human checkpoints?
- Who owns performance after launch?
- What measurable return would make it worthwhile?
If several answers are still “we have not decided,” the next step is not another feature toggle. It is an AI-readiness plan.
Free Thinkers Consulting’s AI Readiness assessment evaluates the data, security, and processes behind your Salesforce AI and Agentforce plans. You leave with a clear roadmap for what to fix, what to test, and where AI can create real value without introducing risk you did not intend to buy.