| Metric (In Millions USD) | 1999 | 2000 | 2001 | Source |
|---|---|---|---|---|
| Total Revenue | 47.3 | 85.0 | 221.3 | Exhibit 1 |
| Gross Profit | 20.8 | 37.5 | 97.5 | Exhibit 1 |
| Net Income | 6.4 | 10.2 | -4.7 | Exhibit 1 |
| Research and Development | 8.9 | 13.8 | 34.6 | Exhibit 1 |
The wireless data industry is defined by high barriers to entry due to the technical complexity of secure, end-to-end encryption. RIM controls the three critical components: the handheld device, the server software, and the network operations center. This integration creates a significant moat against hardware-only competitors like Palm or Motorola.
Buyer power is bifurcated. Individual corporate users have low power, but the carriers who control the network access have high bargaining power. Currently, RIM is dependent on aging Mobitex networks, making the transition to GSM/GPRS a survival requirement rather than a choice.
Option 1: Direct Enterprise Dominance. Focus exclusively on the Fortune 500 by expanding the direct sales force. This preserves the high-touch relationship with IT managers and maintains premium pricing.
Trade-offs: High customer acquisition costs and slow geographic expansion.
Resource Requirements: Significant investment in global sales offices and support staff.
Option 2: Carrier-Led Mass Market Expansion. Pivot to a wholesale model where carriers bundle BlackBerry devices with data plans. This utilizes carrier marketing budgets and retail footprints.
Trade-offs: Loss of brand control and reduced margins due to carrier subsidies.
Resource Requirements: Engineering resources to certify devices on multiple global carrier networks.
Option 3: Software Licensing. License the BlackBerry Enterprise Server and OS to other hardware manufacturers like Nokia or Sony.
Trade-offs: Risks commoditizing the RIM hardware business and complicates security protocols.
Resource Requirements: Transformation into a pure software and services organization.
Pursue Option 2. The window to establish the BlackBerry Enterprise Server as the corporate standard is closing. Competitors like Microsoft are developing mobile versions of Exchange. RIM must use carrier distribution to achieve a dominant installed base before the enterprise software market consolidates. Speed of adoption outweighs the risk of margin dilution from carrier partnerships.
The primary execution risk is the reliance on third-party network upgrades. To mitigate this, RIM will maintain the Mobitex product line as a fallback for the next 24 months. Implementation will follow a tiered rollout: start with financial services firms in New York and London who have the highest urgency for mobile data, then expand to broader enterprise segments as network reliability improves. Contingency funds are allocated to increase the technical support staff by 30 percent to handle expected integration issues during the GSM transition.
Research In Motion must prioritize carrier-led distribution to secure the enterprise market standard. The current transition from Mobitex to GSM networks is the most critical juncture in the history of the company. While direct sales to IT departments built the initial niche, only carrier partnerships provide the scale necessary to block Microsoft and Nokia. The recommendation is to approve the aggressive shift to a carrier-centric model, focusing on the 5810 launch as the primary vehicle for global expansion. Success requires the BlackBerry Enterprise Server to become the default corporate mobile middleware before competitors can replicate the push architecture.
The analysis assumes that corporate IT managers will remain the sole decision makers for mobile hardware. If employees begin to demand devices based on personal preference or consumer features—a trend toward consumerization—the current focus on security and server integration will not be enough to maintain market share.
The team did not fully explore a dual-brand strategy. RIM could have maintained a premium, direct-to-enterprise BlackBerry brand while creating a white-label version of its secure messaging software for other manufacturers. This would have protected the high-end hardware business while capturing the broader market through licensing royalties.
APPROVED FOR LEADERSHIP REVIEW
Building Trust at Scale: Airbnb's Fight Against Adverse Selection custom case study solution
Palantir: Aligning Decisions with Values custom case study solution
Francisco Partners Private Credit Opportunity Fund custom case study solution
CH2M Hill: A Private Firm in a Public World custom case study solution
Jamie's Market: Challenges Hiring and Onboarding Temporary Workers custom case study solution
QuMei's Takeover Bid for Ekornes (A): Decision-Making Process custom case study solution
CityScore: Big Data Comes to Boston custom case study solution
The Beer Cases (A): A-B InBev custom case study solution
Tropos Networks custom case study solution
Doyle's Dealmaking Dilemma (A): Negotiating the Job Search custom case study solution
The Physics of Patient Flows and Wait Lists in Health Care Pathways custom case study solution