---
title: "AI pricing buyers can see and control | Ortoo Orchestrator · Ortoo"
url: https://ortooapps.com/resources/blog/ai-pricing-simple-to-understand-granular-to-control
description: "AI is easier to buy and harder to cost. Why assistants and operational AI need different pricing, and what buyers should see, understand and control."
lang: en
---

Salesforce architecture: https://ortooapps.com/resources/blog?theme=salesforce-architecture

# AI pricing should be simple to understand and granular to control

Elisa Mustonen · 19 October 2026 · 6 min read

Image: A glowing data line rising across a dark violet to teal background, with points marked along it. (https://ortoo.lovable.app/__l5e/assets-v1/9b7b7c99-2f0c-49e7-9a31-f4a4e48c102a/ai-pricing-featured-v2.png)

AI is getting easier to buy and harder to cost. Agentforce editions are the latest example. The right pricing structure depends on how AI is used, and on whether buyers can see, understand and control that use.

AI pricing is a moving target. Model providers such as Anthropic (https://docs.claude.com/en/docs/about-claude/pricing) and OpenAI (https://openai.com/api/pricing/) price input and output differently, discount cached or batched requests, and change the economics with every model generation. Software vendors add their own layer on top: seats, credits, conversations, outcomes. Even when every rate is published, the structure is hard to follow and harder to forecast. And it's often unclear which parts of the spend you control, beyond a usage cap.

Salesforce's new Core, Advanced and Max editions are the latest and most visible example in the Salesforce ecosystem. They come up in a lot of customer conversations right now. They make AI easier to buy. Costing it is a separate job.

Two decisions come before the packaging: how AI should be used in your operations, and which pricing structure fits that use.

## Packaging got simpler. Pricing kept its layers.

The editions cut the number of things you buy. Underneath, Salesforce's Agentforce pricing page (https://www.salesforce.com/agentforce/pricing/) still lists separate meters, each measuring something different.

| Unit | What it measures | List price |
| --- | --- | --- |
| Seat | Access for one person | $195, $395 or $550 per user per month |
| Standard action | One step an agent performs | 20 Flex Credits, or $0.10 |
| Conversation | One customer conversation | $2 |
| Help Agent resolution | One qualifying resolved request | $2 |
| Data 360 consumption | Data processing behind the agent | Priced separately |

Salesforce's own worked examples leave out Data 360 and other consumption services, so an action count is never the full cost. And Flex Credits and conversations aren't supported in the same org, so the model you start on decides the one you stay on.

None of this is unusual. It's what AI pricing looks like across the market right now.

## Different kinds of AI work need different pricing

AI does several different jobs in an organisation, and each one creates value in a different place.

| Kind of AI work | Where the value shows up | How volume behaves | Control it needs | Pricing that fits |
| --- | --- | --- | --- | --- |
| Internal assistants | Per person, spread across the day | Hard to predict per person, low risk per request | Guardrails and data access | Per seat, often unmetered |
| Customer-facing agents | Per conversation at the front, per completed task behind it | Follows customer demand | What happens after the chat ends | Per conversation or outcome at the front |
| Operational execution | Per completed task | High and steady, follows work volume | Granular, step by step | Per task or work item |

Image: Three kinds of AI work on a scale from value per person to value per completed task. Internal assistants fit per-seat pricing and need guardrails and data access. Customer-facing agents fit per-conversation, then per-task pricing and need control over what happens after the chat. Operational execution fits per-task or per-work-item pricing and needs granular, step-by-step control. (https://ortoo.lovable.app/__l5e/assets-v1/562aa9fb-133f-4438-b709-0c9eab382ee4/ai-work-and-pricing.png)

Three kinds of AI work, from value per person to value per completed task.

Per-person value suits per-person pricing. Per-task value suits per-task pricing.

An internal assistant answers questions, drafts and searches. One person's usage is hard to predict, but each request is low risk, and the value sits with the person using it. A seat, often unmetered, fits that well.

An operational execution agent is different. It classifies, enriches, routes and updates records, thousands of times a month, inside processes the business depends on. At that volume, small design choices multiply. You need granular control: which steps use a model at all, which model, what each process may consume, and where a person approves.

Customer-facing agents sit across both. The chat is the visible part. The work happens after it: the case that gets created, the specialist who picks it up, the refund that gets processed, the follow-up that gets sent. Pricing per conversation measures the front door. The back end is operational execution, and it needs the same granular control.

## Seats scale with people. Credits don't.

The Flex Credit allowance in each edition is set per org, per year, as SalesforceDevOps.net reported (https://salesforcedevops.net/index.php/2026/09/14/salesforce-core-advanced-max-editions-value/). Seats are priced per user. Add people and the seat bill grows. The credit pool stays where it is.

| | Core | Advanced | Max |
| --- | --- | --- | --- |
| Annual seat cost, 100 users | $234,000 | $474,000 | $660,000 |
| Included credits per year | 500,000 | 1,000,000 | 2,750,000 |
| Standard actions per year | 25,000 | 50,000 | 137,500 |
| Actions per user per working day | about 1 | about 2 | about 5.5 |

At 1,000 users, the seat cost multiplies by 10. The allowance doesn't move, so Core works out at about one standard action per user every 10 working days.

That structure suits assistant use well: a seat per person, with a shared pool for light agent activity. Operational volume needs its own forecast.

_Illustrative, at published list prices, before discounts. Working days assumed at 250 a year. Confirm the allowance on your order form._

## What one service queue consumes

Take a service team handling 2,000 cases a month, with an agent that triages, enriches and drafts on each one. Salesforce's own pricing examples use five standard actions for a multi-step request.

| Agent actions per case | Actions per year | Flex Credits | Cost at list | How long each allowance lasts (Core / Advanced / Max) |
| --- | --- | --- | --- | --- |
| 5 | 120,000 | 2,400,000 | $12,000 | 2.5 months / 5 months / the full year |
| 12 | 288,000 | 5,760,000 | $28,800 | 1 month / 2 months / under 6 months |

Same team, same seats, same case volume. One design decision more than doubles the consumption line.

Image: A service queue of 2,000 cases a month. Design A uses 5 agent actions per case, 120,000 actions a year, $12,000 at list price. Design B uses 12 agent actions per case, 288,000 actions a year, $28,800 at list price. (https://ortoo.lovable.app/__l5e/assets-v1/0906e2b2-8ed3-414e-bdfb-7100b4986c69/one-queue-two-designs.png)

Same team, same seats. One design choice changes the consumption line.

At this volume, consumption is still small next to the seat bill. The issue is predictability. A seat count is known the day the contract is signed. An action count depends on retries, multi-step requests, how often the agent hands back to a person, and which data services run underneath.

## Simple to understand, granular to control

A bundle helps buyers only when they can see what they use, understand what drives it, and control it against how it should be used.

**See it.** Consumption per process, as it happens, in a view the people who own the process can read.

**Understand it.** What one completed task actually costs: the agent actions per resolved case, the data processing behind them, how often a person corrects the result, and how often a step is retried.

**Control it.** Against how each process should use AI, with more than a usage cap. A model only where judgement is needed. Rules everywhere else, because a step written as a rule doesn't need a model at all. Limits per process, and approvals where the risk is real.

Simplicity comes first. That means few meters, and a unit the buyer already recognises, such as a case or a lead. If the pricing structure is too complex for the buyer to follow, no amount of control will deliver the result they expected. The goal is a structure simple enough to understand and controls granular enough to match how each kind of AI is used.

Image: A self-check before renewal. Simple first: can you explain how your AI use is charged in one sentence? See it: consumption per process, visible as it happens, in a view process owners can read. Understand it: the cost of one completed task, what drives it, and how often a person corrects the result. Control it: a model only where judgement is needed, limits per process, and approvals where the risk is real. (https://ortoo.lovable.app/__l5e/assets-v1/7212717b-5363-4801-84df-5dcacd4c671c/see-understand-control-check.png)

Tick what you can answer today.

## Questions to settle before the next renewal

- Which of your AI use is assistance, and which is operational execution?
- How many agent actions does one completed case or lead take today, and how sure are you of that number?
- Which steps genuinely need a model, and which could run as rules?
- Who sees consumption as it happens, and who's accountable when it runs ahead of plan?
- What sits outside the action count: data services, conversations, outcomes?

## Where Ortoo fits

Ortoo's pricing is one take on this. Ortoo Orchestrator is priced per work item completed, such as a case, a lead or a request. Deterministic steps carry no AI cost. See Ortoo pricing (https://ortooapps.com/pricing).

It's built for the operational side: what happens after the chat. AI is applied to the steps that need judgement, deterministic logic handles the rest, and every step is recorded inside Salesforce, so the cost of a completed piece of work is something you can see.

For the edition-by-edition detail, see what is actually in Agentforce Core, Advanced and Max (https://ortooapps.com/resources/blog/agentforce-core-advanced-max-editions).

## Sources

Checked on 19 October 2026. Prices are published US list prices before discounts.

1. New Salesforce editions bundle everything businesses need for agentic transformation, Salesforce (https://www.salesforce.com/news/stories/salesforce-simplifies-editions-2026/) (3 September 2026)
2. Agentforce pricing, Salesforce: https://www.salesforce.com/agentforce/pricing/
3. Sales Cloud is back on the price list, SalesforceDevOps.net (https://salesforcedevops.net/index.php/2026/09/14/salesforce-core-advanced-max-editions-value/) (14 September 2026)
4. Ortoo pricing: https://ortooapps.com/pricing
5. Pricing, Anthropic (https://docs.claude.com/en/docs/about-claude/pricing) (input and output token pricing, prompt caching and batch discounts)
6. API pricing, OpenAI (https://openai.com/api/pricing/) (input and output token pricing, cached input and batch discounts)

## Related insights

Salesforce architecture

### Agentforce editions: what is actually in Core, Advanced and Max?

What Agentforce Core, Advanced and Max include, how far Flex Credits go, what changes at renewal, and why Workforce Engagement does not settle who gets each case.

Ortoo 11 min read
https://ortooapps.com/resources/blog/agentforce-core-advanced-max-editions

Salesforce architecture

### Centralising Salesforce Routing Logic Without Fragile Code

Understand the limits of custom code and flows for routing and discover a more resilient, centralised model.

Taylor Reed 5 min read
https://ortooapps.com/resources/blog/centralising-salesforce-routing-logic-without-fragile-code

Workflow orchestration

### AI-Powered Round Robin Assignment in Salesforce

Discover how AI-powered round-robin Salesforce assignment drives efficiency for management of Leads, Cases, and more. This article explores the capabilities and limitations of Salesforce-native round-robin functionality and how AI can plug the gaps.

Amy Grenham 4 min read
https://ortooapps.com/resources/blog/round-robin-assignment-in-salesforce-the-ai-effect

READY TO SEE IT IN ACTION

## Map _your_ workflows with our team.

30 minutes, no prep needed. We will map one workflow you handle today and identify where orchestration would change the outcome.

Book a demo: https://ortooapps.com/contact?intent=demo
Map your workflow: https://ortooapps.com/contact?intent=workflow-mapping

## Structured data

```json
[
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "headline": "AI pricing should be simple to understand and granular to control",
    "image": "https://ortoo.lovable.app/__l5e/assets-v1/1f24cc33-017f-489c-b866-09a7fb74a1f6/ai-pricing-social.jpg",
    "datePublished": "2026-10-19T12:19:57.137366+00:00",
    "dateModified": "2026-10-19T12:29:25.015634+00:00",
    "author": {
      "@type": "Person",
      "name": "Elisa Mustonen"
    },
    "publisher": {
      "@type": "Organization",
      "name": "Ortoo Orchestrator",
      "logo": {
        "@type": "ImageObject",
        "url": "https://ortooapps.com/logo.png"
      }
    },
    "mainEntityOfPage": "https://ortooapps.com/resources/blog/ai-pricing-simple-to-understand-granular-to-control"
  },
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "Ortoo",
    "url": "https://ortooapps.com/",
    "logo": "https://ortooapps.com/ortoo-logo-square.png",
    "parentOrganization": {
      "@type": "Organization",
      "name": "Ascendx"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "WebSite",
    "name": "Ortoo",
    "url": "https://ortooapps.com/"
  }
]
```