For Sabre's SabreSonic reservation system, should we invest in expanding third-party integrations or enhancing core functionality for airlines?

Introduction

For Sabre's SabreSonic reservation system, we're facing a critical trade-off between expanding third-party integrations and enhancing core functionality for airlines. This decision will significantly impact our product strategy, user experience, and market position. I'll analyze this trade-off by examining the product context, stakeholder impacts, potential outcomes, and key metrics, ultimately providing a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on the current market dynamics, I'm thinking our competitive positioning might be influencing this decision. Could you share how our market share has been trending compared to our main competitors in the past year?

Why it matters: Helps determine if we need to focus on differentiation or catching up to competitors. Expected answer: Stable market share with increasing pressure from newer entrants. Impact on approach: Would influence whether we prioritize unique integrations or core feature parity.

• Considering our revenue model, I'm assuming airlines pay for core functionality and potentially for each integration. Is this correct, and can you provide a rough breakdown of revenue between core and integration services?

Why it matters: Helps understand the financial implications of each option. Expected answer: 70% from core, 30% from integrations. Impact on approach: Would influence the potential ROI of each option.

• Looking at user behavior, I'm curious about the adoption rate of our current third-party integrations. What percentage of our airline clients actively use at least one third-party integration?

Why it matters: Indicates demand for integrations and potential growth in this area. Expected answer: 60% of airlines use at least one integration. Impact on approach: High usage would support expanding integrations, low usage might prioritize core functionality.

• From a technical perspective, I'm wondering about the current state of our API infrastructure. How scalable is our current system for handling additional integrations?

Why it matters: Determines the feasibility and potential costs of expanding integrations. Expected answer: Moderately scalable, but would require some infrastructure upgrades. Impact on approach: Would influence the timeline and resource allocation for the integration option.

• Regarding our development resources, I'm assuming we have separate teams for core functionality and integrations. What's the current split in terms of headcount between these teams?

Why it matters: Helps understand our capacity to execute on either option. Expected answer: 70% core, 30% integrations. Impact on approach: Would influence the feasibility and timeline of each option based on current team structure.