Nobody buys a house and never looks at it again. You fix the leaking tap, repaint the wall, and once in a while you check whether the foundations are still sound. A Salesforce org is the same. Most teams build it with care, then spend years adding rooms: a new field here, a new automation there, a new app for a team that needed it urgently.
Then one day something feels off. Reports are slow. Nobody trusts the numbers. A simple change takes weeks because nobody is sure what it will break. And now someone wants to add AI on top.
This post explains what a Salesforce health check is, in plain language, how to spot the warning signs, and gives you a five-minute self-test you can run today.
What a “health check” actually is
A health check is a structured look at how your Salesforce is set up and used today, compared with how it should be. It is not an audit to find someone to blame, and it is not a rebuild. It answers three simple questions:
- Is it working? Do people get what they need from it?
- Is it safe? Are the right people seeing the right data?
- Can it grow? Can you add new things, including AI agents, without breaking what exists?
Think of a home inspection. The inspector does not repaint your walls. They tell you what is fine, what needs attention soon, and what is urgent.
Five warning signs your org needs one
1. Nobody trusts the reports. Two people pull the same number and get different answers. This usually points to duplicate records, inconsistent fields, or filters that nobody remembers setting.
2. Everything is slow. Pages take time to load, reports time out, or a process that used to take seconds now takes minutes. Over the years, layers of automation and customization often pile up.
3. Nobody knows what a field is for. If you have dozens of fields and no one can explain half of them, people will fill them in randomly or skip them, and the data gets worse.
4. Changes feel risky. When a simple edit makes your admin nervous because “it might break something,” that is a sign the setup has become tangled.
5. People work around Salesforce. If the real information lives in spreadsheets, chats and inboxes, the org is not doing its job. Usually this means it no longer matches how people actually work.
If you recognized two or more of these, a health check is likely worth your time.
Why this matters even more with AI
AI agents work with what is in your org. They read your records, follow your rules, and act on your data. If the data is inconsistent and the setup is tangled, an agent will inherit that, and it will sound confident while doing so.
In other words, the health of your org sets the ceiling for what AI can do for you. Many teams find that fixing a handful of basics does more for their AI results than any change to the agent itself.
The five-minute self-test
Answer yes or no. Count your “yes” answers.
- Do people on your team trust the numbers in your main reports?
- Can you name who owns each major part of your Salesforce setup?
- Are your key records (accounts, contacts, leads) mostly free of duplicates?
- Can someone explain, in a sentence, what your main automations do?
- Do your pages and reports load in an acceptable time?
- Do you know which licences are used and which are not?
- Are people given access only to the data they need for their role?
- Do new starters know how to use Salesforce without lots of hand-holding?
- Do you have a way to test changes before they go live?
- Do you review your setup at least once a year?
How to read your score
- 8 to 10 yes: Your org is in good shape. Keep reviewing it each year.
- 5 to 7 yes: A few gaps. A short, focused check would likely pay off.
- 0 to 4 yes: Worth a proper health check before you build anything new on top.
This is a rough guide, not a diagnosis. It is meant to get a conversation started inside your team.
What a health check usually covers
The exact scope depends on your org, but most checks look at:
- Data quality: duplicates, missing information, and how consistent the fields are
- Automation: what runs, what overlaps, and what is no longer needed
- Security and access: who can see and change what
- Performance: what is slowing things down
- Usage: what people actually use, and what they ignore
- Readiness for what is next: whether the setup can support new tools, including AI
You should end up with a short, ranked list: what to fix now, what to fix soon, and what can wait.
What to do with the results
Resist the urge to fix everything at once. Pick the two or three items that cause the most pain, fix those first, and measure the difference. Then repeat. Small, steady improvements beat a big clean-up that never finishes.
Common questions
How long does a health check take? It depends on the size and age of your org. A smaller org can be reviewed fairly quickly, while a large, long-running one takes longer.
Will it disrupt my team? A health check mostly looks at your setup, so it should not interrupt day-to-day work. You will need some time from your admin and a few key users.
Do we need to do it before adding AI? Not always, but it is wise. At minimum, check the data and settings your first agent will use.
How often should we do one? Many teams find a yearly check enough, with an extra one before a big change, such as a new product or an AI rollout.
Can our own admin do it? Often yes, for a first pass. An outside view helps most when your admin is stretched, or when you want a second opinion on a tangled setup.
Our take
A healthy Salesforce org is not a perfect one. It is one where people trust the data, changes are safe to make, and there is room to grow. Checking it once in a while is far cheaper than finding out the hard way.
If you would like a second pair of eyes on your org, we would be happy to talk. Aekot is a Salesforce consulting and Agentforce implementation partner.