Vlocity implementation cost: industry cloud licences, OmniStudio work and quotes

Vlocity was the company that built industry-specific applications on top of Salesforce for insurers, banks, telcos, utilities, health providers and the public sector. The rebrand record sums up what happened next: "Vlocity, acquired in 2020, became Salesforce Industries (or Industries Cloud) providing deep, industry-specific solutions." Nobody buys a Vlocity licence any more. You buy an industry cloud edition, and the Vlocity heritage shows up inside it as OmniStudio, the industry data models and the industry processes that sit on top of Sales Cloud and Service Cloud.

So the cost of a Vlocity implementation in 2026 has two halves. The first is the subscription you pay Salesforce, which for most industry clouds is now published on a pricing page. The second is the services work to configure, build, migrate and integrate, which is always quoted and which varies far more between projects than the licence does. This page covers both, and the questions that make two services quotes comparable.

#What Salesforce charges for the industry clouds

Salesforce publishes list prices for the main industry clouds. The figures below were read from Salesforce's own pricing pages as at October 2026. All are in US dollars, per user per month, billed annually, and the pages note that they are provided for information only and subject to change.

Sources: Financial Services Cloud pricing, Health Cloud pricing, Communications Cloud pricing and Energy and Utilities Cloud pricing. The Financial Services Cloud page also lists add-ons with organisation-level prices, such as Digital Origination at US$175,000 per org per year, which matters if a lending process is in scope.

The product framing on the Financial Services Cloud page explains why the per-user figure sits well above a plain Sales Cloud seat: "Financial Services Cloud comes out of the box with all the features in Sales Cloud and Service Cloud, plus an industry-specific data model, objects, and capabilities." You are paying for the industry objects and processes on top of the CRM editions, not instead of them. Communications Cloud describes its Growth edition in similar terms: "A flexible and extendable platform specific to the communications industry to drive efficiency through automation, workflows, and integrations." Read the edition comparison carefully on that page, because several capabilities a telco expects, such as contract lifecycle management and CRM Analytics, are shown as available for purchase rather than included.

The licence arithmetic is easy to do and worth doing before any services conversation. Fifty wealth advisers on Financial Services Cloud Sales Advanced at list is 50 times US$500 times 12, or US$300,000 a year before any discount. Two hundred contact centre agents on Communications Cloud Service Max at list is US$1.92 million a year. Those numbers frame the services budget: a project that cannot get the industry objects into use quickly is paying for seats nobody benefits from. For a deeper look at the subscription side, including negotiation and ramp terms, see the Vlocity licence cost page.

#What a Vlocity-style implementation is made of

Industry cloud projects share the usual phases of any Salesforce delivery, but the effort concentrates in places a Sales Cloud project barely touches. A quote worth comparing breaks the work into these packages.

Discovery and fit to the industry data model. The industry clouds ship objects for financial accounts, policies, care plans, service points, assets, billing accounts and more, depending on the cloud. The first job is mapping your current processes to those objects rather than recreating your old schema beside them. A discovery that ends with a list of custom objects duplicating standard industry objects is the first warning sign in a proposal.

OmniStudio build. This is the direct descendant of Vlocity's tooling: FlexCards for the consoles agents and advisers look at, OmniScripts for guided processes, Integration Procedures for server-side orchestration, and Data Mappers (formerly DataRaptors) for reading and writing records. Effort scales with the number and complexity of these components. A claims intake, a mortgage application or a telco order capture can each run to dozens of OmniScript steps with branching, validation and document generation.

Product catalogue and order management, for communications and media. Communications Cloud projects add product modelling, pricing rules, Industries CPQ and order decomposition into fulfilment. The Communications Cloud page lists the communications data model and TMF APIs as part of the platform, so a telco build will often be measured against TM Forum standards. Catalogue design is usually the single largest work package on these projects.

Data migration. Moving policies, accounts, households, holdings or service history into industry objects is harder than a standard account and contact load, because relationships carry meaning. Household rollups, financial account roles and care team membership all need to be loaded in the right order with the right keys.

Integration with core systems. Industry clouds rarely own the system of record. Core banking, policy administration, claims, electronic health records, billing and operational support systems stay where they are, and Salesforce reads and writes through APIs, MuleSoft or an existing middleware layer. Integration Procedures can call REST endpoints directly, which can reduce the need for middleware on simple reads, but anything transactional or high volume usually goes through an integration platform. How those connections are designed is covered on integrating Vlocity with Salesforce.

Testing, training, cutover and hypercare. Regulated industries carry heavier testing: user acceptance with compliance sign-off, accessibility for customer-facing OmniScripts, and performance testing for contact centre consoles. Training is role-specific, because an adviser, an underwriter and a care coordinator use very different screens.

