How healthy is your org, really?
Seven signals you can pull from Setup in five minutes — active users, custom objects, packages, admin ratio, coverage, cadence, page feel — scored against the typical mid-market org. No metadata access, no scanner, no login.
Seven honest signals
Pull the numbers from Setup, or estimate — the bars update live.
Typical — drifting is the danger
You sit with the majority of mid-market orgs: functional, slower than it should be, accumulating debt quietly. The weakest dimension below is where drift becomes damage.
How you compare
Your shape against the typical mid-market org. A balanced shape beats a spiky one — single weak dimensions drag the others down over time.
Dimensional breakdown
Dashed marks: the typical mid-market org. Overall they land between 55 and 65; top quartile starts around 75.
What your answers say
Adoption is alive but leaking.
The gap between you and a healthy org is usually two or three specific workflows that push users back to spreadsheets. Name them and fix them.
Acceptable but noticeably slower than it should be on the pages people use most.
A two-to-four week profiling pass typically recovers most of the gap.
Well-run: sensible admin coverage and a real release rhythm.
This is the engine room of every other score — keep investing in it ahead of demand, not behind it.
Your top 3 moves
Run a frontline adoption sprint
Find the ten workflows users avoid, fix the three worst, and put champions on the floor. Adoption problems are design problems wearing a training costume.
Typical scope: 4–6 weeksProfile the slow pages
Page-load complaints are usually three records: a bloated page layout, an unbounded report, and a package fighting your own automation. Profile, then prune.
Typical scope: 2–4 weeksFix the admin ratio and release rhythm
Under-resourced admin teams firefight instead of improving. Right-size the team, then move to a fortnightly release cadence with automated tests.
Typical scope: 4–8 weeksGet your org health report
- Your score across all four dimensions
- Where you sit against the typical mid-market org
- Your three moves, scoped and timed
- The Setup checklist to verify each input with real data
We use your email to deliver the report, and for the newsletter only if you opt in. No list sharing, ever.
Questions people ask
What does "typical mid-market org" mean?
The middle of the pack across healthchecks and audits on 250+ APAC programmes, mid-market through enterprise: a total score around 55–65, healthy adoption above 70% active users, and a release cadence of monthly or better.
Why does the admin ratio matter so much?
Because everything else downstream depends on it. Up to about 90 users per admin is workable; past double that, the team can only firefight, debt accumulates, and adoption decays. It is the most predictive single number in the model.
My org scores badly. Is that actually a problem?
Only if it surprises you. Orgs accumulate debt the way houses accumulate cupboards — the score tells you whether it has started costing you speed, adoption or money. A healthcheck turns the score into a prioritised fix list.
Is this the same as a Salesforce healthcheck?
No — it is the two-minute version. A formal healthcheck audits your actual metadata, performance and usage data per cloud, and produces a roadmap that names names. This tells you whether you need one.