Agentforce ROI Calculator: How It Works and What It Really Costs (2026)

TL;DR: An Agentforce ROI calculator estimates the three-year net benefit of Salesforce AI agents: the labour you save, minus what the agents cost to run in Flex Credits. Salesforce's official calculator is free and quick, but it runs on built-in assumptions (a fixed per-case agent cost, a 70% year-on-year ramp) and excludes implementation, licences, and Data 360. Read its benefit line as a ceiling and its cost line as a floor. Run your own numbers on our Agentforce ROI calculator, then use this guide to turn the estimate into a figure you can defend.

What is the Agentforce ROI calculator?

The Agentforce ROI calculator is Salesforce's free, no-login tool for estimating the financial return of deploying Agentforce agents. You pick use cases, enter a few operational numbers, and it returns a year-by-year view of productivity benefit, agent cost, net benefit, and the Flex Credits you would consume. Salesforce labels the output as illustrative only, and states that implementation costs, Salesforce licences, and Data 360 credits are not included.

Two versions are now in circulation. Some regional editions of the official ROI calculator still show the classic three-year ROI model. The US page has been reworked toward a first-year pricing estimate built from seats, actions per agent template, and Data 360 inputs, rounded up to the nearest 100,000 credits. If you searched for an ROI figure and got a price, that is why. Partners publish their own variants; ours focuses on support teams and estimates ticket deflection, freed headcount, and payback from numbers you already know.

How does the Agentforce ROI calculator work?

The three-year model follows the same three steps for every use case:

1. Pick your use cases. The presets are Customer Service, Sales Development Rep, Sales Coach, Field Service and Back Office, Employee Help in Slack, Loan Product Assistance, Quoting, and Customer Insights in Slack. Each has its own action profile, so a service agent and an SDR agent produce very different math.
2. Enter your numbers. Headcount, salary, volumes (cases per rep per day, leads per rep per week, quotes per week), and a year-three target for the share of work agents absorb. Sales presets add conversion rate, deal size, close rate, and gross margin.
3. Read the projection. You get productivity benefit by year, agent cost, net benefit, the cost of doing nothing, total Agentforce investment, and an estimated Flex Credit total.

The assumptions the calculator makes for you

The inputs you type are only half the model. The other half is a set of built-in defaults that Salesforce discloses on the page but most users never read:

• Customer Service: each agent-handled case costs about $0.30, and adoption ramps so year one is 70% of year two and year two is 70% of year three.
• Appointment Scheduling: about $0.43 per scheduled appointment, based on 4 to 5 actions.
• Employee Help in Slack: agents resolve 30% of questions in year one, 40% in year two, and 50% in year three, at $0.20 per task.
• Sales Development Rep: about $0.84 per lead, with untouched leads converting to qualified leads at 50% in year one, 75% in year two, and 100% in year three.
• Quoting: a 20% efficiency gain at $0.40 per quote.

Those per-unit costs are the real lever. If your agent takes twice the actions Salesforce assumes, your cost line doubles while the benefit line stays put. The year-three target matters just as much: a 50% target and a 20% one produce very different paybacks, so anchor it to a small pilot rather than a vendor default. Check which of these inputs the headline number quietly depends on.

How is Agentforce priced in 2026?

You cannot trust an ROI number without understanding the meter behind it. According to Salesforce's pricing page, Agentforce is sold in four ways:

• Flex Credits: $500 per 100,000 credits. A standard or custom action uses 20 credits (about $0.10) in production and 16 in a sandbox, and an Agentforce Voice action uses 30 credits (about $0.15). Prompts run through Salesforce-enabled models also consume credits, from 2 for a basic prompt to 16 for an advanced one, per the Flex Credits rate card.
• Conversations: a flat $2 per conversation, regardless of how many actions it contains.
• Per-user add-ons: $125 per user per month for Sales, Service, and Field Service, and $150 for Industries clouds. A $5 Agentforce User License is also listed, which requires Flex Credits.
• Editions: in September 2026 Salesforce replaced its edition lineup with Core ($195 per user per month, 500,000 Flex Credits), Advanced ($395, 1 million credits), and Max ($550, 2.75 million credits). Max takes over from Agentforce 1 Edition at the same price, and existing Agentforce 1 customers can move to it at no extra cost.

The break-even between the two consumption models is simple arithmetic: $2 buys 20 standard actions at $0.10 each. A conversation that takes 5 to 15 actions costs $0.50 to $1.50 on Flex Credits, so short, deterministic agents favour credits and long, multi-step sessions can favour the flat rate. If your calculator assumes a single per-conversation price, its cost line is wrong in one direction or the other.

Three more lines belong in the model. Enterprise Edition customers and above can get 100,000 Flex Credits free through Salesforce Foundations, according to Salesforce Help, which is enough to prototype before you commit. Customer-facing agents in Salesforce's estimator include an assumption of 10% sandbox credit use, so testing is not free. And Data 360 consumption is billed separately from the agents. Salesforce marks all of this pricing as subject to change, so recheck before you put a figure in front of finance. Each model shifts the payback month differently.

Can you estimate the ROI of AI-powered phone agents like Agentforce?

Yes, and it is worth doing as its own line, because a voice action costs 50% more than a standard one. You model call volume and average handle time the way you would cases, but you price credits against voice actions and count actions per call rather than per chat.

The calculator assumes the telephony is already in place. In practice a phone agent needs a CTI layer that brings call routing, logging, and live caller context into Service Cloud so the agent has something to act on. Budget that integration and its per-seat licensing separately, or your phone-agent payback will look better on paper than in the bank.

What does the Agentforce ROI calculator leave out?

