Selling to IBM

IBM's Consulting segment produced 21.1 billion dollars of revenue in 2025, out of total company revenue of 67.5 billion dollars. That one line explains why selling to IBM is not a single exercise but two.

IBM buys software through a procurement organisation with a portal, a questionnaire and a purchase order. It also runs a global systems integrator that deploys and operates other vendors' software inside other people's companies, and describes that business as the only global consultancy within a major technology company. So selling to IBM and selling with IBM are separate motions, with different entry points, different economics and almost no overlap in the people you must reach. Most vendors work one and never discover the other existed.

Hold a third number alongside those. IBM spent 8.3 billion dollars on research and development in 2025, and its Software segment produced 29,962 million dollars across automation, data, transaction processing and Red Hat. In several categories IBM already ships something that competes with what you sell.

How the buying process actually runs

Indirect purchasing runs through Buy@IBM, powered by SAP Ariba. IBM's source-to-pay platform for indirect goods and services runs on the Ariba Network and covers sourcing events, purchase orders and invoicing. IBM states plainly that joining the Ariba Network is required to continue doing business with IBM. There are no registration fees, and network transaction fees on business between you and IBM are covered by IBM.

A trading relationship request is a mandatory step people miss. The Ariba Network sends one on IBM's behalf, and it must be accepted before purchase orders and invoices can flow, even if your company already holds an Ariba account for other customers. The email lands with whoever is listed, not the person running the account.

Enablement runs by IBM buying country, not by where you sit. IBM rolls Buy@IBM out in waves by the IBM buying country placing the order. A US supplier serving both IBM US and IBM Canada is enabled in the US wave and keeps the old process for IBM Canada until that wave lands, with legacy channels such as Web Order and Invoice retired as each country goes live. If you sell across borders, onboarding is not one event.

The supplier responsibility bar is unusually explicit. Since 2010 IBM has required every first-tier supplier to maintain a social and environmental management system, in place within 12 months of starting business. The published requirements include tracking Scope 1 where applicable and Scope 2 greenhouse gas emissions, publicly disclosing the results of voluntary environmental goals and any regulatory fines incurred in the previous year, and cascading similar requirements to your own suppliers. IBM reserves the right to assess conformance at any point during a purchase order term, and states that failure can ultimately result in discontinued business. Suppliers must also maintain and annually test a business continuity plan covering cyber security.

None of that generates demand. Registration makes you transactable. The purchase still originates with an IBM team that has a problem.

Selling with IBM is a different motion

IBM Partner Plus is the single route for resellers, independent software vendors and systems integrators that build on or sell alongside IBM technology, positioned around incentives, co-marketing funding, quoting tools, hyperscaler marketplace integration and Agent Connect. The house it belongs to is Ecosystem, Strategic Partners and Initiatives, not procurement.

Separately, IBM publishes a named roster of strategic partnerships with dedicated IBM Consulting practices attached: AWS, Adobe, Google Cloud, Microsoft, Oracle, Salesforce, SAP, Samsung and Palo Alto Networks, plus a partnership with OpenAI announced in August 2026. Being on that list is a different business from being a line item in IBM's indirect spend. In one case IBM pays you. In the other, IBM's clients pay you both, and IBM's delivery organisation has a reason to keep you in the account.

Work out which motion you are in first. Does IBM want your product for itself, or for its clients? The answer changes who you meet.

Who owns what, so you know where your deal belongs

You will not be selling to these people. Their remit tells you which part of IBM your deal sits in, and whose priorities it has to survive several levels below.

Names and titles taken from IBM's own senior leadership page, verified 11 September 2026. Senior roles change. Verify at source before using any name.

You cannot sell into this account from the bottom

In 2025 Software produced 29,962 million dollars, Consulting 21,055 million, Infrastructure 15,718 million and Financing 737 million. A deal large enough to justify the cost of selling here runs to seven figures a year, and anything touching the consulting delivery estate is larger still. Nobody signs that from the middle of the organisation. It is approved by someone in or reporting directly into segment leadership, which sets the altitude your entry point has to reach. Most outbound aims where replies are easiest, which is exactly where the authority is not.

There is a second reason to aim high. With 8.3 billion dollars of annual research and development and a portfolio spanning automation, data and security, someone will say IBM could build this, or already has something close. A sponsor senior enough to say the internal team has better things to build keeps the conversation alive.

The layer that matters sits below the public names

The executives above are not who you sell to. The layer that decides is almost entirely unpublished: category managers inside IBM Global Procurement, the offering leaders and practice heads inside IBM Consulting who choose which third-party tools go into a delivery method, the partner development and alliance managers under the ecosystem organisation, and the platform owners in Software and Infrastructure.

