Lianne Toro is VP of Revenue Operations at Meridian Health, a specialty healthcare network that completed an acquisition of a regional practice management firm in Q4 2025. We spoke with her six weeks after she started using OrgLens.
What was the situation when you came into the acquired org?
Lianne Toro: It was a 14-year-old org. The company being acquired had been on Salesforce since 2011, which predates Lightning, predates Process Builder, predates half the things we take for granted. There were fields on the Account object with API names like Account_Old_CRM_ID__c that I'm pretty sure corresponded to a system that no longer exists. Nobody could tell me what it was for.
The previous Salesforce admin had left eight months before the acquisition. There was documentation — a SharePoint folder — but it was for a different version of the org than what we inherited. The documentation described fields that had been deleted and didn't mention fields that had been added since.
We had a board-level commitment to complete the integration by Q2. The incumbent consulting firm quoted us nine months and $340,000 to inventory and document everything. That wasn't going to work.
How did you find OrgLens?
Lianne: Honestly, Reddit. There's a Salesforce admins community and someone had posted about using it for an M&A integration. I signed up the same day. This was a Sunday afternoon — the acquisition had closed on Friday and I was already stressed about Monday.
What happened when you ran the first scan?
Lianne: I connected the org at about 11am on the Monday after close. The scan completed by 5pm. 48,200 fields, catalogued, with AI-generated draft help text for every field that didn't already have it. My first reaction was that the quality was going to be generic — what can a model know about our specific org's conventions?
But it wasn't generic. The descriptions for fields on the core clinical objects were specific. They referenced the picklist values in the context of what they drive — automation, routing rules, report filters. I later understood why: the model sees the validation rules, the page layouts, the automation rules, not just the field name. It's building descriptions from the full context of how the field actually behaves.
"I called our Salesforce consultant at 5:30 that afternoon and told him I didn't need the nine-month engagement. He asked what had changed. I said we'd scanned 48,000 fields and had draft documentation for all of them. There was a long pause."
How did your team work through the review queue?
Lianne: We did it in object-by-object sprints. Three admins, working in parallel on different objects. OrgLens let us assign objects to reviewers, so there was no stepping on each other. We started with Account, Contact, and Opportunity — the objects that appear on the most page layouts and drive the most automation. Those were done in the first week.
The second week we tackled the custom clinical objects. These were the ones I was most worried about — they had the most obscure field names and the most complex automation. The model's drafts were rougher here, because clinical terminology is specific. But they gave us a starting point, and editing a close draft is much faster than writing from scratch.
By the end of week six, we had approved documentation for 92% of fields. The remaining 8% are fields that we've flagged for deprecation — we're not documenting what we're going to delete.
What surprised you most?
Lianne: The findings. OrgLens surfaces things it calls "findings" — anomalies in the org structure that might be problems. We had 847 findings across the inherited org. Some were minor — picklist values with inconsistent capitalization. But some were serious. There were seven validation rules with error messages that just said "Error." with a period. Those had been blocking saves silently for years, and nobody had complained because everyone had learned workarounds.
There was one finding that was genuinely alarming: a field called Patient_Backup_SSN__c on the Contact object with about 12,000 non-null values. That field should not have existed. It wasn't on any page layout, wasn't referenced in automation, but it was being populated by a legacy integration that was still running. The data was sitting there. That's not a documentation problem — that's a compliance incident. OrgLens flagged it. Our team had never seen it.
Where are things now?
Lianne: We kept OrgLens on the Growth plan for ongoing governance. Every time we deploy a new field or modify an existing one, the review queue gets a new item. We treat it like a pull request review — the field doesn't get deployed without documentation. That's a cultural shift, but it's the right one.
The integration completed on time. The internal audit review found zero documentation exceptions on the fields we'd documented. That's the number I care about.