37.7749° N/SF·26

You aren't bad
at Salesforce.

You're just buried in ticket debt. Claude Code gives you the architectural leverage to automate your backlog and finally step out of the reactive firefighting trap.

Become an AI-Native Salesforce Admin →See what changes in Module 1
01Built for admins buried under tickets and technical debt
02Developer-level leverage. No Apex background required.
03Project-based: nine modules, one capstone org you ship
prompt.md
> Build a validation rule preventing
opportunities from closing without
a primary contact role.▍
org · metadata● connected
objects/94
Opportunity.objectread
OpportunityContactRolescan
flows/28
validationRules/142
RequirePrimaryContactRole.rulegenerated · 4s
1  AND(
2    ISPICKVAL(StageName, "Closed Won"),
3    NOT(HasPrimaryContact__c)
4  )
Live composition
SECTION 01 / HERO
02Why this exists
A problem statement

Admins stop building.
They start maintaining.

Most Salesforce admins are exhausted from being the smartest person in the room with the least amount of power. You sit at the center of the company's nervous system. You see the entire machine. But every fix becomes another Jira ticket, another dependency, another sprint, another compromise. Claude Code changes that.

Get the leverage →
  1. 01

    Why reporting is broken

    Filters drift. Roll-ups don't match what leadership thinks they do. Last quarter's number changed twice.

  2. 02

    Why reps hate the CRM

    Six required fields on the opportunity. Three picklists that should be one. The path component nobody trained them on.

  3. 03

    Why onboarding takes too long

    Perm sets layered on perm sets. Page layouts no one can explain. New reps wait two days for access that should take ten minutes.

  4. 04

    Why the flows keep failing

    The brittle ones. Bolted on top of three years of “quick” automations. They break every release. Nobody owns them.

  5. 05

    Why leadership doesn’t trust the pipeline

    Because the forecast process is stale, the close-date discipline is missing, and the dashboard pulled the wrong field. Again.

03The split
Two admin eras, side by side

Admin work is about to
split into two eras.

One half keeps clicking, fighting the queue, and maintaining. The other half orchestrates systems, prototypes instantly, and operates with metadata intelligence. The split is already underway.

admins.old-era● fading
  1. 01Click-heavy.
  2. 02Ticket-driven.
  3. 03Reactive.
  4. 04Maintenance work.
  5. 05Dependency on engineering.
  6. 06Setup menu memorization.
admins.ai-native● ascending
  1. 01Prompt-driven.
  2. 02Architectural.
  3. 03System-level thinking.
  4. 04Instant prototyping.
  5. 05Metadata intelligence.
  6. 06Operational leverage.

The admins who learn this shift become indispensable.

01
PROMPT
Prompt
Plain English request from the admin
→
02
AGENT
Claude Code
Reads your project context
→
03
META
Org Context
Metadata, schemas, flows, rules
→
04
DIFF
Reviewed Output
You read it. You approve it.
→
05
SBX
Sandbox
Validate before production
→
06
PROD
Production
Deploy with confidence
VoiceField testimonial
Todd Barry · Salesforce admin

What changed for
Todd Barry.

Todd Barry, Salesforce admin · field testimonial
Project structure
Three files · one folder

Open VS Code.
Drop in your org.
That's the install.

Claude Code reads three plain text files the way a new hire reads onboarding docs. Write them once. The model speaks fluent your-org from then on.

  1. 01
    claude.md
    The voice.
    Tone, naming conventions, what "good" looks like in your org. The model writes the way you write.
  2. 02
    project.md
    The map.
    Objects, fields, flows, business processes you actually run. Written once, referenced forever.
  3. 03
    agents.md
    The crew.
    Specialized agents for flow review, security audit, documentation, migration. Wired up, ready to call.

Three files. No syntax. No magic. Just context.

ccforsf-org / claude.mdVS Code
EXPLORER
▾ ccforsf-org
mdclaude.md
mdproject.md
mdagents.md
▸ flows
▸ objects
▸ permissionsets
# CC for SF · org

