How I work
Five principles, not a sales pitch.
These aren't marketing language. They're the operating rules I hold myself to on every engagement.
Understand before building
Start with the business problem, not the Salesforce feature — and resolve ambiguity before writing code.
Design for the person using Salesforce
Every screen, field, and workflow should reduce effort, not add to it.
Show progress, not slides
Working software is the update — not a status deck.
No surprises
Problems get surfaced immediately. Trade-offs get explained, not hidden.
Leave you stronger
Documentation, knowledge transfer, and ownership ship with the work.
Modern engineering, used responsibly.
AI can accelerate implementation. It doesn't replace architecture, testing, security, or judgment.
Have a Salesforce problem worth talking through?
If you're implementing Salesforce, struggling with an existing org, or simply trying to work out what the right solution looks like, let's talk. You don't need to have the requirements figured out before reaching out.