Topic
Salesforce
-
Before you pilot Claudeforce
Connecting Claude to your org doesn't loosen your security model, but it means your existing permissions matter more than they used to. Here's what to check first.
-
Claudeforce versus Agentforce, in plain terms
If you already use Agentforce, Claude's been running inside it since late 2025. What Claudeforce actually adds is mostly administrative, not algorithmic.
-
Documenting a validation rule so the next person understands it
The formula says what a validation rule blocks. It doesn't say why. Here's how to turn it into a description someone can act on without opening the builder.
-
Explaining CPQ logic in plain language
A CPQ price rule is unreadable to anyone who didn't build it. Here's how to get it translated for a non-technical approver, and what to verify before trusting the translation.
-
Reviewing SOQL for readability and risk before it ships
A query that runs fine on ten test records can lock up at scale. A checklist for having AI review SOQL for risk, and where to double-check it yourself.
-
Turning business requirements into Salesforce stories
A requirements doc and a story a developer can actually build from are different documents. Here's how to get from one to the other without losing the original ask.
-
What Claudeforce actually is
Salesforce and Anthropic announced Claudeforce in August 2026. Here's what the two halves actually do, and what's confirmed versus still vague.
-
What Claudeforce can't do yet
Beyond the press release, there are real open questions here: unquantified cost, a beta colliding with a Salesforce release window, and a vendor concentration risk architects are already flagging.
-
Writing a Flow description AI can actually follow
AI can't open your Flow. Here's a plain-text way to describe one that's specific enough to actually get help with it.
-
The spec interrogation prompt
The paste-ready scaffold and interrogation prompt, pulled out of the playbook.
-
How to use AI without connecting it to your Salesforce org
Security said no. Requirements, logic design, and specs were never the blocked part. Here is the four-step workflow, with the prompts.