Client systems / Professional practice
From an operational problem
to a working system.
I work between customers, developers, and the people who use business systems. My job is to make a request clear enough to build, test, and support.
A summary of my delivery practice across multiple engagements.
Build around the actual work.
I designed and built four complete Salesforce environments for treatment-center and admissions operations. That work includes custom apps, page layouts, Flow automation, integrations, and safeguards against user error.
One implementation began in January 2024 and remained in operational use in September 2026. I designed and built the environment, including its layouts, apps, workflows, and integrations.
My earlier experience in admissions and call-center operations helps me understand what the people using those systems need to do throughout the day.
Make the behavior explicit.
In my delivery role, I own client relationships and coordinate work across eight Salesforce organizations. I define requirements, acceptance criteria, and effort estimates, then work with offshore developers, QA, and customer stakeholders.
For interface work, that means specifying when a field appears, what must be true before someone can save, which controls belong in the first visible action slots, and what happens to an inquiry that already has an owner.
Explore the three interactive design examples ↗Connect the handoffs.
Through JLT Consulting, I connect Salesforce with tools including CallTrackingMetrics, Google Ads, Microsoft 365, and Power Automate to support intake, routing, attribution, and reporting.
I also built Asana views for scoping, QA, and triage to clarify who owns the next step. In enterprise Salesforce administration, I document procedures and train colleagues on onboarding, deployments, and user lifecycle work.
Carry it into daily use.
My contribution spans direct configuration and implementation as well as requirements and delivery leadership. The linked case studies distinguish my work from colleagues’ contributions and the existing platform components we used.
Client organizations, collaborators, and records are anonymized in the project exhibits. Reconstructed interfaces use synthetic data. The examples document behavior and delivery; they do not claim unmeasured revenue or time savings.