#What drives the cost up or down

Several factors are specific to the Vlocity lineage and move a services quote more than headcount does.

The first is where you are starting from. Organisations that bought Vlocity before the acquisition often still run its managed package, with components in the vlocity namespace. Salesforce has been moving OmniStudio onto a runtime built into the platform, and moving an existing estate of OmniScripts and FlexCards across is a project in its own right: inventory, conversion, regression testing and retirement of the old package. If you are in this position, ask every bidder whether that move is in scope, because it changes the size of the job and the shape of the testing plan. Should I migrate from Vlocity looks at that decision in more detail.

The second is how much of the standard industry process you accept. Every industry cloud comes with prebuilt processes and sample OmniScripts. Teams that adopt them and adjust spend far less than teams that redesign every screen. The cost difference shows up mostly in build and test effort, and again in every later release.

The third is the number of product lines or business units going live together. A bank launching retail and business banking at once, or an insurer covering several lines of business, multiplies the data model decisions and the integration points.

The fourth is the data model choices that cannot easily be reversed. Turning on Person Accounts, for example, is permanent in an org. Getting that decision and the household model right in discovery avoids rework later.

The fifth is regulatory scope. Field-level encryption, event monitoring and audit trail requirements usually mean Shield, and the configuration and testing around it add effort as well as licence cost.

#Choosing the edition before you price the work

The edition you buy changes the services scope as much as the licence. On the Financial Services Cloud page, the Max editions are described as everything in Advanced plus the full Agentforce for Industries suite, and the pricing tables mention Flex Credits for AI, Agentforce, Slack and data features. That is real capability, but it is also real build work: agents need subagents, actions, grounding data and testing, and none of that configures itself because the licence was signed.

A sensible pattern is to price the services for the edition you will actually use in the first release, and to treat the step up to Max as a later phase with its own business case. Buying Max for every seat on day one and then running a Core-shaped project is one of the more expensive ways to adopt an industry cloud, because you pay the higher seat price while the agent features sit idle.

The opposite mistake also happens. A team buys Core to keep the licence line down, then discovers during build that a process it needs is only in Advanced. Upgrading mid-project means a contract amendment, revised training and sometimes rework on screens that were designed around the missing feature. The cheapest moment to settle the edition is discovery, with the edition comparison open beside the process list and a named person on your side signing off each gap.

#How to get quotes you can compare

Industry cloud proposals are difficult to compare because each firm packages the work differently. The way through is to give every bidder the same inventory and ask for the same breakdown.

Send a short pack with the cloud and edition you intend to buy, the number of users by role, the list of processes in scope, the systems you need to integrate with and the volume of records to migrate. If you already run Vlocity or OmniStudio, include a count of OmniScripts, FlexCards and Integration Procedures. Ask each bidder to price separately for discovery, OmniStudio build, data model configuration, data migration, each integration, testing, training, cutover and a fixed hypercare period. Ask which prebuilt industry processes they assume you will adopt unchanged, because that assumption hides inside many lump sums.

Then ask about people. Which certified OmniStudio developers will work on the project, and are they the same people who presented? How much of the work is configuration and how much is code? Who owns the integration design if the core system vendor is involved? Firms with industry cloud depth are tested on who to hire for Vlocity.

#Costs that sit outside most quotes

The services number is rarely the whole budget. These items are commonly missing and are worth asking about directly.

Licence ramp is another quiet cost. If seats start on the contract date while go-live is months away, you pay for the industry cloud before anyone uses it. Ask your account executive about ramped seat counts aligned to the delivery plan.

Training and change management are often scoped thinly. An adviser moving from a spreadsheet and a core banking screen into a FlexCard console needs more than a one-hour session, and adoption is what turns US$500 a seat into value. Plan for refresher training after the first release and after each seasonal Salesforce release, because OmniStudio components and the industry processes change with them.

Integration licences on the other side of the connection are easy to forget as well. Core banking, policy administration and billing vendors sometimes charge for API access or for additional environments used in testing. Ask your own system owners, before the Salesforce quote is final, whether opening those interfaces to a new consumer triggers a fee, a change request or a queue for their own development team, because a delay there holds up the whole integration package.

Finally, keep a line for post go-live work. Industry clouds release new capability three times a year, and some of it replaces custom work you paid for. A small retained team to assess each release, or a managed service, stops the org drifting away from the standard.

#Where this fits with the other Vlocity pages

This page is about the money for a project. The acquisition story is on what happened to Vlocity, and the product itself, with the current industry cloud names, is on the Vlocity industry clouds page. If you are weighing whether to stay on the industry clouds at all, start with the migration page, then return here with a short list of editions to price.