I make the teams around me work better. I've built on Salesforce since 2007 and been a formal architect since 2016, and today I lead the Systems Engineering team behind a Salesforce and go-to-market stack: the platform, CPQ and quote-to-cash, MuleSoft integration, and the DevOps pipeline and controls that ship changes safely. On the side I build my own tools: SaasyLogs, which makes Salesforce debug logs readable, DwelLogs, a free app for keeping track of home upkeep, and DeployLogs, a runlist and go/no-go tracker for deploys that cross teams.
Every project I take on starts with a real problem, whether it's mine, my team's, or my family's. SaasyLogs came from fighting Salesforce debug logs. DwelLogs came from family asking for a simple way to keep up with their homes. DeployLogs came from years of running cross-team deploys from a spreadsheet.
If a tool should exist and doesn't, I'd rather build it than wait for someone else to. That goes double for keeping useful things simple, affordable, and respectful of people's data.
The only sure way to fail is to never try. I pick up new tools and stacks by building something real with them, and I aim past what I already know how to do.
If I have to do something twice, I look for a way to automate it. Good tooling, AI included, frees up time for the problems that actually need a person.
I've been a developer, a Scrum Master, a build manager, and a people manager, often at the same time. The common thread is taking the friction out of how teams work, so they can get to the real work.
Salesforce, CPQ and the quoting process that feeds quote-to-cash, with MuleSoft integration around it. Clean data models and automation that hold up at real volumes, and cleaning up the inherited tech debt that slows everything else down.
CI/CD with the ticket, release notes and deployment history tied to every change. I've run the SOX audit for a CRM four years running, and helped automate monitoring so in-scope changes are caught as they happen.
Growing engineers, admins and contractors into independent experts, and team-health practices that reduce burnout instead of feeding it.
Agile and Scrum across Business Systems and IT, with shared standards for testing and code review, and room for each team's nuances, so nobody reinvents the wheel.
I design, build, and ship all four of these myself, from idea to launch.
Paste or upload a Salesforce debug log into a Google Sheet and see the path your save took: every trigger, flow and class, in order. Then what went wrong, and where the time went.
Debug logs are huge, noisy, and hard to read. Finding the one line that matters eats time on every bug.
I live in these logs, so I built the tool I want on every bug. It isn't on the Workspace Marketplace yet; you can ask for access on the site.
Keep a pulse on your home: the filters, the well, the animals, the thing that broke last week. What your home needs and when, shared with everyone who lives there.
Home upkeep lives in scattered notes, receipts, and memory. Homeowners, condo owners, and renters all lose track of what's due and what it'll cost.
A deploy runlist and go/no-go tracker for Google Sheets, for deploys that cross teams.
Deploys fail in the gaps between teams: steps kept in someone's head, IDs one team creates that the next one needs, and estimates nobody has ever run.
I've run cross-team deploys from a spreadsheet tracker for years. Heroics are not a deploy plan, so the tracker is becoming an app.
Little learning games for curious kids: letters and sounds, counting, typing and quick math, played right in the browser.
A lot of learning games lean on timers, scores and buzzers. For a kid with ADHD or dyslexia, or one who's anxious about typing, that's stress, not learning.
See a need, fill a need, for the kids in my life. Short rounds, every word read aloud, no timers, a hint after two misses, and progress that stays on the device. One game was designed by a kid tester.
I write about building my own tools, leading teams, and the work behind the work.
Leading in a world of AI and numbers: why the human is still Batman, why we're on the same side, and what to do when your team gets called a blocker.
Debugging the debugger, and the time a debug log never mentions.
A first house, a drawer of manuals that never say when, and building the model, the sign-in and the offline mode that came after.
Why heroics are not a deploy plan, and how a spreadsheet tracker from years of cross-team deploys is becoming an app.
Manager, Systems Engineering 2024 – now
Staff Systems Software Engineer, Agile Lead 2023 – 2024
Senior Systems Software Engineer 2021 – 2023
Lead Systems Engineering for go-to-market applications: the Salesforce platform, the MuleSoft integration and CPQ teams, and the delivery pipeline and controls around them. Led the move to Gearset for Salesforce CI/CD, run the CRM's SOX audit and helped automate its monitoring in MuleSoft, evaluated Revenue Cloud in depth, and drove the move to Agile and Scrum across Business Systems and IT.
Lead Salesforce Engineer, SMTS 2015 – 2020
Apex/Force.com QE & Developer, contract 2014 – 2015
Led cross-functional teams from proof of concept to production, with a focus on Apex, performance, and complex back-end logic. Served as Scrum Master and build manager, and mentored developers and admins.
Software Engineer
Core engineer on a Salesforce managed package: new features across many customer orgs, and re-architecting legacy custom solutions.
Salesforce Application Engineer
Full-stack work on internal tools with Apex, PHP, and JavaScript, covering requirements, usability testing, code review, and deployment. Spoke at Dreamforce 2012 on usability, and taught a session on it in Facebook's engineering bootcamp.
Salesforce Developer, Support Operations
Foundational Salesforce engineer. Built the internal tools for global Sales and Support and set the company's first engineering standards for Salesforce.
I'm open to new roles leading Salesforce platform and go-to-market systems teams. Want to talk about one, talk Salesforce, swap debugging stories, or chat about SaasyLogs, DwelLogs or DeployLogs? LinkedIn is the easiest way to reach me.