I worked the trucks before I worked the org.

Most Salesforce consultants learn a service business through a discovery questionnaire. I learned it in attics and crawlspaces, on call, with a customer standing behind me asking how much.

That background changes what I build. When a dispatcher tells me the current process is "fine," I know which part of it they are quietly working around. When a flow requires a technician to scroll through four screens before they can close a call, I know it will get skipped and the data will be garbage by Friday. The field is the acceptance test, not the last phase of the rollout.

It also makes me blunt about scope. Salesforce is a serious platform with a serious price tag, and for some shops the honest answer is that a well-run Jobber or ServiceTitan instance is the right tool for another two years. I would rather tell you that on the first call than discover it together in month five.

How engagements run

Discovery first, always — interviews across office, dispatch, and field, turned into a written architecture doc with the decisions, the tradeoffs, the risks, and the open questions laid out plainly. You get the reasoning, not just the build.

Everything I configure lives in an SFDX project under git. Every change is a commit you can read and roll back. Clicking around production with no source of truth is how orgs quietly rot, and I will not do it, even when it is faster.

Writing

The Field Notes section is the build log — architecture decisions, metadata excerpts, and the things that went sideways, published as engagements happen. If you want to know how I think before you hire me, that is the fastest way to find out.