Categories
CRM Salesforce

CRM Implementation Services: What US Buyers Should Expect (Scope, Cost, Timeline)

Short answer: CRM implementation services cover everything between buying a CRM and your team using it every day: planning, configuration, data migration, integrations, testing, training and support after go-live. In the US, a small and simple rollout usually costs about $5,000 to $20,000 and takes 6 to 10 weeks. A large, multi-team project can run $40,000 to $150,000 or more and take 4 to 9 months (Empat, 2026 guide). Where you land depends on user count, data quality, integrations and who does the work.

Last updated: 29 October 2026. By Ankur Pandey, Marketing Manager at Ashapura Softech Inc.

If you are about to hire a partner for CRM implementation services, the quotes you collect will probably look very different from each other. One firm says $12,000. Another says $45,000. Both can be honest. This guide explains what sits behind those numbers, so you can compare quotes properly instead of guessing which one is wrong.

We are a Salesforce and Odoo consulting firm based in Irving, Texas, with a development center in Ahmedabad, India, and we have worked with small and mid-size businesses since 2012. So yes, we sell CRM implementation services. I have tried to write this the way I would want it explained if I were the buyer: plain numbers, sources you can open, and the parts vendors usually skip.

What are CRM implementation services?

CRM implementation services are the professional work of getting a CRM live and useful in your business. The software is only one input. The rest is decisions and effort: how your sales process maps into the system, which data comes across, which tools it connects to, and how your people learn it.

A decent scope usually includes these pieces:

  • Discovery and requirements: workshops to map your real sales, service or marketing process, not the one on a slide.
  • Solution design: objects, fields, roles, permissions, pipeline stages, reports.
  • Configuration and customization: building the design in the platform, including automation.
  • Data migration: cleaning, mapping and loading records from spreadsheets or an old CRM.
  • Integrations: connecting email, ERP, accounting, marketing tools or your website forms.
  • Testing and user acceptance: your team tries real tasks before launch.
  • Training and change management: role-based sessions, quick guides, an owner for adoption.
  • Go-live and support: a stabilization period after launch where fixes are fast.

If a quote leaves out data migration, integrations or training, ask why. Those are the items that most often show up later as change orders.

CRM implementation services phases from discovery and design to go-live support
The 8 phases of CRM implementation services.

How much do CRM implementation services cost in the US?

There is no single price, because implementation cost is mostly hours multiplied by an hourly rate. Both numbers move with your project.

Here are published ranges from recent 2026 guides. Treat them as planning ranges, not quotes.

CRM implementation cost and timeline by project size in the US for 2026
CRM implementation cost and timeline by project size (source: Empat, 2026).
Project typeTypical effort or sizeCost rangeTypical timelineSource
Small team, standard pipeline, one data import (Salesforce)60 to 150 hours$6,000 to $37,500 at US partner ratesNot statedThe Frontkit
Low complexityUnder 20 users, one team$5,000 to $20,0006 to 10 weeksEmpat
Mid-marketSeveral teams, integrationsVaries widely10 to 20 weeksEmpat
High complexity200+ users, many departments, compliance needs$40,000 to $150,000+4 to 9 monthsEmpat

Another rule of thumb from one implementation firm’s project history: for small and mid-size businesses, implementation tends to cost one to three times the first-year license bill, while mid-market projects run three to ten times (Ecosire). If a partner quotes a tiny fraction of your license cost for anything beyond a starter setup, the same source warns that scope is probably missing, often migration or integrations.

What drives the price

Hourly rate. Rates for Salesforce work in the US vary by role. One 2026 guide puts certified consulting partners at roughly $100 to $250 an hour and senior architects at $200 to $400 (Codleo). Offshore delivery rates are commonly 30 to 60 percent lower than US rates (Clientell), which is why many US firms, including us, deliver with a blended US and India team.

Cheaper per hour is not always cheaper overall. The Codleo guide gives a simple example. Partner A charges $95 an hour and estimates 360 hours plus 60 hours of rework after launch, for $39,900 in total. Partner B charges $170 an hour, estimates 220 hours and has no rework, for $37,400. The higher rate won.

CRM implementation partner example showing a higher hourly rate with a lower total cost
Higher hourly rate, lower total cost (source: Codleo).

Data quality. Messy data takes longer to clean and map. A spreadsheet with five years of duplicate contacts is a bigger job than a clean export from another CRM.

Number of integrations. Each connection to ERP, accounting, email or a marketing tool adds design, build and testing time. See our guide to Salesforce integration with other tools for what that involves.

Customization. Custom objects, approval flows and role-based logic cost more than standard setup.

Compliance and security. SSO, audit trails or industry rules add scope. Empat lists SOC 2, HIPAA or SSO requirements as a cost driver in the higher-complexity case.

Your own time. The same Empat guide says a mid-market project commonly takes 80 to 150 hours of internal staff time. That does not show up on the partner’s invoice, but it is real cost.

Budget a buffer

Requirements change once people see a working system. One 2026 cost guide suggests planning a 15 to 20 percent buffer for change orders on fixed-price projects (Clientell). I would add the buffer to your internal budget even if the quote says fixed price.

How long does CRM implementation take?

For most companies, one provider’s overview puts it at three to six months, with simple SaaS rollouts for small teams taking as little as a few days to a few weeks (Hauer Power). That matches the Empat ranges above.

What stretches a timeline in practice:

  1. Unclear goals at the start, which leads to scope creep.
  2. Data cleanup nobody owned.
  3. Slow feedback from your team during design and testing.
  4. Late integration requirements.
  5. Training squeezed in at the end.

A phased plan helps. Launch the core pipeline first, then add service, marketing or reporting in later phases. We scope projects in phases so clients can see results before committing to the next stage.

Why do CRM projects fail, and what does that mean for you?

You will see scary numbers online. One review of the research puts CRM implementation failure somewhere between 30 and 63 percent (LowCode Agency). Treat those with care. A DestinationCRM article on the topic quotes consultants arguing that the figures depend on how “failure” is defined, and that projects without agreed success metrics cannot be judged fairly either way (DestinationCRM).

So the practical lesson is not “most projects fail.” It is this: write down what success means before you start. Three or four measurable goals are enough, for example:

  • Reps log calls and deals in the CRM, not in personal spreadsheets.
  • Forecast reports come from the system, not a monthly manual rebuild.
  • Leads get a first response within a set time.
  • Duplicate records stay under an agreed level.

When a project drifts, it is usually for people reasons: nobody owns adoption, training is thin, or the system was built for managers’ reports and not for the daily work of the people entering data. Choose a partner who asks about those things in the first call. If your system is already live and has drifted, start with our free CRM health check.

Salesforce, Zoho, HubSpot or Odoo: does the platform change the services you need?

The phases are the same, but the effort is not. Salesforce is highly configurable, so more of the work is design decisions and admin setup. Zoho CRM often suits smaller teams that want lower license cost. Odoo makes sense when you want CRM and ERP in one system. The right choice depends on your process, your budget and how many tools you already run.

If you are still choosing, read our comparison of Zoho vs Salesforce CRM and the breakdown of Salesforce Core, Advanced and Max editions before you request quotes. Picking the wrong edition or platform is a more expensive mistake than picking a slightly pricier partner.

A scoping checklist before you ask for quotes

Send every partner the same brief. You will get quotes you can actually compare.

CRM implementation services scoping checklist to send every partner before quotes
Scoping checklist to send every partner.
  • Number of users and their roles (sales, service, management, admin).
  • Your current system, or “spreadsheets and email.”
  • Rough record counts: accounts, contacts, deals, open cases.
  • Tools to connect, with the version or plan where you know it.
  • Reports you must have on day one.
  • Any compliance requirement (SSO, audit trail, industry rules).
  • Your target go-live date and why it matters.
  • Who on your side will own the project, and how many hours a week they can give.

Questions to ask a CRM implementation partner

  1. Can I see two or three projects similar to mine, with the outcome and timeline?
  2. Who will actually do the work, and where are they based?
  3. What is included in the fixed price, and what triggers a change order?
  4. How do you handle data migration, and who signs off on data quality?
  5. What does training look like, and is it role-based?
  6. What happens after go-live? How long is the support window, and what does it cost afterward?
  7. What do you need from my team each week?

Good partners answer these without hesitation. If the answers are vague, that tells you something.

How we approach CRM implementation services at Ashapura

We work in US hours from our Irving, Texas headquarters and deliver with a team in Ahmedabad. Typical engagements include new CRM rollouts, data migration, integrations, custom development and CRM health checks for teams whose system has drifted from how they actually work. You can see examples in our case studies, such as Salesforce implementation for a fleet management firm and Salesforce for a U.S. industrial supply business.

If you want a second opinion on a quote you already have, or a rough scope and budget range for your project, you can book a free 30-minute consultation. No pitch deck, just a conversation about your setup.

Frequently asked questions

How much do CRM implementation services cost?

For a small team with a simple setup, published 2026 ranges run from about $5,000 to $20,000. Large, multi-department projects with integrations and compliance needs can reach $40,000 to $150,000 or more. Your quote depends mainly on hours, hourly rate, data quality, integrations and customization.

How long does CRM implementation take?

Simple rollouts for small teams can take a few weeks. Mid-market projects often take 10 to 20 weeks, and complex ones can take 4 to 9 months. Clean data, clear goals and fast feedback from your team shorten the timeline.

What is included in CRM implementation services?

Most scopes include discovery, solution design, configuration, data migration, integrations, testing, training and go-live support. Always confirm in writing which of these a quote covers, since migration, integrations and training are the items most often left out.

Should I choose a fixed-price or hourly engagement?

Fixed price works when requirements are clear and stable. Hourly or time-and-materials suits projects where scope will evolve. Either way, ask what triggers a change order, and keep a 15 to 20 percent buffer for scope changes.

Why do CRM implementations fail?

Reported failure rates vary widely because failure is defined differently from study to study. The common causes are unclear goals, poor data, weak training and no owner for adoption. Defining success metrics before you start is the simplest protection.

Can a small business afford CRM implementation services?

Yes. A phased scope lets you launch the essentials first and add features later. Starting with a clean pipeline, basic automation and a tidy data import is often enough to begin, and you can expand once the team is using it.

Sources

About the author

Ankur Pandey is the Marketing Manager at Ashapura Softech Inc., a Salesforce and Odoo consulting firm in Irving, Texas. He writes about CRM and ERP implementation for small and mid-size US businesses.

Categories
Agentforce Salesforce

Salesforce Koa Explained: Should Your Agentforce Agents Switch?

Last updated: October 26, 2026

Short answer: Salesforce Koa is Salesforce’s first CRM reasoning model for Agentforce, built with NVIDIA on the Nemotron 3 Super model and announced on September 15, 2026. It is trained to work through multi-step CRM tasks such as qualifying leads, routing cases and updating opportunities, and Salesforce reports it matches or beats leading models on CRM actions with about 3x fewer errors. It is in pilot now, with general availability expected in Winter 2026 in US regions. Most orgs should test it on high-volume agent tasks when it reaches their region, but should not rip out their current model until Salesforce publishes pricing.

Salesforce Koa CRM reasoning model for Agentforce

What is Salesforce Koa?

Salesforce Koa is a reasoning model built for one job: powering Agentforce agents that work inside CRM processes. Announced at Dreamforce on September 15, 2026 as a joint effort between Salesforce and NVIDIA, it is not a general chatbot model. It was built to understand the shape of a deal, the lifecycle of a service case and the step-by-step tool use that real business workflows need.

Two things make it different from the models Agentforce has used so far. First, it is specialized: the training focused entirely on CRM-style reasoning rather than general knowledge. Second, it is Salesforce-hosted. Salesforce controls the model weights and runs post-training and inference inside its own trust boundary, which matters to any company whose blocker on AI agents has been data leaving the vendor perimeter.

Koa vs a general-purpose model: at a glance

Salesforce KoaGeneral frontier models in Agentforce
Built forCRM workflows: leads, opportunities, cases, follow-upsEverything, with no CRM specialization
BaseNVIDIA Nemotron 3 Super, post-trained by SalesforceVendor frontier models (OpenAI, Anthropic, Google)
HostingInside Salesforce infrastructure, weights controlled by SalesforceCalls out to the model provider
Reported strengthMatches or exceeds leading models on CRM actions with about 3x fewer errors (Salesforce CRM Bench)Stronger on unusual, complex or open-ended tasks
AvailabilityPilot now; GA expected Winter 2026, US regions firstAvailable now
PricingNot published yetKnown through Agentforce consumption

How Salesforce Koa was built, in plain terms

Salesforce started from NVIDIA Nemotron 3 Super, an open-weight 120B model, and post-trained it using supervised fine-tuning plus reinforcement learning (a method called GRPO), with NVIDIA NeMo tooling. The training corpus is fully synthetic: scenarios modeled on 27 years of CRM deployment knowledge across more than 14 industries, covering the reasoning, tool selection and decision-making an agent needs for tasks like generating leads, qualifying opportunities and resolving service cases. Salesforce states that no customer data was used to train the model.

That last point is worth pausing on. The pattern here, a strong open-weight base plus deep domain knowledge layered on top, is becoming the standard recipe for enterprise AI. The moat is not the biggest model; it is the workflow knowledge the vendor can encode into a smaller one.

Where Salesforce Koa shows up in your org

Once it is available to you, Salesforce Koa appears in three places, and you opt in like any other provider:

  • As a managed LLM in the Data Cloud generative models catalogue (Data Cloud is now called Data 360; here is what that rename actually changed)
  • Org-wide, as a fourth model provider option in Agentforce Setup
  • Per agent and sub-agent, selected at the individual agent level

