Salesforce admin to agentic AI: flows and validation rules as tools

What you already own

List these from your current org before day one. Each becomes part of the plan.

• Validation rules such as "Stage cannot be Closed Won without Amount and Close Date".
• Record-triggered and screen flows, with their entry conditions and fault paths.
• Permission sets and profiles that decide who can edit which fields.
• Reports and dashboards the sales team checks every Monday.
• Data Loader or import wizard CSVs from the last cleanup, with the error files.
• Change sets or deployment notes between sandbox and production.

Days 1–30: Python and the API, using your own org's shape

Goal: be able to read and write CRM-shaped data in code.

1. 1Learn Python basics until you can load a CSV, filter rows and write functions without looking up syntax.
2. 2Recreate one of your Data Loader error files synthetically and write a script that explains each failure in plain language.
3. 3Read how the CRM's REST API authenticates and returns records; practise against a developer or sandbox org, never production.
4. 4Write down, from memory, the five validation rules your users complain about most. You will need them in the next phase.

By day 30 you should have a small repository with a README describing what each script does.

Days 31–60: build the agent's guardrails before the agent

Goal: one project that shows you think like an admin about AI.

The project: an assistant reads a sales call summary and proposes updates to an opportunity. Before anything is saved, every proposal is checked against rules that mirror your validation rules and permissions. The script below uses synthetic proposals standing in for model output.

from datetime import date

# Rules mirroring typical CRM validation rules (hypothetical org)
STAGES = ["Prospecting", "Qualification", "Proposal", "Negotiation", "Closed Won", "Closed Lost"]
EDITABLE_BY_AGENT = {"stage", "next_step", "close_date", "amount"}

def check(current, proposed, today=date(2026, 9, 27)):
    problems = []
    for field in proposed:
        if field not in EDITABLE_BY_AGENT:
            problems.append(f"agent may not edit '{field}'")
    new = {**current, **proposed}
    if new["stage"] not in STAGES:
        problems.append(f"unknown stage '{new['stage']}'")
    elif new["stage"] == "Closed Won" and (not new.get("amount") or not new.get("close_date")):
        problems.append("Closed Won needs amount and close date")
    if "close_date" in proposed and date.fromisoformat(proposed["close_date"]) < today and not new["stage"].startswith("Closed"):
        problems.append("close date in the past on an open opportunity")
    if "stage" in proposed and new["stage"] in STAGES and current["stage"] in STAGES:
        if STAGES.index(new["stage"]) - STAGES.index(current["stage"]) > 2:
            problems.append("stage skipped more than two steps; needs human review")
    return problems

opportunity = {"stage": "Qualification", "amount": 480000, "close_date": "2026-11-30", "owner": "neha", "next_step": ""}

# Synthetic model proposals
proposals = [
    {"next_step": "Send revised proposal by Friday", "stage": "Proposal"},
    {"stage": "Closed Won", "amount": None},
    {"owner": "rahul"},
    {"close_date": "2026-09-01"},
    {"stage": "Demo Done"},
]

results = [(p, check(opportunity, p)) for p in proposals]
for p, problems in results:
    print("ACCEPT" if not problems else "HOLD  ", p, problems)

accepted = sum(1 for _, pr in results if not pr)
print(f"{accepted} of {len(results)} proposals would be saved automatically")
assert accepted == 1

Only the first proposal passes. The second tries to close a deal with no amount, the third edits a field the agent should never touch, the fourth backdates the close date, and the fifth invents a stage that does not exist. Each held proposal goes to the opportunity owner for approval instead of being written. That is the same design as a validation rule plus an approval process, applied to model output.

In your write-up, add a small labelled set of twenty call summaries, record how many proposals the model made per summary and how many the guardrails held, and note any case where a guardrail blocked a correct update. That last number matters: rules that are too strict make users switch the agent off.

Days 61–90: connect a model, measure, and tell the story

Goal: a working end-to-end demo and a clear explanation.

1. 1Replace the synthetic proposals with real model calls on synthetic call summaries, using structured output so the proposal arrives as fields rather than free text.
2. 2Run your labelled set, and report the accept, hold and wrong-accept counts.
3. 3Write a one-page design note in admin language: which fields the agent can touch, which permission set it runs under, and who approves held changes.
4. 4Prepare a five-minute walkthrough of the project for interviews.

The Generative & Agentic AI add-on at /courses/gaai covers structured output, tool use, agent state and evaluation over three months. If you want the broader analytics foundation first, the Data Analyst programme at /courses/da is the broader route.

CRM automation engineer before AI engineer

A realistic first target is a role that keeps your platform knowledge central: CRM or automation specialist working on AI features, AI solutions consultant for a CRM partner, or business systems analyst on a team rolling out agents to sales or service. A pure ML engineering title is a longer jump that would need deeper programming first.

Declarative admin to agent builder: the interview version

"I have run a Salesforce org for about three hundred sales users for five years. When we started talking about AI agents updating opportunities, I realised the risk was the same one I manage every day: bad data getting in. So I built a small project where a model proposes opportunity updates and every proposal passes checks that mirror our validation rules and permissions before anything saves. I can show you the numbers from my test set, including the cases where my rules were too strict. I want to work on agents that people can trust inside business systems, and I think admins understand that problem better than most."

To see how your current resume reads against AI roles, try the free skill check.