Richter: Information Technology at Hungary's Largest Pharma Custom Case Solution & Analysis

1. Evidence Brief (Case Researcher)

Financial Metrics

Richter reported 2005 net sales of 150.3 billion HUF (Exhibit 1).
Operating profit margin for 2005 stood at 22.1% (Exhibit 1).
IT budget as a percentage of revenue: 2.2% (approx. 3.3 billion HUF), significantly below the industry average of 4-5% (Paragraph 14).

Operational Facts

Geographic footprint: Operations in Hungary, Poland, Romania, and Russia (Paragraph 4).
IT Infrastructure: Fragmented legacy systems; lack of integrated ERP across international subsidiaries (Paragraph 22).
Personnel: IT department operates as a cost center with limited influence on business strategy (Paragraph 18).

Stakeholder Positions

CEO Erik Bogsch: Prioritizes cost control and market expansion; views IT as a necessary utility rather than a strategic driver (Paragraph 12).
CIO Zsolt Szalay: Advocates for centralized infrastructure and ERP standardization to support international growth (Paragraph 25).

Information Gaps

Quantified ROI of proposed ERP consolidation is missing.
Specific cost of IT system failures or downtime is not provided.

2. Strategic Analysis (Strategic Analyst)

Core Strategic Question

Should Richter transition from a decentralized, fragmented IT cost-center model to a centralized, standardized digital infrastructure to support its international growth strategy?

Structural Analysis

Value Chain: The current IT fragmentation creates silos that impede inventory visibility and clinical trial data management across borders.
Ansoff Matrix: Richter is pursuing market development (expansion into CIS and EU). The current IT posture acts as a ceiling on the speed of this expansion.

Strategic Options

Option 1: Centralized ERP Transformation. Standardize all subsidiaries on a single SAP platform. Trade-off: High upfront capital expenditure and organizational friction, but creates a scalable data backbone.
Option 2: Incremental Optimization. Upgrade local systems while maintaining autonomy. Trade-off: Low disruption, but maintains long-term data fragmentation and higher maintenance costs.
Option 3: Outsource Non-Core IT. Move infrastructure to a managed service provider. Trade-off: Reduces headcount, but fails to address the lack of business-IT alignment.

Preliminary Recommendation

Proceed with Option 1. Richter's international expansion requires a unified operational view that legacy systems cannot provide.

3. Implementation Roadmap (Implementation Specialist)

Critical Path

Audit and Stabilization (Month 1-3): Map all current data flows; identify critical failure points in regional operations.
Governance Setup (Month 4-6): Shift IT from a cost center to a business-partner model; appoint IT liaisons for each regional subsidiary.
Core Pilot (Month 7-15): Implement centralized ERP in the Hungarian headquarters before rolling out to Poland and Romania.

Key Constraints

Cultural Resistance: Regional managers view autonomy as a prerequisite for success; loss of local control will be resisted.
Budget Ceiling: Convincing the CEO to double the IT spend (from 2.2% to 4%) requires demonstrating direct impact on margin expansion.

Risk-Adjusted Implementation

Adopt a phased rollout rather than a big bang. If the Hungarian pilot fails to deliver efficiency gains within 12 months, suspend international deployment.

4. Executive Review and BLUF (Executive Critic)

BLUF

Richter is underinvesting in digital infrastructure, creating a structural bottleneck for its international expansion. The current 2.2% IT spend is insufficient to support a modern pharmaceutical enterprise. The company must transition to a centralized ERP system to capture cross-border efficiencies. The primary risk is not technical; it is the CEO’s perception of IT as a utility. Implementation must focus on demonstrating revenue-linked efficiency gains in the Hungarian pilot before attempting a multi-country rollout. Approve for execution, provided the budget increase is tied to specific, measurable inventory and supply-chain reductions.

Dangerous Assumption

The analysis assumes the regional subsidiaries are willing to trade operational autonomy for corporate standardization. Without executive mandate, this will trigger internal political paralysis.

Unaddressed Risks

Data Sovereignty: Emerging regulations in Russia and Eastern Europe regarding data residency may complicate a centralized cloud or ERP strategy (Probability: High; Consequence: Legal/Operational).
Talent Gap: The current IT department lacks the architectural expertise to manage a large-scale ERP integration (Probability: Medium; Consequence: Project failure).

Unconsidered Alternative

A hybrid model: Standardize core financial and reporting data (the "Global Core") while allowing subsidiaries to maintain localized front-end commercial systems.

Verdict: APPROVED FOR LEADERSHIP REVIEW