The per-agent option is the one to care about. It means you can route your high-volume, well-defined agents to Koa while keeping a frontier model behind the agents that handle messy, open-ended work. Model routing, not model loyalty, is where Agentforce economics are heading, and routing decisions feed straight into how your Agentforce credits get consumed.

The claims, and what is still missing

Salesforce reports that on CRM Bench, its benchmark of real CRM actions like updating an opportunity, routing a case and scheduling a follow-up, Koa matches or exceeds leading model performance with about three times fewer errors. Independent reporting places Koa ahead of some general models on public tool-use benchmarks while still below the top frontier models, which is exactly what you would expect from a specialized model. Early pilot customers include 1-800Accountant, Baxter Credit Union, Engine, Formula 1, UChicago Medicine and Xero.

Three numbers have not been published: price, context window and latency. For a hosted model sold inside Agentforce, price is the one that decides adoption. Until it lands, treat every switch-over plan as provisional.

Should your agents switch to Salesforce Koa?

Our read, as a team that configures Agentforce for US clients:

  • Raise your hand for the pilot if you run Agentforce in a US region and your main blocker has been data boundary or model governance. Koa staying inside Salesforce infrastructure is the strongest part of the offer today.
  • Plan a comparison test, not a migration, if you already have agents in production. Pick one high-volume agent, run the same scenarios on your current model and on Koa when it reaches GA, and compare error rates and credit burn. Switch only on evidence.
  • Fix your data first if your agents are not live yet. A specialized reasoning model still reasons over whatever your CRM contains, and duplicates or stale records produce confidently wrong answers from any model. Data readiness is step one of any Agentforce rollout we run.
  • Wait if you are outside US regions or price-sensitive. GA is US-first and the pricing is unknown, so there is nothing to act on yet beyond awareness.

Free Salesforce implementation checklist

Thinking about Agentforce and Koa? The groundwork is the same: scoping, data readiness and adoption. These are the steps we check on every Salesforce project.

Get the free implementation checklist

How Salesforce Koa compares on benchmarks

Benchmark numbers deserve some skepticism, especially when the benchmark belongs to the vendor, so here is the picture across both kinds of tests.

On CRM Bench, which is Salesforce’s own suite of real CRM actions, Koa matches or exceeds the leading general models while making roughly a third of the errors. On public benchmarks reported independently, Salesforce Koa lands ahead of several well-known general models on multi-turn tool use while sitting clearly below the top frontier models on raw capability. Both results can be true at the same time, and together they describe a specialist: strong inside its domain, ordinary outside it.

The practical question for a business is not which model is smarter in the abstract. It is which model makes fewer mistakes on the twenty tasks your agents repeat hundreds of times a week, and at what cost per task. A model that mis-routes one case in two hundred instead of one in seventy changes your escalation volume, and that shows up in staffing before it shows up in any benchmark chart.

It also matters where the model runs. Salesforce Koa is hosted inside Salesforce’s infrastructure with a serving layer that adds trust and safety controls on top of the model itself. For regulated industries, Salesforce and NVIDIA are extending the same approach to Missionforce and environments like private clouds, where the organization keeps control over the model, data and deployment. If your security team has been the reason your agent project is stuck, these are the paragraphs of the announcement to forward to them.

What to do this quarter if you run Agentforce

Salesforce Koa does not change what makes agent projects succeed. It changes one input, the model, and leaves the rest of the work where it always was. Between now and general availability, three moves make sense.

First, inventory your agents by task type. Mark the high-volume, well-defined workflows (case routing, follow-up scheduling, record updates) separately from the open-ended ones (research, drafting, judgment calls). The first group is Koa’s territory; the second will probably stay on frontier models. Having this split written down turns the GA announcement into a one-day decision instead of a quarter-long debate.

Second, baseline your current error rates and credit consumption per agent. You cannot tell whether a new model is an improvement if you never measured the old one. Even a simple weekly count of wrong answers, escalations and credits burned gives you the comparison you will need.

Third, clean the data your agents read. Every reasoning model, Koa included, answers from the records in front of it. Duplicate accounts, stale pricing in knowledge articles and orphaned contacts produce confident nonsense from the best model on the market. This is unglamorous work, and it is the single highest-leverage preparation for any model you choose.

Frequently asked questions

What is Salesforce Koa?

Koa is Salesforce’s first CRM reasoning model for Agentforce, built with NVIDIA on the Nemotron 3 Super model and trained on synthetic scenarios modeled on 27 years of CRM workflows. It is designed to reason through multi-step CRM tasks and pick the right tools along the way.

Is Koa better than GPT or other frontier models for Agentforce?

It depends on the task. Salesforce reports Koa matches or exceeds leading models on CRM-specific actions with about 3x fewer errors, while independent benchmarks place it below top frontier models on general tasks. Specialized work favors Koa; unusual or open-ended work still favors frontier models.

How much does Salesforce Koa cost?

Salesforce has not published Koa pricing yet, and the context window and latency figures are also unannounced. Pricing will likely sit inside Agentforce consumption, and it is the number to wait for before planning a switch.

Do I need Data 360 to use Koa?

Koa can be selected as a managed LLM in the Data 360 (formerly Data Cloud) generative models catalogue, but it is also available org-wide as a model provider in Agentforce Setup and at the individual agent level. You do not need to adopt the whole data platform just to try the model.

When will Koa be generally available?

Salesforce expects general availability in Winter 2026, starting in US regions. It is currently with select pilot customers, including 1-800Accountant, Formula 1, UChicago Medicine and Xero.

Was customer data used to train Koa?

No. Salesforce states the training corpus was entirely synthetic, built to reflect CRM reasoning and tool use, and that no customer data was used. The model also runs inside Salesforce’s own infrastructure rather than calling an external provider.

Sources

Categories
Agentforce Salesforce

Data Cloud vs Data 360: What Actually Changed in 2026

Last updated: October 26, 2026

If you run Salesforce, you woke up one morning to find Data Cloud had a new name. Data Cloud vs Data 360 is the question every admin and RevOps lead started asking, and the honest first answer is that it is the same product with a new name and a changed center of gravity. The deeper answer, the one that matters for your roadmap, is that the rename signals a shift in what Salesforce expects you to do with your data.

We work on Salesforce data projects every week, so here is the plain version of the Data Cloud vs Data 360 change: what changed, what did not, and what, if anything, you need to do about it.

Data Cloud vs Data 360: the short answer

Data 360 is the new name for Salesforce Data Cloud. Salesforce announced it at Dreamforce in October 2025, and it is available globally. Nothing you built in Data Cloud breaks, and you do not need to reimplement anything. Your data streams, data model objects, identity resolution rules and segments carry over as they are.

If that were the whole story, it would not be worth an article. The reason the Data Cloud vs Data 360 change matters is that it is the sixth name this product has carried, and each rename has marked a change in purpose. This one moves the product from a place where data is stored and queried to a place where data acts.

Data Cloud vs Data 360 at a glance

AreaData Cloud (before)Data 360 (now)
NameSalesforce Data CloudData 360, announced at Dreamforce in October 2025, available globally
Your implementationAs builtCarries over as is, no reimplementation or forced migration
Data streams, model, identity resolution, segmentsIn placeUnchanged
Pricing and licensingExisting contractsUnchanged, as far as Salesforce has said
Center of gravityData you store, query and report onData that acts: feeds agents and workflows in real time
Headline additionsNot availableIntelligent Context, Tableau Semantics, Real-Time Pipelines, Data 360 Lakehouse

Six names, one product: how we got to Data 360

The lineage helps explain the latest Data Cloud vs Data 360 rename. This product has been, in order, Customer 360 Audiences, Salesforce CDP, Marketing Cloud Customer Data Platform, Salesforce Genie, Salesforce Data Cloud, and now Data 360. Each name reflected what Salesforce wanted the product to be at the time, from a marketing data platform to a real-time data engine.

Data 360 is positioned as the data layer for the wider Agentforce 360 framework, as SalesforceBen reported from Dreamforce. In other words, the rename is less about data storage and more about feeding Salesforce’s AI agents the clean, real-time context they need to act. That framing got more concrete when Salesforce announced Koa, its CRM reasoning model for Agentforce, which reads the data this platform unifies.

The six names of Salesforce Data 360 from Customer 360 Audiences to Data 360

What actually changed beyond the name

The Data Cloud vs Data 360 rename came with a set of capabilities that are worth knowing, whether they are brand new or evolutions of existing features. The practical theme across all of them is activation: moving data from something you report on to something that drives agents and workflows in real time.

  • Intelligent Context. Links structured CRM records with unstructured sources such as emails, PDFs and call transcripts, so an agent can reason over a support history or a contract, not just fields.
  • Tableau Semantics. Shared business definitions so a metric like active customer reads the same across clouds and apps, built on the Customer 360 Semantic Data Model.
  • Real-Time Pipelines. Faster ingestion and harmonization across Salesforce clouds and external platforms.
  • Data 360 Lakehouse. A single architecture for live and historical data, rather than separate stores.
  • Einstein Context Index. A vector database that gives agents contextual search across your organization’s data.

If you strip the branding away, the direction is clear. Salesforce wants your data ready to feed agents the moment they need it, which is exactly what an Agentforce implementation depends on.

What did not change

This is the part that saves you a panic. In the Data Cloud vs Data 360 shift, the following did not change: your existing implementation, your data model, your connected sources, your identity resolution, and, as far as Salesforce has said, your pricing and licensing. There was no forced migration and no re-architecture. If you are live on Data Cloud today, you are live on Data 360 today, under a new label.

Data Cloud versus Data 360 what changed and what stayed the same

Free Salesforce implementation checklist

Moving onto Data 360 starts with the same groundwork as any rollout. These are the steps we check on every Salesforce project, from scoping and data to go-live.

Get the free implementation checklist

Free Salesforce implementation checklist

Moving onto Data 360 starts with the same groundwork as any rollout. These are the steps we check on every Salesforce project, from scoping and data to go-live.

Get the free implementation checklist

What you should actually do about it

The Data Cloud vs Data 360 rename itself is a no-op for your operations. The opportunity is in the shift it signals. Here is the short list we give clients.

  1. Do not reimplement. There is no migration project here. Anyone selling you a Data 360 migration is selling you a rename.
  2. Audit your data quality first. Activation only helps if the data feeding your agents is clean. Duplicates, stale records and gaps become visible fast once an agent is acting on them.
  3. Map one activation use case. Pick one place where real-time data could drive an action, for example an agent that reads a customer’s full history before replying, and prove it before expanding.
  4. Connect it to your AI roadmap. Teams that link Data 360 to Agentforce and Einstein early get the advantage. The data layer and the agent layer are now designed to work together.

If you are weighing how Data 360 should feed your agents, our Salesforce Agentforce consulting team can map the data-to-agent path for your specific setup.

Where this leaves you

Data Cloud vs Data 360 is, on the surface, a rename, and you can treat the label change as a non-event. Underneath, the Data Cloud vs Data 360 shift is Salesforce telling you where the platform is going: data that acts, not just data that reports. The teams that read the rename as a prompt to get their data clean and wired into their agents will be the ones who get value from the next wave of Salesforce AI. The teams that treat it as a migration project will waste money on work that does not exist.

Does the Data Cloud vs Data 360 rename change the build-vs-buy question?

A fair question we hear from technical leads in the Data Cloud vs Data 360 debate: if Data 360 is really about activating data for agents, does that change whether you should centralize on Salesforce or keep a separate warehouse or customer data platform? The short answer is that it sharpens the trade-off rather than settling it.

If your agents live in Salesforce and need real-time context to act, keeping that data close to the agent, inside Data 360, removes a round trip and a sync lag that a separate platform introduces. The Data 360 Lakehouse and real-time pipelines exist precisely to make that activation fast.

On the other hand, if your analytics and data science already live in Snowflake, Databricks or BigQuery, you do not have to move them; Tableau Semantics and the partner integrations are designed so Data 360 can share definitions with those platforms rather than replace them.

The Data Cloud vs Data 360 rename does not force a consolidation. It makes the case that the data feeding your agents should be fast and governed, wherever the rest of your stack sits.

Is your data ready for Data 360 activation? A quick check

Because the Data Cloud vs Data 360 shift pushes data from reporting into action, the quality bar goes up. A dashboard can tolerate a few duplicate records; an agent acting on them cannot. Before you lean into the activation story, run this short readiness check.

  • Duplicates. Do you have a working identity resolution and dedupe process, or are the same customers represented several times?
  • Freshness. How old is the data an agent would read? Real-time activation is only as good as your slowest pipeline.
  • Coverage. Are the unstructured sources an agent needs, such as emails and documents, actually connected, or only your structured CRM fields?
  • Definitions. Does active customer or churn risk mean the same thing across teams, or will Tableau Semantics be reconciling conflicting definitions?
  • Governance. Who owns access and retention once an agent, not just a report, is reading this data?

If most of those answers are shaky, that is your real project, and it has nothing to do with the rename. It is the groundwork that makes the Data Cloud vs Data 360 activation shift pay off.

Data Cloud vs Data 360 frequently asked questions

Is Data 360 the same as Data Cloud?

Yes. Data 360 is the new name for Salesforce Data Cloud, announced at Dreamforce in October 2025. It is the same product with a new name and a sharper focus on feeding real-time data to AI agents.

Do I need to migrate from Data Cloud to Data 360?

No. There is no migration. Your existing Data Cloud implementation, data model, connected sources and identity resolution carry over unchanged. Anyone proposing a Data 360 migration project is charging you for a rename.

