The Ecosystem Shift Is Already in Production
Salesforce's Agentforce just crossed $1.5B in annualized revenue — 240% year-over-year growth. That number matters less as a headline and more as a forcing function: when a platform's AI layer scales that fast, the partner and integration ecosystem reorganizes around it whether you planned for it or not. Salesforce Ben's breakdown published this morning details how Salesforce is explicitly restructuring its AppExchange and ISV relationships around Agentforce as the new core.
For non-tech companies that built their revenue operations on Salesforce — with a mix of AppExchange solutions, managed packages, and custom integrations — this is the kind of platform shift that silently degrades your stack before anyone names it as the problem.
What Actually Changes for Operators
The practical risk isn't that Agentforce is bad. It's that native agent functionality will absorb use cases currently served by third-party AppExchange tools you're paying for and maintaining. When Salesforce builds scheduling, enrichment, follow-up sequencing, or forecasting into the agent layer natively, the ISVs covering those gaps lose their reason to exist — and your integrations built on top of them become fragile.
The second-order effect: partners are already realigning their roadmaps toward Agentforce compatibility. If your Salesforce implementation partner hasn't brought this up in a QBR yet, that's information. Either they're behind, or your contract structure doesn't incentivize them to tell you.
This also changes the ROI math on any Salesforce customization work scoped in the last 18 months. Custom flows and triggers built before Agentforce became production-grade may now have a native replacement that's cheaper to run and easier to maintain — or they may be on a collision course with Salesforce's own roadmap.
What to Do Before Q4 Budget Locks
Three concrete moves for operators running a Salesforce-centered revenue stack:
Audit your AppExchange footprint against Agentforce's current feature set. Pull your active managed packages, map each to its primary use case, and check Salesforce's Agentforce release notes for overlap. You're looking for redundancy risk, not immediate action.
Ask your Salesforce AE specifically where your org tier lands on Agentforce access. Agentforce pricing and availability varies by license type. Many operators don't know what they already have access to.
Hold any new third-party integration contracts to a shorter term. If a vendor is pitching a 2-year AppExchange deal for functionality that sits adjacent to what Salesforce is natively building, negotiate 12 months or include an exit clause. The ecosystem is moving too fast for long-term bets on adjacent tooling.
The Salesforce ecosystem has restructured before — from on-premise to cloud, from Sales Cloud to Platform. Each time, operators who waited for certainty paid a switching cost that early evaluators avoided. This cycle is no different, except the pace is faster.