Salesforce Health Check
Findings, not impressions: an objective analysis of your Salesforce org — what works, what doesn't and what it costs you. Without a single change to the system.
A Salesforce org that has been in use for two or three years rarely looks the way it did on the day it was handed over. Fields no one fills in pile up, along with automations that get switched off manually, reports no one opens, and habits that work around the system instead of using it. It all still works, just slower and more expensively.
Salesforce Health Check
from €2,900
Depending on the tier, from access being granted to delivery of the findings and a joint review.
Access is read-only. We change nothing in your system.
The report stays with you and can be used with anyone, not just with us.
If you move up to a higher tier within 30 days, you pay only the difference. For Health Check and Health Check + plan, we credit half the price against a project based on the findings, if you sign it within 90 days. Salesforce licenses are not covered by this analysis and are not included in the price.
Quick Review
€2,900
5 business days. For smaller systems, or when you want to know where you stand before a bigger decision.
- technical review of configuration, access rights and automations
- data quality: duplicates and empty fields
- the ten most important findings, ranked by priority
- a short joint review of the findings
Health Check
€5,900
10 business days. For a system that has been in use for two or three years and that people are starting to work around.
- everything in the Quick Review
- integrations and technical debt
- a half-day workshop with your team
- adoption: who uses the system and who works around it
- full findings by priority, with the consequence of each item
- joint review of the findings
Health Check + plan
€9,900
15 business days. Ahead of a bigger investment: a new product, Agentforce or a change of partner.
- everything in the Health Check
- target state of the system
- a phased improvement plan, with cost estimates
- data readiness for Agentforce and Data 360
- presentation of the findings and plan to management
We don't touch your system
The access we ask for is review-only. We don't change settings, delete fields or switch off automations, not even the ones that are obviously getting in the way. If something needs to change, it goes into the findings, and you decide when and who does it.
The reason is simple: an analysis that “fixes” a few small things along the way is no longer an analysis, but an undocumented change in production. And it is exactly such changes, one by one, that create the state we are measuring.
The findings work without us
You receive the report as a document that stays with you. It is written so that your internal team or any other partner can read it: every finding points to the place in the system it refers to and the consequence if it stays as it is.
If you decide afterwards to do nothing, you have an accurate picture of where things stand. If you decide to act — with us or without us — you have a prioritized action plan. That is the difference between an analysis and a sales pitch disguised as one.
Four steps to the findings
This is how a Health Check runs, over ten business days. The Quick Review skips the workshop, and Health Check + plan adds a roadmap after the findings.
-
01
Access and preparation 1–2 days
We get read access and a list of the systems connected to Salesforce. We also agree on who attends the workshop — usually the administrator, one person from sales and one from support.
-
02
Technical review 3–4 days
We go through the org: configuration, permissions, data, automations, integrations and technical debt. Everything we find is recorded with its exact location in the system, so each finding can be verified.
-
03
Workshop half a day
We sit down with your people and listen to how the work really flows: where the system gets bypassed, what's tracked in a spreadsheet next to it and what slows them down the most. This is usually where it becomes clear that the technical findings and day-to-day work don't tell the same story.
-
04
Findings and review 3–4 days
You receive a document with findings ranked by priority, and we go through it together. Each finding states the consequence if it stays as it is, because some are perfectly fine to leave.
What we need from you
The ten-day timeline only holds if these three things are in place from day one.
Read access
A user with view rights on the production org. No changes, but also no limits on what can be seen, otherwise the findings describe part of the system, not the system.
Half a day for the workshop
One session, three to four people. No preparation needed: we want to see how you work, not how you're supposed to work.
The people who use the system
Not just the administrator and the manager. A salesperson who enters opportunities every day sees what you can't see in the settings.
What comes after the findings
The findings are not the end but a prioritized action plan. Here is where they most often lead, and if they don't lead to us, they are still in your hands.
The system is fine, but nobody uses it
The most common finding. It doesn't call for development, but for training and a few changes that remove user resistance. It's covered by EQS Care, through a monthly pool of hours.
Too much has piled up to patch
Sometimes the cleaner move is to set things up from scratch and carry over only what's worth keeping. That is EQS Start, and these findings define exactly what gets carried over.
The problem is the data, not the settings
Duplicates, incomplete records and history left behind in the old system. Part of that is a job for migration, and part is solved with rules in the org itself.
Salesforce works, the process doesn't
A tool can't fix an agreement that doesn't exist. In that case business processes come first, and only then changes to the system.
What we review and what we don't
The analysis has a boundary, like every package of ours. This is the whole list, and the second list is just as binding as the first.
We review
- org configuration and architecture
- security settings and access rights
- data quality: duplicates, empty fields, invalid formats
- automations — which run, which overlap, which are switched off
- custom fields and objects that are no longer used
- integrations and everything that calls Salesforce from outside
- technical debt: custom code, outdated components, platform limits
- user adoption — who actually uses the system and who works around it
- business processes, through a workshop with your team
Outside the analysis
- any change to the system — the analysis is review-only
- fixing the findings — covered by EQS Care
- a fresh setup on an empty org — EQS Start
- data transfer from another system — migration
- review of the business processes themselves — Services section
- penetration testing and standards-based security audits
- license value assessment and negotiations with Salesforce
Frequently asked questions about the Salesforce Health Check
Which Health Check tier should we choose?
The Quick Review is for smaller systems or for a first look at where things stand. The Health Check is for a system that has been in use for two or three years and that users are starting to work around. Health Check + plan is for the moment before a bigger investment, because in addition to the findings you get an improvement plan with cost estimates. If you're not sure, we suggest a level on the first call — and sometimes that you don't need the analysis at all.
Do you change anything in our system?
No. Access is read-only: we don't change settings, delete fields or switch off automations. Everything that needs to change is in the findings, and you decide when and who does it.
When does a Health Check make sense?
When Salesforce has been in use for two or three years, when users work around it or keep things in spreadsheets next to it, before introducing a new product or Agentforce, and before changing your maintenance partner.
Do you run a Health Check even if EQS didn't implement our system?
Yes, and that's when we do it most often. We analyze any Salesforce system, and the findings are written so that your internal team or any other partner can use them.
Is the cost of the analysis credited toward a future engagement?
Yes, in two ways. If you move up to a higher tier within 30 days of receiving the findings, you pay only the difference: from the Quick Review to Health Check €3,000, from Health Check to Health Check + plan €4,000.
For Health Check and Health Check + plan, we deduct half the price of the analysis from an implementation or improvement project you sign within 90 days, provided the project addresses the findings and is worth at least three times the analysis. The deduction does not apply to fixed-price packages such as EQS Start, the monthly EQS Care or Salesforce licenses.
Request a Salesforce Health Check
Tell us how long you've been using Salesforce and how many users you have. On the first call we check whether you need the analysis at all. Sometimes the answer is no.