Did pricing change with Data 360?

Salesforce did not announce any pricing or licensing change with the rename. If your contract or consumption changes, that would come separately from the renaming, so check your own agreement rather than assuming the new name carries a new price.

What is actually new in Data 360?

The capabilities highlighted alongside the rename include Intelligent Context for working with unstructured content, Tableau Semantics for consistent metrics, real-time pipelines, the Data 360 Lakehouse architecture, and the Einstein Context Index vector database for agent search. The common theme is activating data for AI agents in real time.

How does Data 360 relate to Agentforce?

Data 360 is the data layer of the wider Agentforce 360 framework. It supplies the clean, real-time context that Salesforce AI agents need to reason and act, which is why data quality matters more once you start building agents.

Categories
Agentforce Salesforce

Agentforce Implementation: Cost, Timeline and Readiness (2026)

Most teams come to Agentforce implementation expecting a switch they can flip. The demo takes ten minutes, the agent answers a question, and it feels close to done. Then the project meets real data, real permissions and real edge cases, and the ten-minute demo turns into a multi-month program.

We build on Salesforce every week, and the pattern is consistent: the gap between a working demo and a production agent is almost never the AI. It is the data the agent reads, the actions it is allowed to take, and the cost of every action once real volume hits. This guide walks through what an Agentforce implementation actually involves in 2026, what it costs, how long it takes, and how to tell whether your org is ready before you spend anything.

Agentforce demo versus production implementation comparison

What Agentforce implementation actually means

Agentforce is Salesforce’s platform for building autonomous AI agents that sit on top of your CRM. An agent reads data, decides what to do, and takes actions, for example looking up an order, drafting a reply, updating a case, or escalating to a human.

An implementation is the work of getting one or more of these agents from idea to production. It is not a single task. It is a sequence: deciding what the agent should do, cleaning the data it will rely on, defining the actions it is allowed to perform, testing it against real scenarios, and watching the cost once it goes live.

One point that trips up buyers: Agentforce sits on an existing Salesforce foundation. For service agents that usually means Service Cloud, and recent editions require a capable tier underneath. So the Agentforce cost is an addition on top of your platform license, not a standalone price. Budget for both.

The five phases of an Agentforce implementation

Across projects, a realistic Agentforce implementation moves through five phases. The phase names vary by partner, but the Agentforce implementation work itself does not.

Phase 1: Use case and scoping (about 1 week)

Pick one agent and one job. The teams that struggle are the ones who try to make an agent do everything in version one. The teams that succeed pick a single, high-volume, low-risk task, order status lookups, password resets, appointment scheduling, and prove it before adding scope.

Phase 2: Data readiness (the phase that decides your timeline)

This is where most timeline overruns begin. An agent is only as good as the data it reads. If your knowledge articles are stale, your records are duplicated, or your data is scattered across systems that were never connected, the agent inherits all of it. Deduplicating records, refreshing knowledge, and connecting sources is unglamorous work, and it is the single biggest driver of how long the project takes. If your org already runs Data Cloud, start by reading what the Data 360 rename actually changed, because the new activation features decide how much of this phase you can skip.

Phase 3: Agent configuration (1 to 2 weeks)

This is the part that looks like the demo. You define the agent’s topics, the actions it can take, and the guardrails around them. The work here is less about building and more about restraint, giving the agent exactly the actions it needs and no more, because every extra action is both a risk and a cost.

Phase 4: Testing and guardrails

A production agent needs to be tested against the messy real world, not the happy path. What happens when the customer asks something off-topic? When the data is missing? When the agent is about to take an action it should not? This phase is where a safe agent is separated from a liability.

Phase 5: Launch, monitoring and cost control

Going live is the start, not the finish. Once real volume hits, you watch two things: whether the agent is actually resolving interactions, and what each interaction is costing you. We will come back to that cost, because it is where budgets quietly break.

The five phases of an Agentforce implementation timeline

How long does an Agentforce implementation take?

Here is where an Agentforce implementation forces you to ignore the headline and read the benchmarks.

Salesforce and some partners point to a quick start, and it is true that a basic agent using prebuilt templates can be stood up in days. That is a pilot, not a production rollout.

For a realistic production timeline, independent reporting across many deployments lands in a wide band:

  • A first agent on reasonably clean data: roughly 6 to 8 weeks
  • An enterprise multi-agent program with data harmonization and legacy integration: 12 to 16 weeks
  • At full enterprise scale, third-party analysis has pegged the realistic range at 22 to 44 weeks, or about 5.5 to 11 months, and reported that fewer than 10 percent of customers have scaled it fully

The spread in Agentforce implementation timelines is not because the software is slow. It is because phase 2, your data, varies enormously from one company to the next. A team with clean, connected data moves fast. A team with years of messy records does not.

How much does Agentforce implementation cost?

An Agentforce implementation has two separate costs, and buyers routinely confuse them: the running cost of the agent, and the one-time cost of implementing it.

The running cost: Flex Credits and the models

As of the Salesforce Agentforce pricing page checked in September and October 2026, Salesforce runs several meters at once. For a full breakdown, see our guide to Agentforce pricing. On the model side, Salesforce Koa, the new CRM reasoning model, gives agents a Salesforce-hosted option; which model each agent runs on will shape both error rates and credit burn. In short:

  • Flex Credits: 500 US dollars per 100,000 credits. A standard action consumes 20 credits, so about 0.10 US dollars per action. A voice action is 30 credits, about 0.15 US dollars.
  • Per conversation: 2 US dollars per conversation, regardless of how many actions it triggers.
  • Per resolution (Help Agent): 2 US dollars per resolved conversation, or 400 credits.
  • Per user and editions: the newer Core, Advanced and Max editions run from about 195 to 550 US dollars per user per month, bundling large annual credit pools.

The number almost nobody measures before signing: Flex Credits and the flat 2 dollar conversation model break even at about 20 actions per conversation. Below 20 actions, credits are cheaper. Above 20, the flat conversation model wins. Salesforce’s own example puts a typical exchange at 3 to 6 actions, or about 0.30 to 0.60 US dollars on credits versus 2 dollars flat, so for most well-designed agents, credits are the cheaper meter.

This is why agent design is a cost decision, not just a capability decision. An agent that fires 15 actions where 5 would do nearly triples your bill on the same volume.

For a deeper breakdown of every pricing meter, see the SalesforceBen guide to Agentforce pricing.

Agentforce Flex Credits versus per-conversation pricing break-even chart

The implementation cost

The one-time cost of getting to production depends almost entirely on your data and complexity. Independent benchmarks across the market in 2026 put partner implementation somewhere in the range of about 35,000 to 150,000 US dollars for a mid-market deployment, with strategy and discovery often a separate line, and data preparation frequently the largest hidden cost. At enterprise scale with heavy integration, totals run far higher.

The honest takeaway: ask any partner for a combined total cost of ownership, license plus implementation plus data work plus ongoing credits, before you commit. A quote that covers only the license is the start of the number, not the number. The same discipline applies when you choose a Salesforce implementation partner for any project, not just Agentforce.

An Agentforce readiness checklist

Before you start an Agentforce implementation, run through this. If you cannot answer yes to most of it, fix that first.

  1. One clear use case. Can you name one high-volume, low-risk task the agent will own first?
  2. Clean, connected data. Are the records and knowledge the agent will read accurate and in one place, or do they need work?
  3. Defined actions. Do you know exactly which actions the agent should and should not be able to take?
  4. A cost baseline. Have you estimated the average actions per interaction and modeled it against your worst-case volume?
  5. A human escape hatch. Is there a clean path for the agent to hand off to a person when it should?
  6. An owner. Who watches the agent after launch, both its resolution rate and its credit burn?

A red flag worth remembering: any partner who quotes you an agent build without first insisting on a data readiness assessment is skipping the phase that decides whether the project succeeds.

Where this leaves a buying decision

Agentforce can genuinely take work off a team’s plate. The implementations that deliver that are the ones built on a clear use case, clean data, a tightly designed set of actions, and a cost model someone is actually watching. The ones that disappoint are almost always the ones that treated the Agentforce implementation as a demo that scaled itself.

If you are weighing an Agentforce implementation and want a straight answer on readiness, cost, and timeline for your specific setup, our team offers a Salesforce Agentforce consulting assessment worth doing before anyone talks about a contract.

Frequently asked questions

How long does an Agentforce implementation take?

A first agent on reasonably clean data typically takes 6 to 8 weeks. An enterprise multi-agent program runs 12 to 16 weeks, and third-party analysis puts full enterprise scale at 22 to 44 weeks, about 5.5 to 11 months. The variable that decides it is your data readiness.

How much does Agentforce cost?

Running cost: Flex Credits are 500 US dollars per 100,000 credits, about 0.10 US dollars per action; the per-conversation model is 2 US dollars; the Help Agent resolution model is 2 US dollars per resolved conversation; and the Core, Advanced and Max editions run from about 195 to 550 US dollars per user per month. On top of that, partner implementation for a mid-market deployment is commonly in the 35,000 to 150,000 US dollars range.

Do I need Service Cloud for Agentforce?

Agentforce sits on an existing Salesforce foundation. For service agents that usually means a capable Service Cloud tier underneath, so the Agentforce cost is added on top of your platform license rather than replacing it.

What is the biggest hidden cost in an Agentforce implementation?

Data preparation. Deduplicating records, refreshing knowledge and connecting sources is the single biggest driver of timeline and cost, and it is frequently larger than the agent configuration itself. A poorly designed agent that fires too many actions is the second hidden cost, because every extra action adds to the bill.

Flex Credits or per-conversation pricing: which is cheaper?

They break even at about 20 actions per conversation. Below 20 actions, Flex Credits are cheaper; above 20, the flat 2 dollar conversation model is cheaper. Since most well-designed agents fire only 3 to 6 actions, credits usually win.

Categories
Salesforce

Salesforce Braze Acquisition: What the $5.66B Deal Means for Marketing Cloud Teams

Last updated: October 21, 2026

The Salesforce Braze acquisition landed on October 20, 2026, and my inbox has not been quiet since. Salesforce agreed to buy Braze for about $5.66 billion, paying $47.50 a share in cash. If you run Marketing Cloud, use Braze, or pay for both, you probably have the same question everyone is asking: what actually changes for us, and when?

Short answer: nothing changes this quarter. The deal still has to close, and Salesforce has not shared a combined roadmap yet. But there is a lot you can learn from the announcement itself, and a few smart moves you can make now while everyone else waits for the press cycle to settle.

A quick note on where we’re coming from. Ashapura Softech is a Salesforce partner, and our team works on Marketing Cloud and Data Cloud (now Data 360) projects for US companies. So yes, we have a view. Everything below is our read of public information, not an official Salesforce position, and every number links back to its source.

In this article

  1. The Salesforce Braze acquisition in numbers
  2. What is Braze, and why did Salesforce want it?
  3. Where Braze fits in the Salesforce stack
  4. Braze vs Salesforce Marketing Cloud
  5. What the deal means for you
  6. Three scenarios for real companies
  7. The bigger picture: Salesforce’s 2026 buying spree
  8. Timeline: what happens next
  9. A 90-day checklist
  10. Our take
  11. FAQs

The Salesforce Braze Acquisition in Numbers

Salesforce signed the merger agreement on October 19, 2026 and announced the Salesforce Braze acquisition the next morning. It’s Salesforce’s biggest marketing bet since the ExactTarget deal that created Marketing Cloud. Some early social posts got the numbers wrong, so here are the facts straight from the filings.

Salesforce Braze acquisition at a glance: $5.66B value, $47.50 per share, 58% premium, FY2028 close
The Salesforce Braze deal at a glance. Sources: Salesforce, Reuters, SEC filings.
DetailWhat was announced
Deal valueAbout $5.66 billion in enterprise value
Price per share$47.50 in cash for Braze Class A stockholders
PremiumRoughly 58% over Braze’s October 19 close
Braze customersAbout 2,770, including Canva, Dairy Queen, Instacart and Venmo
Expected closeSalesforce fiscal 2028, pending Braze shareholder and regulatory approval
Break fees$300 million if Salesforce walks away, $191.4 million if Braze does
Guidance impactSalesforce says its fiscal 2027 guidance does not change

One number tells you how serious this is. When Salesforce bought ExactTarget back in 2013, the company that became the core of Marketing Cloud, it paid about $2.5 billion. Braze costs more than twice that. Salesforce is not buying a feature here. It’s buying a new engine for its marketing business.

What Is Braze, and Why Did Salesforce Want It?

Braze in plain English

Braze is a customer engagement platform founded in 2011 and based in New York. It helps brands send the right message at the right moment, across mobile push, in-app messages, web, email, SMS and WhatsApp. The key word is moment. Braze is built on an event-streaming setup, so it reacts to what a customer is doing right now, not what they did in last night’s batch file.

Think of a food delivery app. You add three items to your cart, get distracted and close the app. Ten minutes later you get a nudge with a small offer. That kind of live, behavior-triggered message is what Braze does very well, and it’s why mobile-first brands like Instacart and Venmo use it.

The business is healthy, too. In its fiscal second quarter of 2027 (ended July 31, 2026), Braze reported $227.2 million in revenue, up 26.2% year over year, and 361 customers paying $500,000 or more a year.

The gap it fills in Marketing Cloud

Marketing Cloud is excellent at email journeys and deep CRM data. Real-time app engagement has always been its weaker side, and analysts have said so openly. One analyst quoted by Reuters described Braze as a real-time engagement layer that Salesforce’s marketing business never really had.

