Regrello implementation cost: Agentforce Operations pricing and process work

Supply chain work is mostly coordination. A purchase order changes, so a supplier has to confirm a new date, planning has to re-sequence, a warehouse has to be told, and finance has to accept the revised invoice. The information arrives in emails, spreadsheets and PDFs. Regrello was built to turn that mess into a tracked process, and Salesforce bought it for exactly that reason.

The completion date is on record: "Salesforce completed its acquisition of Regrello on October 1, 2025." The product page now states what it is called: "Now named Agentforce Operations, Salesforce completed its acquisition of Regrello on October 1, 2025." Salesforce's older Agentforce Supply Chain address also resolves to the Agentforce Operations page, so if a proposal uses either name, it means the same product. This guide prices Agentforce Operations as it is sold in October 2026.

#What Agentforce Operations does, in cost terms

The product page describes three ideas, and each one becomes a line in an implementation budget.

The first is the blueprint: a digital description of a process that people and agents both follow. Salesforce offers a head start: "Hit the ground running with 30+ out-of-the-box blueprint templates for common jobs like invoice auditing, onboarding, and PO rescheduling." A template shortens design, but someone still has to adapt it to your approval limits, supplier tiers and exception rules.

The second is participation. Processes in supply chain cross company boundaries, and the page addresses that directly: "Whether you’re an internal employee or external party, you can engage with processes and complete tasks directly from email, Slack, and Microsoft Teams." Suppliers can take part without a Salesforce licence of their own, which changes the licence maths compared with a portal. It also means the design must cover how an external party proves who they are and what they may see.

The third is system access. Salesforce describes an integration agent called Bridget: "Bridget works anywhere, handling any browser-based app, including legacy systems with no APIs." Its diagram names SAP, Oracle Fusion, Workday and Salesforce as examples. For an ERP without a usable API this is a real saving on integration build. It also creates an automated user inside your ERP, and that user has to be governed.

#What Salesforce publishes about the price

Nothing, as at October 2026. The Agentforce Operations page carries no price and invites you to contact Salesforce, and the Agentforce pricing page has no line for Operations. Treat it as quote-only.

What the pricing page does publish is the unit Salesforce uses across Agentforce: "Flex Credits are a new unit of payment for Agentforce that align cost to the business value your AI agents create." It prices them at US$500 per 100,000, with a standard action at 20 credits. Whether Operations processes and back-office agents draw on Flex Credits, on a per-user licence, on a per-process fee, or on a mix, is a question to put to your account executive in writing. Do not assume it either way.

#What sets the price in the negotiation

Because the licence is quoted, the inputs you bring decide the outcome. Prepare them before the first call:

• the processes in scope for year one, named, with monthly volumes, for example purchase order changes, supplier onboarding, invoice audits or warranty claims
• the internal teams involved in each, and how many people actually complete tasks
• the external parties involved, such as suppliers, carriers or contract manufacturers, and how many are active each month
• the systems each process reads or writes, and whether they have APIs
• the term you want, and how quickly you expect to add processes

Ask Salesforce to show the price per process or per volume band, so that adding the fourth and fifth process later is not a fresh negotiation.

#What the implementation is made of

Process selection. Choose two or three processes that are high volume, mostly rule-based, and painful today. Purchase order rescheduling and invoice auditing are common first picks because the inputs are documents and the outcomes are measurable.

Blueprint design. Start from a template where one fits, then write your own approval thresholds, tolerances, escalation paths and owners. Decide what the agent may do alone and what must wait for a person. In procurement and finance, that line is usually set by money and by contract terms.

Exception design. The value of these processes is in the exceptions: a supplier who does not reply, a partial shipment, a price that breaks tolerance, a duplicate invoice. Each needs a rule, a timer and a named human owner.

System access. For each system, decide between an API integration, MuleSoft if you already run it, a Salesforce Flow, or browser-based access through Bridget. Browser access is quicker to start, but your security team will want to know which account it uses, what it can change, and how its actions are logged.

Supplier onboarding to the process. External parties need clear instructions, a contact who can help, and a fallback when they will not engage by email. Plan communications to suppliers as a work package.

Audit and controls. Salesforce describes an audit trail of every action mapped back to the blueprint. Your auditors will still want to see segregation of duties, approval evidence and change control for blueprints. Bring internal audit into design, not into go-live week.

Testing. Test with real documents: last quarter's purchase order changes, last month's invoices, real supplier emails. Synthetic test data hides the formats that break extraction.

Rollout and measurement. Run one process live with a small supplier group, measure cycle time and touch time against the baseline you recorded, then widen.

#How it sits beside Flow and your ERP

