Salesforce's own partners are not seeing Agentforce ROI: what that means before you buy a packaged agent platform
The short answer
Agentforce is a defensible purchase for commodity workflows that live inside Salesforce and an unproven one everywhere else: Salesforce calls it the fastest-growing product in its history (The Register), while a survey of its own implementation partners finds none of them crediting it with bookings. A TD Cowen survey of Salesforce partners across the United States, Europe and Asia, reported on 21 August 2026, found that not one respondent named Agentforce as a driver behind recent bookings activity. (The Register)
Both statements are true because they measure different things. For a CIO at a European mid-cap being pitched a packaged agent platform as the fast, low-risk path, the useful reading is not that Salesforce is failing. It is that platform adoption and delivered business value have come apart, and the gap between them is the risk you inherit when you sign.
Key takeaways
- Salesforce’s own delivery channel is the group reporting no Agentforce-driven bookings. That is the least motivated source available, which is what makes it worth reading. (source)
- KeyBanc’s July 2026 downgrade rested mainly on customer feedback rather than a missed quarter: customer data not in order for meaningful AI work, and a product that “just isn’t there.” (source)
- Salesforce’s two headline numbers measure contracts and a construct, not your return: Agentforce annual recurring revenue above US$1.5 billion, up over 240% year over year on a widened definition (source), and a Salesforce-commissioned Forrester model of a 396% return for a composite customer (source).
- Every Agentforce meter except the prepackaged Help Agent, billed per resolution, charges for activity or seats whether or not a case is resolved. (source)
- Salesforce’s own ROI models assume what a buyer’s business case has to prove. The Forrester composite deflects 25% of cases in Year 1, rising to 35% in Year 3, at US$23 an hour for a service representative, and the ROI calculator excludes licences, Data 360 credits and implementation. (Forrester, calculator)
- The recurring blocker named by analysts is not the agent. It is that the company’s data was never assembled into something an agent can reason over, which is work no packaged platform does for you.
The Agentforce numbers side by side
Seven sets of numbers circulate whenever someone asks whether Agentforce is worth it. They come from different people, measure different things, and were paid for by different parties.
| Source | Who produced it | Date | What it says | What it actually measures |
|---|---|---|---|---|
| TD Cowen partner survey | Investment bank, surveying partners in the US, Europe and Asia | Reported 21 Aug 2026 (The Register) | 11% saw little immediate interest, 56% expect interest once the product matures, about a third report buying and trials, none name Agentforce as a bookings driver (Salesforce Ben) | Whether work is reaching signed delivery, seen by the people who install it |
| Oppenheimer customer survey | Investment bank, interviewing Salesforce customers at Dreamforce 2026 | Reported 12 Oct 2026 (Salesforce Ben) | 85% have tested or deployed Agentforce, about half are still in pilot | What customers have in production, seen by the buyers |
| KeyBanc downgrade | Sell-side analysts: CIO survey, partner and customer checks | Hold-equivalent rating, 9 Jul 2026 (CNBC) | Customer data not in order for AI work, the product “just isn’t there”, more CIOs expect to deprioritise Salesforce than to raise spend (The Register) | Buyer sentiment and budget intent |
| Bernstein research | Sell-side analysts | Earlier report, undated | Agentforce “still in early stage of adoption”; consumption-driven monetisation will take longer than most expect, per The Register | Timing of revenue, not customer return |
| Q2 fiscal 2027 results | Salesforce, reported results | 26 Aug 2026 | Agentforce ARR above US$1.5 billion, up over 240% year over year, on a line that now includes Slackbot and Headless 360 (Salesforce) | Contracts signed, on a definition that widened this quarter |
| Forrester Total Economic Impact study | Forrester Consulting, commissioned and paid for by Salesforce | Nov 2025 | 396% three-year ROI for a composite organisation, customer service only (Forrester TEI) | A vendor-funded model of a customer that does not exist |
| List pricing | Salesforce EU price page | Checked 28 Oct 2026 | Flex Credits at EUR 500 (US$500) per 100k credits, 20 per standard action; US$2 per Help Agent resolution, in the page’s code only; per-conversation and per-user options (Salesforce) | What each unit of work costs; only the Help Agent price depends on resolution |
Three rows report the field view: the partner survey, the customer interviews and KeyBanc’s checks, and investment banks produced all three. The two most-quoted numbers, the ARR growth rate and the 396%, both trace back to Salesforce.
What the partner survey actually found
TD Cowen asked Salesforce implementation partners globally what they were seeing on Agentforce, and the distribution matters more than the headline: a clear majority expect interest later, roughly a third see buying and trials now, and none credit it with bookings. (Salesforce Ben)
The same report found partners’ wider Salesforce business slowing. A third were meeting or beating targets, against 43 percent in the previous quarter, and the report summed up: “Agentforce adoption [is] still subdued.” (The Register)
Read that as a delivery signal rather than a market verdict. Implementation partners are the people who install the thing, bill for installing it, and would very much like it to sell. They are not sceptics with a short position. When that group reports interest without conversion, the constraint is usually somewhere between the pitch and the production system, and the partners are the ones standing in that gap. The survey covered European partners as well as American ones, so this is not a reading a buyer in Munich or Stockholm can file under someone else’s market.
The analyst work published six weeks earlier said the same thing from a different vantage point. On 9 July 2026 KeyBanc downgraded Salesforce to a hold-equivalent rating and removed its price target. (CNBC) It did not point to a missed quarter. It cited mainly customer feedback: enterprises do not have their data in a state where agents can do meaningful work, and the product “just isn’t there” for broad deployment. It also reported that most customers are not willing to pay for AI capabilities through their CRM provider. (The Register)
Salesforce’s spokesperson told The Register that the company is “focused on helping customers move faster, including through forward-deployed engineers and out-of-the-box agents.” (The Register) That forward-deployed engineers appear in the vendor’s own answer says where much of the production work sits. Our piece on who really does forward deployed engineering now covers what those pods are and who funds them.
Agentforce adoption in 2026: what customers told Oppenheimer at Dreamforce
Oppenheimer has interviewed Salesforce customers at Dreamforce since 2012. In 2026, 85% of those it surveyed had tested or deployed Agentforce, and they said around 40% of the data going through Agentforce is handled by a third-party provider rather than Data 360. Analyst Brian Schwartz wrote in a client note, reported by Salesforce Ben on 12 October 2026: “Nearly half [of respondents] remain in the pilot or testing stage, leaving the pace of production adoption and monetization uncertain.” (Salesforce Ben)
Partners see interest without bookings, and customers report trials without production. For a buyer, the data finding matters more than the adoption rate. When a large share of what the agent reads sits outside Data 360, the agent’s context already lives in two places, and someone has to keep them consistent. No Agentforce meter prices that work.
The vendor’s numbers say something else, and both can hold
Seven weeks after KeyBanc’s downgrade, Salesforce reported second-quarter fiscal 2027 results and called it a record quarter. Agentforce annual recurring revenue exceeded US$1.5 billion, up over 240% year over year, and the release notes that from this quarter the Agentforce line includes Salesforce’s AI offerings, Slackbot and Headless 360. (Salesforce)
That definition matters. A growth rate measured across a quarter in which the line started counting more products is not a like-for-like adoption signal. The same release counts 7.0 billion Agentic Work Units delivered to date across Agentforce and Slack, a measure of work the agents did, not of whether it resolved anything for a customer.
Nothing about the vendor’s numbers contradicts the partner survey, and a buyer who lets one cancel the other will draw the wrong conclusion from both. Annual recurring revenue measures contracts signed. It rises on new logos, on bundling, on renewals repriced to include a product, and on enterprises buying capacity ahead of a deployment they have not yet built. Bookings attributable to Agentforce, as reported by the people delivering it, measure work that reached a production workflow and produced something a customer would pay again for. A product line can grow quickly on the first measure while the second stays flat, and that is what an early adoption curve for enterprise software usually looks like from the inside.
The third number is the Salesforce-commissioned Forrester Total Economic Impact study of Agentforce for customer service, which models a 396% three-year return for a composite organisation. (Forrester TEI) Forrester interviewed six decision-makers, and Salesforce provided the customer names. Vendor-commissioned modelling is not worthless, but it is a model: the composite organisation does not exist, its baseline is constructed, and the vendor paid for it. Beside a survey of the vendor’s own delivery channel, it points the other way. The disagreement is the finding, and it is what belongs in front of your board.
How much does Agentforce cost? Pricing models compared
Salesforce publishes four usage meters: Flex Credits at EUR 500 per 100k credits, a fee per conversation, a price per resolution for its prepackaged Help Agent, and the User Licence at EUR 5 per user per month, which also draws Flex Credits. The table is from Salesforce’s EU price page, checked on 28 October 2026, and the AELA row from its buying-models page. Our post on SAP Joule’s limits sets out SAP’s AI Unit pricing in the same format.
| Model | Unit and list price | What triggers a charge | Who carries the cost of an unresolved case |
|---|---|---|---|
| Flex Credits | EUR 500 (US$500) per 100k credits; 20 per standard action, 30 per Voice action | Each action, prompt or translation | The buyer |
| Conversations | EUR 2 (US$2) per conversation; not displayed, marked for existing customers | Each conversation | The buyer |
| Help Agent Resolutions | US$2 per resolution; not displayed, euros “currently unsupported” | A case the Help Agent resolves on its own, start to finish | Salesforce, for this one agent |
| Agentforce User Licence | EUR 5 per user per month, “Requires Flex Credits” | A licensed employee, plus the credits drawn | The buyer |
| Agentforce add-ons | US$125 per user per month for Sales, Service and Field Service; Industries US$150 | A licensed user; employee usage unmetered | The buyer, as a fixed seat cost |
| Agentforce Max Editions | From US$550 per user per month, with 2.75M Flex Credits per org per year | A licensed user, plus credits beyond the pool | The buyer |
| Salesforce Foundations | EUR 0, Enterprise Edition and above | Nothing; adds “key features to your existing CRM” | Not a usage meter |
| Agentic Enterprise License Agreement (AELA) | Fixed price, fixed term; no public list price | Nothing per use: “no overages, and no usage-based billing” | The buyer, as a fixed fee; Salesforce carries usage volume during the term |
The Conversations and Help Agent prices sit only in the page’s code, so confirm them in your quote. On every option except the Help Agent, an agent that does not yet work costs the same as one that does.
What is the Agentic Enterprise License Agreement (AELA)?
Salesforce’s EU buying-models page, which spells it Licence, describes the AELA as “a fixed-price, fixed-term agreement with unlimited access to Salesforce consumption services, no overages, and no usage-based billing”. (Salesforce) The Register described it in December 2025 as “a flat, seat-based arrangement” and reported that Salesforce’s chief revenue officer, Miguel Milano, told investors: “We take the risk because we want our customers to be successful.” He added: “And then I have another 20 years to monetize that customer.” (The Register)
In January 2026, Gartner analyst Hannah Decker told The Register that Gartner expected AELAs to be “converted into defined quantity contracts at the end of the agreement”. Salesforce called the claim that it is moving away from capped agreements “inaccurate”. (The Register) Settle before signing what price and scope apply at renewal, once both sides know how much you use.
How do Agentforce Flex Credits work, and what does a case cost?
A Flex Credit is the unit Salesforce bills agent work in. A standard action draws 20 credits and an Agentforce Voice action 30, so at EUR 500 per 100k credits a standard action costs EUR 0.10, and Salesforce’s own examples price it at US$0.10. An action is one function the agent executes, such as updating a record, summarising a case, answering a product question, or running a prompt or flow. (Salesforce)
The rest of the mechanics, from the same page and the buying-models page:
- Credits are “fungible across Actions, Prompts, Translations, and Voice Actions”.
- “Unused Flex Credits do not roll over into subsequent subscription terms.”
- Flex Credits and Conversations “will not be supported in the same org”.
- Usage above your entitlement carries “no overage penalty” and is billed at your contracted rate; on PayGo, all usage is billed at list price.
- Pre-Purchase is paid upfront; Pre-Commit has a “True-up at term end if usage is below commitment”. Digital Wallet tracks consumption.
Salesforce’s worked examples run from one to five actions per request: a knowledge-base answer takes one, and a “Where is My Order” request two, at US$0.20. They count no retries or clarifying turns, and four of the five note that the example “does not include other costs like Data 360 credits or other consumption services”.
On list prices, a conversation needs more than 20 standard actions before Flex Credits cost more than the US$2 conversation fee. Per resolution, the picture changes, if the Help Agent’s US$2 holds in your quote. Take a generic example, not a client case: four standard actions per conversation, or US$0.40 at list. If one conversation in two ends resolved, each resolution costs US$0.80 on Flex Credits, US$4 on the per-conversation meter and US$2 on the Help Agent price. If one in five ends resolved, Flex Credits reach US$2 per resolution and the conversation meter US$10. The per-resolution price insures against failure rather than discounting success. It also leaves Data 360 and Agentforce unmetered during the interaction, while Salesforce’s Flex Credit examples leave Data 360 costs out.
Will Salesforce charge Flex Credits for MCP and API calls?
Yes, once metering starts. Salesforce Ben reported on 24 September 2026 that agents working with Salesforce will have to be registered under a new Agentic Identity, and every successful call they make, through MCP or directly through an API, will count as a “Headless Platform Interaction” and consume Flex Credits. (Salesforce Ben) Salesforce has not published the multiplier and has promised 30 days’ notice before metering begins. Existing API-based integrations keep their current pricing, and only “active production” orgs are metered.
By 21 October Salesforce had reached out to discuss the change with at least one architect who had criticised it publicly, so the terms may still move. (Salesforce Ben) Salesforce admin Vicki Moritz-Henry put the buyer’s problem plainly: “It’s hard to forecast credit consumption, and that makes it a tough sell internally.” (Salesforce Ben)
Does Agentforce pay-per-resolution pricing fix the ROI problem?
For one prepackaged service agent, it moves the cost of an unresolved case back to Salesforce. It does not change who defines “resolved”, and it does not reach work that sits outside Salesforce.
Salesforce announced the Help Agent on 25 June 2026, with pay-per-resolution pricing available from July 2026. (Salesforce) Organisations pay only when it “autonomously resolves an issue from start to finish”, and “If a customer gives negative feedback or asks for human escalation, there is no charge.” The agent grounds itself “automatically on your Salesforce Knowledge”. Salesforce’s evidence is its own help site, where “Agentforce has handled 4.3 million inquiries and resolved 70 percent of them”. That is the best case for an agent grounded on knowledge the vendor wrote about its own product, not a forecast for yours.
This is a real improvement for the commodity case: a buyer can test a service agent without paying for the conversations it fails. Three checks decide whether the price fits your service desk.
- Compare definitions of resolved. Salesforce’s is start to finish, with no escalation and no negative feedback; yours may require that a case does not reopen within a set window. Ask how a customer who leaves without feedback and calls back the next day is billed.
- Measure how much of your contact volume Salesforce Knowledge can answer. The launch names “Messy data, the single biggest reason agents fail” as the problem, and grounding on Salesforce Knowledge helps only where the answer already lives there. Tag a sample of cases to find that share.
- Check whether your order, billing or ERP data is in reach. Order management, scheduling and account management are actions you add, and the integration behind them sits outside the per-resolution price.
What does an Agentforce business case assume? The ROI assumptions to check before signing
Eight assumptions carry most Agentforce business cases, and Salesforce’s own models state most of them: the Salesforce-commissioned Forrester composite, the price page and the ROI calculator. The last column is work to do before the contract, not after the pilot.
| Assumption | What Salesforce’s own models assume | What it depends on | How to check it before signing |
|---|---|---|---|
| 1. Deflection or resolution rate | Forrester: 25% of cases deflected in Year 1, 35% by Year 3; interviewees saw 15% to 37% | Your contact mix, and whether readable knowledge holds the answer | Tag three months of cases by whether existing knowledge answers them; underwrite resolution, not deflection |
| 2. Actions per resolution | One to five per request in Salesforce’s examples | Lookups and updates per case, plus retries and clarifying turns | Walk 20 real cases and count the system calls |
| 3. Credit consumption | 20 credits per action, 30 for voice; examples exclude Data 360 | Features fired per case, Data 360 billing, the MCP and API multiplier | A written credit forecast per use case |
| 4. Human handling cost | Forrester: US$23 an hour, 8 minutes per case | Your loaded labour cost and handling time | Finance’s loaded cost per handled case |
| 5. Time saved on cases that still reach a person | Forrester: 50% less handling time, plus 2 minutes of admin avoided per case | How much intake the agent completes before the handover | A pilot against a control group |
| 6. Data readiness | Salesforce: “Messy data, the single biggest reason agents fail” | Where each contact reason’s answer lives, and who keeps it current | Name the system and owner behind each top contact reason |
| 7. Integration scope | Forrester: 550 implementation hours | Every system outside Salesforce the workflow reads or writes | List and price each one; ask how your own agents’ calls are classed |
| 8. Ramp and commitment | A three-year ramp in Forrester and the calculator; unused credits do not roll over | Adoption speed and volume growth | Does the case clear on Year 1 performance? Size the commitment to Year 1 volume |
On credit consumption, Salesforce’s pages describe Data 360 billing two ways: the calculator says “Data 360 Credits are used to pay for the consumption of Data 360”, the buying-models page that Flex Credits “can be spent across Agentforce and Data 360”. Confirm in writing which unit your usage draws.
On handling cost, Forrester’s US$23 an hour is a dollar composite. Eurostat puts 2025 average hourly labour costs across the whole economy at EUR 34.9 in the EU and EUR 51.7 in Denmark (Eurostat). That is not a service-role rate, so use finance’s loaded cost, and apply the budget-line check below before counting the saving.
On integration and risk, Forrester’s interviewees reported implementation timelines from two weeks to six months, and several received discounted professional services as beta participants. Forrester itself cut the benefit by 15%, and raised consumption costs by 10% and implementation costs by 15%. Ask which risks any model you are shown includes.
What the Agentforce ROI calculator leaves out
Salesforce’s ROI calculator states its limits in its own notes: results are “provided for illustrative purposes only” and “should not be relied upon”, and “Salesforce licences, Data 360 credit cost and implementation costs not included.”
For customer service, it prices an agent-handled case at about US$0.30, ramps the share of cases agents take over three years with Year 1 at 70% of Year 2, and values hours saved from headcount, average salary and that share. That becomes a saving only if hiring, overtime or outsourcing changes, so ask your finance team which budget line moves, and replace the calculator’s dollar inputs with your own euro costs.
Why the packaged platform is not the low-risk option
The pitch for a packaged agent platform is that it sits inside a system you already run, so the integration work is done and the risk is small. The first half is true. The second does not follow.
An agent is only as capable as the context it can reach and reason over. Inside a packaged platform, that context is bounded four ways, and none of the four is the model:
- The data model. The agent sees what the platform’s objects and fields describe. Everything your business knows that lives in the ERP, the pricing system, the contract archive or the spreadsheets your commercial team actually runs on is outside that boundary until someone does the work to bring it in, and bringing it in usually means copying it into the vendor’s shape.
- The permission surface. Agents inherit the platform’s identity and sharing model. That is convenient until the workflow crosses a boundary the platform was never designed to express, at which point you are building an exception rather than a capability.
- The roadmap. What the agent will be able to do next quarter is decided by the vendor’s product organisation, weighed against every other customer. Your third-most-important workflow is nobody else’s priority.
- The accumulated context. The evaluations, the corrections, the retrieval logic, the domain rules your team encodes over eighteen months of tuning: that is the asset. Inside a packaged platform it accrues as configuration in someone else’s system, and it does not travel.
Model portability gets discussed because it is visible and easy to promise. Those four layers are where the actual dependency accumulates, and they are the reason the KeyBanc feedback keeps returning to data readiness. The blocker enterprises hit is not that the agent is not clever enough. It is that nobody built the layer underneath it, and no packaged platform builds that layer for you, because doing so would mean reconciling systems the vendor does not sell.
Metering of agentic MCP and API calls will add a cost at the same boundary, on every successful call an outside agent makes. Model it before deciding where the context layer sits: it is the practical side of owning your intelligence.
This is the same argument our build vs buy vs embed post makes in the abstract. Agentforce is what it looks like when a real market runs the experiment in public.
When buying is the right call
Buying the packaged agent is correct more often than a company in our position usually admits. The test is narrow and worth applying honestly.
Buy when the workflow lives inside one system of record, is close to commodity, encodes no advantage specific to your company, and you have no appetite to own its maintenance. Case deflection and routing inside a CRM you already run, service-request triage, a first-draft assistant sitting on tickets: these are reasonable purchases, and building them yourself is an expensive way to arrive at a worse version of something you could have configured.
Do not buy when the workflow crosses systems, when the value sits in the handoffs between departments rather than inside any one of them, or when the context that makes the workflow correct is knowledge only your company holds. That is the case where the packaged platform gets you a demo quickly and then stalls at the same wall the partners are describing.
What to establish before you sign
Five questions, asked before the contract rather than after the pilot:
- Where does the context live when this is running? If the answer is “in the platform,” you have rented the intelligence and you are paying to keep it.
- Who owns the evaluation set? The record of what the agent got wrong and how it was corrected is the most valuable artefact the project produces. Establish in writing that it is yours and that it is exportable in a usable form.
- What is the number, and when is it measured? A business number agreed before the build, against a measured baseline, in a defined window. Without that, the ROI conversation happens after the spend, which is the wrong order. Our ROI benchmarks post covers what a defensible baseline looks like.
- What is left at term end? Unused Flex Credits do not roll over, Pre-Commit trues up at term end, and the multiplier for agentic calls is unpublished, so size the commitment to Year 1 volume.
- Who is accountable when it does not work? The partner survey is a description of what happens when nobody is: interest, trials, no bookings, and a product everyone is waiting on someone else to mature.
The pattern here is not specific to Salesforce. It is the same repricing of a delivery assumption that showed up in Accenture’s worst trading day in June. In both cases the market moved on a gap between what a delivery model promises and what it has demonstrated. In both cases the buyer’s protection is the same: own the layer the agents run on, keep it model-agnostic, and tie the engagement to a number somebody is accountable for.
FAQ
Is Agentforce worth it? For a commodity workflow inside Salesforce, such as case deflection or service-request triage in a CRM you already run, it can be a reasonable purchase. Beyond that, the return is not yet demonstrated. A TD Cowen survey of Salesforce’s own implementation partners, reported in August 2026, found none naming Agentforce as a driver of recent bookings. (Salesforce Ben)
Is Agentforce delivering ROI for enterprises? The evidence splits by who is measuring. Salesforce reports Agentforce annual recurring revenue above US$1.5 billion, up over 240% year over year, and a Salesforce-commissioned Forrester study models a 396% three-year return for a composite organisation. Salesforce’s own implementation partners, surveyed by TD Cowen, name no Agentforce-driven bookings. (The Register)
How much does Agentforce cost? For a new buyer, Flex Credits list at EUR 500 (US$500) per 100k credits, and a standard action uses 20 credits, which Salesforce prices at US$0.10. The Agentforce User Licence is EUR 5 per user per month plus Flex Credits, and larger customers can sign a fixed-price, fixed-term AELA. Every option except the prepackaged Help Agent, billed per resolution, charges for activity or seats whether or not a case is resolved. (Salesforce)
What are Agentforce Flex Credits? The unit Salesforce bills Agentforce consumption in: 20 credits per standard action and 30 per Agentforce Voice action, at EUR 500 (US$500) per 100k. Credits are fungible across actions, prompts, translations and voice actions, and unused credits do not roll over into the next subscription term. (Salesforce)
Is Agentforce cheaper with Flex Credits or per conversation? For a new buyer the choice is mostly made: the price page marks Conversations for existing Conversations customers and does not display its price. For an existing customer, at US$0.10 an action and US$2 a conversation, Flex Credits cost more only above 20 standard actions per conversation, and Salesforce’s own examples use one to five. Neither meter depends on whether the case was resolved.
What is Agentforce pay-per-resolution pricing? Salesforce bills its prepackaged Help Agent, available since July 2026, only when it resolves an issue autonomously from start to finish, with no charge after negative feedback or a request for a human. (Salesforce) A US$2 per-resolution figure sits in the price page’s code but is not displayed, and euro pricing is marked unsupported, so confirm the price in your quote.
What is the Agentic Enterprise License Agreement (AELA)? In Salesforce’s description, a fixed-price, fixed-term agreement with unlimited access to Salesforce consumption services, no overages and no usage-based billing. (Salesforce) It moves usage volume risk to Salesforce for the term, while the buyer pays whether or not an agent resolves anything. Settle the renewal price and scope before signing.
Will Salesforce charge for agentic MCP and API calls? Yes, once metering starts: successful MCP or API calls by agents registered under Salesforce’s Agentic Identity will consume Flex Credits as Headless Platform Interactions, Salesforce Ben reported in September 2026. (Salesforce Ben) Salesforce has not published the multiplier and has promised 30 days’ notice before metering begins. Existing API-based integrations keep their current pricing.
What assumptions does an Agentforce business case rest on? Eight: the deflection or resolution rate, actions per resolution, credit consumption, the human handling cost, time saved on cases that still reach a person, data readiness, integration scope, and the ramp and commitment. The Salesforce-commissioned Forrester composite assumes 25% of cases deflected in Year 1 rising to 35% in Year 3, US$23 an hour for a service representative and 550 implementation hours. (Forrester TEI) Check each against your own cases, costs and systems before signing.
Why did analysts downgrade Salesforce over Agentforce? KeyBanc downgraded Salesforce to a hold-equivalent rating on 9 July 2026, citing mainly customer feedback rather than a missed quarter: customer data not ready for agents, the product not ready for broad deployment, and more surveyed CIOs planning to deprioritise Salesforce spend than to raise it. An earlier Bernstein report had called Agentforce “still in early stage of adoption”. (The Register)
Does a packaged agent platform lock you in? It locks in the part that matters most, which is not the model. The data model, the permission surface, the vendor roadmap and the accumulated context all sit inside the platform, and swapping the model underneath does not move any of them.
When is buying a packaged agent platform the right decision? When the workflow is commodity, sits inside one system of record, carries no proprietary data advantage, and you have no intention of owning its maintenance. Case deflection inside a CRM you already run qualifies. A workflow that crosses the CRM, the ERP and two legacy systems, and that encodes how your company competes, does not.
How should a CIO test a vendor ROI claim? Ask who paid for the study, what the baseline was, whether the organisation is real or composite, and what the same number looks like from the people doing the implementations. When a vendor’s model and its delivery channel disagree, the disagreement is the finding. Our AI agent ROI benchmarks for 2026 set out what each common number measures.
Related reading
- Build vs buy vs embed: choosing an enterprise AI delivery model
- Who really does forward deployed engineering now
- Accenture’s worst day on the market: what it tells a CIO about the vendor they are about to sign
- The ROI of enterprise AI agents: 2026 benchmarks
- SAP Joule’s limits: ECC, Microsoft Copilot, MCP and the handoffs it can’t see
- Salesforce fixed the CRM. Workday fixed HR. Nobody owns the handoffs.
- What Palantir AIP and Foundry cost a European mid-cap
Nucleo is an AI-native enterprise transformation company for European mid-caps. When the workflow crosses the CRM, the ERP and the systems no platform sells, we build the context engine, the intelligence layer your company owns, inside your stack, model-agnostic, with engineers embedded and a number agreed before the build starts. The intelligence stays yours. See how an engagement works, or write to us with the workflow the platform stalled on.