Salesforce’s own announcement points the same way. It says Braze will strengthen Marketing Cloud’s cross-channel personalization inside Customer 360, and that Braze’s AI decisioning will help pick the content, offer, channel and timing for each person.

Where Braze Fits in the Salesforce Stack

Salesforce now talks about its platform in layers: Data 360 at the bottom, Customer 360 apps on top of that, Agentforce for AI agents, and SIForce. Braze is expected to plug into the engagement layer, sitting next to Marketing Cloud and reading from the same customer data. The Salesforce Braze acquisition makes a lot more sense once you see that map.

Where Braze fits in the Salesforce stack with Data 360, Customer 360, Agentforce and Marketing Cloud
Where Braze is expected to sit in the Salesforce stack.

If that works the way Salesforce describes, you’d get something many teams have wanted for years. A sales or service event in Salesforce could trigger an in-app message within seconds, and an Agentforce agent could pick up the conversation later with full context. Right now, most teams stitch that together with connectors, custom code and a fair amount of hope.

That’s also why getting your Data Cloud foundation right matters so much here. Real-time engagement on top of messy data just sends the wrong message faster.

Braze vs Salesforce Marketing Cloud: Overlap and Differences

One of the most searched questions since the Salesforce Braze acquisition news broke is whether Braze is better than Salesforce. Honestly, it’s the wrong question. They grew up solving different problems, and the overlap is narrower than the headlines suggest.

Braze vs Salesforce Marketing Cloud comparison of data approach, channels, customers and AI
Braze vs Salesforce Marketing Cloud, before any integration.

Here is how we’d sum it up:

  • Braze shines when your customer lives in a mobile app and you need to react in real time. It’s also comfortable working with data that sits in an outside warehouse.
  • Salesforce Marketing Cloud shines when your marketing is tied closely to CRM data, sales and service records, and big email programs.
  • The overlap sits in journey orchestration, mobile messaging and AI personalization. That’s where you should expect product decisions over the next year.

If you want a refresher on what Marketing Cloud includes today, our complete Marketing Cloud guide walks through each part.

What the Salesforce Braze Acquisition Means for You

Your next steps depend on which side of the deal you’re on. Here’s how we’re advising teams right now.

If you run Marketing Cloud today

Don’t panic, and don’t rip anything out. Your contract, your journeys and your data all keep working. What you should do is ask your Salesforce account executive for anything in writing about roadmap and pricing before your next renewal. Then make a short list of journeys where you wish you had real-time app triggers. That list will be very useful once Salesforce shares how Braze will be packaged.

If you’re a Braze customer

Braze CEO Bill Magnuson has said Braze will keep building as Braze, and that’s a good sign. Still, get the practical things in writing: pricing at renewal, support levels and how your data can move if you ever leave. This matters most if your customer data lives in Snowflake, BigQuery or another warehouse outside Salesforce. Both companies talk about being open and composable. That promise is real today, but it hasn’t been tested through an integration yet.

If you already use both

Plenty of companies already run Braze next to Salesforce CRM, usually with a Braze to Salesforce connector keeping data in sync. Document exactly what that sync does today: which objects, which direction and how often. When the products start to merge, that document saves you weeks. It’s also worth checking whether both tools are messaging the same customer about the same thing. That happens more often than people admit.

Three Scenarios: How the Salesforce Braze Acquisition Could Play Out

The deal will land differently for every company, so here is how we picture it for three very different setups. These are examples we built from common setups, not announced features.

1. A retail brand with a big shopping app

Picture a US apparel retailer with an app, a loyalty program and Commerce Cloud on the back end. Today, its email team lives in Marketing Cloud while the app team runs push and in-app messages in a separate tool. The cart reminder email lands an hour after the push message, often with a different offer. Customers notice.

If Braze ends up wired into the same customer profile as Commerce Cloud and Marketing Cloud, that retailer could run one journey: the app event fires, the customer gets one message on the right channel, and the loyalty points shown are correct. That’s the dream version. Getting there still depends on clean product, order and loyalty data.

2. A fintech app that already uses Braze

Now take a fintech startup that chose Braze years ago and keeps its data in Snowflake. It uses Salesforce only for sales and support. For this team, the Salesforce Braze acquisition raises a fair worry: will Braze slowly start to favor Salesforce data over everything else?

Our advice here is simple. Keep building on Braze the way you do now, but write down every data source that feeds it and ask for written commitments on warehouse support at your next renewal. If the open approach holds, nothing changes for you. If it doesn’t, you’ll know early and have options.

3. A B2B company that only uses email

Plenty of B2B companies run Marketing Cloud or Account Engagement purely for email nurture and events. They don’t have a consumer app at all. For them, Braze may matter less in the short term. The bigger impact could come later, through AI decisioning that picks send times and content inside Salesforce journeys.

For this group, the smartest move is the least exciting one: tidy up lead and contact data, fix consent tracking and make sure Sales Cloud and Marketing Cloud agree on who a customer actually is. Whatever Salesforce builds next will read from that data.

The common thread across all three? The companies that get value fastest are the ones whose data is already in good shape. That’s not a Braze problem or a Salesforce problem. It’s a homework problem, and the good news is you can start on it today.

The Bigger Picture: Salesforce’s 2026 Buying Spree

Braze isn’t a one-off. Since 2025, Salesforce has agreed to buy Informatica for about $8 billion, closed a $3.6 billion deal for Fin on September 10, signed a deal for AI customer research company Listen Labs, and agreed to add AI analytics startup Loops to Tableau. Read together, the pattern is clear. Salesforce wants to own the data, the AI agents and now the moment of engagement itself.

There’s a defensive angle, too. Investors have been worried that AI agents could eat into traditional software spending. Buying companies with strong growth and real AI use cases is one way to answer that. If you’ve been following the Dreamforce ’26 news, our post on what AIforce is and our breakdown of Agentforce’s named agents fill in the rest of that story.

Timeline: What Happens Next

  • October 19, 2026: Merger agreement signed.
  • October 20, 2026: Deal announced. Braze shares jumped more than 50% that day.
  • Coming months: Braze shareholder vote and regulatory reviews.
  • Salesforce fiscal 2028 (February 2027 to January 2028): Expected close, if approvals come through.

Until the Salesforce Braze acquisition closes, Braze and Salesforce operate as separate companies. That means no shared roadmap, no merged pricing and no joint product for a while. Anyone selling you a “Braze plus Marketing Cloud bundle” today is guessing.

A 90-Day Checklist While the Deal Closes

Here’s the practical part. None of these steps depend on the final shape of the Salesforce Braze acquisition, so you can start this week.

Salesforce Braze acquisition 90 day checklist and deal timeline for Marketing Cloud and Braze customers
A 90-day checklist and the deal timeline.
  1. Audit your CRM data. Duplicates, stale contacts and missing consent flags will hurt any real-time tool. Our CRM health check template is a free place to start.
  2. Map your journeys. Mark which ones are email-led and which ones need app or in-app triggers.
  3. Write down your data flows. Know what lives in Salesforce, what lives in a warehouse and what moves between them.
  4. Get renewal terms in writing. Roadmap, pricing caps and data portability for both tools.
  5. Set agent guardrails. Decide who approves AI-generated messages and what frequency limits apply, before agentic features land in your stack.

Free PDF guide

Salesforce Is Buying Braze: Your 90-Day Plan

A 10-page summary of this article with the deal numbers, three scenarios, the timeline and the 90-day checklist. Easy to share with your team.

Download the PDF

Our Take

We think the Salesforce Braze acquisition is a good deal for Salesforce customers, with one big condition: integration has to be done well. Salesforce has a mixed record here. ExactTarget became the base of Marketing Cloud, while some later acquisitions took years to feel like one product.

The teams that will benefit first won’t be the ones with the biggest budgets. They’ll be the ones that walk into 2027 with clean data, clear journeys and a short list of real-time use cases ready to go. That work is worth doing anyway, even if this deal took a different turn tomorrow.

If you’d like a second pair of eyes on your Marketing Cloud setup or a Braze plus Salesforce data flow, talk to our Salesforce team. We’re happy to tell you honestly whether you need to change anything right now. Often the answer is no.

Frequently Asked Questions

When did Salesforce announce the Braze acquisition?

Salesforce announced the deal on October 20, 2026. The merger agreement itself is dated October 19, 2026.

How much is Salesforce paying for Braze?

About $5.66 billion in enterprise value. Braze Class A stockholders will receive $47.50 per share in cash, roughly a 58% premium to the stock’s last close before the news.

When will the Salesforce Braze acquisition close?

Salesforce expects it to close during its fiscal 2028, which runs from February 2027 to January 2028. It needs Braze shareholder approval and regulatory clearance first.

Is Braze a CRM?

No. Braze is a customer engagement platform. It sends messages based on customer behavior, while a CRM like Salesforce stores and manages the customer relationship, sales and service data. Many companies use the two together.

Does Braze compete with Salesforce Marketing Cloud?

Partly. Both handle cross-channel campaigns and customer journeys. Braze is stronger in real-time and mobile engagement, while Marketing Cloud is stronger in email and CRM-connected marketing. After the deal closes, Salesforce plans to use Braze to strengthen Marketing Cloud.

Will Marketing Cloud pricing change because of the deal?

Salesforce has not announced any pricing or packaging changes. Until it does, base renewal decisions on your current contract and ask your account team for written commitments.

What happens to the Braze to Salesforce connector?

Nothing has been announced that changes it. The two companies operate separately until the deal closes, so existing connectors and integrations should keep working as they do today.

Sources

Categories
Agentforce Salesforce

Salesforce MCP Server: 4 Ways to Connect Claude, ChatGPT and Codex to Salesforce (2026)

Last updated: October 19, 2026

Short answer: A Salesforce MCP server lets AI tools such as Claude, ChatGPT, Codex and Cursor read and update Salesforce through the open Model Context Protocol, using each person’s own Salesforce permissions. In 2026 there are four practical routes: Salesforce Hosted MCP Servers for business users and admins, the Salesforce DX MCP Server for developers, packaged plugins such as Salesforce in Claude and the Salesforce plugin for ChatGPT, and Agentforce exchanging tools with other systems over MCP. Start with a read-only server, a small pilot group and a sandbox, and budget for Flex Credits before you switch anything on in production.

Six months ago, connecting an AI assistant to Salesforce meant a custom integration, a middleware project or a lot of copy and paste. Now Salesforce runs MCP servers for you, Anthropic and OpenAI ship Salesforce plugins, and your developers can point Claude Code or Codex at an org with one command. Search interest in “Salesforce MCP server” has followed, and so have the questions we get from US clients: which option is right, is it safe, and what does it cost?

This guide answers those questions in plain terms. We checked Salesforce’s developer documentation, the Summer ’26 release guide and recent coverage on October 19, 2026, and we flag where details are still unclear or come from third parties rather than Salesforce.

What is a Salesforce MCP server?

MCP, the Model Context Protocol, is an open standard that lets an AI application call tools and read data in another system. Think of it as a universal adapter: instead of building a separate integration for every AI tool, a system exposes an MCP server once, and any MCP-compatible client can use it.

A Salesforce MCP server exposes Salesforce records, Flows, Apex actions and other capabilities as MCP “tools”. When you ask Claude or ChatGPT to “show my open opportunities over $50,000 closing this quarter” or “log a follow-up task on Acme”, the assistant calls those tools on your behalf. The important part for admins: on Salesforce’s own servers, every call runs as the signed-in user, so field-level security, sharing rules and permission sets still apply.

4 ways to connect Claude, ChatGPT and Codex to Salesforce in 2026

These options overlap, and many companies will end up using more than one. The table is the quick version. The sections below explain each one.

OptionBest forWhere it runsStatus (Oct 2026)Cost
Salesforce Hosted MCP ServersBusiness users and admins connecting Claude, ChatGPT, Cursor or a custom agent to live CRM dataSalesforce-managed infrastructure, connected over OAuthStandard servers GA in Summer ’26Flex Credits usage
Salesforce DX MCP ServerDevelopers using Claude Code, Codex, Cursor or VS Code with CopilotOn the developer’s machine (npx), against locally authorized orgsLabeled Beta in the Summer ’26 developer guide; individual tools marked GA or non-GAFree, open source
Packaged plugins (Salesforce in Claude, Salesforce plugin for ChatGPT)Sales teams who want ready-made workflows instead of raw toolsInside Claude or ChatGPT, connected by your Salesforce adminSalesforce in Claude in beta; ChatGPT plugin available per Salesforce BenRequires paid AI plans; Salesforce terms per agreement
Agentforce and MCPCompanies building agents that call external tools, or exposing agents to other AI toolsAgentforce, AgentExchange MCP listings, MuleSoftVaries by featureAgentforce consumption

1. Salesforce Hosted MCP Servers

This is the option most business teams will care about. Salesforce hosts the MCP servers, so there is no local server or middleware to maintain. According to Salesforce’s documentation, any MCP-compatible client can connect, and the page names Claude, ChatGPT, Cursor, Postman and custom agents. Salesforce’s Summer ’26 developer guide states that the hosted standard MCP servers are now generally available.

What you can expose:

  • SObject operations. Read, create, update and delete records, respecting field-level security and sharing rules.
  • Custom tools. Apex invocable actions, @AuraEnabled methods, Apex REST methods, Flows and Named Queries.
  • Product integrations. Data 360 SQL queries, Tableau analytics and other products.
  • Prompt templates. Prompt Builder templates that users can call from their AI client.