Agentforce Operations does not replace every Flow in your Salesforce org, and it should not replace controls inside your ERP. A rule that must give the same result every time, such as a three-way match tolerance or an approval limit, is better owned by the ERP or a Flow, with Operations calling it. Salesforce makes the same point about its own product: governed tools execute the work in core systems deterministically. The coordination around that rule, chasing the supplier, gathering the documents and routing the exception, is where Operations earns its place.

That boundary keeps quotes honest. If a bidder proposes rebuilding ERP logic inside blueprints, ask why, and ask who will keep the two copies aligned.

#What drives effort up or down

Effort drops when processes are already documented, owners exist, and your ERP has usable APIs. It rises with each additional legal entity, currency, approval matrix and supplier tier, and with any process that has never been written down. Browser-based access lowers integration build but adds security review, and a screen change in the ERP can still need a fix.

Manufacturers feel this most in purchase order rescheduling. A single changed demand plan can ripple into dozens of supplier confirmations, each with its own reply time and tolerance. The blueprint has to decide how long to wait, when to chase, when to accept a partial commitment, and when planning must step in. Those decisions are business policy, and writing them down often takes longer than configuring the tool. Budget for workshops with planners and buyers, not just with IT.

The other driver is volume of documents. Processes that start from PDFs and emails need extraction tuned to your formats. A handful of large suppliers with consistent documents is easy. Hundreds of small suppliers with their own templates is not.

#The data migration inside a Regrello move

If you were a Regrello customer before the acquisition, the move to Agentforce Operations is closer to a product transition than a data migration, but there is still data to plan for, and a quote should list it.

Start with the process definitions. Your existing workflows, templates, roles and approval rules are the specification for the new blueprints. Export them, with their version history, before anyone redesigns anything.

Then the in-flight work. On the day you switch, some purchase order changes will be half finished, some supplier onboardings will be waiting on documents, and some invoice disputes will be open. Decide whether those finish in the old process or restart in the new one, and tell the suppliers involved which link to use.

Then the evidence. Completed process history, approvals and attached documents are audit records. They usually stay in an archive under your retention policy rather than being reloaded as live work, but your auditors should agree that approach in writing.

Finally the people. Supplier contact lists, internal role assignments and escalation contacts are easy to forget and painful to rebuild. Treat them as a small, separate migration with its own reconciliation.

#A first-year plan that keeps the cost readable

The safest way to spend on Agentforce Operations is in steps that each prove something.

Quarter one. Record baselines for two processes: cycle time, touches per instance, error and rework rates. Negotiate the licence on those two processes with a price for adding more. Design the blueprints and exception rules, and get security sign-off on system access.

Quarter two. Run the first process live with a small supplier group. Compare against the baseline weekly. Fix extraction and exception rules before widening.

Quarter three. Widen the first process to all suppliers in scope and start the second. Bring internal audit in to review evidence from real instances.

Quarter four. Decide the next processes on the measured results, not on the vendor roadmap. Price them as additions, using the rate agreed at the start.

That shape protects you from the most common failure in process automation: buying for ten processes, implementing two, and paying for eight that never start.

#Getting quotes you can compare

Give every bidder the same process list with volumes and systems, and ask them to return:

• a price per process blueprint, including exceptions and testing
• a price per system connection, stating the method for each: API, MuleSoft, Flow or browser access
• the supplier communication plan and who runs it
• the controls and audit evidence they will deliver for each process
• the baseline measures they will capture before go-live

#Costs that are usually left out

• Security review of browser-based access and the automated accounts it uses.
• ERP licence terms for automated or indirect use; check with your ERP vendor before go-live.
• Internal audit time to approve blueprints and evidence.
• Supplier support during the first months, often handled by procurement staff.
• Process owners' time for design reviews and exception handling.
• Consumption, if your contract meters agent actions in Flex Credits.
• Change control for blueprints after go-live, so a quick edit does not bypass an approval.

None of these is large on its own. Together they can rival the partner's fee, and they land on teams, procurement, finance, security and audit, whose time rarely appears in an IT business case. Put them in the case as named days per team, agreed with each team's lead before the project starts.

#Where the other Regrello questions live

How Regrello's processes map to agents is on Regrello and Agentforce. The acquisition story is on what happened to Regrello. Licence questions, including existing Regrello contracts, are on Regrello licence cost. Integration surfaces in detail are on integrating Regrello with Salesforce. Whether to move off a working process tool is on should I migrate from Regrello, and how to test a partner is on hire a Regrello Salesforce partner.

Our Agentforce consulting team can help you pick the first two processes and build the volume and systems pack that Salesforce and any partner should price from.