For Broadridge's LTX bond trading platform, should we prioritize expanding the number of supported fixed income asset classes or improving liquidity in existing ones?

Introduction

The trade-off we're examining for Broadridge's LTX bond trading platform is whether to prioritize expanding the number of supported fixed income asset classes or improving liquidity in existing ones. This decision is crucial for LTX's growth strategy and market position in the electronic bond trading space. I'll analyze this trade-off by considering market dynamics, user needs, technical feasibility, and business impact.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about the current market share of LTX. Could you provide insights into our current position in the electronic bond trading market compared to competitors?

Why it matters: Helps gauge the urgency of expansion vs. consolidation Expected answer: Mid-tier player with room for growth Impact: Higher market share might favor liquidity improvement, while lower share could push for expansion

• Business Context: Based on our revenue model, I assume transaction fees are a primary income source. How does this split between different asset classes?

Why it matters: Identifies which strategy aligns best with revenue goals Expected answer: Majority from corporate bonds, with growing interest in other classes Impact: Even split might favor expansion, while heavy concentration could prioritize liquidity

• User Impact: Considering our user base, are we seeing more demand for new asset classes or improved liquidity in existing ones?

Why it matters: Aligns product strategy with user needs Expected answer: Mixed feedback, with some users requesting new classes and others emphasizing liquidity Impact: Clear user preference would strongly influence the decision

• Technical Feasibility: Given our current platform architecture, how complex would it be to add new asset classes compared to enhancing liquidity features?

Why it matters: Assesses resource requirements and potential timeline Expected answer: Adding classes is more complex but feasible; liquidity improvements are iterative Impact: Significant technical challenges might favor the less complex option

• Resource Allocation: How flexible is our development team capacity for taking on either of these initiatives?

Why it matters: Determines if we can pursue both strategies simultaneously or need to choose Expected answer: Limited capacity, requiring prioritization Impact: Abundant resources might allow pursuing both, while constraints force a choice