ADVANCED BUSINESS CASE STUDY • AREA: CUSTOMER RELATIONSHIP MANAGEMENT (CRM)
- Course: PGDM – Customer Relationship Management
- Concepts/Theories – CRM through orchestrating Relational Governance and Value Co-Creation in High-Stakes IT Outsourcing
- Teaching Note: This Caselet teaches students on the B2B CRM strategy followed by IBM for large Strategic Outsourcing deals in the area of Consulting, IT & Application Services
Looking through the window of her office at the IBM GTS headquarters located in Armonk, New York, Clara Vance, the Senior Vice President of IBM Global Technology Services (GTS), could not help but feel uneasy. The year was 2025 October, and on her desk were three IT outsourcing contracts of IBM—the biggest and longest-term ones, each amounting to billions of dollars and covering everything from cloud migration to mainframes, cybersecurity, and enterprise AI orchestration. All three contracts amounted to being the most valuable asset of IBM’s B2B relational network.
Through more than a century, the company known as International Business Machines (IBM) had successfully navigated through many systemic changes in the market by constantly adjusting its core value proposition—from hardware computing machines to enterprise software and then on to global IT consulting and outsourcing services. Currently, IBM finds itself in a hybrid cloud generation and generative AI computing environment, where competition from companies like Accenture, Tata Consultancy Services (TCS), Infosys, and even hyperscalers like Amazon Web Services (AWS) and Microsoft Azure was extremely fierce.
The core challenge confronting Vance was not fundamentally technical; it was deeply relational. In complex, longterm B2B IT outsourcing (ITO), a customer relationship is not merely a pipeline of transactions managed via a software platform.
However, IBM’s leadership quickly realized that in high-value IT outsourcing, operational CRM (tracking emails, meetings, and tickets) and analytical CRM (predicting churn based on server utilization data) were insufficient. The strategic core of IBM’s CRM had to be built on Relational Governance and Value Co-Creation. Unlike consumer marketing, where CRM aims to manage thousands of transactional touchpoints efficiently, IBM’s B2B CRM was task-oriented toward managing a small number of deeply interdependent, structurally locked relationships where switching costs were measured in hundreds of millions of dollars and years of organizational disruption.
The Structural Architecture of IT Outsourcing Relationships
IT Outsourcing contracts at IBM typically follow a long-term cycle, lasting anywhere from 7 to 15 years. These arrangements involve the wholesale transfer of a client’s IT infrastructure, data centers, application development, and technical support staff to IBM. Consequently, the relationship goes through distinct lifecycle stages that require differing CRM interventions:
1. Transition and Alignment Phase
This phase represents the first 12 to 18 months of the contract. The CRM priority here is minimizing “buyer’s remorse” and managing change. IBM deploys a Transition Management Office (TMO) that functions as a specialized CRM unit. This unit aligns the divergent corporate cultures of IBM and the client, maps key decision-makers, and establishes baseline communication protocols.
2. Operational Stabilization Phase
Spanning years 2 through 5, this phase shifts the focus to performance against Service Level Agreements (SLAs). Here, analytical CRM tools monitor systems metrics. Trust is built through structural compliance. The account team focuses on delivery excellence, ensuring that server uptime, software patches, and helpdesk resolution times meet or exceed contractual baselines.
3. The Innovation and Renewal Pivot
Occurring around year 5 onwards, this is where many long-term relationships face structural vulnerability. The client begins to take operational stability for granted. The initial cost savings realized by outsourcing become the new baseline, and executive stakeholders ask: “What have you done for me lately?” If IBM’s CRM strategy
remains stuck in operational reporting, the relationship degrades into a commoditized utility arrangement, leaving it open to competitive displacement at the contract’s expiration.
The Core Pillars of IBM’s Retention Strategy
To prevent relational degradation, IBM’s strategic CRM framework rests on three interrelated structural mechanisms: Relational Governance, Joint Value Co-Creation, and High Switching Costs via Technology Imbrication.
Pillar I: Multi-Level Relational Governance
IBM does not manage a client relationship through a single point of contact. Instead, its CRM strategy mandates an architecture of matrixed touchpoints across three organizational tiers:
- Operational Level: Daily interactions between IBM systems engineers and client IT operations teams. The focus is on technical execution and tactical problem-solving.
- Managerial/Tactical Level: Monthly and quarterly reviews between IBM Account Directors and the client’s IT Directors or Chief Information Officer (CIO). The focus here is on resource allocation, capacity planning, and SLA reviews.
- Strategic/Executive Level: Bi-annual or annual steerco meetings involving IBM Senior Vice Presidents (and occasionally the CEO) and the client’s C-suite executives (CEO, CFO, Chief Digital Officer). The focus shifts entirely to long-term business strategy, joint innovation horizons, and macro-economic alignments.
By formalizing this multi-level governance, IBM ensures that a single operational failure at the ground level does not poison the high-level executive relationship, and conversely, that strategic commitments made at the top are effectively operationalized below.
Pillar II: Joint Value Co-Creation and Innovation Centers
A major evolution in IBM’s CRM approach is shifting from a provider-vendor paradigm to a joint value creation paradigm. IBM sets up co-innovation hubs (often leveraging IBM Garage methodologies) inside the client’s relational ecosystem. Through these garages, IBM designers, developers, and product managers work side-by-side with client business units to build custom applications using IBM’s hybrid cloud and AI platforms (such as watsonx).
From a CRM perspective, this serves two strategic purposes: it shifts the conversation from cost reduction to top-line growth for the client, and it integrates IBM’s developers directly into the client’s future business planning, yielding deep relational insights that no competitor can easily replicate.
Pillar III: Asymmetric Switching Costs and Structural Bonding
In B2B CRM theory, customer retention is driven by both absolute satisfaction (affective commitment) and structural dependence (calculative commitment). IBM masterfully constructs structural bonds through technological and procedural integration. When a client outsources to IBM, their internal processes are re-
engineered to map onto IBM’s proprietary service delivery frameworks (aligned with ITIL standards). Furthermore, legacy systems are migrated onto IBM-managed hybrid environments.
The mathematical and financial expression of these switching costs can be evaluated through Customer Lifetime Value (CLV) models tailored for enterprise accounts. Let the net margins from an outsourcing account in year t be denoted by Mt, the formal marketing/relational tracking costs by ct, and the discount factor by r. The baseline
evaluation model for an expected contract tenure of n years is formulated as:
CLV = Σ(t=0 to n) [ (Mt − ct) / (1 + r)t ] − AC
Where AC represents the initial Customer Acquisition Cost. In high-stakes outsourcing, if a client contemplates switching to a competitor, they must calculate the Total Cost of Switching (TCS), which includes contract termination penalties, data migration risks, operational disruption costs, and the cost of retraining personnel. For a client to rationally churn, a competitor’s discount must exceed the value threshold:
ΔV > TCS
IBM’s CRM strategy continually updates and communicates this switching cost calculation implicitly to the client’s CFO by demonstrating how deeply intertwined IBM’s infrastructure has become with the client’s baseline operational continuity.
The Impasse at Global Bank Corp and Telco Unify
Back in her office, Clara Vance focused on the two troubled accounts. The first was Global Bank Corp (GBC), an international financial institution that had outsourced its core infrastructure, retail banking application management, and compliance systems to IBM under a 10-year, $1.8 billion contract signed in 2021. The contract was at its exact midpoint.
Over the past four years, IBM had maintained an exemplary record with GBC. Server uptime was clocked at 99.999%, cybersecurity protocols had successfully thwarted several high-level DDoS attacks, and routine software updates were delivered ahead of schedule. However, GBC’s new Chief Digital Officer, Aris Thorne, brought a different philosophy. Thorne was an advocate for public-cloud-first architectures and open-source systems. He viewed IBM’s proprietary mainframes and structured private cloud configurations as a “legacy trap.”
In a recent steering committee meeting, Thorne remarked, “IBM runs our backend smoothly, but we are paying a premium for utility maintenance. Competitors are offering us hyper-scalable options that could slice our run-rate costs by 30%. We don’t just need a vendor who keeps the lights on; we need an agile CRM partner that helps us deploy consumer-facing generative AI interfaces at rapid speed.” The internal CRM account metrics for GBC showed an alarming trend: while operational satisfaction scores (CSAT) were high among data center managers, the
*Net Promoter Score (NPS)* among the executive C-suite had dropped from +45 to -12 within twelve months.
The second account was Telco Unify (TU), a leading telecommunications provider in the Asia-Pacific region. IBM had managed their billing systems, network optimization analytics, and customer care back-end since 2018 under
an expansive relational agreement. The relationship was approaching its renewal deadline in late 2026. Unlike GBC, Telco Unify had experienced several operational bumps. A major system migration glitch in late 2024 had caused billing delays for millions of subscribers, costing TU nearly $15 million in regulatory fines and customer churn.
IBM’s account director for TU had managed the crisis using classic recovery strategies: invoking liability limits gracefully, deploying a swat team of engineers at zero cost to fix the issue, and providing extensive financial credits on subsequent invoices. Yet, the relationship remained strained. The client’s executive leadership felt vulnerable, realizing how much power IBM held over their vital operations. Competitors were exploiting this anxiety, positioning themselves as alternative, modular vendors under a “multi-sourcing strategy” where no single vendor would have complete control.
Evaluating Strategic Alternatives
Vance called an urgent meeting with her senior CRM strategists, B2B marketing experts, and Account Directors. She presented a comparative performance matrix of the two accounts to frame the discussion (see Table 1).
| Relational Dimension | Global Bank Corp (GBC) | Telco Unify (TU) |
| Contract Value / Duration | $1.8 Billion / 10 Years (Signed 2021) | $2.2 Billion / 8 Years (Signed 2018) |
| Operational Performance (SLAs) | Exemplary (99.999% Uptime, Zero major breaches) | Volatile (Significant billing system glitch in 2024) |
| C-Suite NPS Trend | Declining rapidly (+45 to -12) | Stagnant / Low (+5) |
| Perceived Primary Risk | Perceived lack of innovation; high cost baseline | Relational vulnerability; fear of single-vendor lock-in |
| Competitor Positioning | Hyperscalers offering low-cost, agile public cloud | Boutique & Indian SI providers promoting multi-vendor models |
The account teams offered two wildly different strategic approaches to stabilize and retain these accounts:
Approach A: The Contractual Compliance & Price Aggression Route
The Account Director for Global Bank Corp argued for financial restructuring: “We should optimize our internal costs and offer GBC a proactive 15% reduction in their infrastructure run-rate fees in exchange for adding another three years to the contract duration right now. We wrap this up in strict SLA terms. If they try to move to a public cloud hyperscaler, the data egress fees and transition risks will cost them three times what they save. Let’s rely on our calculative commitment and lock them in contractually.”
Approach B: The Relational Transformation & Joint-Venturing Route
Conversely, the CRM Strategy Director countered: “If we double down on contractual lock-in and price cuts with GBC, Aris Thorne will hate us even more. He will spend the next three years actively building workarounds to bypass IBM. Instead, we must pivot our CRM positioning. We should offer to co-invest $50 million of our own funds to build an ‘AI Innovation Lab’ within the bank, leveraging IBM watsonx to co-create their new consumer banking products. We shift from selling server uptime to co-creating business value. For Telco Unify, we must move away from a defensive stance regarding the 2024 failure. We should design a joint governance council where risk and reward are shared based on their *subscriber retention metrics*, not just IT milestones.”
The Crossroads
Clara Vance adjusted her notes. She knew that both approaches carried immense risks. Approach A offered immediate financial predictability and leveraged IBM’s historic strength in structured contracts, but it risked alienating progressive C-suite executives who felt constrained by legacy systems. Approach B could transform the relationships into visionary partnerships, driving high affective commitment and long-term retention, but it required upfront capital expenditure, deep organizational flexibility, and a willingness to step into ambiguous, non-standardized service territories.
As she prepared her final recommendation for the IBM Executive Committee, Vance had to answer a fundamental question in B2B Customer Relationship Management: How do you balance formal contractual governance with relational flexibility to secure the lifetime value of enterprise clients in an unstable, fast-moving technology ecosystem?
Case-Based Discussion Questions
- Analyzing Relational Governance: Critically evaluate IBM’s multi-level relational governance framework. In the case of Global Bank Corp, why did exemplary operational performance (high SLAs) fail to translate into high C-suite relationship equity (NPS)? Analyze this disconnect using the concepts of operational vs. strategic CRM.
- Deconstructing Switching Costs: Using the customer financial data concepts and equations presented in the case, analyze the role of asymmetric switching costs in customer retention. Is it ethically and strategically sound for a B2B firm like IBM to rely on calculative commitment (structural lock-in) when an account’s affective commitment (relationship satisfaction) is deteriorating?
- Formulating a Relationship Recovery Strategy: Develop a comprehensive relationship recovery and retention strategy for Telco Unify. How should IBM reconcile the client’s fear of single-vendor dependency and structural vulnerability after the disastrous 2024 billing system failure? Recommend specific CRM mechanisms to rebuild trust.
- Strategic Decision Making: If you were Clara Vance, which strategic option (Approach A vs. Approach B) would you implement for Global Bank Corp, and why? Structure your response by balancing immediate profitability metrics against long-term Customer Lifetime Value (CLV).
Teaching & Learning Notes for Students
Case Relevance & Target Audience: This business case is designed for MBA students pursuing specialized courses in Customer Relationship Management (CRM), B2B Marketing, Services Marketing, and Strategic Account Management.
Key Pedagogical Objectives:
To distinguish between consumer CRM (transactional, high-volume) and complex B2B CRM (relational, high-interdependence).
- To understand the interplay between formal contractual mechanisms and informal relational norms in long-term governance.
- To master the concepts of Affective Commitment (staying because you want to) and Calculative Commitment (staying because you have to due to switching costs).
- To evaluate service recovery frameworks in high-value enterprise settings following catastrophic operational failures.
Theoretical Frameworks to Apply:
Students are encouraged to apply the Sourcing Governance Theory, which balances formal contracts with relational trust. Additionally, use the Service-Dominant (S-D) Logic framework pioneered by Vargo and Lusch to analyze how IBM can transition from a value-in-exchange model (charging for hardware/ maintenance uptime) to a value-in-use or value-co-creation model (collaborating via the IBM Garage framework to unlock new revenue streams for the client).
Finally, students should utilize the Relationship Lifecycle Model to map how client expectations drift over a decade-long engagement, identifying specific points where account managers must actively reinvent their relational value proposition to prevent relationship obsolescence.
Reference Sources
IBM Corporate and Thought Leadership Sources
- IBM Customer Experience (CX) Overview
- Discusses customer experience, customer lifetime value, customer loyalty, and retention as strategic business objectives. (IBM)
- IBM Customer Retention Framework
- Provides IBM’s perspective on customer retention, relationship management, customer engagement, and value-based selling. (IBM)
- IBM Customer Experience Management (CXM)
- Explains how customer data, analytics, and CRM systems contribute to long-term customer relationships. (IBM)
- IBM Institute for Business Value – Experience Matters
- Highlights the strategic role of customer experience and relationship-building in competitive advantage. (IBM)
- IBM Customer Engagement Strategy
- Useful for understanding lifecycle engagement and relationship management principles. (IBM)
IBM Annual Reports and Corporate Reports
- IBM Annual Reports Archive
- Contains information on IBM’s consulting business, client relationships, hybrid cloud strategy, and long-term customer engagements.
- IBM Investor Relations
- Useful for understanding IBM’s business model evolution from hardware to consulting, outsourcing, and cloud services.
Academic References on CRM
- Francis Buttle & Stan Maklan (2019).
Customer Relationship Management: Concepts and Technologies.
Routledge.- One of the most widely used MBA-level CRM textbooks.
- Adrian Payne & Pennie Frow (2017).
Strategic Customer Management: Integrating Relationship Marketing and CRM.
Cambridge University Press. - Philip Kotler, Kevin Lane Keller, Chernev, A. (Latest Edition).
Marketing Management.
Pearson.
- Chapters on relationship marketing, customer lifetime value, and strategic CRM.
Key Account Management and B2B Relationship Literature
- Malcolm McDonald & Rogers, B.
Key Account Management: The Definitive Guide.
Wiley. - Robert Palmatier.
Relationship Marketing.
Marketing Science Institute. - Relationship Marketing literature by Christian Grönroos and Evert Gummesson.








