Engineer by training. Salesforce by choice.
I trained as a mechatronics engineer — the discipline where a motor failing on the factory floor teaches you more than any textbook. Operators don't care how elegant your circuit is; they need it to work.
I moved into Salesforce with that same standard. 7 years in. Multiple clouds, dozens of orgs, mostly cleanup work — the brittle trigger nobody's touched in 2 years, the portal users can't figure out, the integration that silently drops records on Tuesdays.
Third-party attestations.
The work most consultants don't want to take.
A handful of patterns I see often enough that I keep a playbook for each one.
Multi-thousand-line files where every change is a guess. Decompose section by section, ship a component library, retire the relic without a full rebuild.
Click counts that don't match how people actually work. Cut clicks, consolidate flows, ship a reusable LWC library your team can extend.
Standard Opportunity objects forced into deal cycles they were never designed for. Object architecture that fits the actual sale.
Brittle automation chains losing records on a schedule nobody monitors. Replace with services your admins can read and your team can trust.
Who I work with — and who I don't.
Save us both a discovery call. If you're in the left column, let's talk. If you're in the right, I'll usually know who can help.
- Companies whose Salesforce can't keep up with how they've grown
- Support teams whose customer portal is making things worse, not better
- Teams whose admin is solid but stuck on a hard problem
- Buyers who want a senior expert, not another planning meeting
- Lowest-bid, shortest-timeline work
- Looking to hire a full-time Salesforce admin (different gig — happy to refer one)
- Enterprise procurement with 6-month vendor onboarding
- Template-shopping for a cookie-cutter setup
Where I've worked.
Got an org that needs untangling?
A 30-minute call is free. I'll tell you whether I can help, and if I can't, I'll usually know who can.