IBM Champions

Hi Jean-Marie,

your instinct is right, and the good news is you can prove it with Microsoft's own documentation, which is the cleanest competitive weapon there is.

First, the category error. Microsoft's own overview defines Azure Service Bus as "a fully managed enterprise message broker with message queues and publish-subscribe topics":
https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview
A message broker, in Microsoft's own words. And Microsoft's own integration architecture guidance presents the actual integration platform as API Management, Logic Apps, Service Bus and Event Grid working together:
https://learn.microsoft.com/en-us/azure/architecture/integration/integration-get-started
So whoever positioned Service Bus alone as the alternative has already conceded your point: the honest comparison is IBM webMethods Hybrid Integration versus the whole Azure Integration Services assembly, and for your client's requirements you would typically also need to add the Logic Apps enterprise integration capabilities for EDI, plus a do-it-yourself construction for managed file transfer. That is four to six separately priced, separately monitored, separately skilled services versus one platform.

Second, map it to what your client actually needs. BC, Akeneo, a WMS, a webshop, HubSpot, plus worldwide file exchange with suppliers and customers, plus order-to-ship flows to automate: that is application integration, B2B/EDI, managed file transfer, APIs and monitoring together. IBM webMethods Hybrid Integration covers exactly that scope natively, applications, APIs, events, messaging, B2B/EDI and file transfers under one unified control plane, which is how IBM describes the platform itself:
https://www.ibm.com/products/webmethods-hybrid-integration
For a small IT team, one control plane and one skillset versus five services with five operating models is not a nuance, it is the decision. Their past bottleneck with external consultants makes this argument for you.

Third, the analyst proof points, both official and current. IBM was named one of just three Leaders in The Forrester Wave for iPaaS Q3 2025, with the top score in the Current Offering category:
https://www.ibm.com/forms/mkt-53930
And on the API side, IBM was named a Leader in the 2025 Gartner Magic Quadrant for API Management for the tenth consecutive time (API Connect being the API management capability within webMethods Hybrid Integration):
https://www.ibm.com/new/announcements/ibm-named-a-leader-in-the-2025-gartner-magic-quadrant-for-api-management

Fourth, two tactical suggestions from my experience in these bake-offs. Force the like-for-like TCO: ask the client to have the other party price and staff the FULL equivalent scope, EDI partner onboarding, file transfer, API management, monitoring, environment separation, not the Service Bus list price. Consumption pricing across half a dozen metered services is also much harder to forecast than a platform subscription, which finance people notice. And neutralize the ecosystem card early: their stack is mostly non-Microsoft anyway (Akeneo, HubSpot, the WMS, the webshop), BC exposes standard APIs that any integration platform consumes, and putting the data backbone of the company inside one hyperscaler's toolbox is a lock-in decision worth naming out loud.

Fifth, the strongest competitive information is a working flow. If you can get them to agree to a small PoC, one real order-to-ship flow with one supplier including a file exchange, built with their team watching, the time-to-value argument closes itself. And for the official battle cards, the webMethods sales kits and competitive assets are on Seismic via Partner Plus, worth grabbing before the next meeting.

One last honest note that will also help your credibility in front of the client: Service Bus is a perfectly fine broker for event-driven workloads built inside Azure. That is simply not the problem your client described. Keeping that distinction clean makes your whole argument stronger.

Good luck with the deal, and let us know here how it lands, this is a matchup many of us keep meeting.

Regards

Roberto

Thanks Roberto. Exactly what I was looking for. I'll keep you posted!!!

Glad it helped, Jean-Marie. And yes, please keep the community posted on how the client conversation lands: this matchup keeps coming up (I run into the same argument regularly in Italian bake-offs, so any lessons from your side would be genuinely useful for the rest of us). If more angles come up once you get into the PoC or the TCO comparison, feel free to ping me directly. Good luck with this one!

Cheers,
Roberto

After the meeting with the BP that positioned Azure Service Bus, I am even more convinced about the fact that IBM Webmethods is the right choice for the customer. They had to admit that Service Bus is not the right choice for our needs and is missing quite some functionality. After calculating a draft TCO it is clear that also on the long term, when including the missing pieces on the MS platform it will be more expensive and much more difficult to maintain then Webmethods. I have requested a quote via TDSynnex for a 3 year contract. Hopefully the license price will be in the range of expectations of the customer.

I will keep you posted and thanks again Roberto!!!

Great update, Jean-Marie, and honestly the best possible outcome of that meeting: when the other side has to concede the functional gap themselves, the TCO conversation is already half won. Nice work making them price the full scope, that is exactly where these comparisons get honest.

On the quote side, two things from my experience with IBM software through distribution, for whatever they are worth. First, if the number comes back above the customer's range, do not take it as final: ask TD Synnex about deal registration and special bid options for a competitive situation like this one, a documented bake-off against Azure is exactly the scenario those mechanisms exist for. Second, double check that the sizing assumptions in the quote match wave one of your SSA OneData program rather than the full two-year vision. Oversizing day one is the classic way a technically won deal misses the budget, and growing the platform later is always easier than shrinking a quote now.

Fingers crossed for the numbers, and please do close the loop here when it lands. A thread that starts with a competitive question and ends with a signed deal is the kind of case study this community loves.

Cheers,
Roberto

Thanks Roberto, and indeed I know the game with the distri and IBM, especially in a competitive situation like this. So, I applied already to get the "best" possible price :-) In the meantime I received the quote, so I can have the discussion with the customer. I have also created a full documented decision document (with chatGPT) to have the discussion and make it very visible for the customer.

I had an article published about this very issue in the press and for me this issue and the issue of AI induced burnout are the two biggest challenges that are actually affecting us all; I know that we have all heard of the Forbes $3 trillion COBOL skills crisis but I feel we have much bigger problems and that they are waiting to hit!

My only hope is that we do not see a domino effect where once vendor is happy to report issues - that we see many others all sharing the same experience and some of this I feel is that we do not always share about issues that affect us until it is too late.

Maybe those who work for ISV's can ask about these challenges in passing and we can start to help each as a community.