The Blog
Practical Salesforce engineering – Apex patterns, integration architecture, and platform decisions explained.
-
Data Cloud as the agent’s foundation: why messy data breaks Agentforce before it starts
Agentforce rarely fails because the agent is dumb. It fails because the data underneath it was never clean enough to act on in the first place.
-
What I check in the first 30 minutes on a new Salesforce org
No documentation, no handover, just org access. Here’s the exact order I check things in before touching anything.
-
Admin vs developer vs architect: where the real leverage sits on a Salesforce team
Admin, developer, architect: the titles on a Salesforce team rarely match who’s actually moving outcomes. Here’s what to look for instead of the badge.
-
Field-level security audits: what most orgs get wrong
Page layouts aren’t security, permission sets sprawl, and integration users get god-mode access nobody scoped. What a real field-level audit catches.
-
Retiring old automation: the unglamorous work that pays off
Every Salesforce org accumulates automation nobody remembers building. Here’s how to find the dead weight, prove it’s dead, and retire it safely.
-
Multi-cloud Salesforce: keeping Service Cloud and Marketing Cloud in sync without a mess
Service Cloud and Marketing Cloud drift apart fast once two teams own two clouds. Here’s the field-ownership matrix that stops the chaos before it starts.
-
What Agentforce needs from your data model before it can work well
Agentforce is only as reliable as the data underneath it. Here’s what to fix in fields, sharing rules, and Data Cloud before you configure a single action.