--- title: "Ortoo Orchestrator pricing — per work item, predictable as you scale" description: "Ortoo Orchestrator is priced per work item handled, not per user or per action. One price covers every agent, step, and retry; you choose the LLM, so spend stays forecastable as volume grows." lang: en json-ld: | [ { "@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/" }, { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What counts as a work item?", "acceptedAnswer": { "@type": "Answer", "text": "A work item is the unit your team handles end to end through one orchestrated workflow. In service, that is usually a case. In revenue, a lead or an opportunity. In intake or claims, a request. In custom workflows, you define it. We agree the definition during onboarding and it stays consistent across reporting and billing." } }, { "@type": "Question", "name": "What happens when a work item runs through many steps or retries?", "acceptedAnswer": { "@type": "Answer", "text": "The price for the work item does not change. All agent actions, deterministic rules, retries, and routing decisions inside that work item are included. The only variable is the AI cost on the LLM you chose, paid by you to your provider with full visibility on every call." } }, { "@type": "Question", "name": "How does the AI cost form?", "acceptedAnswer": { "@type": "Answer", "text": "AI cost stays bounded by the LLM contract you control directly. Choose your own LLM provider and model per workflow step. Choose from OpenAI, Anthropic, Google, Azure, others. You can configure and switch providers and models per workflow and steps. Set clear limits on AI spend per step (cost ceilings, retry limits, fallback logic). No contractual relationship with Ortoo on the AI provider side. Please note that deterministic steps executed by Ortoo Orchestrator do not use AI and stay free from any AI cost." } }, { "@type": "Question", "name": "Can we start with one workflow and add more later?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Most teams start with the workflow that has the highest predictability gain, usually service or intake. Once the model is proven, you expand. Adding a workflow is a scoping conversation about volumes and integrations, not a platform upgrade." } }, { "@type": "Question", "name": "Is there a pilot or trial?", "acceptedAnswer": { "@type": "Answer", "text": "We run scoped pilots for qualifying teams. One workflow, a defined volume window, clear success criteria. Tell us which workflow you want to start with and we will scope a pilot in your context." } }, { "@type": "Question", "name": "Is Ortoo pricing predictable, or does the bill spike when we get busy?", "acceptedAnswer": { "@type": "Answer", "text": "Pricing tracks the work your team completes, cases, leads, or claims, so it moves with operational volume, not with how many agent actions are executed. That is a number your operations team already forecasts each month, so the bill stays legible: a busier month costs more in proportion to the work handled, with no hidden per-action multipliers stacking on top. You agree the work-item definition and the commercial terms up front." } }, { "@type": "Question", "name": "How does work-item pricing compare to a per-user routing tool?", "acceptedAnswer": { "@type": "Answer", "text": "A per-user routing tool charges by seat and does one job: assignment. Ortoo Orchestrator prices the whole work item, intake, AI triage, routing, and the steps after assignment, handled end to end. They are not priced the same way because they are not the same scope. If assignment is genuinely the whole job, per-seat routing can be the simpler cost, and that is a fair choice. If the workflow also needs handling before and after routing, one work-item price covers what would otherwise be several tools and the integration between them." } }, { "@type": "Question", "name": "Is the price published, or is it quote-only?", "acceptedAnswer": { "@type": "Answer", "text": "We quote per work item against your actual volumes and the workflows you want to orchestrate, so the number reflects your operations. Tell us the workflow you want to start with and your monthly volume, and we come back with a scoped quote and a clear starting point." } }, { "@type": "Question", "name": "How do we forecast and control spend as we scale?", "acceptedAnswer": { "@type": "Answer", "text": "You forecast from operational volumes already in your reports: monthly cases, leads, or claims. AI cost stays bounded by the LLM contract you hold directly, you choose the provider and model per step and set limits on AI spend, and deterministic steps run with no AI cost at all. Adding a second or third workflow is priced on its own volume rather than multiplying a per-action surface, so the cost curve stays legible as you expand." } } ] } ] --- [Skip to main content](#main-content) [Support](/support)[Contact](/contact) [![Ortoo logo, workflow orchestration for Salesforce](/assets/ortoo-logo-gradient-C54UkOOH.webp)](/) Ortoo Orchestrator Solutions Why Ortoo Resources About [Pricing](/pricing) [Map your workflow](/contact?intent=workflow-mapping)[Book a demo](/contact?intent=demo) [Book a demo](/contact?intent=demo) Pricing # Pay per _work item_ handled One price covers the full work item. One case. One lead. One claim. Every agent, every routing decision, and every retry is included. AI runs only where it adds value, on the LLM you choose, under the controls you set. [Get a quote ](/contact?intent=quote)[Estimate your volume](/contact?intent=quote) How pricing works ## One price per work item, handled end to end A work item is the unit your team already measures. A service case. A sales lead. An insurance claim. An intake request. Whatever the workflow, Ortoo Orchestrator runs every step inside that work item under a single price. No per-action billing. [See how it works](/why-orchestrator) - 01 ### One price covers the full sequence A workflow can run three steps or thirty. The price for the work item does not change. Every agent action, every deterministic rule, every routing decision is included. - 02 ### Deterministic workflow steps don't add AI costs Routing, SLA logic, validation, data updates, notifications, none of these touch an LLM. AI runs only where interpretation is needed, on the model you choose. - 03 ### Cost tracks operational volume, not actions  Pricing scales with the cases, leads, or claims your team handles. Not with agent actions volume. You forecast from numbers your operations team already reports. Cost models compared ## Why work-item pricing stays predictable at scale There are two ways to price AI-driven workflows. One bills you for every action. The other bills you for the work your team actually completes. Per-action AI billing ### Cost moves with the model You pay for - Each conversation billed separately. Each action billed separately. - AI runs at every step, including work that does not need it. - No ceiling on cost per work item. - Spend shifts with how the model behaves that day. - Finance cannot forecast cleanly as volume grows. Ortoo Orchestrator ### Cost moves with your operations You pay for - One price per work item, end to end. - Every agent and every step included. - Deterministic workflow steps don't add AI costs. - You choose the LLM per step. You set the policy. You control the AI spend. - Forecastable from the case, lead, or claim volumes you already track. Want the full picture? See the [Why Orchestrator comparison](/why-orchestrator). What changes as volume grows ## Control AI cost. Forecast with more precision. Per-action billing penalises scale. Work-item pricing changes the shape of your cost curve. A busy month costs more only in proportion to the work you handled, never because the action count multiplied. [Book a demo ](/contact?intent=demo) ### You control AI cost directly Deterministic workflow steps don't add AI costs. Set clear limits on AI spend where AI is used. AI cost stays bounded by the LLM contract you control directly. Choose your own provider and model per workflow step. ### Forecasting stays simple Finance teams forecast Ortoo cost from operational volumes already in your reports. Monthly cases. Monthly leads. Monthly claims.  ### Adding workflows is additive, not multiplicative A second or third workflow does not multiply your cost surface. Each one is priced on its own work-item volume. Shared orchestration capabilities stay included. FAQ ## Pricing questions teams ask ### What counts as a work item? + A work item is the unit your team handles end to end through one orchestrated workflow. In service, that is usually a case. In revenue, a lead or an opportunity. In intake or claims, a request. In custom workflows, you define it. We agree the definition during onboarding and it stays consistent across reporting and billing. ### What happens when a work item runs through many steps or retries? + The price for the work item does not change. All agent actions, deterministic rules, retries, and routing decisions inside that work item are included. The only variable is the AI cost on the LLM you chose, paid by you to your provider with full visibility on every call. ### How does the AI cost form? + AI cost stays bounded by the LLM contract you control directly. Choose your own LLM provider and model per workflow step. Choose from OpenAI, Anthropic, Google, Azure, others. You can configure and switch providers and models per workflow and steps. Set clear limits on AI spend per step (cost ceilings, retry limits, fallback logic). No contractual relationship with Ortoo on the AI provider side. Please note that deterministic steps executed by Ortoo Orchestrator do not use AI and stay free from any AI cost. ### Can we start with one workflow and add more later? + Yes. Most teams start with the workflow that has the highest predictability gain, usually service or intake. Once the model is proven, you expand. Adding a workflow is a scoping conversation about volumes and integrations, not a platform upgrade. ### Is there a pilot or trial? + We run scoped pilots for qualifying teams. One workflow, a defined volume window, clear success criteria. Tell us which workflow you want to start with and we will scope a pilot in your context. ### Is Ortoo pricing predictable, or does the bill spike when we get busy? + Pricing tracks the work your team completes, cases, leads, or claims, so it moves with operational volume, not with how many agent actions are executed. That is a number your operations team already forecasts each month, so the bill stays legible: a busier month costs more in proportion to the work handled, with no hidden per-action multipliers stacking on top. You agree the work-item definition and the commercial terms up front. ### How does work-item pricing compare to a per-user routing tool? + A per-user routing tool charges by seat and does one job: assignment. Ortoo Orchestrator prices the whole work item, intake, AI triage, routing, and the steps after assignment, handled end to end. They are not priced the same way because they are not the same scope. If assignment is genuinely the whole job, per-seat routing can be the simpler cost, and that is a fair choice. If the workflow also needs handling before and after routing, one work-item price covers what would otherwise be several tools and the integration between them. ### Is the price published, or is it quote-only? + We quote per work item against your actual volumes and the workflows you want to orchestrate, so the number reflects your operations. Tell us the workflow you want to start with and your monthly volume, and we come back with a scoped quote and a clear starting point. ### How do we forecast and control spend as we scale? + You forecast from operational volumes already in your reports: monthly cases, leads, or claims. AI cost stays bounded by the LLM contract you hold directly, you choose the provider and model per step and set limits on AI spend, and deterministic steps run with no AI cost at all. Adding a second or third workflow is priced on its own volume rather than multiplying a per-action surface, so the cost curve stays legible as you expand. Ready to talk numbers ## Get a quote shaped around your _volume_ Tell us which workflow you want to orchestrate first and what your monthly volume looks like today. We come back with a scoped quote and a starting point. No procurement guesswork. [Book a demo ](/contact?intent=demo)[Map your workflow](/contact?intent=workflow-mapping) ![Ortoo logo, workflow orchestration for Salesforce](/assets/ortoo-logo-C6Mjw-cG.svg) Workflow orchestration in Salesforce, executed by specialized agents under controlled AI. PRODUCT - [Orchestrator](/orchestrator) - [Solutions](/solutions) - [Pricing](/pricing) ## PRODUCT - [Orchestrator](/orchestrator) - [Solutions](/solutions) - [Pricing](/pricing) WHY - [Why Orchestrator](/why-orchestrator) - [Customers](/case-studies) ## WHY - [Why Orchestrator](/why-orchestrator) - [Customers](/case-studies) RESOURCES - [Blog](/resources/blog) - [Downloads](/resources/downloads) ## RESOURCES - [Blog](/resources/blog) - [Downloads](/resources/downloads) USE CASES - [Case assignment](/case-assignment) - [Lead assignment](/lead-assignment-in-salesforce) - [Email-to-Anything](/solutions/email-to-anything) - [See all use cases](/use-cases) ## USE CASES - [Case assignment](/case-assignment) - [Lead assignment](/lead-assignment-in-salesforce) - [Email-to-Anything](/solutions/email-to-anything) - [See all use cases](/use-cases) COMPANY - [About](/about-ortoo) - [Ascendx Approach](/ascendx-approach) - [Careers](https://ascendx.cloud/vacancies/) - [Contact](/contact) ## COMPANY - [About](/about-ortoo) - [Ascendx Approach](/ascendx-approach) - [Careers](https://ascendx.cloud/vacancies/) - [Contact](/contact) LEGAL - [Privacy policy](/privacy) - [Terms of service](/terms) - [Cookie policy](/cookies) ## LEGAL - [Privacy policy](/privacy) - [Terms of service](/terms) - [Cookie policy](/cookies) © 2026 Ortoo. An Ascendx Company. All rights reserved. [](https://www.linkedin.com/company/ortooapps/)[](https://x.com/OrtooApps)