Information Systems Consulting at it's finest
I'm an engineer by training with nine years in the Salesforce ecosystem. I take on a handful of projects at a time, mostly for nonprofits and organizations I believe in.
Embedded Files
what I do
what I do
Most of my work is Salesforce: automation that's gotten tangled, Flows and Apex that stepped on each other, technical debt that has piled up. I've spent years sorting through these kinds of problems and I'm good at it.
But it's not only Salesforce. The same thinking applies whenever a system has gotten messy — data that's drifted out of shape over the years, processes that used to work fine but don't anymore, tools that the team has quietly stopped trusting. If something's broken or slow and nobody can explain why, that's usually where I end up.
I don't take on a lot at once. A few projects at a time, scoped tightly, so the work actually gets done right.
approach
approach
I start by looking at what's actually happening — not what someone documented years ago. In Salesforce, that means debug logs, dependency chains, tracing execution paths to figure out why something fires three times when it should fire once. For data work, it means getting into the actual records and understanding how things got the way they are before trying to clean them up.
I studied engineering and information systems, and it comes through in how I work. I tend to build tools to see what's going on — visualizations, dependency maps, that kind of thing. I think about systems in terms of how they fail, not just how they're configured. Once I understand the problem, I either fix it or tell you exactly what needs to happen so your team can.
Happy to talk before anything's formal. No cost, no pitch.
Page updated
Report abuse