Standard servers are switched off by default and are found in Setup under MCP Servers. Community walkthroughs describe three standard servers, one with broad read and write access, one read-only and one write-only. You can also build custom servers that combine standard tools with your own Flows and Apex. Salesforce says hosted MCP servers are intended for customers with Flex Credits and that usage may be billed. Third-party reviews report that the feature is available in Enterprise Edition and above. Confirm both points with your account executive for your own contract.

2. Salesforce DX MCP Server (for developers)

The Salesforce DX MCP Server is an open-source server, published on GitHub by the Salesforce CLI team, that runs on a developer’s machine with npx -y @salesforce/mcp. It works with Claude Code, Cursor, Cline, VS Code with Copilot, Windsurf, Zed and other clients. It groups its tools into toolsets such as orgs, data, metadata, testing, code-analysis, devops and lwc-experts, and Salesforce Ben reports that Codex gets access to more than 60 Salesforce developer tools through it.

Two details matter for safety. First, the server only works with orgs you have already authorized locally through the Salesforce CLI. Second, the required --orgs flag limits which of those orgs it can touch. Pass an explicit username or alias for a sandbox rather than ALLOW_ALL_ORGS, which the project itself warns to use with caution. By default only tools marked GA are enabled, and non-GA tools need an extra flag.

Salesforce MCP server setup: a developer connecting an AI coding assistant to a Salesforce sandbox
Point developer tools at a sandbox with an explicit org alias, never at every org on the machine.

3. Packaged plugins: Salesforce in Claude and the Salesforce plugin for ChatGPT

If your sales team wants results rather than raw tools, packaged plugins are the faster route. Salesforce in Claude was announced on August 26, 2026 as part of the expanded Salesforce and Anthropic partnership. It comes with 37 prebuilt sales skills for jobs such as meeting prep, deal health reviews, pipeline reviews and CRM updates. An admin makes the connection centrally and chooses who gets access, sellers sign in with their own Salesforce credentials, and by default Claude asks the seller to approve changes before writing them back. We covered the wider partnership in our guide to what Claudeforce is and how it compares in Claudeforce vs Agentforce.

On the OpenAI side, Salesforce Ben reports a Salesforce plugin for ChatGPT, formerly the Agentforce Sales app, which lets users read and edit accounts and opportunities, plus a Tableau plugin for querying Tableau data. Both respect existing user permissions.

4. Agentforce and MCP: the other direction

MCP is not only about outside assistants reaching into Salesforce. The Summer ’26 guide lists exposing Agentforce agents as MCP tools through hosted MCP servers, and Salesforce’s developer blog describes extending Agentforce with external MCP tools through MuleSoft. AgentExchange now lists MCP servers next to classic apps. Before you enable one, run the checks in our AgentExchange installation guide, because an MCP tool behaves more like a contractor than a package.

How to connect Claude to a Salesforce MCP server, step by step