IBM makes this harder than most companies its size: the same product can belong to procurement, to an alliance team or to a consulting practice depending on how it gets used, and those three run on different cycles. The buying committee has to be assembled one person at a time, and the first person you find is often in the wrong one of the three.

The board is a published second-degree map

Following the 2026 annual meeting IBM's board consists of 13 directors. Read it as a network, and note which roles are current and which are former.

• Arvind Krishna, Chairman, President and Chief Executive Officer of IBM.
• Alex Gorsky, IBM's Lead Director, and former Chairman and Chief Executive Officer of Johnson & Johnson.
• Thomas Buberl, Chief Executive Officer of AXA S.A.
• Ramon Laguarta, Chairman and Chief Executive Officer of PepsiCo, who joined the IBM board in March 2026.
• Michael Miebach, Chief Executive Officer of Mastercard.
• Marianne C. Brown, former Chief Operating Officer, Global Financial Solutions, at Fidelity National Information Services.
• David N. Farr, retired Chairman and Chief Executive Officer of Emerson Electric.
• Michelle J. Howard, retired Admiral of the United States Navy.
• Andrew N. Liveris, retired Chairman and Chief Executive Officer of The Dow Chemical Company, chairs the Directors and Corporate Governance Committee.
• F. William McNabb III, retired Chairman and Chief Executive Officer of The Vanguard Group.
• Martha E. Pollack, President Emerita of Cornell University.
• Peter R. Voser, retired Chief Executive Officer of Royal Dutch Shell, chairs the Audit Committee.
• Alfred W. Zollar, former Executive Advisor at Siris Capital Group.

Three sitting chief executives sit here: AXA, PepsiCo and Mastercard. If anyone in your network is senior at those, or at FIS, Emerson, Dow, Vanguard, Cornell, Shell or Siris Capital, there is a published two hop path to an IBM director. Almost nobody works this map, because it needs a database rather than a memory.

Other connector routes

The Kyndryl population. IBM spun out its managed infrastructure services business as Kyndryl in November 2021, an independent company that started life with roughly 90,000 professionals. Almost all have former IBM colleagues who stayed, many on the same client estates. No other technology company hands you an alumni pool of that size created in a single day.

Red Hat. Red Hat operates as an IBM company with its own chief executive, Matt Hicks, who sits on IBM's senior leadership list. Its people, open source communities and customer base form a distinct network, and a relationship there is not the same asset as a relationship in Armonk.

The alliance partners themselves. The AWS, SAP, Salesforce, Microsoft, Oracle and Adobe field organisations already work joint accounts with IBM Consulting, and their alliance teams can route you to the IBM practice that has the problem.

Your own customers who buy IBM Consulting. A champion who has watched your product work inside an IBM-led programme is a more credible referrer than anyone on your payroll, and usually has a named IBM engagement lead they can ask.

A company of any scale is not looking at a handful of routes into IBM. It is looking at thousands of relationships, any one of which might be one hop from the person who matters. Finding which paths actually exist is what a relationship intelligence platform is for.

And then you have to get to your own connector

This step kills more introductions than the external ask does. Suppose the best route runs through one of your own directors who also sits on a board with an IBM director. You have to get that person to prioritise it, write something credible, and spend a relationship that took years to build, on you. Ask twice in a quarter and you will not be asked again. The same holds at every level: asking a customer champion to introduce you to their IBM engagement partner is asking them to lend you their credibility. Two reps approaching the same connector about the same account in the same month is common, and invisible at most companies.

Three rules for the introduction itself

Name the motion, not the company. "An introduction to whoever owns third-party tooling decisions in the SAP practice inside IBM Consulting" is actionable. "An introduction to IBM" is not, and at a company that is simultaneously a buyer, a competitor and a channel it is actively unhelpful.

Write the blurb your connector will forward. They will not write your pitch. Give them a paragraph they can send unedited, and let them confirm the other side wants it first. Double opt-in costs a day and protects the relationship. The forwardable blurb is the whole craft.

A warm path starts the clock, it does not skip it. You still accept a trading relationship request, clear the supplier responsibility requirements and wait for your buying country wave. What it buys you is a real conversation, months earlier, with someone who can tell you whether IBM wants your product for itself or for its clients.

See the warm paths into IBM

Everything above describes the problem: a company that is buyer, competitor and channel at the same time. What it does not tell you is which of your own relationships already reaches inside. That is a question about your network, not theirs, and it is the one most teams answer from memory.

Boomerang maps the warm paths your company already has into accounts like IBM, across your team, your customers, your board and investors, and your partners. It then drafts the ask, routes it through the right connector and tracks it to a booked meeting. Book a 15-minute walkthrough and see it run against your own target accounts.