A fixed-scope review that shows Valley organizations where their Salesforce access, data and automation carry risk, and which fixes should come first.
Think of a Phoenix health check as a bounded audit: it describes your org exactly as configured today, without changing anything. With read-only access, we examine profiles, permission sets and sharing, measure duplicates and incomplete records, inventory automation and code, and interview a few users. The deliverable is a findings list ordered by risk and by the effort each fix needs. For servicing operations and healthcare organizations here, access and data-exposure findings usually rise to the top, followed by the automation debt that slows every change.
Finance and insurance is one of the council's target sectors, and financial firms with large Valley operations often have big user populations whose access grew one exception at a time. A health check compares actual permissions against the roles people hold today, finds admin rights granted for a project and never removed, and checks field-level security on sensitive data. The output gives risk and compliance teams a specific remediation list rather than a general warning.
Healthcare organizations need a health check that treats patient data as the first concern. We review which profiles can see or export records containing health information, whether Shield or encryption settings match your policies, how guest and portal users are restricted, and what integrations write into the org. Findings are ranked so privacy exposures are addressed before cosmetic issues, and the report is written for both the Salesforce owner and compliance leadership.
Semiconductor suppliers often handle confidential customer information and technical files, and their orgs gather quotes, drawings and contacts from very large customers. A health check looks at where those files live, who can reach them, and whether sharing rules still reflect which teams serve which customer. It also inventories the custom objects added for qualification tracking, which frequently duplicate each other after years of incremental changes by different admins over time.
Agentforce acts with the permissions it is given and reads whatever records it can reach. Loose sharing, stale knowledge articles and conflicting automation become visible to customers once an agent uses them, so we check each of these before any AI pilot is scoped.
Renewal conversations go better with facts. The review compares purchased licenses and add-ons against actual logins and feature use, so you can see which users have gone quiet, which features were bought but never configured, and where license types could be adjusted.
Org metadata shows what exists; it does not show where people work around the system. Short interviews with service agents, sales reps and managers reveal the shadow spreadsheets and manual steps that metadata scanning misses, which often explains poor data quality.
How our salesforce health check works →
Client names are anonymized, and these projects are not specific to Phoenix.
No. Read-only access for the review team covers almost all of the analysis. We examine configuration metadata, usage statistics and record counts, and do not need to change anything. If your policies restrict external access, we can work through a screen-share with your admin for sensitive areas. The kickoff agrees who we interview and which business processes matter most, so the findings reflect your priorities.
The recurring themes are broad permissions granted for convenience, duplicate accounts that split activity history, automation from several eras firing on the same object, and fields or packages nobody uses. Each finding comes with the risk it poses and the effort to fix it, so your team can separate urgent security items from cleanup that can be scheduled over later quarters.
Whoever suits the finding. Many items, such as removing unused fields or tightening a permission set, are within reach of a capable in-house admin once identified. Others, like consolidating automation or redesigning sharing, benefit from experienced help. The report says which is which, and some Phoenix organizations pair the review with an optimization project or ongoing managed services to work through the list.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.