> Voice. Naming. Guardrails.

## Voice
- Plain language. Short sentences.
- Show the diff before you propose.

## Conventions
- Custom fields end in __c
- Flows live in /flows
- Validation rules use AND() / NOT()

## Guardrails
- Sandbox first. Always.
- No bulk DML without review.
mainUTF-8Markdown
SignalThe market is converging here
Anthropic · SaaStr AI 2026 keynote
Anthropic SaaStr AI 2026 slide titled 'We built on what's already working' showing Salesforce as the system of record with Claude doing the work between Gong, Jira, Fin, Ironclad, Snowflake, Slack, Gmail, Clay, and LeanData
Anthropic · SaaStr AI 2026
James Wang · RevOps @ Capchaseon LinkedIn

Salesforce is a perfect GTM data lake. Most GTM tools sync into it natively. Claude sits on top through the Salesforce MCP server — the intelligence layer that reads the system of record and surfaces insights that used to take hours to pull manually. Capchase and Anthropic arrived at the same architecture independently. That's not a coincidence.

Salesforce as the
GTM data lake.
Claude on top.

Anthropic showed their own GTM stack at SaaStr AI 2026. Salesforce sits in the middle as the system of record. Gong calls, Jira tickets, Slack comms, Snowflake warehouse, Clay enrichment — all of it pipes in. Claude sits on top, connected through the Salesforce MCP server, doing the work between the tools.

Salesforce was already the GTM data lake. Now Claude is the intelligence layer that reads it — surfacing in seconds what used to take an analyst an afternoon. The architecture on the left — from Anthropic's own GTM team — confirms it.

SignalThe future is headless
API-first · CLI-ready · AI-native

The UI is dying.
Admins who adapt win.

Salesforce is moving to APIs, CLI, and AI-first workflows. Clicking through Setup will not be enough anymore.

Admins who can command Salesforce will build faster, earn more, and stay in demand.

This is how you get ahead before everyone else catches on.

Conference speaker on stage
Marc Benioff@Benioff

Welcome Salesforce Headless 360. No browser required. Our API is the UI. Salesforce, Agentforce, and Slack are now exposed through APIs, MCP, and CLI.

Salesforce signal · Headless workflows
04The shifts
Three emotional shifts · same product

Most admins already know
exactly what should happen.
The bottleneck is execution.

Claude Code collapses the distance between what you imagine and what you can actually ship. Three shifts, real artifacts, no fluff. Each one is a thing you'd normally have to file a ticket for.

See the shifts →
★Admin Backlog42 items · sorted by Priority
List View · Recently Modified⌕ Search this list…
#
P
Subject
Owner
Age
Type
T-2841
High
Territory routing flow for net-new Leads
Sarah K.
14d
Flow
T-2837
High
Validation: Close Date required at Negotiation
Marcus R.
9d
Rule
T-2829
Med
Audit profiles with Modify All on Account
Priya S.
22d
Audit
T-2818
High
Migrate Quote Builder Aura → LWC
DevOps
31d
LWC
T-2807
Low
Document active Opportunity flows
Unassigned
6d
Docs
T-2792
Med
Permission set: Finance read-only on Opp
Sarah K.
18d
Perms
T-2774
High
Apex test class for CommissionTrigger
Marcus R.
27d
Apex
+ 35 more   ·   oldest item: 89 days
Live list view · BrightPath sandboxEvery row is a Tuesday afternoon you don't get back.
01Shift 01 · scroll to advance
01 / 03
01Shift 01
Imagine → ship

Stop feeling trapped inside your own org.

