Agentforce Cost Calculator: Estimate Flex Credits and Monthly Spend for One Workflow

If you are trying to budget a single Agentforce workflow, the headline number rarely gives you the answer. Agentforce is priced by consumption, which means you pay for what an agent actually does, not for a fixed seat. That is useful when volume is unpredictable, but it makes one honest question surprisingly hard to answer: what will this one workflow cost per month?

The difficulty is that a single request usually breaks into several discrete actions behind the scenes. A customer asking about an order might trigger an authentication step, a record lookup, and a response. Multiply that across a real monthly volume and the "cost per interaction" you assumed can drift well away from the invoice. This guide walks through a simple, repeatable way to estimate Flex Credits and monthly spend for one workflow, using Salesforce's own pricing structure, so finance and IT can agree on a defensible number before committing.

Why Agentforce cost is hard to estimate for one workflow

Three things make workflow-level budgeting harder than it looks.

First, consumption pricing ties cost to activity rather than to a predictable seat count, so your estimate depends on how often the workflow runs and how much work each run involves. Second, a single request commonly performs more than one metered action, so the "per conversation" or "per action" figure people quote is not the same as the cost of completing a real task. Third, the consumption model is chosen at the org level, so the model that is cheapest for one workflow may not be the model your org has selected for everything else.

The practical result is that teams tend to over-anchor on the most quotable number and then get surprised. A better approach is to estimate from the workflow itself: how many actions per run, how many runs per month, and which pricing model applies.

How Agentforce pricing actually works

Before you can estimate anything, it helps to be precise about the model. The rates below change over time, so treat the structure as durable and confirm current figures on Salesforce's Agentforce pricing page.

Consumption pricing: Flex Credits and Conversations

Agentforce offers two consumption-based models, and an org uses one or the other. Under Flex Credits, you pay per action, and each action an agent performs draws from a shared pool of credits. Under the Conversations model, you pay a flat rate per customer-facing conversation. Salesforce is clear that the two models cannot run in the same org at the same time, so this is a genuine either-or decision rather than a mix. Salesforce lists the current per-credit and per-conversation rates on its pricing page and its Agentforce Rate Card.

Per-user licensing and bundled editions

Consumption is not the only option. Salesforce also offers per-user licensing for employee-facing use, including a lower-cost user license that still draws on Flex Credits, unmetered add-ons for licensed employees, and bundled Agentforce 1 Editions that combine an add-on with a block of credits. For a workflow that is used constantly by a fixed group of employees, a per-user model can be more predictable than counting actions. For a spiky, customer-facing workflow, consumption is often the better fit. The right choice depends on who uses the workflow and how steady the volume is.

What counts as an "action"

This is the input that drives everything else. An action is a specific function an agent executes, such as updating a record, summarizing a case, answering a question, or running a prompt or flow. Each action is metered individually, and standard actions and voice actions draw different amounts of credit, with voice being the more expensive of the two. The number of actions a request uses depends on how many discrete functions the agent performs. Salesforce's own worked examples make this concrete: a simple knowledge answer can be one action, while a service case-management task might count three, such as identifying the customer, retrieving their cases, and adding a comment. Counting actions per run is the heart of any Agentforce estimate.

The inputs you need to estimate one workflow

An Agentforce estimate for a single workflow comes down to a short list of assumptions. Gather these before you touch any rate.

How to run the estimate

You can build the whole estimate in a spreadsheet in a few minutes. The steps below are the same math Salesforce uses in its published examples.

1. Define the one workflow precisely, including its trigger and what a completed run looks like.

2. List the discrete actions the agent performs in a single run, and count them.

3. Estimate runs per month, for example requests per day multiplied by working days, or total conversations across a channel.

4. Multiply actions per run by runs per month to get actions per month, then convert to credits using the current per-action credit amount and per-credit price from Salesforce's pricing page.

5. Compare that figure against the Conversations model and against per-user licensing for the same volume, so you can see which model is cheapest for this specific workflow.

6. Add the costs that sit outside the rate card, such as data and implementation, which we cover below.

7. Build in a buffer for complex runs, then validate the assumptions with a small metered pilot before you commit.

Because the rates change, keep the model and the volumes in your spreadsheet and pull the live per-action and per-credit numbers from Salesforce rather than hard-coding them. That way the estimate stays current when pricing shifts.

A worked example: a case-intake workflow

Imagine a support team that wants an agent to handle inbound case intake. A customer submits a request, and the agent identifies the customer from their email, pulls the relevant record, and creates or updates a case. That is three discrete actions per run, which lines up with the kind of service example Salesforce publishes.

If that workflow runs a few dozen times per working day, the monthly math is straightforward: three actions per run, multiplied by runs per day, multiplied by working days per month, gives you actions per month. Convert actions per month to credits at the current per-action amount, then apply the current credit price to get a monthly figure. The number that moves your estimate most is not the rate; it is the three actions per run and the volume. Double the complexity of the workflow, and you roughly double the cost.

