Infosys' Relationship Scorecard: Measuring Transformational Partnerships Custom Case Solution & Analysis

1. Evidence Brief (Case Researcher)

Financial Metrics

Infosys revenue growth: Transitioning from traditional IT services to high-value transformational consulting.
Client revenue concentration: High reliance on top 25 clients; shift required toward long-term partnership models (Source: Exhibit 1).
Pricing model shift: Moving from T&M (Time and Materials) to outcome-based pricing (Paragraph 4).

Operational Facts

Infosys Business Consulting (IBC) mandate: Move from staff augmentation to strategic advisor status.
Relationship Scorecard (RSC) implementation: A multi-dimensional metric tool designed to quantify intangible partnership health (Paragraph 12).
Internal alignment: Friction between legacy delivery teams and new consulting units regarding account management (Paragraph 15).

Stakeholder Positions

CEO/Leadership: Seeking to institutionalize "client intimacy" as a scalable asset.
Delivery Managers: Skeptical of qualitative metrics; prefer binary delivery KPIs (uptime, bug rates).
Client Procurement: Focused on cost-reduction; resistant to "value-based" pricing models (Exhibit 3).

Information Gaps

Specific weighting of the RSC components (e.g., how much weight is given to trust vs. delivery quality).
Longitudinal data on RSC score correlation to account churn rates.

2. Strategic Analysis (Strategic Analyst)

Core Strategic Question

Can Infosys operationalize trust and intimacy through a quantitative scorecard without alienating legacy delivery teams or commoditizing the client relationship?

Structural Analysis

Value Chain Analysis: The shift from IT execution to strategic consulting requires moving the point of engagement from the CIO office to the C-suite. The RSC is a tool to bridge this gap.
Principal-Agent Problem: Delivery managers are incentivized on immediate project margins; the firm needs them to invest in long-term account health.

Strategic Options

Option 1: The Balanced Scorecard Integration. Embed the RSC directly into the compensation structure for account managers.
- Trade-offs: High internal resistance; risk of gaming the metrics.
Option 2: The Advisory-Led Model. Use the RSC strictly for internal account planning, not as a client-facing negotiation tool.
- Trade-offs: Lower risk of client pushback; limited impact on changing account behavior.
Option 3: The Co-Creation Pilot. Invite top-tier clients to co-develop the scorecard, making it a joint governance tool.
- Trade-offs: Highest potential for true partnership; high resource intensity.

Preliminary Recommendation

Adopt Option 3. By making the RSC a collaborative governance mechanism, Infosys shifts the client conversation from price-per-hour to mutually agreed-upon business outcomes.

3. Implementation Roadmap (Implementation Specialist)

Critical Path

Phase 1 (Days 1-30): Standardize the RSC taxonomy across the top 20 accounts.
Phase 2 (Days 31-60): Pilot joint-governance sessions with three high-trust clients.
Phase 3 (Days 61-90): Refine the RSC based on client feedback and align internal incentive structures.

Key Constraints

Cultural Inertia: Engineers are trained to optimize for code, not relationships.
Client Procurement: Procurement teams often lack the mandate to value soft benefits like trust or strategic alignment.

Risk-Adjusted Implementation

Build in a 20% buffer for account manager training.
If client engagement is low, pivot to internal-only use (Option 2) to avoid negative perceptions of "metrics theater."

4. Executive Review and BLUF (Executive Critic)

BLUF

Infosys must transition the Relationship Scorecard from a reporting tool to a governance mechanism. The current danger is treating the scorecard as a substitute for client intimacy rather than a diagnostic of it. By co-developing the scorecard with clients, Infosys forces both parties to define what success looks like beyond cost-per-hour. This converts the relationship from a vendor-client transaction into a strategic partnership. If the client refuses to participate in defining the scorecard, Infosys has identified a transactional account that should not receive high-cost consulting investment. The scorecard is a filter for account potential, not just a measurement of account health.

Dangerous Assumption

That clients actually want a strategic partnership. Many large enterprise clients prefer a commoditized, low-cost vendor model. The scorecard must be used to fire clients who refuse to move up the value chain.

Unaddressed Risks

The Gaming Risk: If account managers are compensated on RSC scores, they will manipulate the input data. Independent audit of the scorecard is mandatory.
The Delivery Gap: High RSC scores will not survive a major system outage. Operational stability remains the foundation of all consulting claims.

Unconsidered Alternative

Tiered Account Management: Explicitly abandon the attempt to build transformational partnerships with all clients. Use the RSC to segment the portfolio: "Partners" (High RSC focus) vs. "Utilities" (Cost/Efficiency focus).