PostSurveyAutoUpdate.flow-meta.xml42 lines · validated
YOU
Build a record-triggered flow that promotes the Opportunity to Proposal when the Site Survey completes, files a panel-upgrade task, and Chatter-warns on heavy shade.
CLAUDE CODE
<Flow xmlns="urn:sf...">
  <decisions>
    <name>Survey_Complete</name>
    <rules>
      <conditions>
        <field>Survey_Status__c</field>
        <operator>EqualTo</operator>
        <value>Complete</value>
      </conditions>
    </rules>
  </decisions>
  <actionCalls>
    <name>Promote_To_Proposal</name>
    ...
05Live walkthrough
An hour's work · in three minutes

From a sentence
to a deployed Flow.

A real recording from my dev org. One prompt builds the flow, connects it to Salesforce DX, and runs the test loop end-to-end. The kind of thing that used to eat a full afternoon.

UpdateContactRoleOnClosedWon.flow-meta.xml● live · 3 min
Caption“I used to be deathly afraid of flows. Now all I do is test them. Claude does the build.”
0100:12
The prompt
“Hey Claude, create a contact-role flow on the Opportunity object. When an opportunity is closed, update the contact's role.”
0200:38
Flow generated
Claude reads the org via Salesforce DX, drafts UpdateContactRoleOnClosedWon, and auto-optimizes the trigger so it only fires on the transition to Closed Won.
0301:25
Tested in the org
Open the flow in Setup. It's there. Confirm record-triggered, after-save, decision-maker assignment.
0402:40
End-to-end
Relate a Contact to the Opportunity (Claude does it via anonymous Apex), close the deal, watch the Contact's role flip to Decision Maker.
06The curriculum
Nine modules · BrightPath Energy capstone

Nine modules.
Zero fluff.

Every module is project-based. You'll build real components, write real Apex, and ship real automation. Not watch someone else do it.

  1. 01

    Setting up Claude Code for Salesforce

    Install Claude Code, connect it to your org via the Salesforce DX MCP server, and tune your CLAUDE.md file so every prompt knows your fields, your flows, your code. The 20-minute setup that makes the next eight modules work.

  2. 02

    The prompt patterns that actually work

    Copy-paste prompt templates for LWC, Apex, SOQL, Flow, and metadata work. Not theory. The exact structure that returns shippable code on the first try.

  3. 03

    Fields, layouts, and permissions on autopilot

    Create custom fields, drop them on the right layouts, and update permission sets in one prompt instead of fifteen clicks across Setup. Works for standard and custom objects.

  4. 04

    Validation rules without the formula fog

    Five validation rules, each teaching a different concept: text format, cross-object lookups, state machines with PRIORVALUE and ISCHANGED, running-user context with $Profile, multi-select picklists with INCLUDES. You'll never copy from Stack Exchange again.

  5. 05

    Flows from plain English

    Describe the automation in one sentence. Get a working Flow. Screen flows, record-triggered, scheduled. Plus the patterns that keep your Flows fast and bulkified.

  6. 06

    Approval processes the native way

    Two real approval processes built with the engine that already ships with Salesforce: Opportunity discount routing and high-cost warranty claim approval. Plus the moments when you should not use Flow for this.

  7. 07

    Apex triggers that solve Flow's blind spots

    Three triggers every admin first tries to build in Flow and then quietly gives up on: cascading owner changes, smart Lead deduplication, and a Custom Metadata-driven Case status state machine. Each one comes with a full prompt, a handler class, and a test class.

  8. 08

    Lightning Web Components, real ones

    Build ten production-grade LWCs on the BrightPath capstone org: timeline, kanban, calendar grid, installer heatmap, document checklist, and more. Each one ships with CSS, an Apex controller, and a metadata file.

  9. 09

    Capstone: BrightPath Energy

    Ship a full working Salesforce org for a fictional solar company in Austin. Nine objects, twenty-five-plus custom fields, five validation rules, four flows, two approval processes, three Apex triggers, one batch job, ten LWCs, and a hundred-plus seeded records. The portfolio piece you can actually show a hiring manager.

Sixty-plus prompts. Hours of video. One real Salesforce org you build from scratch.

