For Altium's NEXUS platform, should we emphasize expanding integration capabilities with third-party tools or concentrate on enhancing native features within the Altium ecosystem?

Introduction

The trade-off we're examining for Altium's NEXUS platform is whether to focus on expanding integration capabilities with third-party tools or enhancing native features within the Altium ecosystem. This decision is crucial for Altium's product strategy and market positioning. I'll analyze this trade-off by considering user needs, technical feasibility, business impact, and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking our users might be increasingly relying on specialized third-party tools. Could you share any data on the most requested third-party integrations from our user base?

Why it matters: Helps prioritize integration efforts and understand user workflows Expected answer: A list of top 3-5 requested integrations Impact on approach: Would focus integration efforts on high-demand tools

• Considering our revenue model, I'm assuming NEXUS is a subscription-based platform. How does our pricing structure currently account for third-party integrations versus native features?

Why it matters: Informs potential revenue impacts of each strategy Expected answer: Premium tier includes some integrations, native features available at all levels Impact on approach: Might suggest tiered integration offerings or bundled packages

• Looking at user segments, I'm thinking different types of users might have varying preferences for native vs. integrated tools. Can you provide a breakdown of our user base by company size or industry vertical?

Why it matters: Allows for targeted feature development and integration strategies Expected answer: Mix of enterprise, mid-size, and small businesses across multiple industries Impact on approach: Could lead to segmented approach, prioritizing different strategies for different user groups

• From a technical perspective, I'm curious about our current API capabilities. How robust is our existing API for supporting expanded third-party integrations?

Why it matters: Determines feasibility and resource requirements for integration expansion Expected answer: API exists but may need enhancements for broader integration support Impact on approach: Might require allocating resources to API development before pursuing integrations

• Considering our development resources, I'm wondering about our team's expertise. Do we have more in-house expertise in developing native features or in creating and maintaining integrations?

Why it matters: Influences resource allocation and potential hiring needs Expected answer: Stronger native feature development team, less integration experience Impact on approach: Might suggest focusing on native features or investing in integration training/hiring