What is our primary use case?
My main use case for IBM watsonx Orchestrate is to build AI agents so that we could show conversational data from a lot of different applications.
There was a specific use case in which I connected the agent to a Salesforce CRM with the native connectors, and I used the agent so that the users could see opportunities, commercial visits, and also information from different clients.
I decided to connect with Salesforce specifically because it was a native connector and I had a test environment of a Salesforce CRM. This integration impacted my workflow by being very useful in cases where the commercial agents are on the street going to see a different client, and for example, they want to see information faster without going to the application on the desktop to search. It is much faster to ask an agent, and that was basically the main impact—how fast they could get the information, and it provided a very comfortable and satisfying user experience.
In general, I use agents with tools so that we can see data stored in different applications.
What is most valuable?
I think the best features IBM watsonx Orchestrate offers in my experience are the collaborator agents, where the possibility of having an orchestrator agent associated with collaborator agents is something very powerful. I liked the OpenAPI connector a lot because it provides developers a whole new world of possibilities to interact with different systems that are not native connectors in IBM watsonx Orchestrate. Developing those OpenAPI tools with Python is great.
I used agents to connect with different data sources, allowing us to have the commercial data of an enterprise in different scenarios. For example, in Salesforce or another system, we can have a collaborator agent that reviews all that data, with one agent reading from Salesforce and another reading directly from a private database with an OpenAPI tool.
IBM watsonx Orchestrate has positively impacted my organization by providing a new optimized environment in which I could create much more powerful and complex agents, helping us create different opportunities and show demos at various events, allowing clients to see what we can do with the platform.
What needs improvement?
I think IBM watsonx Orchestrate could be improved by addressing issues related to variables, as some agents can have certain variables which may not get the transparency needed for developers to know if they are working effectively when sent to a collaborator agent. This would be a good area for improvement.
For how long have I used the solution?
I have been using IBM watsonx Orchestrate for about two months.
Buyer's Guide
IBM watsonx Orchestrate
October 2026
Learn what your peers think about IBM watsonx Orchestrate. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
920,223 professionals have used our research since 2012.
What do I think about the stability of the solution?
IBM watsonx Orchestrate is stable.
What do I think about the scalability of the solution?
IBM watsonx Orchestrate's scalability is great.
Which solution did I use previously and why did I switch?
In general, for building agents, I have previously used Azure services.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for IBM watsonx Orchestrate reveals that it is expensive. I haven't had the chance to share it with clients, but the monthly licensing fees are quite high.
Which other solutions did I evaluate?
Before choosing IBM watsonx Orchestrate, I evaluated other options including Copilot Studio, N8N, and Azure Agents. Those would be the main ones I looked at.
What other advice do I have?
I haven't talked with many business users about leveraging the no-code tools within IBM watsonx Orchestrate, but the tools require establishing connections, something that business users may not be familiar with, so they often need to call us, the developers, for assistance.
I used the Agent Development Kit (ADK) for addressing the variables in agents, which required development with the ADK, and it was very intuitive. I especially enjoyed using it when placing agents in different channels beyond default options because it allows me to directly associate tools or knowledge bases with agents in a declarative way.
I would advise others looking into IBM watsonx Orchestrate to consider it technically, as I think it is the best platform for creating agents, especially with the potential for connecting with other platforms through Watsonx Governance for security and governance, although licensing is quite a challenge. I would rate this review an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner