What does Regrello-style process automation cost at Salesforce?

Regrello is an awkward subject for a licence guide because the honest starting point is an absence. Salesforce announced the acquisition in August 2025, completed it on 1 October 2025, and said it planned to fold the technology into Agentforce and Slack. Today there is no product page, price card or rate line for Regrello by name. That does not leave a buyer helpless. It means the useful work is to model the pieces Salesforce named, and to know where your own contract is silent.

#What Salesforce said it was buying

The announcement describes the deal in one sentence: "Salesforce has signed a definitive agreement to acquire Regrello, an AI-native solution that automates complex business processes." It goes on to say that Regrello's technology "takes business data and turns it into agile, agentic workflows", and that, after the acquisition closed, Salesforce planned to integrate Regrello with Agentforce and Slack to help customers turn manual, inefficient activities into agentic automations. The chief product officer's quotation talks about turning unstructured artefacts into coordinated workflows that bring humans and agents together on the Salesforce Platform.

Read that as a statement of direction, not of packaging. A plan to integrate is not a product SKU. We read the Agentforce, Service Cloud, Data 360, Commerce and Slack pricing pages on 13 October 2026 and none lists Regrello. If a seller shows you a quote with a Regrello line, ask what it is called on the order form, which edition it belongs to, and which meter applies. If the answer is vague, you have found the open question.

#The two meters you can actually model

Because Salesforce pointed at Agentforce and Slack, those are the two commercial surfaces to model. Agentforce actions are metered in Flex Credits. The Agentforce pricing page lists Flex Credits at US$500 per 100,000, with a standard action using 20 credits, which is US$0.10. Slack is sold per user: on its pricing page Pro was US$8.75 per user per month paid monthly and US$7.25 when paid annually, and Business+ was US$18 monthly and US$15 annually. Both paid plans include unlimited message history, which Slack describes this way: "Every message, file and conversation shared in Slack is saved and fully searchable."

An agentic process touches both. An agent that chases a late delivery confirmation, reads the reply, updates a record and posts a summary to a channel draws actions on one side and puts people in Slack on the other. Neither meter is exotic. What is new is the volume: a process that ran once a day in a workflow engine can run for every record that changes once an agent is allowed to act on it.

The first row assumes 2,000 exception cases a month, each needing six actions: look up the order, read the supplier reply, draft a response, update the case, notify the owner and log the outcome. The examples are illustrations of arithmetic, not a forecast for your business and not a Regrello price.

#Flex Credits or the employee add-on?

The comparison most buyers need is not Regrello against anything. It is metered actions against the unmetered employee add-on. Salesforce lists add-ons at US$125 per user per month for Sales, Service, Field Service and Operations, described as "Unmetered Agentforce usage for employees". At US$0.10 an action, US$125 buys 1,250 standard actions. A user who triggers fewer than that in a month is cheaper on credits; a user who triggers more is cheaper on the add-on.

That break-even is much higher than most employee workflows will reach. Even a heavy user working through thirty cases a day, with six actions each, would use about 3,600 actions across twenty working days, so the add-on wins for them. But an employee who occasionally asks an agent a question will use a few dozen, and for them credits are far cheaper. The practical answer is usually a split: add-ons for a small group of power users, credits for everyone else and for the agents that act without a person present.

Two caveats apply. The add-on is for employee-facing use and sits on top of a Cloud or Industry user licence, so it is not a way to buy a process agent that runs in the background for your suppliers. And the Max editions, which Salesforce lists from US$550 per user per month with the add-on included and 2.75 million Flex Credits per org per year, change the arithmetic entirely if you were about to upgrade for other reasons.

#Where existing automation fits

Many orgs already run process automation, and the instinct is to ask whether a new product replaces it. In licence terms the answer is no by default. A flow that is working today is already covered by whatever your edition entitles you to, and moving it to an agent does not cancel that entitlement; it adds consumption. A buyer who treats every existing flow as a candidate for agentic replacement is repricing the org, and it is rarely the right call.

The sensible rule is selective. Keep deterministic, high-volume steps in the tool that handles them cheaply and predictably. Move the work that needs judgement, reading unstructured replies, deciding between options, coordinating several parties, to an agent, and meter it. A process split this way costs credits only for the steps that need an agent, and the licence conversation becomes a scoping conversation.

Ask your account team to confirm in writing what automation entitlements your edition already includes, because editions have been repackaged and a line you assume you own may be elsewhere. Then ask what, if anything, changes if you adopt an agentic orchestration product, and whether it consumes credits from the same pool as your other agents.

