Revenue Cloud · CPQ · Agentforce · MCP
Revenue Cloud and Quote-to-Cash,
with Agentforce on top —
explained by someone who actually ships.
I don't just write about the platform — I build on it. Quote-to-Cash on Revenue Cloud comes first: the product catalog, pricing, quotes, tiered approvals and contracts, the integrations that carry an order on into ERP and finance, and Configra — my own managed package on Revenue Lifecycle Management. On top of that I build the Agentforce agents that work on it, grounded in the org's own data and acting through Apex, with one rule throughout: the language model extracts intent, code sets the numbers. And because an agent that works near a quote has to be trusted, I build the checks around it too. These guides are the notes from that work: the hard parts, solved and documented, in plain language.
Eight ways in
Pick your depth
Revenue Cloud
RLM, CPQ, Billing, and the full quote-to-cash lifecycle.
Explore →CPQ
Configure, Price, Quote — products, rules, discounts, and quote documents.
Explore →Agentforce
Agents that take real action — topics, custom Apex actions, grounding, the Einstein Trust Layer, and evals. Written while shipping a live, deployed agent.
Explore →MCP
Model Context Protocol — connecting Claude to Salesforce with Hosted MCP Servers (GA April 2026), exposing custom Apex as tools, and agent loops that build orgs.
Explore →Data Cloud
Data 360 — ingestion, DLO/DMO, identity resolution, SQL Calculated Insights, and the Query API that grounds agents in real data.
Explore →OmniStudio
FlexCards, OmniScripts, DataRaptors, and Integration Procedures.
Explore →Integration
MuleSoft, APIs, and connecting Salesforce to SAP, Stripe, and DocuSign.
Explore →Foundations
Apex, LWC, Flow, and certification fundamentals.
Explore →Latest articles
All articles →Call It, Don't Hand Off
Transitioning to a connected subagent hands control away and the answer never comes back. Invoking it as an action returns the response to the router — the one difference that turns three specialists into a single reply.
Multi-Agent Orchestration: Who Owns What, and Who Answers
A router agent above three specialists — records, triage, scheduling — with exclusive ownership, a fixed order, and escalation held by exactly one of them. The design rules I only learned by publishing five versions of each.
Apex as an MCP Tool: The Loop That Builds and Verifies Itself
Six custom deployment tools written as tested Apex, exposed over MCP, and driven in a loop that only stops when the test runner says all green at 90% coverage. What happened when one handler came back at 88%.
Learn here
Practical Salesforce guides from shipped work.