This is the typical path for connecting Claude to Salesforce Hosted MCP Servers, based on Salesforce’s setup guide and published walkthroughs. Menu names can change between releases, so follow the current Salesforce documentation alongside it.

  1. Pick the server. In Setup, open MCP Servers and choose a standard server. Start with the read-only one for a pilot. Activate it and copy its server URL.
  2. Create an External Client App. In Setup, open External Client App Manager and create an app for your AI client. Enable OAuth, set the callback URL your AI client documents (for Claude, community guides show https://claude.ai/api/mcp/auth_callback), and add the scopes Salesforce’s guide lists for MCP access along with refresh tokens.
  3. Secure the app. Require PKCE. Set permitted users to admin-approved users and assign access through a permission set for your pilot group. Some walkthroughs suggest letting all users self-authorize and relaxing IP restrictions. We do not recommend that in production.
  4. Add the connector in Claude. In Claude, add a custom connector, paste the server URL, and enter the consumer key and secret from the External Client App.
  5. Sign in and test. Each user signs in with their own Salesforce login. Test with a user who should not see certain records and confirm they cannot.
  6. Widen slowly. Move to a read-write server or a custom server with specific Flows only after the pilot shows the answers and updates are right.

Security checklist before you switch on a Salesforce MCP server

Salesforce’s servers respect your security model. That is good news only if your security model is in good shape. Before go-live, we check:

  • Profiles and permission sets. Users with “View All Data” or broad admin rights will have the same reach through an AI assistant. Clean these up first.
  • Sharing rules and field-level security. Sensitive fields such as salary, health or financial data should be hidden from users who do not need them, in Salesforce itself.
  • Read before write. Start with a read-only server. Add write tools through specific Flows with validation rather than open record edits.
  • Who can connect. Use admin-approved users and a permission set, not self-authorization for everyone.
  • Developer tools on sandboxes. Lock the DX MCP Server to named sandbox orgs and keep deployments in your normal release process.
  • Logging and review. Decide who reviews what the assistants did during the first month, and how a connection gets switched off.
  • Data policy. Check your AI vendor’s data handling terms and your own customer contracts before connecting regulated data.

If you are not sure where your org stands, our free 30-point CRM health check includes a security and access section that covers most of this list.

Salesforce MCP server security review: a team checking permissions before connecting AI tools to Salesforce
Review profiles, permission sets and sharing before any AI tool gets a connection.

What a Salesforce MCP server costs

Hosted MCP Servers are tied to Flex Credits, Salesforce’s consumption currency, and Salesforce says usage may be billed. Salesforce has not published a simple per-call price on the documentation page we checked, so model the cost with your account executive using realistic volumes. A pilot of 20 sellers asking a few questions a day costs very differently from an always-on integration. Our Flex Credits explainer walks through how consumption pricing works. The DX MCP Server is free and open source, and AI plugins need paid plans from Anthropic or OpenAI.

Which Salesforce MCP option should you use?

  • Sales leaders who want quick wins: pilot Salesforce in Claude or the ChatGPT plugin with a small team, because the workflows are already built.
  • Admins who want control: use Hosted MCP Servers with a custom server that exposes only the Flows and objects you choose.
  • Developers: use the DX MCP Server against sandboxes for metadata, tests and code review.
  • Companies building agents: design Agentforce first, then decide which external MCP tools it needs and which agents to expose. Our Agentforce consulting team can help scope this.

What we see in our own Salesforce projects

On one US consumer electronics project, Service Cloud, CPQ and Agentforce handle 430,000 orders and 280,000 contacts, with 60% of cases deflected. At that scale, the main design decision was never which AI tool to connect. It was which user each agent and integration runs as, and what that user can see. On a B2B industrial supply project, the AI layer was only as good as the pricing data it could reach, which first meant moving contract rates out of spreadsheets and into Salesforce CPQ connected to Odoo ERP. These are results from specific projects, not promises. Read more in our consumer electronics case study and industrial supply case study.

Our rule for MCP is the same as for any integration: sandbox first, least-privilege users, read before write, and a named owner who reviews activity during the first month.

Frequently asked questions

What is a Salesforce MCP server?

It is a server that exposes Salesforce data and actions to AI tools through the open Model Context Protocol. AI clients such as Claude, ChatGPT, Cursor or Codex can then read and update Salesforce, with each call running under the signed-in user’s permissions on Salesforce’s own servers.

Is the Salesforce MCP server free?

The Salesforce DX MCP Server for developers is free and open source. Salesforce Hosted MCP Servers are intended for customers with Flex Credits, and Salesforce says usage may be billed. AI plugins also need paid plans from the AI vendor.

Can Claude or ChatGPT see all my Salesforce data?

Not on Salesforce’s hosted servers or official plugins. They work only with records the signed-in user can already access, so field-level security, sharing rules and permission sets still apply. That is why cleaning up broad permissions comes first.

Do I need a developer to set it up?

For Hosted MCP Servers, an admin can create the External Client App, activate a server and connect a client without code. Custom tools built on Apex or Flows, and the DX MCP Server, need developer or admin skills.

What is the difference between Hosted MCP Servers and the DX MCP Server?

Hosted MCP Servers run on Salesforce infrastructure and connect business users’ AI tools to live org data over OAuth. The DX MCP Server runs on a developer’s machine and gives coding assistants tools for metadata, testing and org management on locally authorized orgs.

Is it safe to connect AI tools to Salesforce?

It can be, if you start with a read-only server, limit who can connect, keep developer tools on sandboxes and review activity. The biggest risk is usually existing over-broad permissions, which an AI assistant will inherit.

Getting started

If you are planning a Salesforce MCP pilot, start with one team, one read-only server and one question you want answered faster. We help US companies plan permissions, build custom MCP tools on Flows and Apex, and model Flex Credits costs. See our Salesforce development services or talk to us about a short readiness review.

About the author. Ankur Pandey is Marketing Manager at Ashapura Softech, a Salesforce and Odoo consulting partner based in Irving, Texas, with a delivery center in Ahmedabad, India. He works with the company’s Salesforce delivery teams on CRM, Agentforce and integration projects for US businesses and writes about what Salesforce product changes mean in practice.

Disclosure: Ashapura Softech is a Salesforce consulting partner. We have no commercial relationship with Anthropic or OpenAI.

Sources

Categories
Salesforce

Agentforce Specialist Certification: 2026 Study Guide and 4-Week Plan

Last updated: October 19, 2026

Short answer: The Salesforce Certified Agentforce Specialist exam has 60 scored multiple-choice questions plus up to five unscored ones, a 105-minute time limit and a 72% passing score. Registration costs USD 200 and a retake costs USD 100, plus taxes. There are no prerequisites. The current outline is aligned to the Spring ’26 release and is weighted most heavily toward AI Agents (35%), with Prompt Engineering and Data 360 Fundamentals at 20% each. Plan on about four weeks of study with daily hands-on time in a free Developer Edition org.

US searches for the Agentforce Specialist exam rose about 60% over the past week on Google Trends, and admins we interview ask the same thing: what is on the test now, and how should I study? This guide answers that using the official exam guide and Trailhead pages we opened on October 19, 2026, plus trade press where Salesforce is silent.

Know this up front: the exam started as AI Specialist, became the Agentforce Specialist exam in March 2025, and has since been rewritten around Agent Script, Data 360 and multi-agent orchestration. Many online guides describe an older version, so we flag the differences.

Agentforce Specialist exam facts at a glance

This table comes from the official Salesforce Certified Agentforce Specialist Exam Guide on Salesforce Help.

ItemCurrent official detail
Official nameSalesforce Certified Agentforce Specialist (exam code AI-201 appears in the Trailhead Academy exam link)
Questions60 scored multiple-choice questions plus up to 5 unscored questions
Time105 minutes
Passing score72%
Registration feeUSD 200 (JPY 30,000), plus applicable taxes
Retake feeUSD 100 (JPY 15,000), plus applicable taxes
PrerequisitesNone. Salesforce recommends, but does not require, Platform Administrator and Platform App Builder
Release alignmentSpring ’26
DeliveryProctored, at a testing center or online. No reference materials allowed
LanguagesEnglish, French and Japanese
MaintenanceOne maintenance module on Trailhead each year. Miss the due date and the certification expires

A few conflicts you will run into:

  • Time limit. Salesforce’s original February 2025 announcement blog said 90 minutes. The current exam guide says 105 minutes. Go with the guide.
  • Passing score. A Salesforce Ben guide last updated in April 2026 lists 73%. The official guide we opened today says 72%.
  • Price. At the early 2025 relaunch, Salesforce Ben reported the exam was free under Salesforce’s AI for All initiative. The guide now lists USD 200, and we found no current free voucher on official pages today.

What changed: from AI Specialist to Agentforce Specialist

According to Salesforce Ben’s February 2025 report, the AI Specialist exam was renamed and reworked as the Agentforce Specialist exam, with the updated version applying to exams scheduled on or after March 3, 2025. Existing AI Specialist holders did not need to retest. Their credential converted to Agentforce Specialist on that date.

The outline has moved since. The 2025 version had five sections, including separate Service Cloud and Sales Cloud sections. The Spring ’26 guide drops those and adds Agent Script, hybrid reasoning, Testing Center, governance and multi-agent protocols. A practice test focused on Einstein Copilot or Model Builder is out of date.

The wider 2026 context matters too. Salesforce Ben reported in June 2026 that Salesforce is retiring 24 certifications and renaming 16 others, with most new names including “Agentforce.” The renames took effect on July 24, 2026. The Agentforce Specialist certification kept its name, and the guide now calls the recommended admin credential “Platform Administrator.” One Agentblazer Legend requirement still says “AI Specialist,” which is a leftover label, not a separate exam.

Agentforce Specialist exam outline and section weightings

This is where your study time should follow the numbers. AI Agents alone is more than a third of the exam.

SectionWeightApprox. questions (of 60)Key objectives from the guide
AI Agents35%21Agent Script building blocks, hybrid reasoning in Canvas and Script View, filters, variables and template expressions, topics and actions, channels (digital experience, email, voice, Slack), agent security context, Employee vs Service agents, when to use the Agent API
Prompt Engineering20%12When to use Prompt Builder, template access controls, template types such as field generation and flex, grounding choices, creating and activating templates, prompt best practices, Trust Layer features, restricting models
Data 360 Fundamentals20%12Agentforce Data Library concepts and considerations, chunking, indexing and retrievers
Testing, Deployment, and Maintenance10%6Testing Center tests and evaluations, deploying agents and prompt templates from sandbox to production
Governance and Observability10%6Managing and monitoring agents, agent analytics and optimization
Multi-Agent Orchestration5%3When a multi-agent design fits, purpose of open protocols including MCP and A2A

The question counts are our own arithmetic from the weightings. Salesforce does not publish a per-section count.

Agentforce Specialist exam practice: building and testing an agent in a Developer Edition org
Hands-on practice in a free Developer Edition org matters more than reading for the Agentforce Specialist exam.

A practical 4-week study plan

This Agentforce Specialist plan assumes 60 to 90 minutes on weekdays and a longer weekend session. If you already build agents at work, compress it to two or three weeks. If you have never configured Salesforce, add a week of admin basics first.

Week 1: Foundations, prompts and the Trust Layer

  • Sign up for a free Developer Edition org and connect it to your Trailhead account.
  • Complete the Become an Agentblazer Champion 2026 trail. It covers Prompt Fundamentals, Prompt Builder Basics, The Agentforce Trust Layer and a hands-on service agent build.
  • In your org, build one field generation template and one flex template. Ground each one in record data and note which grounding method you used and why.

Week 2: Data 360 and the Data Library

  • Complete Agentforce Data Library Basics and build a file-based data library.
  • Read the Salesforce Help topics on chunking, indexing and retrievers until you can explain each to a non-technical colleague.
  • Connect a short policy PDF to an agent through a data library and ask questions the file cannot answer. Watch how the agent responds.

Week 3: AI Agents, the 35% section

  • Complete Agent Script Basics and the Build an Agent Using Agentforce DX project.
  • Build an agent with two custom topics and at least one custom action backed by a flow. Switch between Canvas and Script View to see how the same logic is expressed.
  • Use variables and filters to make one behavior deterministic, for example only offering a refund action when an order status is “Delivered.”
  • Complete Use Employee Agents to Get Work Done, then write down three scenarios where an Employee agent fits and three where a Service agent fits.
  • If you write Apex, attempt the Apex for Agentforce superbadge.

Week 4: Testing, deployment, governance and review

  • Complete Agentforce Testing Center, Agentforce Deployment for Service Agents, Agentforce Analytics and Monitoring, and MCP for Agentforce: Quick Look.
  • Run a batch of tests against your week 3 agent in Testing Center, including AI-generated tests, and fix at least one failing case.
  • Work through the Cert Prep: Agentforce Specialist module.
  • Re-read the exam guide objective by objective. Mark each one green, amber or red, and spend the last three days on the red ones.

Trailhead trails and modules mapped to each section

We opened every item below on Trailhead today.

Exam sectionVerified Trailhead content
Prompt EngineeringPrompt Builder Basics (about 45 minutes); Prompt Fundamentals and The Agentforce Trust Layer inside the Become an Agentblazer Champion 2026 trail
Data 360 FundamentalsAgentforce Data Library Basics; the “Ground Your Agent with Data” and “Manage Your Agent’s Data” sections of Become an Agentblazer Legend 2026
AI AgentsAgent Script Basics; Build an Agent Using Agentforce DX; Use Employee Agents to Get Work Done (Champion trail); Apex for Agentforce superbadge
Testing, Deployment, and MaintenanceAgentforce Testing Center; Agentforce Deployment for Service Agents
Governance and ObservabilityAgentforce Analytics and Monitoring; the “Test and Monitor Your Agent” section of the Legend trail
Multi-Agent OrchestrationMCP for Agentforce: Quick Look; the multi-agent unit in Cert Prep: Agentforce Specialist
All sectionsDesign and Implement AI Agents with Agentforce trail (about 9 hours), which runs from planning through configuration, testing, deployment and monitoring

The exam guide recommends earning Agentblazer status. The 2026 version has three levels, Champion, Innovator and Legend, taken in order, and Legend includes a step called “Become a Salesforce Certified Agentforce Specialist.” Apex for Agentforce was the only related superbadge we could verify, and it is aimed at developers.

Hands-on practice in a free Developer Edition or Playground

Reading alone will not get you through scenario questions. Salesforce’s developer blog says the Developer Edition, relaunched in March 2025, is free, includes Agentforce and Data Cloud, ships with the Coral Cloud sample app, and does not expire while in use. Sign up at developer.salesforce.com/signup.

Practice ideas that line up with the outline:

  1. Grounding comparison. Build the same prompt template three times, grounded with merge fields, a flow and a data library. Compare the output and write down when each makes sense.
  2. Restrict a model. Find where model access is controlled and practice limiting which models a template can use. The guide lists this as an objective.
  3. Deterministic guardrails. In Agent Script, gate an action behind a variable check. Then try to talk the agent into skipping the check.
  4. Security context test. Run the same action as two users with different permissions and see how the running user changes what the agent can do.
  5. Test, break, fix. Write ten Testing Center cases, deliberately break a topic description and see which tests catch it.

One caution: superbadges such as Apex for Agentforce require a fresh org created from the superbadge’s own sign-up link. Do not use your practice org for those.

Three practice examples written by us

These are original practice examples written by the Ashapura team for study purposes. They are not real exam questions and are not taken from any exam or dump.

Practice example 1

A support manager wants agents to answer warranty questions using a 40-page PDF policy that changes every quarter. The admin does not want to rebuild prompts each time the policy changes. What is the most suitable approach?

  • A. Paste the policy text into the agent’s topic instructions
  • B. Add the PDF to an Agentforce Data Library and ground the agent on it
  • C. Create a custom field on Case that stores the full policy text
  • D. Build a flex prompt template with the policy hardcoded

Our answer: B. A data library keeps unstructured content separate from prompts, and updated files can be re-indexed without rewriting instructions.

Practice example 2

A company’s service agent should only offer the “Issue Refund” action after it confirms the order has been delivered. Testing shows the agent sometimes offers refunds early. What should the specialist do first?

  • A. Add more examples to the topic description
  • B. Use a variable and a filter so the action is available only when delivery status is confirmed
  • C. Switch the agent to a different language model
  • D. Remove the action and ask customers to call

Our answer: B. The guide calls out filters and variables as the way to manage deterministic behavior. Wording changes alone leave the decision to the model.

Practice example 3

Sales reps want an assistant inside Salesforce that summarizes their open opportunities and drafts follow-up emails. No customers will interact with it. Which agent type fits best?

  • A. Service agent deployed to a website
  • B. Employee agent
  • C. An external bot connected through the Agent API
  • D. A field generation prompt template only

Our answer: B. Internal users working on their own records is the Employee agent use case. A Service agent is built for customer-facing conversations.

Common mistakes we see

  • Studying an old outline. Many courses still teach the 2025 five-section version of the Agentforce Specialist exam. Check that yours covers Agent Script, Testing Center and MCP or A2A.
  • Underweighting AI Agents. At 35%, weakness here is hard to make up elsewhere.
  • Skipping hands-on work. Scenario questions often have two workable answers. Building is how you learn which one Salesforce treats as best practice.
  • Treating Data 360 as optional. It is 20% of the exam. Know chunking, indexing and retrievers well enough to choose between them.
  • Ignoring security context. Questions about which user an agent runs as trip up people who only build as a system admin.
  • Forgetting maintenance. The current Agentforce Specialist certification module is “Agentforce Specialist Certification Maintenance (Summer ’26).” Miss the due date and the credential expires.

How hiring managers view the Salesforce Certified Agentforce Specialist

The honest answer: it helps you get shortlisted, but it rarely wins the job on its own.

The market data supports both halves of that. Salesforce Ben’s October 16, 2026 coverage of the 10K Salesforce Ecosystem Report found overall Salesforce job demand down 13% this year, while demand for Agentforce skills rose 63% globally and 87% in North America. So AI skills are where the openings are.

At the same time, Salesforce Ben’s July 2026 careers guide found that about 32% of admins already hold the Agentforce Specialist certification and another 27% plan to earn it. When a third of candidates have the same badge, it stops being a differentiator. The same survey’s consistent theme was that hands-on experience beats credentials, and it noted that only 32% of developers had shipped an AI project.

When we interview admins and developers, a Salesforce Certified Agentforce Specialist badge tells us someone has learned the vocabulary. The interview tells us whether they can design a topic, scope an action safely and explain why a test failed. If you are hiring, our free Salesforce admin and developer interview scorecard gives you structured questions to separate the two. If you are a candidate, use it to rehearse.

What we see in our own Salesforce projects

The exam’s emphasis on deterministic behavior, data grounding and testing matches where real projects spend their effort.

On a US consumer electronics retailer project, Agentforce runs alongside Service Cloud and CPQ across 430,000 orders and 280,000 contacts, with 60% of cases deflected. Results like that depend on parts of the outline people skim: clean data, clear topic boundaries and testing before customers see anything.

On an industrial supply distributor project, customer contract rates and volume tiers lived in dozens of spreadsheets and pricing errors surfaced after invoicing. Sales Cloud and CPQ were connected to Odoo ERP and Avalara, with Agentforce in the mix. An agent there is only as good as the pricing data it can reach, which is exactly the point of the Data 360 section.

Our takeaway for candidates: the people who do well on our Agentforce work think about data access and failure cases first. The Agentforce Specialist exam rewards the same habit. If your company is weighing the data side, our Data Cloud consulting page explains how we approach it.

Agentforce Specialist exam review: a candidate checking notes against the official exam guide
Review the official exam guide weightings once more in the final week, so your study time matches the exam.

Frequently asked questions

How many questions are on the Agentforce Specialist exam?

There are 60 scored multiple-choice questions plus up to five unscored questions, with 105 minutes to finish, according to the official exam guide.

What is the passing score for the Agentforce Specialist certification?

The official exam guide lists a passing score of 72%. Some third-party guides show 73%, so rely on the Salesforce guide.

How much does the Agentforce Specialist exam cost?

Registration is USD 200 and a retake is USD 100, plus applicable taxes. The exam was free under a 2025 promotion, but the current guide lists the full fee.

Are there prerequisites for the Salesforce Certified Agentforce Specialist?

No. Salesforce recommends Platform Administrator and Platform App Builder certifications as helpful background, but neither is required.

Is the AI Specialist certification the same as Agentforce Specialist?

It is the same credential under a new name. AI Specialist holders were converted to Agentforce Specialist on March 3, 2025, but the exam outline has been rewritten since then.

How do I maintain the Agentforce Specialist certification?

Complete one certification maintenance module on Trailhead each year. The current one is Agentforce Specialist Certification Maintenance (Summer ’26). Missing the due date causes the certification to expire.

Getting started

If you are preparing for the Agentforce Specialist certification, start with the official guide, a Developer Edition org and the Champion trail this week. If your team needs Agentforce delivered rather than studied, our Salesforce development team builds, tests and deploys agents for US businesses and can work alongside your certified staff.

About the author. Ankur Pandey is Marketing Manager at Ashapura Softech, a Salesforce and Odoo consulting partner based in Irving, Texas, with a delivery center in Ahmedabad, India. He works with the company’s Salesforce delivery teams on CRM, Agentforce and integration projects for US businesses and writes about what Salesforce product changes mean in practice.

Disclosure: Ashapura Softech is a Salesforce consulting partner and delivers Agentforce projects. We have no affiliation with Salesforce’s certification program and receive nothing for exam registrations.

Sources

Categories
Salesforce

How to Choose a Salesforce Implementation Partner in 2026

Last updated: October 19, 2026

Short answer: Choose a Salesforce implementation partner on evidence you can check yourself: their consultant listing and reviews in Salesforce’s partner marketplace, the current certifications of the named people who will do the work, and a written discovery process, SOW and support plan. Salesforce changed its consulting partner tiers in 2026 (the track now uses Summit and Select), so treat the tier badge as one signal, not the deciding factor.

If you have been asked to find a Salesforce implementation partner this quarter, you have probably noticed that every firm’s website says roughly the same thing. Certified experts, proven methodology, hundreds of projects. The words stop being useful very quickly.

This guide is for US buyers comparing Salesforce implementation partners who want something better than a sales deck. It covers what a partner does versus what Salesforce provides, the 2026 partner program changes, certifications by role, delivery and pricing models, and what to get in writing before anyone builds anything.

One note first: we are a Salesforce consulting partner ourselves. We have kept this vendor-neutral, relied on Salesforce’s own pages wherever possible, and listed every source at the end.

Before you shortlist partners, read our guide to CRM implementation services for typical cost ranges and the questions to ask.

What a Salesforce implementation partner does, and what Salesforce does

Salesforce sells licenses, runs the platform and offers support plans. A Salesforce implementation partner turns those licenses into a working system for your business.

Every license includes the Standard Success Plan, which Salesforce describes as self-guided resources plus technical support. Premier is priced at 30% of net license fees and adds 1-to-1 sessions with Salesforce experts and 24/7 support for business-stopping issues. Signature adds a designated Customer Success Manager and 15-minute response times for critical issues. None of these plans is a team that designs and builds your org.

Salesforce also has its own Professional Services group, and its page says plainly that “Most customers use both” Professional Services and certified partners. Salesforce’s consulting program page cites IDC research that 78% of high usage customers engaged with consulting partners.

A good partner typically owns:

  • Discovery, requirements and solution design
  • Configuration of objects, permissions, flows and approvals
  • Data migration and cleanup from legacy CRMs, spreadsheets or help desks
  • Integrations with ERP, tax, telephony and ecommerce systems
  • Agentforce design: which jobs an agent handles, its actions, guardrails and testing
  • Testing, training, cutover and support after go-live

Business decisions, process ownership and data quality stay with you whoever you hire, ideally with an internal admin who owns the system long term.

On terminology, “Salesforce consulting partner” is the program name, while “Salesforce implementation” describes the work. Most Salesforce implementation partners are consulting partners in the program, and buyers use the terms interchangeably.

How the program ranks a Salesforce implementation partner in 2026

From four tiers to two

For years, consulting partners were ranked in four tiers: Base, Ridge, Crest and Summit. Salesforce’s FY26 program material (March 2025) says tiers were “earned based on a partner’s Trailblazer score,” a scorecard covering customer success, innovation, growth and impact.

On March 2, 2026, Salesforce announced a new consulting track with two tiers, Summit and Select, removing “legacy scorecards and incentive calculations.” Salesforce says recognition is now “tied strictly to project outcomes, CSAT, and certifications.” Salesforce Ben describes Summit as the tier for partners “aligned to strategic growth” and Select for “proven delivery partners.” Salesforce’s program page, updated in June 2026, also describes new firms starting as Provisional partners and moving toward a Registered tier.

Plenty of partner websites still show Ridge or Crest badges, which may simply be out of date. We could not find an exact public cutover date, so ask which tier the firm holds today rather than judging an old badge.

When you compare Salesforce implementation partners, keep tier in proportion: it reflects a partner’s overall Salesforce business. A Select firm with deep experience in your industry can suit a mid-market project better than a Summit firm focused on much larger accounts.

Competencies replace Navigator distinctions

The bigger change for buyers is specialization. Salesforce says the program “evolves 170 legacy distinctions into 28 core competencies,” with a growing focus on Agentforce and Data 360. Salesforce Ben and Futurum Group both report two levels per competency, Accredited and Expert, based on certifications, completed projects and customer satisfaction scores. Salesforce’s announcement does not publish those thresholds, so ask each Salesforce consulting partner on your shortlist which competencies and levels it holds. A competency in the exact product you are buying tells you more than the overall tier.

How to verify a Salesforce implementation partner yourself

Salesforce’s partners page invites you to “Explore Partners on AgentExchange,” and that link currently opens the consultant directory at appexchange.salesforce.com/consulting. In April 2026 Salesforce combined AppExchange, Slack Marketplace and the Agentforce ecosystem into one marketplace called AgentExchange, so you will see both names for now. Based on Salesforce’s Trailhead guide to finding consultants:

  1. Use the Find Consultants wizard (expertise, company size, location) or search a specific phrase. Trailhead’s example is “Agentforce Service consultants in Arizona.”
  2. Check each listing’s summary bar: star rating, completed projects, certified experts and year founded.
  3. Open the Expertise tab for products, industries and individual consultants’ current certifications.
  4. Read the Reviews tab, including the critical reviews.
  5. Verify named individuals on Trailhead’s credential verification page, which searches by full name.

Certifications to look for on the delivery team

Company-level certification counts look good on a listing, but the people assigned to your Salesforce implementation matter far more. Ask for the names and roles of the proposed team, then check their credentials. Salesforce renamed about 35 certifications in 2025, according to Salesforce Ben, and Trailhead has renamed more since, so résumés may use older names.

Salesforce implementation discovery: two colleagues mapping requirements on a whiteboard
A good discovery workshop surfaces data ownership and integration questions before anyone quotes a fixed price.

What to look for by role, using current names:

  • Admins: Salesforce Certified Platform Administrator (formerly Administrator), Platform Administrator II (formerly Advanced Administrator) and Platform App Builder.
  • Sales and service leads: Salesforce Certified Agentforce Sales Consultant and Agentforce Service Consultant. Their Trailhead URLs still say Sales Cloud and Service Cloud, which tells you what they replaced.
  • Agentforce work: Salesforce Certified Agentforce Specialist. Trailhead describes holders as “responsible for managing and optimizing Agentforce.”
  • Developers: Platform Developer (formerly Platform Developer I) and Platform Developer II.
  • Data projects: Salesforce Certified Data Cloud Consultant, still named that way on Trailhead even though program material now says Data 360.
  • Quoting: CPQ Administrator (formerly CPQ Specialist).
  • Marketing and integration: Marketing Cloud Engagement Consultant, MuleSoft Developer and MuleSoft Platform Integration Architect.
  • Architecture: Application Architect, System Architect and, for complex multi-cloud programs, Certified Technical Architect.

A certification proves someone passed an exam and kept it maintained. It does not prove they delivered a project like yours, so pair every credential check with a question about a comparable project.

Onshore, offshore or blended: which delivery model fits

Where the team sits affects cost, communication and how fast problems get fixed. India, for example, is roughly 9.5 to 13.5 hours ahead of US time zones depending on the zone and daylight saving. That can slow a project down or, if planned well, give you work done overnight.

ModelHow it worksFits best whenWatch out forRelative cost
OnshoreWhole team based in the USHeavy workshop schedule, data residency rules, many stakeholders needing live accessBudget can force a smaller team or reduced scopeHighest
OffshoreTeam based in another country, such as IndiaWell-defined build work, enhancements, a strong product owner on your sideFew overlap hours, requirements lost in handoffsLowest
BlendedUS-facing lead or architect plus an offshore build teamMid-market projects that need live discovery on a fixed budgetA “US lead” who is really a salesperson, unclear split of dutiesMiddle
NearshoreTeam in a nearby country with similar hours, such as Latin AmericaYou want full working-day overlap below onshore ratesSmaller talent pools for niche products like CPQ or MuleSoftMiddle

We run a blended model ourselves, so weigh our view accordingly. The honest test for any Salesforce implementation partner is simple: who attends your workshops, who writes the code, who you call when something breaks at 9 a.m. your time, and how many overlap hours you get.

Pricing models: fixed bid, time and materials, retainers

We have not found a reliable, current public benchmark for Salesforce implementation costs, so we are not quoting dollar figures. Ask each shortlisted Salesforce consulting partner for an itemized estimate against the same requirements. Here is how the common structures behave:

  • Fixed bid. One price for agreed scope. Good when requirements are clear. The vendor protects its margin through change control, so read the assumptions as carefully as the price.
  • Time and materials. You pay for hours at agreed rates. Flexible when scope is still moving, such as an early Agentforce pilot. The risk sits with you, so insist on weekly burn reports and a not-to-exceed cap.
  • Retainer. A monthly block of hours for admin, enhancements and release support. Check whether unused hours roll over.
  • Phased hybrid. Paid discovery first, then a fixed or capped build based on what discovery found. Often the fairest structure for both sides.

Licenses are billed by Salesforce, not the partner, and Agentforce usage has its own consumption model. Our explainer on Agentforce pricing and Flex Credits covers that separately.

Red flags when evaluating a Salesforce implementation partner

  • A firm price before detailed questions about your data, integrations and processes.
  • Senior people on sales calls who will not be on your delivery team, and no named team.
  • Proposed consultants whose certifications do not appear on Trailhead’s verification page.
  • No references, or only references from very different industries or project sizes.
  • Data migration “included” with no plan for mapping, test loads or reconciliation.
  • Guaranteed Agentforce outcomes, such as a deflection rate, before anyone sees your case data.
  • Unclear ownership of code, configuration and documentation, or no mention of life after go-live.

A 12-question checklist for vetting Salesforce implementation partners

Send every shortlisted Salesforce implementation partner the same questions, in writing, so the answers are comparable.

  1. Which tier and competencies do you hold today, and at what level for the products in our scope?
  2. Who exactly will work on our project, in what role, with which current certifications?
  3. Can we speak to two recent clients with a similar size, industry and product mix?
  4. What does your discovery phase include, and what documents do we receive at the end?
  5. How do you handle data mapping, cleanup, test loads, reconciliation and sign-off?
  6. Which integrations have you built with our systems, and how do you monitor errors?
  7. How do you decide what Agentforce should and should not do, and how do you test agents?
  8. What is your delivery model, how many overlap hours do we get, and who is our single contact?
  9. How do you price change requests, and what assumptions sit behind your estimate?
  10. Who owns the code, configuration, documentation and test scripts at the end?
  11. What post go-live support do you offer, for how long, with what response times?
  12. How will you hand the system over to our internal admin?

For internal planning, our free 40-item Salesforce implementation checklist covers the project side in more detail.

What a good discovery phase and SOW contain

Discovery is where most Salesforce implementation projects are won or lost. It should involve the people who do the work, not just their managers, and look at real data. By the end you should have current-state process maps, prioritized requirements split into phases, a data inventory (sources, volumes, quality issues, what will not move), an integration map, a solution design including any Agentforce use cases, and a risk list with a realistic timeline.

The statement of work turns that into commitments: scope and explicit out-of-scope items, deliverables with acceptance criteria, named roles on both sides, assumptions, change control, a testing plan with user acceptance testing, data migration, training, cutover, the support period, payment milestones tied to deliverables, and ownership of IP and documentation. If something you care about is not in the SOW, assume it is not included.

Post go-live support: what to agree before launch

Agree these points with your Salesforce implementation partner before launch, not after real users find the gaps:

  • Hypercare: a defined window with the project team on call and clear exit criteria.
  • Response times: written targets by severity and a named contact.
  • Release readiness: who tests each seasonal Salesforce release against your customizations in a sandbox.
  • Agent monitoring: who reviews Agentforce conversations, tunes instructions and watches consumption.
  • Handover and health checks: admin training, documentation, and periodic reviews. Our free CRM health check template is one way to structure them.

What we see in our own Salesforce projects

A few patterns repeat across our work, and they shape how we would evaluate any Salesforce consulting partner, including us.

Pricing problems are usually data problems first. For a B2B industrial supply distributor, customer-specific contract rates and volume tiers lived in dozens of spreadsheets, reps used different versions, and pricing errors surfaced after invoicing. The project connected Sales Cloud and CPQ to Odoo ERP and Avalara, with Agentforce. Ask a partner how it will consolidate pricing rules before it shows you quoting screens.

Migration and integration carry more risk than configuration. A multi-brand retailer with five brands had a legacy CRM that crashed at peak season, no 360-degree customer view, Amazon, Walmart and eBay orders reconciled outside the CRM, and support siloed in Zendesk. Sales Cloud, CPQ, Service Cloud Voice, Marketing Cloud and Agentforce went into one org, and more than 2 million records moved from the legacy CRM and Zendesk with zero data loss. That depends on a written migration plan, test loads and reconciliation.

Agentforce results depend on volume and clean service data. For a US consumer electronics retailer, Service Cloud, CPQ and Agentforce handle 430,000 orders and 280,000 contacts, with 60% of cases deflected. That is one project’s result, not a promise, and any partner guaranteeing a deflection rate before seeing your data is guessing.

Salesforce implementation partner and client team reviewing the plan on a laptop
The partner you choose should leave your team able to run the org, not dependent on the partner for every change.

If your project is mainly about AI agents, our separate guide on how to choose an Agentforce implementation partner covers the questions that are specific to Agentforce.

If you want to interview the admins or developers who will actually work on your org, our free Salesforce interview scorecard gives you a structured way to assess admin and developer candidates.

Frequently asked questions

What is the difference between a Salesforce implementation partner and a Salesforce consulting partner?

Usually they are the same firms. Consulting partner is the track name in the Salesforce Partner Program, while implementation describes designing, building and launching your org. Some consulting partners focus on strategy or managed services, so ask how much of their work is hands-on delivery.

Does Salesforce still use the Base, Ridge, Crest and Summit tiers?

Not for the consulting track. In March 2026 Salesforce announced two tiers, Summit and Select, and replaced 170 distinctions with 28 competencies. Many partner websites still show older badges, so ask which tier and competencies a firm holds today.

How do I check whether a partner’s consultants are really certified?

Ask for the full names of the proposed team and search them on Trailhead’s credential verification page. The partner’s consultant listing in Salesforce’s marketplace also shows individual consultants’ current certifications on the Expertise tab.

Is an offshore Salesforce implementation partner a good idea for a US company?

It can be, if the work is well defined, you have a strong internal product owner and the partner guarantees enough daily overlap hours. For workshop-heavy discovery, a blended model with a US-facing lead often works better.

Should I choose a fixed bid or time and materials contract?

Fixed bid suits a well-understood scope, while time and materials suits work still taking shape, such as an early Agentforce pilot. Many buyers pay for a short discovery phase first, then choose the build contract based on what it found.

How long should post go-live support last?

There is no standard length. Agree a named hypercare window in the SOW with exit criteria, written response times by severity and a handover plan for your admin, then decide whether you need a retainer afterwards.

Getting started

Shortlist three Salesforce implementation partners, send them the same 12 questions, and compare written answers before you compare prices. If you would like Ashapura Softech on that list, see how we approach Salesforce implementation and CRM development and ask us the same questions you ask everyone else.

About the author. Ankur Pandey is Marketing Manager at Ashapura Softech, a Salesforce and Odoo consulting partner based in Irving, Texas, with a delivery center in Ahmedabad, India. He works with the company’s Salesforce delivery teams on CRM, Agentforce and integration projects for US businesses and writes about what Salesforce product changes mean in practice.

Disclosure: Ashapura Softech is a Salesforce consulting partner and could be one of the firms you evaluate; no partner paid to be mentioned in this guide.

Sources

Categories
Salesforce

Salesforce AgentExchange: What Replaced AppExchange and 6 Checks Before You Install

Last updated: October 19, 2026

Short answer: Yes, AppExchange is now part of AgentExchange. In April 2026, around its TDX developer event, Salesforce merged it with the Slack Marketplace and the Agentforce ecosystem into a single marketplace. Installed apps are still managed from the same Installed Packages page. What changed is how listings are found, bought and governed, and the fact that agents and MCP servers now sit next to classic managed packages. Before installing anything, check its security review status, the permissions and data it needs, who an agent acts as, and how it is priced.

If you typed AppExchange into Google this week and landed on a page called AgentExchange, you are in the right place. Salesforce AgentExchange is the new name and shape of the Salesforce marketplace. The apps you know are still listed, but agents, MCP servers and Slack apps now sit in the same catalog, and buying can happen inside your Salesforce account.

This guide to AgentExchange is for admins, IT leads and RevOps teams who make install decisions, and for partners with listings. Everything here comes from Salesforce documentation, announcements and trade press we checked on October 19, 2026. Where Salesforce has not said something publicly, we say so.

Is AppExchange now AgentExchange? What actually happened

Yes, but the name has a two-step history, which is why search results look confusing. Articles from 2025 describe a small agent parts store. Articles from 2026 describe the merged marketplace.

March 2025: an agent parts store for Agentforce

Salesforce first used the name in March 2025. Its March 4, 2025 press release described a marketplace and community for Agentforce, launching with more than 200 partners including Google Cloud, Docusign, Box and Workday. It mostly offered building blocks rather than finished products: actions, prompt templates, topics and agent templates that builders dropped into their own agents. Diginomica called it the agent equivalent of AppExchange, which at the time still sold complete apps in its own storefront.

April 2026: one marketplace instead of three

At TDX 2026 in mid-April, Salesforce merged the catalogs. Salesforce Ben, Diginomica and CX Today reported the change on April 15, 2026, and Salesforce Italy published its press release on April 17. The new marketplace brings together AppExchange, the Slack Marketplace and the Agentforce ecosystem. At launch Salesforce counted more than 10,000 Salesforce apps and experts, more than 1,000 agents, subagents, tools and MCP servers, and more than 2,600 Slack apps and agents. Tyler Carlson, who leads product for the marketplace, explained the reasoning to Diginomica in one line: “Work does not happen in one place anymore.”

Salesforce also announced a $50 million AgentExchange Builders Initiative. It was presented as a commitment combining capital, technical guidance and go-to-market programs, not as a named venture fund. SalesforceDevOps.net reported that it includes engineering help, lead referrals and marketing development funds, aimed at small development shops and early-stage startups.

What happened to existing listings, URLs and reviews

This is what most people searching the old name want to know, and the public record is thinner than you might expect. Here is what we could confirm:

  • The old address still works as a front door. When we opened appexchange.salesforce.com on October 19, 2026, its page title read “Salesforce AppExchange is now AgentExchange”.
  • Reviews came along. The Italian press release counts more than 186,000 reviews, ratings, use cases and compliance indicators in the unified marketplace.
  • Documentation was renamed in place. The Salesforce installation guide now uses the new name throughout while its URLs still contain the old one, and the install permission is listed as Download AgentExchange Packages.
  • Installed packages are handled the same way. The install FAQ still sends admins to the Installed Packages page in Setup to uninstall or reinstall.

What we could not confirm is whether every old listing URL redirects one-to-one. If your wiki or procurement records link to specific AppExchange apps, click through and update them.

AppExchange vs AgentExchange: what changed

The table compares the old storefront with what Salesforce has documented for AgentExchange. Items marked as planned were roadmap in the April announcements, not shipped features.

AreaBefore April 2026Now
ScopeSalesforce apps and consultants. Agent building blocks had their own catalog from March 2025, and Slack apps a separate marketplace.One catalog for Salesforce apps, agents, subagents, tools, MCP servers, Slack apps and consulting services.
DiscoveryWebsite search by keyword and category.Semantic search powered by Data 360, listings surfaced inside Agentforce Builder, and a browser in Slack. Conversational search with comparisons was planned for fall 2026.
BuyingContracts usually agreed directly with each partner.Private offers accepted inside your Salesforce account, with unified billing and automated provisioning. Public offer checkout was planned for winter.
Security reviewRequired before public distribution for solutions subject to review.Same rule, now called the AgentExchange security review. Private listings are still not reviewed.
Admin controlsProfile selection at install, plus standard Salesforce permissions.Salesforce says admins control data permissions, API scopes and integration boundaries at user, role and profile level.
Partner sidePublishing through the Partner Community.An AgentExchange Partner Console, a new ISV MCP Tool Action listing type, a Go-to-Market app for offers and the $50M Builders Initiative.

What to check before installing from AgentExchange

A listing is a starting point, not an approval. Salesforce’s own install FAQ warns that third-party apps with data access may be able to reach other data in your org. Run the six checks below for every app, agent or MCP server, free or paid.

AgentExchange app review: an admin checking permissions and data access before an install
Before installing anything from AgentExchange, check what data the app or agent can reach and who approved it.

1. Security review status, and whether the listing is private

Solutions that are subject to review must pass the security review before they can be distributed publicly, according to the ISVforce Guide. Salesforce also says it periodically reviews publicly listed apps. Two catches: private listings get no security review at all, and none of the Salesforce pages we read describe a passed review as a guarantee. Treat it as a floor, not a sign-off.

2. Which profiles get access at install

Your edition changes what happens during install. In Enterprise, Unlimited, Performance and Developer Editions you choose which profiles get access. In Professional and Group Editions, packages install with full access for all profiles. In every edition, custom objects arrive in “In Development” status, hidden from standard users until you mark them Deployed. Install into a sandbox first, grant access to admins only, and widen it later.

3. What data it reads and where that data goes

Ask the publisher for a plain list of the objects and fields the product reads and writes, the external endpoints it calls, and any data it stores outside Salesforce. Salesforce says admins can restrict data permissions, API scopes and integration boundaries, but you can only set sensible limits if you know what the product needs.

Tools that work through Slack add a second system to review. When ZoomInfo relisted its ZoomInfo MCP integration in August 2026, connecting its data to Slackbot, it said access control, permissions and audit logging carry over from the customer’s existing ZoomInfo and Slack settings. Sensible design, but your review now has to cover both permission models.

4. Who the agent acts as, and how MCP tools connect

Agents run as a user, and that user is where most risk sits. Salesforce Ben explained in September 2026 that a new Agent User gets the Einstein Agent license and the Einstein Agent User profile and “starts essentially blank”. For unidentified or merely verified visitors, a service agent runs under its own permissions. Only when a visitor is authenticated does it run as that logged-in user. Verification tells the agent who someone is, not what data they may see, so check which permission sets an agent listing adds and whether it filters records by the verified customer.

For MCP servers listed on AgentExchange, Salesforce’s packaging documentation says a managed package can carry the server definition (credentials setup, service registration and a permission set), but tool actions and Agentforce Gateway policies are not packageable yet, so you set tool access and limits in each org. Tools stay inactive until an admin selects them, and credentials are entered in your org. A Salesforce Developers post from August 2026 shows the same allowlist step for external servers. Ask each vendor which authentication method the server uses and whether each tool can be switched off separately.

5. The pricing model

Pricing varies by listing. To accept a private offer, a user needs the Manage Billing User permission, opts in under Offers Marketplace in Setup and reviews the terms. Accepting creates an order and invoice, and licenses are provisioned automatically. Salesforce’s ISV guidance for Summer ’26 also encourages partners to move from per-user monthly pricing to per-action or per-process pricing based on Flex Credits. If a product charges that way, ask whether its fees stack on top of your own Agentforce consumption. Our Flex Credits explainer covers how that metering works.

6. Reviews, publisher and package type

Read recent reviews from companies on your edition, and use the test drive, which gives you a working demo as a read-only user. Confirm whether the package is managed. Managed packages are upgradeable and keep the publisher’s namespace, and components from publicly listed managed packages do not count against your edition’s allocation of custom objects, tabs and apps. Unmanaged and unlisted packages do. Installs can also fail if a package needs features you have not enabled, so read the requirements first.

What changed for ISVs and partners listing products

For partners, April was more than a rename. Here is what the sources we read confirm about Salesforce AgentExchange for ISVs:

  • Reach. Carlson told Diginomica the merged store gives builders a route to more than 160,000 enterprise customers, and Salesforce’s ISV blog cites more than 20 million Salesforce and Slack users. Listings also surface inside Agentforce Builder.
  • A new listing type. The ISV MCP Tool Action listing lets partners expose their own MCP servers hosted outside Salesforce.
  • Commerce. The Go-to-Market app supports private offers with tailored pricing, unified billing and automated provisioning, and Salesforce’s ISV blog mentions feature-based licensing.
  • Publishing. AI-assisted publishing tools and improved listing pages were announced for fall 2026.
  • Security review. Partners start a review from the Solutions page of the Partner Console, which requires the Manage Listings permission.
  • Funding. The $50M Builders Initiative described above.

What we could not find is any statement about changes to AgentExchange listing fees or revenue share. If that affects your business model, check your partner agreement and the Partner Community rather than press coverage.

The ISV blog also recommends replacing custom connectors with MCP tools, noting that because Salesforce and Slack both support MCP, a metadata update can bring an app’s capabilities into Slack. At Dreamforce 2026, the partner session list included talks on MCP on AgentExchange and on how Salesforce vets agents for safety. Our SIforce explainer covers where partner integrations fit in Salesforce’s agentic layer.

Agents vs classic managed packages: how admins should evaluate them

A managed package adds metadata to your org: objects, fields, Apex, flows and components. You can see all of it in Setup, and you upgrade it on a schedule you control. An agent or MCP tool listing on AgentExchange is closer to bringing in a contractor. What matters is what it does at runtime, which records it touches, which outside systems it calls, and whose permissions it uses.

So for a package you mostly check what it installs. For an agent you check what it does. This is the sequence we use:

  1. Write the job down in one sentence, with one measure of success.
  2. Install in a sandbox with realistic, non-sensitive data.
  3. Open the agent user and its permission sets. Start from nothing and add access on purpose, one object at a time.
  4. Test as an unidentified visitor, a verified visitor and an authenticated user. Try to pull another customer’s record. If you can, so can the agent.
  5. Review each MCP tool before you allowlist it, and leave off the ones you do not need.
  6. Turn on logging. Salesforce’s product page says the Audit Trail feature records agent actions and outputs. Read transcripts every week during the pilot.
  7. Model cost at the volume you expect in month six, not pilot week.
  8. Agree the off switch before go-live: who deactivates the agent or its tools, and how.

Classic packages with broad data access still deserve scrutiny. The agent list is longer because behaviour is less predictable than a screen a person clicks through.

What we see in our own Salesforce projects

Ashapura builds on the Salesforce platform and delivers implementations for US companies, so marketplace decisions come up regularly in our work. The checks above reflect that experience.

Take the industrial supply distributor we worked with. Customer-specific contract rates and volume tiers lived in dozens of spreadsheets, and pricing errors surfaced only after invoicing. The fix connected Sales Cloud and CPQ to their Odoo ERP and to Avalara, with Agentforce on top. The hard part was deciding what data moves where and under whose permissions, which is the same question to ask of any listing that touches pricing or tax.

Scale sharpens the agent user question. In our consumer electronics project, Service Cloud, CPQ and Agentforce handle 430,000 orders and 280,000 contacts, with 60% of cases deflected. At that volume, whether an agent runs on broad permissions or only sees the verified customer’s records is the main design decision, not a detail.

Our habit is simple: nothing from AgentExchange goes straight into production, every agent gets its own least-privilege user, and someone owns the weekly transcript review in the first month.

AgentExchange evaluation: colleagues comparing agents and managed packages
Agent or managed package? The evaluation steps are similar, but agents need extra checks on identity and actions.

If you are still choosing classic packages from the AppExchange catalog, our earlier roundup of must-have Salesforce AppExchange apps groups widely used apps by what they do.

Frequently asked questions

Is AppExchange gone?

The name is retired, but the catalog of Salesforce apps is still there. In April 2026 Salesforce combined it with the Slack Marketplace and the Agentforce ecosystem into one marketplace, and the old web address now opens with a notice announcing the new name.

Do I need to reinstall apps I installed from AppExchange?

We found no Salesforce guidance asking customers to reinstall anything because of the rename. Installed packages are still managed from the Installed Packages page in Setup. Upgrades follow the publisher’s normal release process, so check with each vendor if you are unsure about a specific package.

Is every listing on the marketplace security reviewed?

No. Solutions that are subject to review must pass the security review before they can be distributed publicly, and Salesforce says it periodically reviews publicly listed apps. Private listings get no security review, so admins should inspect them carefully before installing. A passed review is a baseline, not a guarantee.

What is an MCP server listing?

MCP, the Model Context Protocol, is a standard way for agents to call external tools. Partners can now list MCP servers, including a listing type for servers hosted outside Salesforce. Installing one usually means entering credentials in your org and choosing which tools to switch on, because tools stay inactive until an admin selects them.

How do I buy an app through a private offer?

A user with the Manage Billing User permission opts in to partner offers under Offers Marketplace in Setup, then reviews the offer from the Partner Offers tile on the Your Account page. Accepting it creates an order, you are invoiced as the offer describes, and licenses are provisioned automatically.

What is the AgentExchange Builders Initiative?

It is a 50 million dollar commitment Salesforce announced in April 2026 to help partners build and sell on the marketplace. Reports describe it as a mix of capital, technical guidance and go-to-market programs such as lead referrals and marketing development funds. None of the coverage we read describes it as a separate venture fund.

Getting started

Weighing a marketplace app or agent and want a second opinion on permissions, data flows or cost? We can help you plan and test it in a sandbox first. See our Salesforce development services to learn how we work with US businesses.

About the author. Ankur Pandey is Marketing Manager at Ashapura Softech, a Salesforce and Odoo consulting partner based in Irving, Texas, with a delivery center in Ahmedabad, India. He works with the company’s Salesforce delivery teams on CRM, Agentforce and integration projects for US businesses and writes about what Salesforce product changes mean in practice.

Disclosure: Ashapura Softech is a Salesforce consulting partner.

Sources