Gerry M.Private profile: Upwork shows its earnings only to signed-in members, so we check it every few weeks, not daily. MRR here is a rough estimate (Upwork's six-month earnings ÷ months active). Last read Nov 5, 2026.

I’m a Salesforce developer who builds the automation other developers get stuck on, and I bring AI/LLM tooling into the org in ways most Salesforce shops haven’t caught up to yet. The technical core: Apex (triggers, batch and schedulable jobs, bulkified patterns), Flow architecture and the hard debugging (recursive loops, async paths, governor and scheduled-path limits), validation rules, permission sets, and integration users. When automation misfires in production, I find the actual cause instead of patching symptoms. Where I’m different: I build AI-native tooling on top of Salesforce. I’ve built a custom MCP (Model Context Protocol) server in TypeScript with PKCE OAuth to let LLMs read and safely mutate Salesforce data, connected multiple orgs to AI assistants, and written CLI tooling to make org changes safer and faster. If you want to wire Claude or another LLM into your Salesforce workflows without handing it a loaded gun, that’s the work I do. A few things I’ve fixed or built: • Traced a production Flow that was hitting scheduled-path limits to a Task automation silently re-triggering itself, and stopped the loop without losing data. • Killed trigger recursion in an account-hierarchy merge using a before/after-delete pattern with static-variable guards. • Cleaned up ~1,100 confirmed duplicate account pairs with clear winner/merge logic, without breaking downstream automation. • Built a Sailthru-to-Salesforce sync on schedulable Apex, abstracted through Custom Metadata so config changes don’t require code changes. • Stood up an MCP server that lets an LLM query and update Salesforce through scoped OAuth, with explicit read vs. write boundaries. What I build: • Apex development: triggers, batch/schedulable, async, test coverage • Flow design and debugging, including the ones that broke in production • REST/SOAP integrations and middleware between Salesforce and your stack • MCP servers and API tooling that connect LLMs to Salesforce safely • Data migration, deduplication, and org cleanup • CLI tools and scripts that automate the tedious admin work How I work: I start by understanding the problem before I touch the org, because the fastest fix is often not the one you asked for. I write code that’s bulkified, tested, and documented, so your team isn’t stranded after the engagement ends. I scope honestly, flag risk early, and will tell you when a problem doesn’t need custom code at all. If you’ve got an integration to build, a Flow that’s misbehaving, a migration you’re nervous about, or an idea about putting AI to work in your Salesforce org, send me the details and I’ll tell you honestly what it’ll take.