When the partners aren’t getting paid, look harder at the product

The Register ran a piece this week that should get more attention than it will: Salesforce partners are reportedly not seeing meaningful revenue from Agentforce. Not customers grumbling. Partners. The consultancies and integrators who staffed up practices, sat through the certifications, and built their 2026 pipeline around Marc Benioff’s favorite word.

That detail matters more than another “AI pilot stalls” headline would. Partners are the canary in any enterprise software ecosystem. They only make money when customers actually deploy, expand, and renew. When a vendor’s sales numbers look fine but the partner channel is starving, it usually means the product is being sold but not used. Licenses in a drawer. Pilots that never graduate.

I’ve been saying for a while that agents bolted onto a SaaS platform were going to hit this wall, and I want to walk through why, because the reasoning matters more than the schadenfreude.

The bolt-on problem, specifically

An agent is only as useful as what it’s allowed to touch and what it’s trusted to do. Agentforce, by design, lives inside Salesforce. That’s great if your entire operational reality lives inside Salesforce. Almost nobody’s does. The customer record is in the CRM, sure, but the contract is in a document system, the invoice history is in the ERP, the actual conversation with the client is in email, and the tribal knowledge is in somebody’s head or a shared drive from 2019.

So the “agent” either stays narrow enough to be safe and ends up doing work a workflow rule could have done in 2015, or it reaches outward through connectors and suddenly you’re paying platform prices for integration work while your governance story gets murkier with every hop. Neither version produces the outcome the demo promised. Partners can’t bill against outcomes that don’t materialize.

Then there’s pricing. Agentforce launched with per-conversation pricing, and consumption models like that put the customer in a strange position: the more successful the agent is, the bigger the bill, and the bill is set by the same vendor that controls the platform, the model access, and the switching costs. CFOs noticed. Variable AI bills tied to usage you can’t fully predict are exactly the kind of thing that keeps a pilot a pilot forever. Nobody signs off on production when they can’t forecast the line item.

What actually gets agents into production

Here’s what we’ve learned building AgentWorks deployments, and it’s almost boringly unglamorous.

First, the job comes before the agent. You don’t buy an agent platform and then hunt for use cases. You pick one process with a measurable cost, in hours or dollars or errors, and you build the agent to do that process. Scope is a feature. An agent that does one thing inside hard boundaries ships. An agent that “can do anything across your org” gets stuck in security review, and it should.

Second, governance is designed in, not reviewed in. Every AgentWorks agent runs against defined permissions, logged actions, and a human checkpoint wherever the blast radius justifies one. When compliance asks “what can this thing actually do, and who approved it,” the answer is a document, not a shrug. Your data, your rules. And that has to include the AI working on that data. Your AI, your rules, which means you decide what the agent reads, what it writes, which model it runs on, and where all of it lives. On a platform vendor’s agent, most of those decisions were made for you before you ever logged in.

Third, the economics have to be legible. We do fixed pricing on this work because a client cannot govern what they cannot forecast. If the marginal cost of the agent doing its job is a surprise, the agent will be throttled by the finance department long before it’s throttled by any technical limit.

And fourth, model agnosticism. The right model for a contract-summarization agent and the right model for a triage agent are often different, and both will be different again in eight months. An agent architecture that lets you swap the model without rebuilding the system is worth more than any single model choice you make today. Platform agents lock that decision to the platform’s roadmap.

The honest read on the Register story

None of this means Salesforce built something worthless, and this isn’t a pile-on. It means the “add agents to the platform you already pay for” pitch has a structural flaw: the platform’s interests and the customer’s interests diverge exactly at the points that determine whether an agent earns its keep. Scope, data reach, pricing, and model choice. The partners caught in the middle are just the first ones to feel it, because they’re the only party in the ecosystem paid strictly on real adoption.

The agent era is going to be won by narrow, governed, accountable deployments that a specific team relies on every day. We use ours daily, which is how we know which parts of the pitch survive contact with an actual Tuesday.

If you’ve run an agent pilot this year, on Agentforce or anything else, I’m genuinely curious: what killed it or what saved it? Was it governance, cost, scope creep, or something nobody warned you about? Tell me. The failure stories are teaching us more than the keynotes are.