There’s been a lot of chatter lately about Agentforce, Salesforce’s agentic technology stack. Some of it is fair. A lot of it misses the bigger picture.

Let’s unpack what’s going on and why we shouldn’t be too quick to judge this early chapter.

We’ve all heard the comments:

“It’s clunky.”

“It’s hard to use.”

“The use cases feel… underwhelming.”

Some of this is understandable. Agentforce today is in its early, highly constrained form — and that’s by design. This is Salesforce playing the long game. When a platform the size of Salesforce introduces automation and agentic tech, they can’t afford to let it run wild. Their customers aren’t just a few early adopters — they’re thousands of companies all with different tech stacks, data models, and workflows. Because of that, Salesforce has to prioritize safety, governance, and control over flashy use cases that could end up breaking critical business processes.

The result? 

Agentforce today is more like a guided, workflow-specific chat configuration tool. It’s constrained to ensure nothing goes sideways at scale.

That’s not a flaw. It’s a necessary starting point.

Let’s be clear: Agentforce already works. You can do things with it today, and we’re already seeing real examples of how it can help. Nue fully supports Agentforce. But it’s important to understand what it actually is. Agentforce is not a product feature of Revenue Cloud (RC) or Nue, it’s a deeper layer of technology being built into the Salesforce platform itself. Think of it as the infrastructure for smarter, more automated tools across everything Salesforce offers — the first step in a broader evolution toward agentic platforms. 

The reality is that agentic GTM is still an emerging category, and most companies (and RevOps teams) are still figuring out what to do with it. There’s no groundswell of demand for agents yet because there’s still a knowledge gap around what’s possible and how it maps to business outcomes.

For RevOps and GTM teams, the real power of agents is that they free teams from the operational drag of siloed systems.

At Nue, agents are part of a bigger picture: enabling more agile, omnichannel revenue operations.

If you’re judging Agentforce by what you see in the market today, you’re missing the point. As it exists now, Agentforce is version one of a much bigger play.

We also shouldn’t expect Agentforce to be the only agentic player in the game. Other agent technologies from OpenAI, Anthropic, and other major AI platforms will have a say in this.

This is where the space will get interesting.

We see agentic technology becoming embedded across the stack, from platforms like Salesforce to dedicated AI-native platforms, and ultimately enabling agents that don’t yet exist today.

At Nue, we support agents. We talk about agents. But we also approach them with pragmatism, not hype.

It’s easy to criticize what feels early, constrained, or imperfect. But that’s how every important technology starts — safe, guided, and carefully rolled out at scale. Over time, the constraints will loosen, the tooling will improve, and new, more powerful agents will emerge.

So my advice?

Don’t judge Agentforce (or agentic GTM) by what you see today.

Judge it by where it’s going.

That’s a conversation we’re excited to keep leading.

See how Nue brings practical, powerful automation to revenue operations — today and tomorrow — by booking a demo.