Every calculator shares one blind spot: it prices the software, not the project. The number assumes the agents are already built, integrated, and trusted. Six costs live outside the tool, and together they often outweigh the software line:

• Data readiness and Data 360. Agents are only as good as the records they read, so deduplication, field hygiene, permissions, and grounding are real line items. Data 360 is optional for agents that only need native CRM data, but required once an agent needs unified or unstructured data, and Salesforce excludes its credits from the ROI output.
• Implementation labour. Topics, actions, instructions, guardrails, testing, and rollout. Some use cases are a few clicks; others need custom actions and Apex, and the calculator does not know which you face.
• Integration. Every system an agent must read from or write to (telephony, billing, ticketing, ERP) is a small project of its own, not a checkbox.
• Change and adoption. Salesforce's own disclaimer names implementation practices and user adoption as factors in actual results. A deflection target you never train your team to hit is fiction.
• Governance and security. Audit, privacy alignment, and agent monitoring are recurring work, not a one-time setup.
• Attribution. Isolating the agent's impact from concurrent staffing or process changes needs a measured baseline, not a projection.

The gap between an agent as a demo and an agent as a dependable decision-support platform is exactly where projects stall; we wrote about closing it in what it takes to drive ROI from AI agents.

How do MCP and headless agents change the integration line?

The biggest recent shift in that integration line is the Model Context Protocol (MCP), the open standard for connecting agents to tools and data. Salesforce announced MCP support across its platform in June 2025, including a native MCP client for Agentforce, and its MCP gateway adds a central server registry, access controls, and rate limiting. In April 2026 it launched Headless 360, which exposes core Salesforce functions as APIs, MCP tools, and CLI commands, with more than 60 new MCP tools at launch. The new Max edition is slated to include an allocation of Headless 360 capacity.

For an ROI model, that means an agent can reach external systems through one standard handshake instead of a bespoke connector per system, and agents can run inside your own product or workflow rather than only inside the Salesforce UI. Done right, it lowers the per-connector build cost older ROI models never captured, but only when your data and permissions are already in order. Tekunda is the first and only firm delivering headless Salesforce with MCP in production, building the MCP servers and the headless CRM implementation together. We cover the adoption path on our headless MCP on Salesforce page.

How do you turn the estimate into a number you can defend?

Treat the calculator output as step one, then do four things:

1. Capture a real baseline first. Average handle time, interaction volume, cost per interaction, resolution rate, and escalation rate. A calculator that starts from a guessed baseline returns a guessed ROI, and every post-launch gain should be a measured delta against these numbers.
2. Right-size the automation target. Replace the default year-three target with what a pilot actually achieved on your case mix and knowledge coverage. We cap our own estimate at a deflection we have sustained in production (see our ASSA ABLOY engagement), not a marketing best case, because an inflated rate produces a payback no one hits.
3. Replace the per-unit cost with a real action count. Count the actions a representative conversation takes, price them against the billing model you will run, add sandbox testing and prompt consumption, then add Data 360 if your agents need it.
4. Put the project in the investment line. Integration, data preparation, and change management belong there, and payback should be the month cumulative savings overtake cumulative spend, not a three-year total.

The result will almost always be smaller and later than the calculator's figure. That is the point: a conservative number that lands is worth more than an optimistic one that gets the programme cancelled in year two.

Do you need a security review or a Salesforce PDO?

For an internal Agentforce rollout, no AppExchange security review applies; that gate is for managed packages listed on the AppExchange. If you are an ISV building an agent-powered product to sell, it does apply and it belongs in your model: a paid submission fee, a code and behavioural audit against secure coding practices, and scans you now run yourself since Salesforce retired its hosted Chimera scanner. Working through the security review checklist up front is far cheaper than a failed submission.

That distinction also decides the partner type you need. A system integrator implements Salesforce inside your business; a Salesforce PDO (product development outsourcer) designs, builds, and maintains commercial AppExchange apps and shepherds them through the review. Internal rollouts want implementation depth; an ISV shipping an agent-powered product wants PDO experience.

How do you choose an Agentforce implementation partner?

A calculator gives you a target; a partner gets you there, and the calculator's blind spots are exactly where that partner earns its fee. Ask for specifics on four things: an agent they shipped to production, not demoed; how they integrated it; the deflection they actually measured; and whether they price against current Flex Credit and edition rates rather than a stale spreadsheet. Then ask them to rebuild the estimate with your real data before you sign anything.

The calculator also cannot tell you whether to configure Agentforce or build a custom agent: standard use cases with clean data favour configuration, while deep, differentiated workflows sometimes justify a custom build. We lay out that decision in Agentforce vs custom AI agents. Either way, Tekunda builds, integrates, and ships the agents behind these numbers, which is why our estimates start conservative. See how we approach Agentforce, or talk through your numbers once the estimate is worth acting on.

FAQ

Is the Agentforce ROI calculator free?

Yes. Salesforce's official calculator and Tekunda's are both free and return an estimate without a purchase.

How accurate is the Agentforce ROI calculator?

It is directional. It relies on built-in per-unit costs and ramp assumptions and excludes implementation, licences, and Data 360, so pressure-test it against a pilot.

How much does an Agentforce action cost?

A standard action uses 20 Flex Credits, about $0.10 at $500 per 100,000 credits. A voice action uses 30 credits, about $0.15.

Should I use Flex Credits or the $2 conversation model?

Below roughly 20 standard actions per conversation, Flex Credits are cheaper; above it, the flat $2 rate can win. Model both against a real action count.

Does the calculator include Data 360 costs?

No. Salesforce excludes Data 360 credits from the ROI output, so add them yourself if your agents need unified or unstructured data.