#Slack seats are a decision, not a default

The Slack line is the one most often assumed rather than examined. If your teams already work in Slack, the incremental seat cost of an orchestration project is zero and the question is only whether the plan you hold supports what you want. If they do not, you are adding a collaboration platform to a process project, and that is a larger decision than the process.

Look at who needs a seat. The agent does not take one. The people who approve exceptions, answer questions the agent cannot resolve and watch progress do. In a procurement exception process that might be a dozen buyers and a handful of managers, not the whole company. Whether suppliers or other outside parties can join a channel without a paid seat each, and under which plan, is a question for the Slack pricing page and your agreement, not something to assume.

Compare Pro and Business+ against what you need, not against the price alone. At the annual rates read on 13 October 2026, the gap on 150 seats is US$7.75 a seat a month, or US$1,162.50 a month. Pay it if the extra features Slack lists for Business+ matter to the process; do not pay it by default.

#Three scenarios for the same process

To see how the pieces interact, run one supplier-exception process three ways, all at list prices and all illustrative. In the first, a small team of twelve handles 500 cases a month at six actions each. That is 3,000 actions, or US$300 a month, plus twelve Slack Business+ seats at US$180 a month. The agent is the cheaper half of the bill.

In the second, volume rises to 5,000 cases a month. Actions are 30,000, or US$3,000 a month, while the team grows to thirty people at US$450 in Slack. Now the agent dominates, and each retry or extra step per case matters: one more action per case adds US$500 a month.

In the third, the process is extended to customer-facing updates and runs at 20,000 cases a month. That is 120,000 actions, US$12,000 a month, and you should ask whether a different meter, such as per-conversation pricing for the external part, would be cheaper. The point of the exercise is not the totals. It is that the shape of the cost changes as volume grows, and a licence chosen at pilot scale may be wrong at production scale.

#Contract mechanics to settle before signing

The Agentforce page sets out several rules that apply wherever the actions are drawn. Flex Credits and Conversations cannot be used in one org. Credits are available on PayGo and Pre-Commit, billed monthly in arrears, and the Pre-Commit model carries a true-up at the end of the term if usage falls below the commitment. Unused credits do not roll over. And for overruns, "If you exceed your entitlement, your rate is your contracted rate billed monthly in arrears."

Those rules matter for orchestration because volume is hard to predict. A new automation may be quiet for a month and then busy once an upstream team changes its habits. Start with PayGo or a modest Pre-Commit, use the free Digital Wallet to watch consumption, and widen the commitment once you have two or three months of real data. Set alerts at thresholds that give someone time to act, and name the person who acts.

Also ask whether any credits are shared with Data 360. The Data 360 pricing page describes Flex Credits that can be moved between Data 360 and Agentforce, and an agent that reads documents or profiles will draw on both. A process that looks cheap on actions can become expensive on data if nobody forecast the second meter.

#Right-sizing an orchestration licence

Pick one process, not a portfolio. Choose something with a clear owner, a measurable cycle time, and a known failure mode. Count the cases per month, the steps in each case, and which of those steps need judgement. Estimate actions per case from the steps that need an agent, add a retry allowance, and multiply. That gives a monthly credit figure you can price at US$0.10 an action.

Then count the people. Who will approve, who will handle exceptions, who needs to see progress in a channel? Slack seats and, where relevant, Service or Sales seats follow those roles. Finally, test sensitivity. If cases double, or actions per case rise by half because the agent retries more, what happens to the bill? A good plan shows its own worst case.

Compare offers on the same footing. Any quote that bundles orchestration, agent actions and Slack should break the bundle into units, rates and terms so that you can see what you are paying for each. A single "platform fee" with no stated meter is the least comparable form of price.

#Questions for the account team

• What is the product called on the order form, and which edition or add-on does it belong to?
• Which meter applies, and what is my contracted credit rate?
• Do my existing automation and Slack entitlements already cover any of this?
• Are credits shared with Data 360, and what happens to unused credits at term end?
• What does an overrun cost, and how will I be alerted?

For the work design, covering which process is complex, who owns the finish and what stays in Flow, read Regrello and Agentforce. The acquisition record is on what happened to Regrello, the integration shape on integrating Regrello with Salesforce, and the decision to move on should I migrate from Regrello. Salesforce's completion notice reads: "Salesforce completed its acquisition of Regrello on October 1, 2025." Unused credits are covered by a single rule on the pricing page: "Unused Flex Credits do not roll over into subsequent subscription terms." All pricing in this guide was read on 13 October 2026 and Salesforce notes that it is subject to change.