the context
Moving Dentists Building Legacies is a dental-practice brokerage in Yorba Linda, California — they connect dentists selling their practices with buyers, and every deal spans equipment sales, a practice transaction, and an ongoing customer relationship. I joined as Lead AI Automation Engineer to build the data and automation layer that pipeline runs on.
the problem
There was no single source of truth. Equipment sales, practice transactions, and customer relationships lived as disconnected records with no consistent model tying them together — which meant every new deal meant re-deriving structure that should have already existed, and every automation idea had nothing solid underneath it to build on.
the approach
I architected a centralized Notion CRM and operational data model from scratch — one schema for equipment sales, practice transactions, and customer relationships, built to be a foundation other systems could extend rather than another one-off view.
With that foundation in place, I built AI agents that read new business information as it comes in and autonomously update the relevant records, extending automation across the company’s core sales operations and removing a layer of repetitive administrative work that used to fall on people.
Agents making changes to real business data need guardrails, not just capability, so I also designed an AI onboarding and governance framework: documented operating procedures that let a new agent get added to the business and run consistently, instead of every new automation being a one-off integration nobody else understands.
Day to day this is a partnership, not a solo build — I work directly with leadership to translate business needs into practical AI systems, which is the difference between an agent that’s clever and one that’s actually trusted with the data.
results
- One centralized operational data model where before there were disconnected views
- AI agents handling record updates that used to require manual entry
- A governance framework so new automation is documented and consistent, not ad hoc
- An ongoing role, not a one-off project — the system keeps extending as the business’s needs do
The throughline from the earlier CRM work to this role: the hard part was never the automation itself. It’s building something structured enough that automation has something solid to stand on.