A check-up for every Salesforce org you look after.
Anya reads a client’s org and tells you what it costs, what stands in the way of changing it, and where its own rules and its records disagree. It needs read-only access and asks nothing of anyone to get started.
Built for Salesforce implementation consultancies.
- Over a limitData storage is 3,449 MB over its allocation.
- Licence dateA package licence lapsed four days ago, with every seat taken.
- Installed package12 of the 38 fields the field service package installed are filled in on 1 record in 20 or more.
Three kinds of finding, kept apart.
They differ in one way that matters to you: whether anyone has to be asked before the number is right. Two of them never do.
What it costs, and what blocks change
Limits, licences, code and installed packages, each read against something fixed.
- Data storage at 129% of its allocation.
- 360 of 1,414 reports not run in a year, and on no dashboard.
- A package licence that lapsed last week, with every seat taken.
Nothing to ask
Where the org disagrees with itself
The org’s own configuration says what its data should look like. Anya checks whether it does.
- On 50,752 of 57,190 cancelled jobs, all made before 2025, the reason given is not one of the six on the list.
- Two in five job line items are placed on the map at least 70 km from their own job.
- On 1,999 of 2,000 appointments the due date is seven days after the earliest start: a default, not a deadline.
Nothing to ask
What needs your judgement
Overdue visits, stalled jobs, work closed without evidence. These depend on how the business runs, so Anya shows you what it depends on.
- Each open question is listed with the figure under every answer.
- A score that turns on a question is shown as a range until it is answered.
A handful of questions, sized
What you get
Two documents, in your branding, ready to share on a screen or leave with a client.
The org census
A few pages of measured fact: a cover of gauges, the six things that stand out, then the detail in three parts.
See a sample census for an invented org, and the one-page summary that goes with it (both PDF).
The operations review
A scorecard of how the work is going. It starts provisional, with each score drawn as the range it could take. Answer the questions and the ranges close into single figures you can stand behind.
Is an appointment marked “Subcontracted” still live work, or is it finished with?
| If it is | Appointments overdue | Operations score |
|---|---|---|
| Still live work | 2,077 of 6,878 (30%) | 85.3 |
| Finished with | 385 of 4,964 (8%) | 92.0 |
That is one question from a real review. Your consultant can see which questions matter and leave the rest.
How access works
- Your admin creates one userRead-only, in production. About ten minutes.
- Anya reads the orgSettings and counts. Nothing is written, changed or run.
- You get the censusIn your branding, with the one-page summary.
- You switch the login offOn the day of the walkthrough. Lists of record IDs are deleted within 14 days.
Read-only, always
A read-only login that you grant and can revoke. Anya never writes to an org or changes a setting.
Nobody named
People are counted, never identified. Lists hold record IDs, not names.
It says whose it is
What a package installed is reported under the vendor’s name, never counted against your client.
Your NDA first
We sign your NDA or data agreement before reading anything.
Run a Salesforce consultancy?
Try it on one org you already look after. The first two partners get pilot terms.
- You give read-only access to one client org.
- You get its census back, in your branding.
- You tell us, honestly, what you would use and what is missing.
Working with data in another system? Get in touch anyway.