01
ChatGPT is an always-available technical pair partner
When the peer you'd normally ask is in a meeting, ChatGPT fills the gap. Christopher had a big formula that wasn't working, pasted it in, and it told him exactly what was wrong so he could test the fix — no waiting on a human to free up.
Why it matters: Salesforce admins and RevOps engineers can compress the debugging loop from 'wait for a colleague' to 'get a second opinion on demand,' which matters most on small teams where technical reviewers are scarce.
RevOps LeadersRevenue Executives
02
Plain-English in, working Salesforce config out
Christopher pastes a plain-language request — 'people should not be able to move an opportunity to SQL from Nurture unless the Type field has a value' — and ChatGPT returns a validation rule using ISCHANGED, PRIORVALUE, ISPICKVAL, ISBLANK and TEXT, which he copies straight into Salesforce.
Why it matters: The syntax barrier that once gated admin work drops away. Stakeholders can describe rules the way they think about the business, and the admin's job shifts toward reviewing and refining rather than hand-typing every formula.
RevOps LeadersRevenue Executives
03
Keep a human in the loop — 'no errors found' is not 'correct'
ChatGPT reported no errors on a validation rule that used ISBLANK on a picklist field, which doesn't behave as expected (you need to wrap it in TEXT). Christopher caught it by eye because he already understood the Salesforce gotcha.
Why it matters: LLM output still needs an operator who knows the platform's edge cases and the business context. Trusting generated config blindly ships silent bugs; a human review gate is non-negotiable.
RevOps LeadersRevenue Executives
04
Re-prompting refines the output like a peer-review loop
Christopher told ChatGPT its ISBLANK version had an error and it corrected itself; he jokes 'maybe it learned from this morning.' The 20–30-minute client formula he shows took a few prompts and re-prompts to get exactly right.
Why it matters: Treat the tool as an iterative collaborator, not a one-shot oracle — the same back-and-forth you'd have across a couple of meetings with a teammate, compressed into minutes.
RevOps Leaders
05
'What does this formula do?' turns AI into a translation layer
Pasting an inherited, jargon-dense formula and asking ChatGPT to explain it returns a plain-English breakdown — e.g., 'if the term end date is blank, it calculates the day by adding one year to the closed date' — including how it handles a leap year via MOD(YEAR, 4).
Why it matters: Admins can understand and document configuration they didn't write, and explain it to others in seconds instead of spending 20 minutes writing a page of explanation.
RevOps LeadersRevenue Executives
06
AI collapses the research tax on inherited Salesforce orgs
As Anthony notes, every new Salesforce instance is 'a complete labyrinth of workflows and validation rules' that a team has to reverse-engineer before doing any real work. Translation-on-demand shortens that discovery dramatically.
Why it matters: Onboarding to an unfamiliar org — a constant in fractional and agency RevOps — gets faster and less error-prone when you can ask the system to explain itself.
RevOps LeadersRevenue Executives
07
Two value modes: do it faster, or solve something more complex
Anthony's framing: leveraging AI either helps you do a known task faster, or helps you solve something harder by giving you inspiration for potential solutions you couldn't reach alone.
Why it matters: Evaluate AI use cases against both axes. Speed wins are obvious; the underrated win is unlocking work that was previously beyond an individual's skill ceiling.
RevOps LeadersRevenue Executives
08
Augmentation, not replacement — the email-and-paper precedent
Christopher counters the fear with history: in the '90s people thought email would kill paper, but it grew the industry (paper companies pivoted to the cardboard boxes now shipping from Amazon). He cites a Goldman Sachs estimate that 20–25% of jobs face automation, then asks how many jobs email erased versus created.
Why it matters: The default posture toward AI in RevOps should be adoption and augmentation, not defensive avoidance. History rhymes: new tooling tends to enhance technical roles and expand the work, not eliminate it.
Revenue ExecutivesRevOps Leaders