Advanced Apex: Async, Bulk & Performance
Async Apex, bulk design and performance at volume — the code that works on ten records and dies on ten million.
CRM Cloud Mastery
Every course below is open to browse: the full curriculum, the level it starts at and what it costs, before you sign up for anything.
Async Apex, bulk design and performance at volume — the code that works on ten records and dies on ten million.
What an agent actually is: topics, grounding, actions, channels, guardrails, testing and the cost of running one.
The contact centre you cannot staff your way out of: service design, knowledge, channels, case management and analytics with Agentforce.
Agentforce at specialist depth: subagents, actions, prompt engineering, Data 360 grounding and multi-agent orchestration.
Apex taught as a platform language: governor limits, bulk and the order of execution from the first line, not the last.
The composite Application Architect view: the data model as a change budget, and designing for the next change.
A full implementation, start to finish: discovery, design, plan, two build waves, migration, integration, UAT, cutover and hypercare.
Data architecture for the Platform Data Architect exam: modelling, MDM, large data volumes, migration and governance.
Getting data in, keeping it right, and cleaning up what you inherited — including the external ID discipline nobody teaches.
Flow from first screen to production: choosing the tool, building it properly, and owning it once it is live.
Four front doors and one leaver: Salesforce as service provider and identity provider, SSO, and proving access ended.
Integration architecture: turning a business need into requirements, designing the solution, and keeping it alive past year two.
The JavaScript a Salesforce developer actually needs — types, scope, async, the DOM and testing — up to the Certified JavaScript Developer exam.
LWC from the component model up: templates, composition, data, forms, security, testing and shipping.
OmniStudio end to end: Data Mappers, Integration Procedures, FlexCards and OmniScripts, and when not to use them.
The full Platform Administrator syllabus, taught as one inherited org you configure, secure, automate and hand over.
Year two in the same org: the Advanced Administrator syllabus, taught as the problems that only appear once a system is in use.
A timed run at the Platform Administrator exam: how it is scored, domain by domain, ending in a full-length mock.
The Platform App Builder syllabus: designing a data model, building logic without code, composing the UI, and shipping it.
The org that three companies built: advanced Apex, integration, UI, testing and performance at Platform Developer II depth.
A timed run at the Platform Developer exam: what it scores, domain by domain, and the run itself.
Reports that are correct and dashboards somebody actually opens — including how to show a trend in an org that keeps no history.
Data 360 from the connector inwards: ingestion, the data model, mapping, identity resolution, insights and activation.
Data 360 at consultant depth: solution design, ingestion, transformation, harmonisation, identity, insights, activation and grounding AI.
What is actually being bought: the hiring process as it runs, the live scenario round, discovery, saying no, and staying hired.
The whole platform in one sitting: what Salesforce is for, how a record moves through it, and where the work actually happens.
Who the user is, which records they see, and how to prove it — the sharing model taught as a set of deliberate decisions.
Segments that survive six months, activation as a promise to another system, and honouring the customer's no.
Sharing and visibility as a design surface, decided end to end on one worked org.
What the board actually assesses: reading the scenario, solutioning against a clock, drawing it, presenting, and the Q&A.
The credential map read honestly, the four routes in, and what actually gets you hired.
The governance and observability half of Agentforce: the Trust Layer, evaluations, deployment and keeping an agent honest.
Waves land 4 Sep, 2 Oct and 9 Oct 2026. Why the Data 360 section looks thin, what the Agentforce renames signal, and the deprecations that actually break things.
Four ways to ground an agent in Data 360, when each is right, and why zero-copy federation is the wrong choice for the retrieval path of a live conversation.
Every Agentforce project has this argument in week three. The rule that sorts deterministic steps from generative ones, and why each half needs a different test.