To keep this example honest and current, plug your own volumes and the live rates into Salesforce's four published examples on the pricing page, which show the same actions-times-volume structure with Salesforce's own credit math.

Sensitivity: what moves the number most

Once you have a base estimate, it is worth stress-testing it. A few variables dominate the result.

The takeaway is that a simple, well-scoped workflow with few actions per run is far easier to budget than a broad, multi-step agent that fans out across many functions.

What the estimate leaves out

An action-only estimate is a floor, not a ceiling. Salesforce notes in its own examples that the figures do not include costs such as Data 360 credits or other consumption services, so a workflow that needs enterprise data grounding can carry meaningful additional cost. Beyond that, implementation, configuration, testing, change management, and the ongoing admin time to maintain and monitor the workflow all sit outside the list price. When you present a number to finance, label the consumption estimate clearly and add these categories separately so nobody mistakes the rate-card figure for the total cost of running the workflow.

Flex Credits or Conversations for your workflow?

Salesforce frames the choice simply. Conversations offer flat, predictable pricing and are optimized for external, customer-facing agents. Flex Credits align cost to the value each action delivers, scale across any use case, and provide more granular usage tracking and more buying-model flexibility. In rough terms, a workflow with only a few actions per conversation tends to favor Flex Credits, while a conversation that fans out into many actions can favor the flat Conversations rate. Because the models cannot coexist in one org, model selection is a decision to make with your account team, using your real workflow mix rather than a single example. Salesforce covers this in the FAQ on its pricing page.

Where a governed workflow layer fits

Estimating cost and controlling it are two different problems. Once you can forecast a workflow, the next question is how to keep consumption predictable in production, especially for a single high-frequency workflow that has to end in clean Salesforce data.

This is the point where a governed workflow layer can help. ConvoPro is a practical AI workflow layer for Salesforce that turns messy inputs into structured, reviewable Salesforce action while keeping Salesforce as the system of record. For a bounded workflow such as case intake, that means structured capture, a review-before-create step, and admin-controlled connectors, tools, and actions, so the work follows a defined path rather than an open-ended agent loop. That predictability is useful when you are proving one workflow and want a spend you can reason about.

ConvoPro complements Salesforce-native tools rather than replacing them. Agentforce remains the right choice when you are ready to build, deploy, and orchestrate AI agents at scale with the data and governance readiness that requires. ConvoPro is useful when the immediate need is one governed Salesforce workflow before a broader agent or data program, and the Salesforce-native route is more than that single workflow requires. The right choice depends on workflow scope, governance needs, timeline, and implementation complexity. ConvoPro prices its software per user and itemizes model usage separately; you can review the current model on the ConvoPro pricing page. If you are weighing whether to license a tool, build custom, or start with a governed workflow, our guide on managed package versus custom development compares the operating load of each path.

Frequently asked questions

How much does one Agentforce workflow cost per month?

There is no single number, because Agentforce is priced by consumption. Estimate it from the workflow: count the discrete actions per run, multiply by runs per month to get actions per month, then apply Salesforce's current per-action and per-credit rates from its pricing page. Add data and implementation costs separately, since the rate-card figure does not include them.

How are Flex Credits calculated?

Each action an agent performs, such as updating a record, summarizing a case, or answering a question, draws a set amount of Flex Credits, and each action is metered individually. Standard actions and voice actions draw different amounts, with voice being higher. The current credit amounts and the per-credit price are listed on Salesforce's pricing page and Agentforce Rate Card.

Can I use Flex Credits and Conversation pricing at the same time?

No. Salesforce does not support both models in the same org. You choose one, and switching from Conversations to Flex Credits requires swapping the existing Conversation SKUs, coordinated through your account team.

Do unused Flex Credits roll over?

Salesforce states that unused Flex Credits do not roll over into subsequent subscription terms. Plan your purchase against a realistic monthly estimate, and use Salesforce's usage tracking to watch consumption during the term.

What is not included in an Agentforce cost estimate?

Salesforce's own examples exclude costs such as Data 360 credits and other consumption services. On top of consumption, implementation, configuration, testing, change management, and ongoing admin time all sit outside the list price, so treat the action-based figure as a floor.

Is there a free way to test consumption before buying?

Salesforce offers a free Foundations tier that includes builder tools and a block of credits for testing, which is enough to run a real pilot and gather actual consumption data. Pair that with Salesforce's usage tracking so your estimate is grounded in real numbers before you commit.

Next step

The most reliable estimate comes from one clearly scoped workflow with a known action count and volume, validated against live rates. If you want help scoping that first workflow and keeping its spend predictable, talk to ConvoPro about your Salesforce workflow, or see ConvoPro pricing to compare the model.