Red Pill or Blue Pill: The SMB Guide to AI on Salesforce
Salesforce wants to sell you Agentforce. Sometimes that's the right answer. For most small-business workflows, it isn't. Here's the map — and the cost math to back it up.
Two pills, one Salesforce
At TDX 2026 Salesforce made a big, confident bet. They called it Headless 360 — an umbrella for Agentforce Vibes 2.0, Agent Script, DevOps Center MCP, the Experience Layer, Testing Center, Agent Fabric, and a reworked Partner Program that now pays partners on AI outcomes rather than implementation hours. Read the announcement and you'd be forgiven for thinking every Salesforce customer is about to be running AI agents inside their org by the end of the year.
It's an exciting direction. It's also one direction.
I want to offer my clients — especially my small and mid-sized clients — a more accurate map. There are two viable paths for bringing AI to a Salesforce practice right now, and the right answer depends entirely on the workflow, not on which SKU a Salesforce AE has quota to sell this quarter.
I call them the Blue Pill and the Red Pill.
The right answer depends entirely on the workflow, not on which SKU a Salesforce AE has quota to sell this quarter.
Eric Lovgren, lovgren.ai
The Blue Pill: Agentforce and the Salesforce-native stack
Take the Blue Pill and you stay inside the Salesforce world. Agents run on Salesforce-hosted infrastructure. They're defined in Agent Script, tested in Testing Center, deployed through DevOps Center MCP, governed by Agent Fabric, and exposed to end users through the Experience Layer in Slack, Teams, ChatGPT, Claude, or Gemini. Everything is inside the trust boundary Salesforce has built over twenty-five years. Everything is covered by Salesforce's support contract and Salesforce's regulatory certifications.
For a large swath of workflows, this is exactly what you want:
- Public-facing agents your customers interact with directly.
- 24/7 autonomous workflows that need to run whether a human is awake or not.
- Regulated or sovereign-runtime requirements — healthcare, financial services, government — where "the AI runs inside the platform we've already been audited on" is a meaningful compliance story.
- Enterprise write-privilege at scale where you need Testing Center, Observability, Session Tracing, and a Salesforce SRE on the other end of a support ticket when something breaks at 2 a.m.
The cost of the Blue Pill is usage-based. You'll see it billed as Flex Credits at roughly $0.10 per agent action, $2 per standard-tier conversation, or $125–$550 per user per month on the Agentforce SKU depending on tier. Your cost curve scales linearly with volume — every additional action is another dime.
For the workloads above, that dime is often worth it. You're paying for a runtime your organization has already certified, integrated, and trained on.
The Red Pill: Claude, MCP, and Salesforce as the data backbone
Take the Red Pill and you flip the architecture. Your team — admins, analysts, operations — sits in front of Claude Desktop, Claude Code, or Claude's Cowork mode. Salesforce is still the system of record. Claude talks to it through the Model Context Protocol (MCP), which is an open standard that exposes Salesforce data and operations as tools any AI assistant can call.
In this model the admin is the agent. You ask Claude in natural language: "Clean up the duplicate accounts in the manufacturing segment." "Draft a governance risk brief for Monday's steering committee based on these five field changes." "Reach into our Machinify Spiff calculations and tell me why the March commission run under-paid Rep X by $412." Claude reads, reasons, writes back to Salesforce, and shows its work. You approve or correct. Nothing runs unless you push the button.
In this model, the admin is the agent.
Eric Lovgren, lovgren.ai
The cost structure is radically different. You pay a flat Claude subscription — Pro at $20 a month, Team at $30 a user, Max at $100–$200 a month — and you use Salesforce admin licenses you already have. Your cost curve is flat. Ten actions or ten thousand actions, the bill is the same.
The Red Pill is the right answer for a different — and, for SMBs, much larger — class of workflows:
- Admin-in-the-loop work. Field changes, data cleanups, permission-set reshuffles, report rewrites, flow refactors. An admin reviews the output; nothing autonomous is required.
- Batch and back-office. Monthly commission audits, quarterly territory reshuffles, annual renewal analyses. The work doesn't need to run 24/7, so you shouldn't be paying 24/7 pricing.
- Async analysis. "Research this industry." "Compare these three vendors." "Summarize last quarter's support cases by theme." Things you need thought from, not a robot for.
- Cost-sensitive SMBs where a per-action price, multiplied across every admin task, adds up to a budget line the founder never authorized.
The two paths, side by side
| Blue Pill (Agentforce) | Red Pill (Claude + MCP) | |
|---|---|---|
| Cost curve | Per-action, scales with volume | Flat subscription |
| Best-for workloads | Customer-facing, 24/7 autonomous, regulated runtimes | Admin-in-the-loop, batch, back-office, async analysis |
| Who's in the loop | Runs autonomously | Admin approves every action |
| Who builds it | Salesforce-native tooling and SRE | Your existing admin, with Claude |
| Fits ~70–80% of SMB cases | ✗ | ✓ |
A concrete cost example
Imagine a mid-sized service company with a Salesforce org and a single admin. They want to auto-categorize inbound cases, clean up their account data weekly, generate quarterly commission audit reports, and help a senior ops person draft governance memos. Put numbers on it:
- 3,800 agent actions per month (roughly 125 per business day)
- Blue Pill: 3,800 × $0.10 × 12 = $4,560 per year in Flex Credits alone, before any Agentforce SKU or implementation work
- Red Pill: Claude Team at $30/user × 1 admin × 12 = $360, or Claude Max at $200/month × 12 = $2,400, plus the same Salesforce admin license they already had
$4,560
Blue Pill / yr (Flex Credits)
$1,080–$2,400
Red Pill / yr (flat)
That's $1,080–$2,400 a year instead of $4,560, and the Red Pill number is flat. Doubling volume doesn't double it. For an SMB with a tight operating budget, that's not a rounding error — that's the difference between an AI program that ships and one that stalls at "let's revisit next quarter."
This is not a hypothetical. I run my own Salesforce practice this way. Agentforce is enabled in my org. I deliberately do not use it for admin work. I sit in Cowork with Claude, talk to Salesforce through MCP, and do the job. I'm selling the operating model I live in.
When the Blue Pill still wins
I don't want to be a one-note advisor. There are situations where the Blue Pill is clearly right and I'll recommend it without hesitation:
Customer-facing agents (case-deflection bots, appointment booking, self-service shopping guides) belong in the Experience Layer. Regulated verticals where the auditor wants a single certified runtime. True 24/7 autonomy with write-privilege at scale and no admin in the loop. And programs already spending enough on Agentforce that the per-action price is amortized into a fixed cost — where Testing Center, Observability, Session Tracing, and Agent Fabric are earning their keep.
For those workloads, the Blue Pill earns its dime.
Why so few Salesforce partners offer the Red Pill
This is the part most partners won't say out loud, so I'll say it: most Salesforce consulting firms are compensated in ways that reward selling you more Salesforce. Partner tiers, Summit-level incentives, AE-referred pipeline, bonuses tied to SKU attach rates — the economics push the partner to recommend the Salesforce-native answer even when a cheaper, simpler answer exists for the client.
A partner on the Salesforce side of the table cannot credibly tell you "skip Agentforce here," because their economics punish them for saying it.
I've deliberately structured Lovgren Consulting Group to sit on the other side of that incentive table. I've declined partner-program tiers that require me to send leads back to Salesforce. I don't take work from Salesforce AEs, because the moment I do, the AE is my real client, not you. I find clients through referrals and content, and I stay with those clients for years — long past the one-year rotation of whoever the Salesforce AE happens to be this cycle.
That client-alignment is the only reason I can write this post.
My recommendation
For most of my small and mid-sized clients, here's my answer:
- Use the Red Pill for 70–80 percent of your AI work — the admin, analysis, back-office, and async workloads.
- Use the Blue Pill for the specific, high-value, customer-facing, or autonomous workloads where it earns its cost.
- Don't buy the pitch that your org is going to be "AI-native" by running every workflow through Agentforce. Be thoughtful. Be parsimonious. Measure.
If you're a business owner or an ops leader on Salesforce and you'd like a straight-talk review of which pill fits which workflow in your org, that's exactly the conversation I'm here to have. I'll implement either path. I'll tell you when to pay the dime and when not to. And I'll stay on your side of the table while we do it.
— Eric Lovgren
Lovgren Consulting Group