What a Salesforce Health Check report contains, page by page

Page 1: the score

One number, 0–100, across six areas: data and objects, automation overlap, integration reliability, release safety, adoption, security and access. It is a baseline for before and after, and the one line leadership reads. A sample org we use in proposals scores 61: data 58, release safety 66, automation overlap 41, adoption 54, integration reliability 72, security and access 79. The low number is where the money is.

The six areas, and what "good" looks like

• Data and objects. Duplicates, fields nobody fills, objects configured and empty. Good: one record per customer, required fields that are actually required, a data dictionary someone maintains.
• Automation overlap. Flows, triggers and workflow rules competing on the same object. Good: one automation per event, documented, with an owner.
• Integration reliability. Transfers that fail silently, retries nobody sees. Good: idempotent writes, alerts to a person, a runbook.
• Release safety. Changes straight to production. Good: environments, user acceptance testing, a rollback path, a change log.
• Adoption. Licences paid for, logins that stopped. Good: screens that match the job, and three reasons people avoid the system, named.
• Security and access. Shared logins, permissions nobody reviewed since the last admin left. Good: named individuals, least privilege, a review date.

Pages 2–9: findings, each with a price

Every finding is ranked by business impact and carries estimated hours and the cost to fix. "Fourteen Flows and three triggers compete on Opportunity: 14 hours of admin time a month and stage changes that do not stick. Fix: 32 hours, $2,600." Usually there are ten to fifteen. The sum of the findings is the budget to fix everything; the top three are usually what gets done, and the report says which three.

Page 10: AI and Agentforce readiness

When an assistant gives weak answers, the cause is almost always gaps in data, not prompts. We learned that on our own prompt tests at a wealth-management client: the weak scores traced back to empty objects and stale fields, not to the wording. This page says which gaps, in which objects, and what to close first, and what not to switch on yet.

Pages 11–13: the 30/60/90-day roadmap

What to do first, what can wait, what to stop doing. The roadmap ends in one concrete next step with its price and the Health Check credit already applied: "the next 30 days are a Two-Week Wins at $5,500; your credit brings it to $4,000". The roadmap is a budget, not a wish list.

Page 14: method, access and who was interviewed

Read-only access only, through a user your admin creates and deactivates. Two 45-minute interviews with a process owner and the admin, one 60-minute readout with your team. The automated scan and what was checked by hand, listed, so another partner can repeat it.

What the five days look like for your team

About three hours of your time in total. Day one: your admin creates a read-only user; we start the scan. Day two: a 45-minute interview with the person who owns the process that hurts most. Day three: a 45-minute interview with the admin. Day five: a 60-minute readout where we walk through the score, the top findings and the next step, and you push back. The report is delivered the same day and the user is deactivated.

What it is not

It is not a sales deck. There are no slides about our company, no "transformation journey", no logos. It is also not a complete list of everything wrong with the org; it is the list of what costs you money, ranked. A finding that does not change a number or a decision does not make the cut.

How clients use it

Three ways we have seen. The most common: the first fix on the roadmap, with the credit applied. The second: a budget document for the next year, handed to the CFO. The third, which we encourage: handed to the partner the client already has, as the brief for what to do next. The report is yours. Whoever does the work, you paid $1,500 to know what the work is.

A sample finding, end to end

Finding 3 of 12. Fourteen Flows and three Apex triggers fire on Opportunity stage change. Two of them set the same field to different values depending on order of execution, so stage changes "do not stick" about one time in eight. Admin time spent re-setting stages: roughly 14 hours a month. Business impact: forecast reports are wrong on the day they are read. Fix: consolidate into one record-triggered Flow with an order of operations, retire two triggers, add a test. 32 hours, $2,600. Roadmap: first 30 days. Credit applied: this fix is part of the Two-Week Wins at $4,000 after the Health Check credit.

That is what every finding looks like: what, how often, what it costs you now, what the fix is, what the fix costs, when. No adjectives.

What we need from you to start

• One read-only user, created by your admin.
• The name of the person who owns the process that hurts most, for a 45-minute interview.
• The admin, or whoever answers requests now, for another 45 minutes.
• A 60-minute slot on day five for the readout, with the people who will decide what happens next.

The Health Check is $1,500, five business days, credited in full against any fix within twelve months. How it runs.