I build the Salesforce systems that go-to-market teams run on. I handle the architecture and integrations across our GTM and revenue systems, and I build AI tooling to help deliver and maintain the work.
SaaS Company didn't have a standard quote-to-cash process, so I designed and built one. I worked with sales, finance, and RevOps to agree on how it should work, then built it in Salesforce so it could take on new product lines later without a rebuild.
Teams across the company defined the customer lifecycle differently, which made the systems and reporting inconsistent. My team built a company-wide Customer Journey Map to get everyone on the same definitions, and I led the work to rebuild Salesforce and the surrounding GTM systems around it.
I built a custom MCP server early, before most companies had one, so AI tools can reach Salesforce data securely. On top of it I run a set of agents that diagnose issues and carry out Salesforce work in a sandbox, and I review and approve the output before anything ships.
I reworked the pricing and contract structure for a consultancy and built the Salesforce setup behind it. It gave the leadership team revenue forecasting they hadn't had before.
Built an AI tool that scans the web to flag spam and fraudulent leads, so the team spends less time qualifying them.
Built an AI tool that reads a Salesforce org and writes technical and business-process documentation from its metadata.
Catalogs every field with its definition, usage, automations, and dependencies, and keeps itself current so the team can see downstream impact.
Connected Databricks data into Salesforce with zero-copy, so the data is available natively without copying or migrating it.
Tooling that checks data integrity across the org and flags problems before they cause downstream issues.
An internal knowledge base that answers process questions and updates itself as the org changes.
Browser extensions that remove day-to-day friction for support, success, and sales reps.
At a SUD/Behavioral Health Company: automated survey scoring, dynamic screen flows, and cross-object reporting.
Built several Salesforce orgs from scratch and cleaned up others that had accumulated tech debt.
I focus on the underlying cause of a problem rather than the symptom, because that is usually where it actually lives. I judge work by the impact it has on the business, not the volume of it. I build systems to be simple and loosely coupled so they are easy to change later, and I keep both the team and the systems healthy over time. Good systems and processes should let teams own their work and innovate without waiting on me. Most of what I build comes back to a few principles: clarity, simplicity, scalability, flexibility, and decoupling.