07What you're really buying
Escape velocity

You are not buying
an AI course.
You are buying escape velocity.

Escape velocity from:

  1. 01

    ticket queues

  2. 02

    operational suffocation

  3. 03

    endless reactive work

  4. 04

    dependency on engineering

  5. 05

    feeling “technical, but not technical enough”

  6. 06

    feeling trapped maintaining systems you know could be better

The moment admins feel Claude Code working inside a real org, something changes. They stop feeling like support staff. They start feeling like operators.

07What it looks like
Prompt → reviewable artifact

The kind of thing
an admin would say.

A snapshot of the prompt-to-artifact loop you'll run every day in the course. The example on the right is real output from a real org. Below: other prompts admins use to put Claude to work.

Other things admins ask Claude
→Draft a Flow that creates a follow-up task when a Lead is converted but the account has no opportunities.
→List the metadata changes I'd need to add a 'Health Score' field to Account, with formula and page layout updates.
→Audit which permission sets grant access to the SSN__c field on Contact and flag anything risky.
demo · prompt → artifact● example
Write a validation rule that requires a Close Date in the future for any Opportunity in 'Negotiation' stage.
AND(
  ISPICKVAL(StageName, "Negotiation"),
  OR(
    ISBLANK(CloseDate),
    CloseDate <= TODAY()
  )
)
08What this looks like in real life
Before · After

The org stops feeling
heavier than you.

before.txt● heavy
  1. —Waiting weeks for dev bandwidth.
  2. —Manual documentation.
  3. —Clicking through Setup.
  4. —Fear of breaking production.
  5. —Constant firefighting.
after.txt● operating
  1. +Prototype instantly.
  2. +Audit entire systems conversationally.
  3. +Generate documentation automatically.
  4. +Ship changes independently.
  5. +Understand org architecture clearly.
08Safety & trust
How to operate without breaking things

Speed,
without chaos.

The course is structured around four operating principles. They're how you keep the leverage of AI without giving up the discipline that production orgs demand.

Ship fast, stay safe →
01

Review everything

Every diff is yours to read before it ships. The model proposes; you dispose.

02

Sandbox first

Validate against a sandbox org. Promote only what passes.

03

Partner, not autopilot

Claude Code is leverage on top of your judgment, not a replacement for it.

04

Governance respected

Existing Salesforce permissions, profiles, and SOX controls all still apply.

09Instructor
Built by an operator
Amit, instructor. 8× Salesforce Certified, GTM Engineer.
AmitSF·26
8×Salesforce Certified
·GTM Engineer
·AI Tools Builder

Stop being a
"point-and-click" admin.
Start being a Salesforce
architect.

I've spent years in the Salesforce ecosystem doing RevOps, sales operations, and CRM architecture. I was the admin who was scared of Flows. When Claude Code came out, everything changed.

I went from filing Jira tickets and waiting two weeks to just… building the thing myself. This course is everything I wish someone had shown me on day one.

- Amit
Avan Grid · Solo AdminSlalom · Salesforce Consultantdice.com · Business Systems DirectorwebAI · RevOps Manager
More about me
11Identity shifts
Illustrative outcomes · real testimonials at launch

You stop feeling like
support staff.

The three lines below describe what the course is built to produce. They are illustrative — sample student outcomes used to communicate the promise of the course, not attributed quotes. Real cohort testimonials will replace these at first cohort.

I've been a Salesforce admin for 8 years and this was the first time I felt like I could actually think architecturally instead of just managing tickets.
Illustrative
Sample student outcome
Claude made me realize how much operational intelligence I already had trapped in my head.
Illustrative
Sample student outcome
I stopped feeling like the person who maintains Salesforce and started feeling like the person shaping how the company operates.
Illustrative
Sample student outcome
I've been a Salesforce admin for 8 years and this was the first time I felt like I could actually think architecturally instead of just managing tickets.
Illustrative
Sample student outcome
Claude made me realize how much operational intelligence I already had trapped in my head.
Illustrative
Sample student outcome
I stopped feeling like the person who maintains Salesforce and started feeling like the person shaping how the company operates.
Illustrative
Sample student outcome
DisclosureIllustrative student outcomes used to communicate the promise of the course. Not attributed quotes. Real cohort testimonials with full attribution ship after Cohort 01.
12Enrollment
One tier · everything included

