Every year of admins, consultants and quick fixes leaves your org heavier: fields nobody fills in, screens nobody trimmed, and the reasoning behind it all sitting in the head of whoever has since moved on. We hand you a field-by-field decision list — what to remove, what to document, what to leave alone — that your own admin can start working through the same week. Launch pricing is published below.
Years of admins and consultants adding fields nobody ever pruned.
So nothing gets deleted. The org keeps growing, and every screen, layout, and integration keeps paying for fields that stopped earning their keep years ago.
Custom objects layered on top of each other, year after year.
Metadata debt and tangled dependencies mean even a small edit can ripple through formulas and relationships no single person has mapped.
Fields with no description, no help text, no record of why they exist.
When that admin or consultant moves on, the reason a field exists — or whether it's still needed — leaves with them.
Names, emails, and other personal details, scattered across standard and custom fields alike.
Without a scoped answer, a compliance review or a data subject request means searching the whole org from scratch, every single time.
Free health checks tell you what's wrong. A Data Dictionary tells you what to do.
The findings, the scores, and what we'd tackle first — in a form you can hand to a board or a funder without translating it.
One sheet per object, one row per field, and a decision waiting on every row. This is the part your team acts on, not just reads.
We go through the verdict together — what's safe to cut now, what needs a second look, and what to leave alone. Included in every package.
Every object in scope on one page: how many fields it carries, how many are actually on a screen, how many custom fields are on none, and how many records it holds.
Every convention spelled out in the file itself, so the workbook still explains itself months after the call.
Account, Contact, Opportunity, and every other object in your scope — each one a row per field, with twenty columns of context.
The identity of the field, so there's no guessing which one a row refers to.
What the org itself records about why the field exists — and, far more often, the blank where that should have been.
The named screens the field sits on. These are the columns that answer the question that stops every cleanup: will anyone notice if this goes?
How often the field is filled in, split by how old the record is, with an arrow for whether that's rising or falling. A field that was used and got abandoned looks nothing like one that was never used.
A Keep / Remove / Check / Unsure dropdown and a free-text note, on every single row. This is where your cleanup plan gets built.
A custom field that sits on no screen at all and was filled on 0% of records in the last year is highlighted in red as a delete candidate. That rule is fixed, not a judgement call — everything outside it stays for you to weigh.
We never write to your org. The decisions arrive documented and prioritised; your admin executes them on your own schedule.
Custom fields scored as deprecation candidates, built from population percentages and CreatedDate cohorts at one, three, and five years — so fields that were used and got abandoned are caught, not just the ones born dead.
Metadata debt, overloaded objects, and dependencies pulled from relationships and the references buried inside formula fields.
Fields with no description and no help text, expressed as a single documentation-debt percentage for the org.
Fields exposing personal data, drawn straight from your org's own security and compliance classifications — not guessed.
For a lean org running on a straightforward, standard-objects setup.
Data Dictionary delivered in 3 business days from the day access is granted.
For an org that's scaled past its original setup, with custom objects layered on over the years.
Data Dictionary delivered in 5 business days from the day access is granted.
For a large, highly customised org spanning multiple teams or business units.
Data Dictionary delivered in 8 business days from the day access is granted.
What can move the price: extra objects agreed at the scoping call, orgs running managed packages that need separate treatment, or unusually large orgs. If any of that looks like you, we'll say so on the call, before anything is booked in.
For a lean org running on a straightforward, standard-objects setup.
Data Dictionary delivered in 3 business days from the day access is granted.
For an org that's scaled past its original setup, with custom objects layered on over the years.
Data Dictionary delivered in 5 business days from the day access is granted.
For a large, highly customised org spanning multiple teams or business units.
Data Dictionary delivered in 8 business days from the day access is granted.
What can move the price: extra objects agreed at the scoping call, orgs running managed packages that need separate treatment, or unusually large orgs. If any of that looks like you, we'll say so on the call, before anything is booked in.
We confirm your segment, package, and any extra objects — nothing here is assumed from the price table alone.
About 15 minutes
Your Salesforce admin sets up the read-only permission set and the dedicated user, scoped to exactly what was agreed on the call.
Once access is live, we run the census, the population counts, and the scoring — read-only, start to finish.
3 to 8 business days, depending on package
You get the PDF to read and share, and the workbook with a Keep / Remove / Check / Unsure marker on every row — the cleanup plan itself, ready for your admin to work through.
We talk through the verdict together — what's safe to cut, what to fix first, and what's worth watching.
Included in every package
The dedicated user is deactivated the same day your Data Dictionary is delivered — nothing stays open after the job's done.
Same day as delivery
311 of those fields are custom — added by admins and consultants over the org's lifetime.
Custom fields scored as deprecation candidates — flagged for review, not guessed at.
No description, no help text — a 62% documentation-debt rate for the org.
Personal data mapped to exactly where it sits, not just flagged as “somewhere in here.”
Objects where metadata debt and tangled dependencies concentrate.
Too few records for a confident verdict — left unscored, rather than given a false one.
These figures come from an illustrative example org, built to show the format — not a real client's data, and not a case study. Your own numbers depend entirely on your org.
Access is limited to the Salesforce objects included in the package you choose — nothing wider, nothing assumed.
We work through a purpose-built user and a permission set built for the job. Your admin can review exactly what it grants — before it's ever switched on.
We run counts and rollups to reach a verdict on usage. We don't pull record-level data out of your org, and we don't keep a working export of it.
Once your Data Dictionary is in your hands, access is switched off the same day — it doesn't sit active waiting to be remembered later.
A standard NDA is available on request. If you'd rather have one signed before anything is granted, raise it at the scoping call and we'll have it in place first.
Not quite yet — we're taking a first small group of clients before general availability, and the way in is the waiting list. The prices above are the launch prices, and the first five organisations on the list get them at half. Joining costs nothing and commits you to nothing; we come back to you directly when a place opens.
No — and that's deliberate. We never write to your org. What you get is every decision documented and prioritised, with the safe deletions already marked; your own admin executes them, on your schedule, with a record of why each call was made. If you'd rather we took the execution on as well, raise it at the walkthrough call and we'll quote it separately.
Yes — read-only access, scoped to exactly the Salesforce objects included in your package. We run aggregate queries only; we never export individual records. If granting access is a hard no for your organisation, say so at the scoping call: running the counts on your side and sending us the output instead is something we can talk through, though it's not how the packages above are built.
Yes. We work through a dedicated user and a purpose-built permission set, and your admin can inspect exactly what it grants before it's ever switched on.
No — and it's worth being upfront about why. Salesforce keeps no “last used” timestamp on a field, so the only way to tell a dead field from a quiet one is to count how many real records have it populated, and that takes read access to actual data, not just metadata. What keeps that safe is procedural — the scoped permission set, the NDA, the same-day deactivation — not a platform limit that only allows aggregates, because no such limit exists.
The dedicated user is deactivated the same day your Data Dictionary is delivered. Access doesn't sit active waiting to be remembered later.
Yes — a standard one, available on request. Raise it at the scoping call and we'll have it in place before anything is granted.
3, 5, or 8 business days, depending on your package — Core, Growing, or Complex — counted from the day access is granted, not from when you book the call.
That gets agreed at the scoping call. Extra objects beyond your package's scope are added there, and it may move the price — we'll say so before anything is booked in.
It's firm for the scope listed. These are launch prices, held for everyone who comes in through the waiting list, and halved for the first five. What can move it — extra objects, managed packages needing separate treatment, unusually large orgs — is spelled out above the packages, so there's no surprise at the call.
No. Nothing is paid online and no card details are collected anywhere on this page. Scope and price are agreed on a short call before anything is booked in.
Three things: the PDF to read and share, the workbook your team works through, and a walkthrough call to decide in. The workbook is the one that does the work — one sheet per object, one row per field, and a Keep / Remove / Check / Unsure dropdown on every row. You also get a shareable link for the PDF; it expires and can be revoked. Personal data is excluded from the shared version by default, and if it's included at your request, the link is password-protected.
Join the waiting list and we'll come to you directly when a place opens — or take the sample first and decide once you've seen one.
Regularly, we share the most practical tips and lessons from real projects solving real problems.