One workflow can
justify the entire course.

You already understand the business. This teaches you how to finally move at the speed of your understanding. Not eventually. Immediately.

Open · Cohort 01

Claude Code
for Salesforce.

Become the operator your org actually needs. Architectural thinking, AI-native workflows, and the leverage to ship without waiting. One price. Everything included. Lifetime access.

  • ✓BrightPath Solar capstone: full org build, end to end
  • ✓6 custom objects + 25+ fields, fully wired with relationships
  • ✓3 Account / Opportunity record types and page layouts
  • ✓4 production Flows (screen, record-triggered, scheduled)
  • ✓2 Apex triggers with handler classes · 90% test coverage
  • ✓1 Apex batch + Schedulable job (annual production estimator)
  • ✓1 Lightning Web Component (Installation Timeline)
  • ✓Permission sets + custom app for 3 user personas
  • ✓100+ records of seeded data · 2 reports + 1 live dashboard
  • ✓Installation walkthrough for VS Code
  • ✓Lifetime access · all future updates
  • ✓CLAUDE.md Starter Template + Skill Pack for Salesforce
Launch price · USD
$197reg. $697
One-time · lifetime access
Secure checkout
Loading secure checkout…
Guarantee

30-day money-back, no questions asked. Go through the course; if you didn't level up your admin skills, email me for a full refund.

No Salesforce add-on license required beyond Enterprise / Unlimited / Developer edition.

+ 03Bonuses · included free
Three bonuses, yours at no extra cost

The extras that make this
a no-brainer.

Course alone gets you the skill. These bonuses get you the unfair advantage: the community, the receipts, and the tools I personally won't ship without.

Bonus 01
The Inner Circle

Private Slack for course members.

When 'just ask the team' isn't an option.

You're the solo admin. Or the senior on a two-person team. Either way, there's no Slack channel to drop your weird Flow error into at 4:55pm on a Friday. This one is. Working admins, the instructor, and the kind of community where 'is this CPU-time limit normal?' gets answered in 12 minutes, not 12 days.

✓ IncludedLifetime access
Bonus 02
The 1:1 Call

Free 15-minute discovery call with Amit.

Bring any question. No agenda required.

Ask how to break into Salesforce consulting. Ask why your Claude Code session keeps going sideways on the same Apex class. Ask which AI tool to layer on top of your current stack. Whatever's blocking you, get a real answer from someone who's shipped it — and walk away with a next step.

✓ Included1:1 with Amit
Bonus 03
The Plugin Pack

Handpicked Claude Code plugins for serious leverage.

My personal plugin stack for faster Claude Code work.

You get the exact plugins I use to make Claude Code more useful across real projects, including Superpowers and Claude Mem. These are the productivity boosters, memory tools, workflow helpers, and repo habits I trust when I want Claude to move faster without losing context.

✓ IncludedCurated by Amit
Course · twelve modules + capstone✓ Included
Bonus 01 · The Inner Circle (lifetime)✓ Included
Bonus 02 · 1:1 Discovery Call with Amit✓ Included
Bonus 03 · The Plugin Pack✓ Included
Regular price$697
Your price today$197
12Frequently asked
Practical objections, answered

Questions, answered.

The honest version of every question that gets asked before enrollment.

14The next era

The admins who learn this now
will define the next era
of Salesforce.

The future belongs to operators who can think systemically and execute instantly.

Enter the AI-Native Era →See the curriculum

You were never the bottleneck. The tooling was.